Crews on the field without sieg engines...

[cegorach]

Did you use Gnome ? One space button in wrong place can casu such problem very easily.

[caravel]

I'm using gnome editor yes. It reads the file back in ok, with no errors but I have seen from experience that all is very often not what it seems with the gnome editor. Thanks for the tip, I'll go over it with a text editor and see if there's any extra spaces in there.



Edit: No, same number of tabs and spaces in both modded and unmodded versions of the file. I've visually checked and rechecked the syntax also. Ever line is correctly tabbed, and terminated with a carriage return and line feed in both files.

Edit2: Fixed it. The moral of this story is: Don't use the gnome editor to edit the projectilestats file. It had added two extra values ("250" and "FLAMING_ARROW") to the ninjastar line near the end. I didn't put those in there so I'm not sure where they came from unless the gnome editor somehow put them in there. When I load the file with gnome editor it loads ok and they're not visible, but when loading it up with notepad++, there they were. Editing with notepad++ and removing those values it fixed the problem.

[R'as al Ghul]

Gnome editor sometimes creates files that have a lot of crap at the file-end.
It's a great tool, no doubt but I've had this problem many times.
If you get errors check with notepad or, even better, with wordpad.

R'as

[macsen rufus]

Gnome editor sometimes creates files that have a lot of crap at the file-end.

I can second that - any unexpected crashes I usually find it's best to first open up any files recently Gnomed, using Notepad, and there's occasionally a load of guff at the end. Seems like Gnome has a tendency to do a random copy and paste. Deleting the guff and resaving using Notepad usually solves the problem. If not, THEN you're looking for the missing space, comma-in-hiding, mysteriously inappropriate faction colours etc etc