Re-organize source code into sub modules?

[andytorrestb]

Currently the source code is broken into four modules: src/game_entities, src/gui, src/services, and src/scenes.

1. Is it worth dividing each module into sub-modules. For example, src/game_entities/ contains 30 files! This could be organized into sub-modules such as characters, items, behaviors, etc. The items module would likely also have sub-modules (wearable, env, etc).
2. On a similar note, is it worth considering the MVC architecture to re-organize these modules?

[Grimmys]

That's a good point that you are bringing, 30 files in a single folder is definitely too much.
Dividing src/game_entities into maybe entities, items and maybe something like misc for skill, alteration and effect (or would it be gameplay? I don't know) sounds nice.

Scenes shouldn't be divided for now I believe.

Services... I don't know how the split could be.

But I don't think MVC would be nice however, it's an architecture that is more proper to web applications in my opinion, for games I think the current architecture with Scenes and Services is good.
Like what could be in the controller layer? Scenes?