Thunderbrd
C2C War Dog
Some issues have come back up regarding maximum selection groups being exceeded on very large maps by the Barbarian player. This is an old problem resurfacing again and one big way to begin the process of resolving it (or at least what should probably be a first step to resolution) would be to split Barbarians and Animals into their own special player assignments. (At the moment they are all barbarians.)
Doing this would break compatibility.
A few other things have been recently discussed as to causes to break compatibility or things we'd like to clean up that can only be done when compatibility is broken.
As it looks like we should now take action to split Barbs and Animals (and reserve a few more potential player slots for other NPC player definitions to be possible to insert down the road without breaking compatibility again) I'm initializing this thread so we can discuss and collect our thoughts as to what could and should be done during this breakage period.
If we do this right it may be the one and only time since the SVN began that we will truly break save compatibility. Of course, Alberts makes a valid point that many times we do things that will corrupt previously saved games if they are loaded into the new code environment but usually that can be overlooked. THIS type of compatibility breakage would mean old saves can't be loaded at all past this point.
So we should do it once and do it right.
Therefore, let's generate a list of tasks to do while we go about this.
So far we have:
I know DH said he had a few things to do during a breakage as well. What else would we need to add to this list?
Doing this would break compatibility.
A few other things have been recently discussed as to causes to break compatibility or things we'd like to clean up that can only be done when compatibility is broken.
As it looks like we should now take action to split Barbs and Animals (and reserve a few more potential player slots for other NPC player definitions to be possible to insert down the road without breaking compatibility again) I'm initializing this thread so we can discuss and collect our thoughts as to what could and should be done during this breakage period.
If we do this right it may be the one and only time since the SVN began that we will truly break save compatibility. Of course, Alberts makes a valid point that many times we do things that will corrupt previously saved games if they are loaded into the new code environment but usually that can be overlooked. THIS type of compatibility breakage would mean old saves can't be loaded at all past this point.
So we should do it once and do it right.
Therefore, let's generate a list of tasks to do while we go about this.
So far we have:
- Split Barbs into Animals and Barbs and reserve 5 player slots for these kinds of NPC groups.
- Clean out unused and unnecessary Game Options.
- Possible further cleanups in the enums - deleting an established enum value disrupts saves.
- Rename some xml types to match their text labels.
I know DH said he had a few things to do during a breakage as well. What else would we need to add to this list?