ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.

Internal Error

From ModEnc
Revision as of 13:24, 19 October 2004 by Marshall (talk | contribs) (link to reconnection error page)
Jump to navigation Jump to search

A general error returned by the TS engine and it's derivates. The message itself doesn't say much, and can be caused by almost anything you do wrong, so it's impossible to say where exactly it came from when it blasts your screen.

If you get an internal error, all you can do is try to track it down. Review your latest rules-changes and play again to see when it occurs. Make sure you always know what happens...the more things happening simultaneously, the harder it is to see what caused the IE.

P.S.: And just because you found a mistake and fixed it, that doesn't mean there can't be a second one that's still causing the error ;)

List of known reasons for Internal Errors (please expand)

Internal Errors caused by weapons:

1. Missing warhead on a weapon.

2. Typo for a weapon entry on a unit/infantry/aircraft/building so that it points to a non-existent weapon.

3. Cluster weapon not attached to another unit.

4. A warhead with CellSpread bigger than 10.

5. A weapon that is used in a game mode but not attached to another unit in the main rules file.

6. Setting off an area-effect warhead that is also Temporal=yes.


Other Internal Error causes:

7. A vehicle that can deploy into a building becomes neutral (such as relinquishing mind-control to a defeated player). Solution: make the vehicle immune to mind-control.


See also: [[Reconnection Error]


Software used to find Internal Errors

INI Checker is a very useful program that can check your rules, art and sound ini files for typos and missing references.