> There are not that many mods that work with 2.3 anyway. I'd estimate
> half of them are already adapted (NTW, Dydo). Perhaps it is easier to
> just fix the 1-2 mods that exist and are still not adapted?
>
> - Per
FYI - as soon as I have some time I am going to update few warzone txt
files by
On Sun, Mar 7, 2010 at 9:32 AM, Guangcong Luo wrote:
> Well, how's about the fact that every single previous mod uses that
> system, and that if you change "== 0" into "== 5", we are suddenly
> compatible with every mod your change dropped support for?
...
> The old code also clearly intended to d
On Sun, Mar 7, 2010 at 2:09 AM, Per Inge Mathisen
wrote:
> What's with the screaming all caps?
It's for emphasis. I'd normally use italics/bold, but, y'know, ASCII medium.
> Since the above documentation was written at the same time as the
> faulty code I was fixing, I could not trust it to be c
On Sun, Mar 7, 2010 at 7:21 AM, Guangcong Luo wrote:
> Previously, the "player" column was something like "5 = available to
> human", and "1, 3, 4, 5, and 6 = available to AI". This is WELL
> DOCUMENTED [1], and is used this way in all Pumpkin code, old mods,
> new mods, etc.
What's with the scre
Guangcong Luo wrote:
> I'm proposing another change that restores backwards-compatibility:
> rename the column to "available_to_humans", and have "5" or "YES" be
> available to humans (and every template is available to AIs). Then,
> for new `template.txt`, the column would always be either "YES" o
Hey, everyone!
Per recently committed a template overhaul to trunk. It was very nice,
and improved template loading significantly (though I think it may the
cause of the new borg template bugs), but there's one thing I want to
address: The changed `template.txt` format for mods.
Previously, the "
