[Gamer_Z]

Quote:

Originally Posted by Yashas It does not matter if you are doing it right or wrong; do it how you like.

Except when at one point you decide to go on a joint venture with other scripters / make a team, adhering to well established principles and standards is a must to be able to quickly and efficiently progress forward. Else you'll be stuck with an unmaintainable mess. Good luck with that, especially with a "it does not matter" mindset. If you are sure that this will be a solo venture then yes, this might apply, but even then it's good to train yourself for team efforts.

As for the topic starter: Divide your source files according to functionality (components). This is exactly what you do when you bundle includes into your mode - each include you use has a different type of functionality. e.g. a_vehicles is for managing vehicles, a_players for managing players, you could make your own houses include which will contain all callbacks required for it to work, all commands, all dialogs, etc. Then you could make a vehicle ownership include where you do the same (again all commands/dialogs/other callbacks). And so on. Just to name some examples.

With this approach you try to make each component as independent as possible of each other (so you could basically drag and drop the files into another mode). Ofcourse this is not always 100% possible (well then your 'components' just gets bigger) but try to keep that in mind.

If some components have sub components then divide accordingly.