To make sure I understand correctly, only the AI computations have been moved to the controller's computer, right? It doesn't affect the performance of other players? And I would also assume that the AI computations are no worse than running a single player game with the same AI?
If that's the case, I would say remove the old functionality entirely. No need to clutter the source code with near-obsolete functionality. Surely the expectation that one player has the resources akin to playing a single player game is not at all unreasonable?
Git: How can I check this ( big ) change in, in a proper way? I think I want a branch for this to try it with others.
I notice that most of MG's development seems to go into the main branch right now. Have you considered adopting a more pro-branching strategy? Branching works really well in git. Unlike SVN, a branch merely needs to store the difference from the previous revisions (SVN would usually make a whole freaking copy). Git also focuses on a "working directory" model. You work on a current branch. Thus, it's very easy to do some work in a feature branch, then switch to a bug fix branch for something that needs your attention more before switching back to what you were doing -- all without breaking your current work or creating new copies of everything.
I found
this to be an interesting read, back when I was learning git.
Regarding distribution, everyone will just have to checkout your branch as normal (
git clone -b <branch> https://github.com/MegaGlest/megaglest-source.git). It'd probably be best to distribute executables, however, if you want people to test.
If the tester already has the repo cloned, they can just run
git pull; git checkout <branch>. That will switch their current working directory (so they'll need to do
git checkout master when they're done).
