Code organization, class division and design

This might be an iffy topic, but I really feel the code needs a tune up. It’s quite hard to read off the bat, and the classes like game need to be split up (it’s 8000 lines long damnit) into coherent classes like MainMenu or ActionProcessor and ideally reduce coupling.

And I think anyone interested should check out http://astyle.sourceforge.net/ and/or http://geosoft.no/development/cppstyle.html

I want to see the source increase in readability, increase in maintanability and if that means the game runs a hertz or two slower, then so be it.

I don’t want to bash the code anyone has done, let’s just treat this as a meta-bug and start by agreeing a 8000 line class is a problem :slight_smile:

PS: Folders. Here are some that would be welcomed: Item, Monster, Mission, NPC, Vehicle, Engine (or GUI, Screen, whatever)

Feel free to do these things and request your branch be pulled. People have made some progress on this front, but extra hands overhauling code and writing it in a better and more modular form would certainly be appreciated.

Ok, good to know you guys are open minded on these types of changes, ill start doing some basic stuff sometime tonight.