Quote:
Originally Posted by mgellan
1. Start with the current rev of eqemu and keep any changes required to "classic-ify" the code parameter driven and checked into the main code base so we're not creating a fork that will never get merged back into the main project.
|
I am not source control expert but I do not think this is viable. My source has gotten further and further custom. You have to think the current EqEmu source has code for instancing, AA's (cannot completely remove), bots, mercs, etc. Do you really want to keep all of that in there if it is not needed? I started stripping all of that out my first month with Legacy of FrostStone. I would want more streamlined code. When you are debugging there are a hell of a lot less lines of code when you take out routines that are not needed. If something cool comes to EqEmu source and I think it is needed I have added it to mine.
That being said I do not think you can merge back in if the changes are that drastic, sounds like a nightmare.
Threaded Mode
