ModEnc² - User contributions [en]

Internal Error

2025-12-08T12:21:20Z

Askhati: /* Tiberian Sun 2.03 */

[[Image:Ts_ie.png|thumb|150px|right|Tiberian Sun's Internal Error]]
[[Image:Ra2_ie.png|thumb|150px|right|Red Alert 2's Internal Error]]
[[Image:Yr_ie.png|thumb|150px|right|Yuri Revenge's Internal Error]]
[[Image:Rp_ie.png|thumb|150px|right|RockPatch's Internal Error]]
The '''Internal Error''' (often just written short-hand as '''IE''') is a general error returned by the [[Tiberian Sun]] [[engine]] and its derivates. The message itself gives no information about what the error actually was or what went wrong, thus leaving it to the modder to know what could have caused the error and to find the cause in their mod's changes.

If you experience an Internal Error, you should:
# Check if the EIP reported in your except.txt file matches an EIP for which the IE cause is known (see below).
# Think about whether a distinctive event immediately preceeded the error (e.g. a unit being built, a weapon being fired, etc.). If this was the case then take a look at the changes you applied to that unit/weapon/whatever and see if there are any mistakes. 
# Carefully check your latest modifications, with the help of a diff between the current rules set and the previous, working rules if possible (for this reason, and in case you mess up your code beyond repair, you should always keep recent backups of working code).
Remember that the more code you add at the same time, the more likely it is to introduce multiple bugs and IE causes (and just because you found one mistake in your code, that doesn't mean there can't be another).

==Except.txt==
If your game crashes because of an Internal Error, a file named except.txt is generated in your game folder. This file is a dump of certain runtime-data from the game at the moment the error occurred and could potentially tell you exactly what went wrong ''if'' you knew the engine code. 
Due to his research into the game's binary and his efforts to develop the RockPatch, pd has occasionally been able to indicate the area of the engine where the error occurred (for example, an error occurring in the voxel-loading routines may indicate a problem with a custom voxel).
However, pd has other commitments and should not be treated as the go-to guy for any IEs you may have. Further more, pd may not neccessarily be able to help - without the source code or a comprehensive understanding of the game's binary the file is of little use. (cp. [[SYNCx.txt]])

According to an early version of [[Except.txt]] (which now redirects here), this file includes the full structure and a stack dump of a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/context_str.asp CONTEXT] element.

IEs that share the same cause also share the same <tt>EIP:</tt> value in except.txt, so knowing that value might help you determine the cause of your IE (see the list of known IE causes (below) which also includes the corresponding EIP). However, it should be noted that some shared IE causes in INI code can yield one of several different EIP values (depending on the circumstance), and that some rare IE causes can actually yield totally random EIP values. As such, if you do have an unexplained IE, you should check all of the known causes.

== Known causes of Internal Errors and their EIPs ==
Since "Internal Error" is the game's response to almost any fatal error, its causes are diverse. Most common are causes related to weapons and warheads, with a missing warhead probably being the most commonly reported cause. Note that some IE causes may be prevented (or at least have certain limits extended (e.g. CellSpread)) by the [[RockPatch]], which in turn has opened up potential for new IE causes ([[RockPatch]]-specific IEs are not listed here).

=== Some useful tips ===
If an integer between {{Tt|0x00812000}} and {{Tt|0x00B78300}} appears in the stack, subtract {{Tt|0x00400000}} from it and look at the resulting address in {{Tt|gamemd.exe}} with a hex editor. If you find some INI flag, you can be almost sure this flag was the one being read when the problem happened and as such its values (or absence thereof) is the problem.


=== Specific game versions ===

==== Yuri's Revenge 1.001 ====

{{:Internal_Error/YR}}

==== Tiberian Sun 2.03 ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00415698|eip}}
| You used a [[TrailerAnim]] on an animation but forgot to set a [[TrailerSeperation]].
|-
! {{Anchor|0042A061|eip}}
| Wall=yes on a normal building.
|-
! {{Anchor|0043541C|eip}}
| Building turret animation has an invalid pointer to an [[AnimTypeClass]] when charging up. See Nod Obelisk of Light for example.
|-
! {{Anchor|00435BED|eip}}
| Building uses `SiloDamage=yes` to fill with tiberium, but a matching [[SpecialAnim]] has not been defined on the building's art.ini entry.
|-
! {{Anchor|00446E61|eip}} {{Anchor|00446F68|eip}}
| Airburst weapon bullet was null. If you have {{f|Airburst|yes|link}} or {{f|Splits|yes|link}} on a [[projectile]], you must also define {{f|AirburstWeapon|link}}.
|-
! {{Anchor|00451C16|eip}}
| {{f|CellAnim|link}} has invalid {{f|Image|link}}.
|-
! {{Anchor|0046C7E2|eip}}
| Fog of War was enabled and crashed the game.
|-
! {{Anchor|004BAEF8|eip}}
| [AI] BuildRefinery= -> one of your factions is missing an entry here, which will cause a crash when the AI tries to use this faction. Will not trigger a crash for human players.
|-
! {{Anchor|004BAF12|eip}}
| [General] HarvesterUnit -> one of the objects in this list is incorrect OR this list has exceeded 127 characters. Commonly triggered when adding new MCV and harvester object codes here when expanding the playable faction list in the TSC 6.00+ builds.
|-
! {{Anchor|004C1680|eip}}
| A house has no buildable {{f|HarvesterUnit|link}}. This crash is typically caused by a [[house]] with an incorrect {{f|ActsLike|link}} setting in a [[map]] when using [https://github.com/CnCNet/ts-patches/blob/9a6440cc921c0941da19e2b1691c45f8d701109d/src/buildconst_harvesterunit_baseunit.asm this patch]. In this case, {{f|ActsLike}} must always point to a house that owns at least one unit listed in {{f|HarvesterUnit}}. Also, make sure all houses listed in the map's {{tt|[Houses]}} list have a valid section. e.g. {{tt|[GDI]}}, defined in the map.
|-
! {{Anchor|004C445E|eip}}
| A unit's Secondary weapon doesn't exist. Check the spelling and cases.
|-
! {{Anchor|004C6428|eip}}
| AI does not have any buildings available for it to build. Check {{f|BuildConst|link}}=, {{f|BuildPower|link}}= etc.
|-
! {{Anchor|004CB997|eip}}
| [[TeamTypes|Team]]'s owner house is invalid. Check if there's a map trigger creating a team whose {{f|House|link}} is invalid or undefined (the house must be one of the houses listed in the map).
|-
! {{Anchor|004D2451|eip}}
| An infantry was about to take damage from a source with no valid [[Warhead]]= set.
|-
! {{Anchor|004D6626|eip}} {{Anchor|004D8BF3|eip}}
| Infantry with missing image in rules.ini (same as missing sequence in art.ini).
|-
!{{Anchor|004F886D|eip}}
| Trying to access colors in header while building radar image; related to the Radar High/Low Colors for terrain tiles.
|-
!{{Anchor|004F8EDD|eip}}
|The number of [[VehicleTypes]] in the [[BaseUnit]] section is incomplete.
|-
! {{Anchor|005A4814|eip}}
| Railgun with wrong particle keys.
|-
! {{Anchor|005A59B4|eip}}
| {{tt|[GasCloudSys]}} with a limited {{f|Lifetime|link}}. This system has hardcoded properties and must exist throughout the game, ergo you must set {{f|Lifetime|-1}} or leave it undefined (it defaults to -1).
|-
! {{Anchor|005A5A83|eip}}
| Invalid {{f|Image|link}} on an [[animation]] attempting to [[SpawnsParticle|spawn particles]] ([[Vinifera]] only). The image must be an existing [[shape]].
|-
! {{Anchor|005A5EB6|eip}}
| {{f|ParticleCap|1|link}} on a {{f|BehavesLike|Spark|link}} particle system.
|-
! {{Anchor|005A640F|eip}}
| {{f|NextParticle|link}} defined on a particle spawned by a {{f|BehavesLike|Smoke|link}} particle system.
|-
! {{Anchor|006233EC|eip}}
| TeamClass::Calc_Center was not able to calculate Team Zone(Unit to center team around) and returned a null pointer to Zone; subsequent attempt to access Zone results in crash.
|-
! {{Anchor|0062E6F6|eip}}
| It was attempted to use a normal colored house on a multiplayer map.
|-
! {{Anchor|006428C6|eip}}
| [[Trigger]] event had an invalid [[House]] parameter.
|-
! {{Anchor|00649563|eip}}
| A [[trigger]] failed to spring. Look for a trigger with invalid parameters, for example a misspelled or undefined [[house]].
|-
! {{Anchor|006703D4|eip}}
| WaveClass Sonic exception, normally triggered by a unit with a weapon that has IsSonic=yes set, firing to the south of the screen and the user scrolling up. No certain fix for this as we know, although [http://ppmsite.com/forum/viewtopic.php?t=31604 HyperPatch] has been confirmed to fix it at least on some systems. Another fix is disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll], although the fix doesn't work on Windows OS's newer than XP.
|-
! {{Anchor|0067159B|eip}}
| WaveClass Sonic exception. Not sure if this is code related, could be end user.
|-
! {{Anchor|006717CB|eip}}
| WaveClass laser exception. This can be fixed by setting DetailLevel= to 1 or 0 in SUN.ini. In addition, disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll] fixes it, but this fix only works on Windows operating systems older than Vista.
|-
! {{Anchor|0067159B|eip}}
| | You have set {{sl|AudioVisual|ShakeScreen}} to zero.
|-
! {{Anchor|00681363|eip}}
| Missing weedguy hack. (second stage Cluster weapons need to be assigned to a unit, to work)
|-
! {{Anchor|006A877A|eip}}
| LightSize>94 was set on a particlesystem.
|-
! {{Anchor|006B6AE6|eip}}
| Multiple reasons, depending on the stack dump in the except:
* If {{Tt|0066F44F}} appears near the top of the stack dump - A [[Warhead]] whose {{f|Verses|link}} could not be processed. {{Tt|EBP}} value says how many values remained to be parsed when an error occurred - (5 - {{Tt|EBP}}) is the 0-based index of the problematic value.
|-
! {{Anchor|006BB69C|eip}}
| conyard construction as building was canceled in the sidebar.
|-
! {{Anchor|90900004|eip}}
| Generic exception.
|}

==== Unverified / lacking information ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00494BCD|eip}}
| (Ares 3.0) A corrupted SHP image was drawn. Check mix files for any .shp files marked by XCC Mixer as 'unknown' under "type".
|-
|-
! {{Anchor|1118A7A5|eip}}
| Probably caused by trying to destroy a tag, but supplying the tag and not a trigger (FA2 offers Triggers, but I hand-typed a tag (among other things). Occams razor suggests this is the culprit.
|-
! {{Anchor|655B4A9C|eip}}
|(Ares 0.E) Setting a [ParticlePart] with 2 BehavesLike= simutaneously (for example , 'both Like=railgun' and 'Like=smoke' exist) may cause an EIP as above . Remove BehavesLike=railgun , and keep Like=smoke here in a [RailgunPart] to avoid this EIP and still gets a railgun with specific SHP-animation rail.
 ''(Two BehavesLike in Ares 0.D is still available , but 0.E not .)''
|-
! {{Anchor|?|eip}}
| Removing a building from the PrerequisitePower= list, while it exists in one of the (GDI/NODRegular/Third)PowerPlant= lists will cause an IE the moment any of your Power buildings get destroyed or sold as long as you own a Construction Yard. YR mods that remove Yuri's side from the game, should not remove YAPOWR from PrerequisitePower=.
 ''(Could not be reproduced thus far.)''
|-
! {{Anchor|?|eip}}
| Calling for an animation that is not listed under {{tt|[[Animations|[Animations]]]}} might trigger an IE.
 ''(That can be caused by multiple issues at various EIPs.)''
|-
! {{Anchor|?|eip}}
| Building a unit in-game whose VXL/SHP was inserted in an original game MIX instead of an expansion MIX.
 ''(Does this really happen? Sounds more like the mix editor crapping up than simply "game should blow up because you changed stock files".)''
 ''Further more, why would anyone eschew the normal method of ''expand''ing the game''. I don't see anyone testing/replicating this so I propose removing it from the list. //Marshall''
|-
! {{Anchor|006F3481|eip}}
| The (elite) secondary weapon (or its warhead) of the object you just selected could not be found (see [[#Broken-reference_Causes|broken-reference causes]], below).
 ''(Marshall retested this and found that the EIP for a missing secondary weapon is actually 006F352E (see above). Not sure what is meant by "you just selected" as the IE will occur the instant the unit is created/promoted. Please can someone else confim that EIP 006F3481 is incorrect and remove this entry if so. Although, it begs the question of where this EIP came from? - it was added by DCoder on 2008-03-04 (id 14195))''
:I'm sorry, I made a mistake analyzing that one. I saw it at [http://www.cannis.net/forum/index.php?s=&showtopic=8560&view=findpost&p=170096 C-GEN] and analyzed it. But in fact it was caused by the ''ElitePrimary'' being wrong, not EliteSecondary. (Though 006F352E in your comment has "ElitePrimary" as the cause as well, I assume you meant 004D5108.) Just cause a certain EIP causes an IE, doesn't mean another EIP cannot cause an IE for the same reason - there are quite a lot of code paths in the game, and under certain circumstances the first EIP doesn't get hit. I just reanalyzed the function which both these EIPs fall under, and I can say this: 006F3481 IEs if (Elite)Secondary is broken, 006F352E - if (Elite)Primary is. The function is responsible for selecting which weapon a unit should use against a certain target in idle mode, the EIP you reported above for (Elite)Secondary (004D5108) is correct, but is only hit if the unit is in Guard mode scanning for targets when promotion happens. [maybe this part should go off to a talk page?] ''//[[User:DCoder|DCoder]]''
''(Just tested this a bit more and got several new EIPs for when the unit was promoted (added in this revision), can't seem to get any consistent results - will need to test this further. //Marshall''
|-
! {{Anchor|?|eip}}
| Setting {{f|CarryOverCap|0|link}}. Default value is -1, positive values do not cause an IE.
 ''I have tested this and couldn't get an IE to occur. Are there any specific circumstances that are required to trigger an IE on a map with CarryOverCap=0? Note that, in FA2YR, CarryOverCap defaults to zero so I would expect this IE to have been seen more often if it was really a problem. //Marshall''
: This setting applies when you progress from one campaign map to another. However, I now see that the default campaigns use 0, so there must be something else amiss. A quick investigation shows that this value is not divided by, so there shouldn't be an exception at all... Will contact Apollo who submitted this as the cause. ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|?|eip}}
| Warheads that are not listed under {{tt|[[Warheads|[Warheads]]]}} have been reported to cause an IE, although the exact details are not established. It is not neccessary for every warhead to be listed (for example, removing the Grand Cannon warhead from the list appears to have no effect on the game), however there is no reason not to list every warhead. '''Validity questionable - if someone can replicate this then please provide an except.txt.'''
''Simply thinking about this, putting warheads on the list should guarantee their position in the internal array, so if there is anywhere that references warheads by internal array position then this is important. However, even if you change an existing weapon's warhead to a non-parsed one in a game mode file, you ''still'' won't get an IE because default warhead values will be used. Because of this, I'm starting to wonder if the reports of un-listed warheads causing an IE are erroneous. If someone can replicate this then please provide an except.txt //Marshall''
: Verified under a debugger - if a weapon exists and links to a warhead that does not, this will not cause an IE, warhead stats will simply remain defaulted. (In other cases, warheads should also remain defaulted but functional. I have not verified every warhead loading location now, but my applicable ini flags tables should indicate whether or not uninited objects cause issues.) ''//[[User:DCoder|DCoder]] 12:44, 11 May 2008 (UTC)''
|-
! {{Anchor|?|eip}}
| If a falling paratrooper (who has nearly reached the ground) is killed by an area-effect mutation weapon. Point based mutations seem to be okay (the falling paratrooper explodes) and the [[Super weapon:Genetic Mutator|Genetic Mutator]] seems incapable of killing falling paratroopers. If you have an area-effect mutation weapon, you should ensure that all paratroopers are immune to it (this also means that you can't have a buildable paradrop plane and an area-effect mutation weapon in the same mod).
|-
! {{Anchor|00000000|eip}}
| Placing two buildings on a map in the map editor so that they overlap, and then destroying or garrisoning one of them in-game. Note that this error is intermittent so may not immediately be noticeable. Use [[FinalAlert]]'s {{tt|Options}} {{arr|r}} {{tt|Show Building Outline}} feature to see the actual areas taken up by buildings, since there are some buildings whose foundation is different from their visual size, and make sure you don't have any buildings that overlap.
Given the unusual EIP value (all zeroes) that has been gathered from testing, it may be a corrupt EIP and not a true indication of the source of the error. Note that this EIP has also been gathered from other 'random-EIP' causes.
:Indeed it is not a true indication, EIP 00000000 can be acquired in several ways. If you can provide an except, I will be able to provide more specific details to look for, like in the case of 0045EC90 . ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|004A2684|eip}}
| Starting a game on any map concludes in a "unable to read scenario" error while loading. The cause of this is an empty uimd.ini file or possibly another empty ini file without any content.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|007564BD|eip}}
| Internal error when starting a game, possibly caused by attempting to load graphics from a corrupt mix file.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|404E0000|eip}}
| Selectable=no on spawned [[AircraftTypes]].
''// [[User:Bbglas007|Bbglas007]]''

This error also occurs if there are overlapping structures and/or overlapping rubble on the map and units try to pathfind over them or one of the buildings is destroyed. Keep in mind that an existing building with Image=none (like for example a nuclear silo) still remains its Bib as it is read from art.ini. So if you give a [NUKE] Image=none it still remains its 3x3 Bib, which counts as an overlapping building. In general don't have overlapping buildings on your map.

''// [[User:DoctorEvil|DoctorEvil]]'' and ~ [[User:RAZER|RAZER]]
|-
! {{Anchor|006E2449|eip}}
| This error occurs when you fire a trigger action 42 (Do explosion at...) at an undefined waypoint.
''// [[User:DoctorEvil|DoctorEvil]]''
|}

===Broken-reference Causes===
*Most of the flags that point to an object type do not verify that the object type exists and will try to invoke it anyway. This includes pointers to weapons, projectiles, warheads, particles, particle systems and infantry/unit/aircraft/building types, among other things.
*All object types must be parsed in order for them to be invoked successfully. For example, a weapon must be parsed by being referenced by a unit in the main rules (weapons used in a game mode that aren't referenced in the main rules will not have been parsed, nor will shrapnel weapons that haven't been referenced by a dummy unit).
*Note that all weapons have to specify a {{f|Warhead|link}} tag and the tag must not be blank otherwise an IE will occur. However if the specified {{f|Warhead|link}} does not exist then that will not cause an IE, as the game will use default warhead settings.
*Your object type may not be 'missing' as such, you may just have mis-spelled its ID (e.g. "MagenticBeam" as opposed to "MagneticBeam"). Always check your typing carefully to make sure you don't  any words out.

===Tank Bunker / Sell Unit IEs===
*There are two IEs that can occur after using a 'Sell Unit' superweapon on a tank-bunkered unit. Both of these IEs can yield seemingly random EIP values (due to the fact that, when the unit is sold, the building's "BunkeredUnit" pointer isn't cleared and so points to garbage memory. Attempts to dereference it will be met with varying levels of failure).
*An IE may occur the instant you sell the unit.
*If an IE does not occur the instant you sell the unit, then the Tank Bunker will have been rendered unusable as the walls are still up. If the 'broken' Tank Bunker is sold or destroyed then an IE will occur (this IE ''does'' always happen). This IE frequently yields EIP 004593BB, although has been known to yield seemingly random EIP values (for the reason stated above).
*The only way to prevent these IEs is to make sure a player never has access to both the Sell Unit superweapon and the Tank Bunker at the same time. (To achieve this, the building that provides the superweapon must be uncapturable and immune to mind-control as must the Tank Bunker. Further more, unless both buildings are country specials, you will need to remove MCVs from crates and make Construction Yards uncapturable and immune to mind-control too.)

==Software used to find Internal Errors==
*[http://dc.strategy-x.com/checker INI Checker] (can check your rules, art and sound files for syntactic errors like typos and missing references)
*[[ExceptChecker]] (primarily for RockPatch-related IEs, it analyzes except.txt, tries to find references to code added by the patch or known routines, and ''might'' then be able give a direction)
*[[Debugger]] (if you know assembler)

==Note==
*After observing [[IE]] for several times, I found that ''' "EIP " ''' that occurs are expressed in categories such as unit errors, image errors, sound errors, configuration + settings errors, etc.

== See also ==
*[[Reconnection Error]]
*[http://forums.renegadeprojects.com/showthread.php?pid=2034#pid2034 Confirmation the Infantry Linking IE also applies to modifications done by maps]

[[Category:Bugs_and_Errors]]

SiloDamage

2025-12-08T12:18:21Z

Askhati: Add note about requiring SpecialAnim

{{Flag
|name={{PAGENAME}}
|files={{Categ|Art(md).ini}}
|values={{Values|bool}}
|default=no
|types=[[BuildingTypes]]
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}
Specifies whether or not this building's image should be based on its current [[Storage|Tiberium storage level]]. This enables the building to use {{f|SpecialAnim|link}} for the storage fill animation.

==Note:==
If you define this on an art.ini entry, you must also define a matching [[SpecialAnim]]; if not, the game will crash the moment the silo structure tries to fill up with tiberium.

==See Also==
* [[SpecialAnim]]

Internal Error

2025-11-01T20:56:13Z

Askhati: /* Tiberian Sun 2.03 */

[[Image:Ts_ie.png|thumb|150px|right|Tiberian Sun's Internal Error]]
[[Image:Ra2_ie.png|thumb|150px|right|Red Alert 2's Internal Error]]
[[Image:Yr_ie.png|thumb|150px|right|Yuri Revenge's Internal Error]]
[[Image:Rp_ie.png|thumb|150px|right|RockPatch's Internal Error]]
The '''Internal Error''' (often just written short-hand as '''IE''') is a general error returned by the [[Tiberian Sun]] [[engine]] and its derivates. The message itself gives no information about what the error actually was or what went wrong, thus leaving it to the modder to know what could have caused the error and to find the cause in their mod's changes.

If you experience an Internal Error, you should:
# Check if the EIP reported in your except.txt file matches an EIP for which the IE cause is known (see below).
# Think about whether a distinctive event immediately preceeded the error (e.g. a unit being built, a weapon being fired, etc.). If this was the case then take a look at the changes you applied to that unit/weapon/whatever and see if there are any mistakes. 
# Carefully check your latest modifications, with the help of a diff between the current rules set and the previous, working rules if possible (for this reason, and in case you mess up your code beyond repair, you should always keep recent backups of working code).
Remember that the more code you add at the same time, the more likely it is to introduce multiple bugs and IE causes (and just because you found one mistake in your code, that doesn't mean there can't be another).

==Except.txt==
If your game crashes because of an Internal Error, a file named except.txt is generated in your game folder. This file is a dump of certain runtime-data from the game at the moment the error occurred and could potentially tell you exactly what went wrong ''if'' you knew the engine code. 
Due to his research into the game's binary and his efforts to develop the RockPatch, pd has occasionally been able to indicate the area of the engine where the error occurred (for example, an error occurring in the voxel-loading routines may indicate a problem with a custom voxel).
However, pd has other commitments and should not be treated as the go-to guy for any IEs you may have. Further more, pd may not neccessarily be able to help - without the source code or a comprehensive understanding of the game's binary the file is of little use. (cp. [[SYNCx.txt]])

According to an early version of [[Except.txt]] (which now redirects here), this file includes the full structure and a stack dump of a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/context_str.asp CONTEXT] element.

IEs that share the same cause also share the same <tt>EIP:</tt> value in except.txt, so knowing that value might help you determine the cause of your IE (see the list of known IE causes (below) which also includes the corresponding EIP). However, it should be noted that some shared IE causes in INI code can yield one of several different EIP values (depending on the circumstance), and that some rare IE causes can actually yield totally random EIP values. As such, if you do have an unexplained IE, you should check all of the known causes.

== Known causes of Internal Errors and their EIPs ==
Since "Internal Error" is the game's response to almost any fatal error, its causes are diverse. Most common are causes related to weapons and warheads, with a missing warhead probably being the most commonly reported cause. Note that some IE causes may be prevented (or at least have certain limits extended (e.g. CellSpread)) by the [[RockPatch]], which in turn has opened up potential for new IE causes ([[RockPatch]]-specific IEs are not listed here).

=== Some useful tips ===
If an integer between {{Tt|0x00812000}} and {{Tt|0x00B78300}} appears in the stack, subtract {{Tt|0x00400000}} from it and look at the resulting address in {{Tt|gamemd.exe}} with a hex editor. If you find some INI flag, you can be almost sure this flag was the one being read when the problem happened and as such its values (or absence thereof) is the problem.


=== Specific game versions ===

==== Yuri's Revenge 1.001 ====

{{:Internal_Error/YR}}

==== Tiberian Sun 2.03 ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00415698|eip}}
| You used a [[TrailerAnim]] on an animation but forgot to set a [[TrailerSeperation]].
|-
! {{Anchor|0042A061|eip}}
| Wall=yes on a normal building.
|-
! {{Anchor|0043541C|eip}}
| Building turret animation has an invalid pointer to an [[AnimTypeClass]] when charging up. See Nod Obelisk of Light for example.
|-
! {{Anchor|00446E61|eip}} {{Anchor|00446F68|eip}}
| Airburst weapon bullet was null. If you have {{f|Airburst|yes|link}} or {{f|Splits|yes|link}} on a [[projectile]], you must also define {{f|AirburstWeapon|link}}.
|-
! {{Anchor|00451C16|eip}}
| {{f|CellAnim|link}} has invalid {{f|Image|link}}.
|-
! {{Anchor|0046C7E2|eip}}
| Fog of War was enabled and crashed the game.
|-
! {{Anchor|004BAEF8|eip}}
| [AI] BuildRefinery= -> one of your factions is missing an entry here, which will cause a crash when the AI tries to use this faction. Will not trigger a crash for human players.
|-
! {{Anchor|004BAF12|eip}}
| [General] HarvesterUnit -> one of the objects in this list is incorrect OR this list has exceeded 127 characters. Commonly triggered when adding new MCV and harvester object codes here when expanding the playable faction list in the TSC 6.00+ builds.
|-
! {{Anchor|004C1680|eip}}
| A house has no buildable {{f|HarvesterUnit|link}}. This crash is typically caused by a [[house]] with an incorrect {{f|ActsLike|link}} setting in a [[map]] when using [https://github.com/CnCNet/ts-patches/blob/9a6440cc921c0941da19e2b1691c45f8d701109d/src/buildconst_harvesterunit_baseunit.asm this patch]. In this case, {{f|ActsLike}} must always point to a house that owns at least one unit listed in {{f|HarvesterUnit}}. Also, make sure all houses listed in the map's {{tt|[Houses]}} list have a valid section. e.g. {{tt|[GDI]}}, defined in the map.
|-
! {{Anchor|004C445E|eip}}
| A unit's Secondary weapon doesn't exist. Check the spelling and cases.
|-
! {{Anchor|004C6428|eip}}
| AI does not have any buildings available for it to build. Check {{f|BuildConst|link}}=, {{f|BuildPower|link}}= etc.
|-
! {{Anchor|004CB997|eip}}
| [[TeamTypes|Team]]'s owner house is invalid. Check if there's a map trigger creating a team whose {{f|House|link}} is invalid or undefined (the house must be one of the houses listed in the map).
|-
! {{Anchor|004D2451|eip}}
| An infantry was about to take damage from a source with no valid [[Warhead]]= set.
|-
! {{Anchor|004D6626|eip}} {{Anchor|004D8BF3|eip}}
| Infantry with missing image in rules.ini (same as missing sequence in art.ini).
|-
!{{Anchor|004F886D|eip}}
| Trying to access colors in header while building radar image; related to the Radar High/Low Colors for terrain tiles.
|-
!{{Anchor|004F8EDD|eip}}
|The number of [[VehicleTypes]] in the [[BaseUnit]] section is incomplete.
|-
! {{Anchor|005A4814|eip}}
| Railgun with wrong particle keys.
|-
! {{Anchor|005A59B4|eip}}
| {{tt|[GasCloudSys]}} with a limited {{f|Lifetime|link}}. This system has hardcoded properties and must exist throughout the game, ergo you must set {{f|Lifetime|-1}} or leave it undefined (it defaults to -1).
|-
! {{Anchor|005A5A83|eip}}
| Invalid {{f|Image|link}} on an [[animation]] attempting to [[SpawnsParticle|spawn particles]] ([[Vinifera]] only). The image must be an existing [[shape]].
|-
! {{Anchor|005A5EB6|eip}}
| {{f|ParticleCap|1|link}} on a {{f|BehavesLike|Spark|link}} particle system.
|-
! {{Anchor|005A640F|eip}}
| {{f|NextParticle|link}} defined on a particle spawned by a {{f|BehavesLike|Smoke|link}} particle system.
|-
! {{Anchor|006233EC|eip}}
| TeamClass::Calc_Center was not able to calculate Team Zone(Unit to center team around) and returned a null pointer to Zone; subsequent attempt to access Zone results in crash.
|-
! {{Anchor|0062E6F6|eip}}
| It was attempted to use a normal colored house on a multiplayer map.
|-
! {{Anchor|006428C6|eip}}
| [[Trigger]] event had an invalid [[House]] parameter.
|-
! {{Anchor|00649563|eip}}
| A [[trigger]] failed to spring. Look for a trigger with invalid parameters, for example a misspelled or undefined [[house]].
|-
! {{Anchor|006703D4|eip}}
| WaveClass Sonic exception, normally triggered by a unit with a weapon that has IsSonic=yes set, firing to the south of the screen and the user scrolling up. No certain fix for this as we know, although [http://ppmsite.com/forum/viewtopic.php?t=31604 HyperPatch] has been confirmed to fix it at least on some systems. Another fix is disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll], although the fix doesn't work on Windows OS's newer than XP.
|-
! {{Anchor|0067159B|eip}}
| WaveClass Sonic exception. Not sure if this is code related, could be end user.
|-
! {{Anchor|006717CB|eip}}
| WaveClass laser exception. This can be fixed by setting DetailLevel= to 1 or 0 in SUN.ini. In addition, disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll] fixes it, but this fix only works on Windows operating systems older than Vista.
|-
! {{Anchor|0067159B|eip}}
| | You have set {{sl|AudioVisual|ShakeScreen}} to zero.
|-
! {{Anchor|00681363|eip}}
| Missing weedguy hack. (second stage Cluster weapons need to be assigned to a unit, to work)
|-
! {{Anchor|006A877A|eip}}
| LightSize>94 was set on a particlesystem.
|-
! {{Anchor|006B6AE6|eip}}
| Multiple reasons, depending on the stack dump in the except:
* If {{Tt|0066F44F}} appears near the top of the stack dump - A [[Warhead]] whose {{f|Verses|link}} could not be processed. {{Tt|EBP}} value says how many values remained to be parsed when an error occurred - (5 - {{Tt|EBP}}) is the 0-based index of the problematic value.
|-
! {{Anchor|006BB69C|eip}}
| conyard construction as building was canceled in the sidebar.
|-
! {{Anchor|90900004|eip}}
| Generic exception.
|}

==== Unverified / lacking information ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00494BCD|eip}}
| (Ares 3.0) A corrupted SHP image was drawn. Check mix files for any .shp files marked by XCC Mixer as 'unknown' under "type".
|-
|-
! {{Anchor|1118A7A5|eip}}
| Probably caused by trying to destroy a tag, but supplying the tag and not a trigger (FA2 offers Triggers, but I hand-typed a tag (among other things). Occams razor suggests this is the culprit.
|-
! {{Anchor|655B4A9C|eip}}
|(Ares 0.E) Setting a [ParticlePart] with 2 BehavesLike= simutaneously (for example , 'both Like=railgun' and 'Like=smoke' exist) may cause an EIP as above . Remove BehavesLike=railgun , and keep Like=smoke here in a [RailgunPart] to avoid this EIP and still gets a railgun with specific SHP-animation rail.
 ''(Two BehavesLike in Ares 0.D is still available , but 0.E not .)''
|-
! {{Anchor|?|eip}}
| Removing a building from the PrerequisitePower= list, while it exists in one of the (GDI/NODRegular/Third)PowerPlant= lists will cause an IE the moment any of your Power buildings get destroyed or sold as long as you own a Construction Yard. YR mods that remove Yuri's side from the game, should not remove YAPOWR from PrerequisitePower=.
 ''(Could not be reproduced thus far.)''
|-
! {{Anchor|?|eip}}
| Calling for an animation that is not listed under {{tt|[[Animations|[Animations]]]}} might trigger an IE.
 ''(That can be caused by multiple issues at various EIPs.)''
|-
! {{Anchor|?|eip}}
| Building a unit in-game whose VXL/SHP was inserted in an original game MIX instead of an expansion MIX.
 ''(Does this really happen? Sounds more like the mix editor crapping up than simply "game should blow up because you changed stock files".)''
 ''Further more, why would anyone eschew the normal method of ''expand''ing the game''. I don't see anyone testing/replicating this so I propose removing it from the list. //Marshall''
|-
! {{Anchor|006F3481|eip}}
| The (elite) secondary weapon (or its warhead) of the object you just selected could not be found (see [[#Broken-reference_Causes|broken-reference causes]], below).
 ''(Marshall retested this and found that the EIP for a missing secondary weapon is actually 006F352E (see above). Not sure what is meant by "you just selected" as the IE will occur the instant the unit is created/promoted. Please can someone else confim that EIP 006F3481 is incorrect and remove this entry if so. Although, it begs the question of where this EIP came from? - it was added by DCoder on 2008-03-04 (id 14195))''
:I'm sorry, I made a mistake analyzing that one. I saw it at [http://www.cannis.net/forum/index.php?s=&showtopic=8560&view=findpost&p=170096 C-GEN] and analyzed it. But in fact it was caused by the ''ElitePrimary'' being wrong, not EliteSecondary. (Though 006F352E in your comment has "ElitePrimary" as the cause as well, I assume you meant 004D5108.) Just cause a certain EIP causes an IE, doesn't mean another EIP cannot cause an IE for the same reason - there are quite a lot of code paths in the game, and under certain circumstances the first EIP doesn't get hit. I just reanalyzed the function which both these EIPs fall under, and I can say this: 006F3481 IEs if (Elite)Secondary is broken, 006F352E - if (Elite)Primary is. The function is responsible for selecting which weapon a unit should use against a certain target in idle mode, the EIP you reported above for (Elite)Secondary (004D5108) is correct, but is only hit if the unit is in Guard mode scanning for targets when promotion happens. [maybe this part should go off to a talk page?] ''//[[User:DCoder|DCoder]]''
''(Just tested this a bit more and got several new EIPs for when the unit was promoted (added in this revision), can't seem to get any consistent results - will need to test this further. //Marshall''
|-
! {{Anchor|?|eip}}
| Setting {{f|CarryOverCap|0|link}}. Default value is -1, positive values do not cause an IE.
 ''I have tested this and couldn't get an IE to occur. Are there any specific circumstances that are required to trigger an IE on a map with CarryOverCap=0? Note that, in FA2YR, CarryOverCap defaults to zero so I would expect this IE to have been seen more often if it was really a problem. //Marshall''
: This setting applies when you progress from one campaign map to another. However, I now see that the default campaigns use 0, so there must be something else amiss. A quick investigation shows that this value is not divided by, so there shouldn't be an exception at all... Will contact Apollo who submitted this as the cause. ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|?|eip}}
| Warheads that are not listed under {{tt|[[Warheads|[Warheads]]]}} have been reported to cause an IE, although the exact details are not established. It is not neccessary for every warhead to be listed (for example, removing the Grand Cannon warhead from the list appears to have no effect on the game), however there is no reason not to list every warhead. '''Validity questionable - if someone can replicate this then please provide an except.txt.'''
''Simply thinking about this, putting warheads on the list should guarantee their position in the internal array, so if there is anywhere that references warheads by internal array position then this is important. However, even if you change an existing weapon's warhead to a non-parsed one in a game mode file, you ''still'' won't get an IE because default warhead values will be used. Because of this, I'm starting to wonder if the reports of un-listed warheads causing an IE are erroneous. If someone can replicate this then please provide an except.txt //Marshall''
: Verified under a debugger - if a weapon exists and links to a warhead that does not, this will not cause an IE, warhead stats will simply remain defaulted. (In other cases, warheads should also remain defaulted but functional. I have not verified every warhead loading location now, but my applicable ini flags tables should indicate whether or not uninited objects cause issues.) ''//[[User:DCoder|DCoder]] 12:44, 11 May 2008 (UTC)''
|-
! {{Anchor|?|eip}}
| If a falling paratrooper (who has nearly reached the ground) is killed by an area-effect mutation weapon. Point based mutations seem to be okay (the falling paratrooper explodes) and the [[Super weapon:Genetic Mutator|Genetic Mutator]] seems incapable of killing falling paratroopers. If you have an area-effect mutation weapon, you should ensure that all paratroopers are immune to it (this also means that you can't have a buildable paradrop plane and an area-effect mutation weapon in the same mod).
|-
! {{Anchor|00000000|eip}}
| Placing two buildings on a map in the map editor so that they overlap, and then destroying or garrisoning one of them in-game. Note that this error is intermittent so may not immediately be noticeable. Use [[FinalAlert]]'s {{tt|Options}} {{arr|r}} {{tt|Show Building Outline}} feature to see the actual areas taken up by buildings, since there are some buildings whose foundation is different from their visual size, and make sure you don't have any buildings that overlap.
Given the unusual EIP value (all zeroes) that has been gathered from testing, it may be a corrupt EIP and not a true indication of the source of the error. Note that this EIP has also been gathered from other 'random-EIP' causes.
:Indeed it is not a true indication, EIP 00000000 can be acquired in several ways. If you can provide an except, I will be able to provide more specific details to look for, like in the case of 0045EC90 . ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|004A2684|eip}}
| Starting a game on any map concludes in a "unable to read scenario" error while loading. The cause of this is an empty uimd.ini file or possibly another empty ini file without any content.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|007564BD|eip}}
| Internal error when starting a game, possibly caused by attempting to load graphics from a corrupt mix file.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|404E0000|eip}}
| Selectable=no on spawned [[AircraftTypes]].
''// [[User:Bbglas007|Bbglas007]]''

This error also occurs if there are overlapping structures and/or overlapping rubble on the map and units try to pathfind over them or one of the buildings is destroyed. Keep in mind that an existing building with Image=none (like for example a nuclear silo) still remains its Bib as it is read from art.ini. So if you give a [NUKE] Image=none it still remains its 3x3 Bib, which counts as an overlapping building. In general don't have overlapping buildings on your map.

''// [[User:DoctorEvil|DoctorEvil]]'' and ~ [[User:RAZER|RAZER]]
|-
! {{Anchor|006E2449|eip}}
| This error occurs when you fire a trigger action 42 (Do explosion at...) at an undefined waypoint.
''// [[User:DoctorEvil|DoctorEvil]]''
|}

===Broken-reference Causes===
*Most of the flags that point to an object type do not verify that the object type exists and will try to invoke it anyway. This includes pointers to weapons, projectiles, warheads, particles, particle systems and infantry/unit/aircraft/building types, among other things.
*All object types must be parsed in order for them to be invoked successfully. For example, a weapon must be parsed by being referenced by a unit in the main rules (weapons used in a game mode that aren't referenced in the main rules will not have been parsed, nor will shrapnel weapons that haven't been referenced by a dummy unit).
*Note that all weapons have to specify a {{f|Warhead|link}} tag and the tag must not be blank otherwise an IE will occur. However if the specified {{f|Warhead|link}} does not exist then that will not cause an IE, as the game will use default warhead settings.
*Your object type may not be 'missing' as such, you may just have mis-spelled its ID (e.g. "MagenticBeam" as opposed to "MagneticBeam"). Always check your typing carefully to make sure you don't  any words out.

===Tank Bunker / Sell Unit IEs===
*There are two IEs that can occur after using a 'Sell Unit' superweapon on a tank-bunkered unit. Both of these IEs can yield seemingly random EIP values (due to the fact that, when the unit is sold, the building's "BunkeredUnit" pointer isn't cleared and so points to garbage memory. Attempts to dereference it will be met with varying levels of failure).
*An IE may occur the instant you sell the unit.
*If an IE does not occur the instant you sell the unit, then the Tank Bunker will have been rendered unusable as the walls are still up. If the 'broken' Tank Bunker is sold or destroyed then an IE will occur (this IE ''does'' always happen). This IE frequently yields EIP 004593BB, although has been known to yield seemingly random EIP values (for the reason stated above).
*The only way to prevent these IEs is to make sure a player never has access to both the Sell Unit superweapon and the Tank Bunker at the same time. (To achieve this, the building that provides the superweapon must be uncapturable and immune to mind-control as must the Tank Bunker. Further more, unless both buildings are country specials, you will need to remove MCVs from crates and make Construction Yards uncapturable and immune to mind-control too.)

==Software used to find Internal Errors==
*[http://dc.strategy-x.com/checker INI Checker] (can check your rules, art and sound files for syntactic errors like typos and missing references)
*[[ExceptChecker]] (primarily for RockPatch-related IEs, it analyzes except.txt, tries to find references to code added by the patch or known routines, and ''might'' then be able give a direction)
*[[Debugger]] (if you know assembler)

==Note==
*After observing [[IE]] for several times, I found that ''' "EIP " ''' that occurs are expressed in categories such as unit errors, image errors, sound errors, configuration + settings errors, etc.

== See also ==
*[[Reconnection Error]]
*[http://forums.renegadeprojects.com/showthread.php?pid=2034#pid2034 Confirmation the Infantry Linking IE also applies to modifications done by maps]

[[Category:Bugs_and_Errors]]

Internal Error

2025-11-01T20:12:14Z

Askhati: /* Tiberian Sun 2.03 */

[[Image:Ts_ie.png|thumb|150px|right|Tiberian Sun's Internal Error]]
[[Image:Ra2_ie.png|thumb|150px|right|Red Alert 2's Internal Error]]
[[Image:Yr_ie.png|thumb|150px|right|Yuri Revenge's Internal Error]]
[[Image:Rp_ie.png|thumb|150px|right|RockPatch's Internal Error]]
The '''Internal Error''' (often just written short-hand as '''IE''') is a general error returned by the [[Tiberian Sun]] [[engine]] and its derivates. The message itself gives no information about what the error actually was or what went wrong, thus leaving it to the modder to know what could have caused the error and to find the cause in their mod's changes.

If you experience an Internal Error, you should:
# Check if the EIP reported in your except.txt file matches an EIP for which the IE cause is known (see below).
# Think about whether a distinctive event immediately preceeded the error (e.g. a unit being built, a weapon being fired, etc.). If this was the case then take a look at the changes you applied to that unit/weapon/whatever and see if there are any mistakes. 
# Carefully check your latest modifications, with the help of a diff between the current rules set and the previous, working rules if possible (for this reason, and in case you mess up your code beyond repair, you should always keep recent backups of working code).
Remember that the more code you add at the same time, the more likely it is to introduce multiple bugs and IE causes (and just because you found one mistake in your code, that doesn't mean there can't be another).

==Except.txt==
If your game crashes because of an Internal Error, a file named except.txt is generated in your game folder. This file is a dump of certain runtime-data from the game at the moment the error occurred and could potentially tell you exactly what went wrong ''if'' you knew the engine code. 
Due to his research into the game's binary and his efforts to develop the RockPatch, pd has occasionally been able to indicate the area of the engine where the error occurred (for example, an error occurring in the voxel-loading routines may indicate a problem with a custom voxel).
However, pd has other commitments and should not be treated as the go-to guy for any IEs you may have. Further more, pd may not neccessarily be able to help - without the source code or a comprehensive understanding of the game's binary the file is of little use. (cp. [[SYNCx.txt]])

According to an early version of [[Except.txt]] (which now redirects here), this file includes the full structure and a stack dump of a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/context_str.asp CONTEXT] element.

IEs that share the same cause also share the same <tt>EIP:</tt> value in except.txt, so knowing that value might help you determine the cause of your IE (see the list of known IE causes (below) which also includes the corresponding EIP). However, it should be noted that some shared IE causes in INI code can yield one of several different EIP values (depending on the circumstance), and that some rare IE causes can actually yield totally random EIP values. As such, if you do have an unexplained IE, you should check all of the known causes.

== Known causes of Internal Errors and their EIPs ==
Since "Internal Error" is the game's response to almost any fatal error, its causes are diverse. Most common are causes related to weapons and warheads, with a missing warhead probably being the most commonly reported cause. Note that some IE causes may be prevented (or at least have certain limits extended (e.g. CellSpread)) by the [[RockPatch]], which in turn has opened up potential for new IE causes ([[RockPatch]]-specific IEs are not listed here).

=== Some useful tips ===
If an integer between {{Tt|0x00812000}} and {{Tt|0x00B78300}} appears in the stack, subtract {{Tt|0x00400000}} from it and look at the resulting address in {{Tt|gamemd.exe}} with a hex editor. If you find some INI flag, you can be almost sure this flag was the one being read when the problem happened and as such its values (or absence thereof) is the problem.


=== Specific game versions ===

==== Yuri's Revenge 1.001 ====

{{:Internal_Error/YR}}

==== Tiberian Sun 2.03 ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00415698|eip}}
| You used a [[TrailerAnim]] on an animation but forgot to set a [[TrailerSeperation]].
|-
! {{Anchor|0042A061|eip}}
| Wall=yes on a normal building.
|-
! {{Anchor|0043541C|eip}}
| Building turret animation has an invalid pointer to an [[AnimTypeClass]] when charging up. See Nod Obelisk of Light for example.
|-
! {{Anchor|00446E61|eip}} {{Anchor|00446F68|eip}}
| Airburst weapon bullet was null. If you have {{f|Airburst|yes|link}} or {{f|Splits|yes|link}} on a [[projectile]], you must also define {{f|AirburstWeapon|link}}.
|-
! {{Anchor|00451C16|eip}}
| {{f|CellAnim|link}} has invalid {{f|Image|link}}.
|-
! {{Anchor|0046C7E2|eip}}
| Fog of War was enabled and crashed the game.
|-
! {{Anchor|004BAEF8|eip}}
| [AI] BuildRefinery= -> one of your factions is missing an entry here, which will cause a crash when the AI tries to use this faction. Will not trigger a crash for human players.
|-
! {{Anchor|004BAF12|eip}}
| [General] HarvesterUnit -> one of the objects in this list is incorrect OR this list has exceeded 127 characters. Commonly triggered when adding new MCV and harvester object codes here when expanding the playable faction list in the TSC 6.00+ builds.
|-
! {{Anchor|004C1680|eip}}
| A house has no buildable {{f|HarvesterUnit|link}}. This crash is typically caused by a [[house]] with an incorrect {{f|ActsLike|link}} setting in a [[map]] when using [https://github.com/CnCNet/ts-patches/blob/9a6440cc921c0941da19e2b1691c45f8d701109d/src/buildconst_harvesterunit_baseunit.asm this patch]. In this case, {{f|ActsLike}} must always point to a house that owns at least one unit listed in {{f|HarvesterUnit}}. Also, make sure all houses listed in the map's {{tt|[Houses]}} list have a valid section. e.g. {{tt|[GDI]}}, defined in the map.
|-
! {{Anchor|004C445E|eip}}
| A unit's Secondary weapon doesn't exist. Check the spelling and cases.
|-
! {{Anchor|004C6428|eip}}
| AI does not have any buildings available for it to build. Check {{f|BuildConst|link}}=, {{f|BuildPower|link}}= etc.
|-
! {{Anchor|004CB997|eip}}
| [[TeamTypes|Team]]'s owner house is invalid. Check if there's a map trigger creating a team whose {{f|House|link}} is invalid or undefined (the house must be one of the houses listed in the map).
|-
! {{Anchor|004D2451|eip}}
| An infantry was about to take damage from a source with no valid [[Warhead]]= set.
|-
! {{Anchor|004D6626|eip}} {{Anchor|004D8BF3|eip}}
| Infantry with missing image in rules.ini (same as missing sequence in art.ini).
|-
!{{Anchor|004F886D|eip}}
| Trying to access colors in header while building radar image; related to the Radar High/Low Colors for terrain tiles.
|-
!{{Anchor|004F8EDD|eip}}
|The number of [[VehicleTypes]] in the [[BaseUnit]] section is incomplete.
|-
! {{Anchor|005A4814|eip}}
| Railgun with wrong particle keys.
|-
! {{Anchor|005A59B4|eip}}
| {{tt|[GasCloudSys]}} with a limited {{f|Lifetime|link}}. This system has hardcoded properties and must exist throughout the game, ergo you must set {{f|Lifetime|-1}} or leave it undefined (it defaults to -1).
|-
! {{Anchor|005A5A83|eip}}
| Invalid {{f|Image|link}} on an [[animation]] attempting to [[SpawnsParticle|spawn particles]] ([[Vinifera]] only). The image must be an existing [[shape]].
|-
! {{Anchor|005A5EB6|eip}}
| {{f|ParticleCap|1|link}} on a {{f|BehavesLike|Spark|link}} particle system.
|-
! {{Anchor|005A640F|eip}}
| {{f|NextParticle|link}} defined on a particle spawned by a {{f|BehavesLike|Smoke|link}} particle system.
|-
! {{Anchor|006233EC|eip}}
| A TeamClass - which had previously already been deleted - was instructed to attempt to perform per-frame logic.
|-
! {{Anchor|0062E6F6|eip}}
| It was attempted to use a normal colored house on a multiplayer map.
|-
! {{Anchor|006428C6|eip}}
| [[Trigger]] event had an invalid [[House]] parameter.
|-
! {{Anchor|00649563|eip}}
| A [[trigger]] failed to spring. Look for a trigger with invalid parameters, for example a misspelled or undefined [[house]].
|-
! {{Anchor|006703D4|eip}}
| WaveClass Sonic exception, normally triggered by a unit with a weapon that has IsSonic=yes set, firing to the south of the screen and the user scrolling up. No certain fix for this as we know, although [http://ppmsite.com/forum/viewtopic.php?t=31604 HyperPatch] has been confirmed to fix it at least on some systems. Another fix is disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll], although the fix doesn't work on Windows OS's newer than XP.
|-
! {{Anchor|0067159B|eip}}
| WaveClass Sonic exception. Not sure if this is code related, could be end user.
|-
! {{Anchor|006717CB|eip}}
| WaveClass laser exception. This can be fixed by setting DetailLevel= to 1 or 0 in SUN.ini. In addition, disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll] fixes it, but this fix only works on Windows operating systems older than Vista.
|-
! {{Anchor|0067159B|eip}}
| | You have set {{sl|AudioVisual|ShakeScreen}} to zero.
|-
! {{Anchor|00681363|eip}}
| Missing weedguy hack. (second stage Cluster weapons need to be assigned to a unit, to work)
|-
! {{Anchor|006A877A|eip}}
| LightSize>94 was set on a particlesystem.
|-
! {{Anchor|006B6AE6|eip}}
| Multiple reasons, depending on the stack dump in the except:
* If {{Tt|0066F44F}} appears near the top of the stack dump - A [[Warhead]] whose {{f|Verses|link}} could not be processed. {{Tt|EBP}} value says how many values remained to be parsed when an error occurred - (5 - {{Tt|EBP}}) is the 0-based index of the problematic value.
|-
! {{Anchor|006BB69C|eip}}
| conyard construction as building was canceled in the sidebar.
|-
! {{Anchor|90900004|eip}}
| Generic exception.
|}

==== Unverified / lacking information ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00494BCD|eip}}
| (Ares 3.0) A corrupted SHP image was drawn. Check mix files for any .shp files marked by XCC Mixer as 'unknown' under "type".
|-
|-
! {{Anchor|1118A7A5|eip}}
| Probably caused by trying to destroy a tag, but supplying the tag and not a trigger (FA2 offers Triggers, but I hand-typed a tag (among other things). Occams razor suggests this is the culprit.
|-
! {{Anchor|655B4A9C|eip}}
|(Ares 0.E) Setting a [ParticlePart] with 2 BehavesLike= simutaneously (for example , 'both Like=railgun' and 'Like=smoke' exist) may cause an EIP as above . Remove BehavesLike=railgun , and keep Like=smoke here in a [RailgunPart] to avoid this EIP and still gets a railgun with specific SHP-animation rail.
 ''(Two BehavesLike in Ares 0.D is still available , but 0.E not .)''
|-
! {{Anchor|?|eip}}
| Removing a building from the PrerequisitePower= list, while it exists in one of the (GDI/NODRegular/Third)PowerPlant= lists will cause an IE the moment any of your Power buildings get destroyed or sold as long as you own a Construction Yard. YR mods that remove Yuri's side from the game, should not remove YAPOWR from PrerequisitePower=.
 ''(Could not be reproduced thus far.)''
|-
! {{Anchor|?|eip}}
| Calling for an animation that is not listed under {{tt|[[Animations|[Animations]]]}} might trigger an IE.
 ''(That can be caused by multiple issues at various EIPs.)''
|-
! {{Anchor|?|eip}}
| Building a unit in-game whose VXL/SHP was inserted in an original game MIX instead of an expansion MIX.
 ''(Does this really happen? Sounds more like the mix editor crapping up than simply "game should blow up because you changed stock files".)''
 ''Further more, why would anyone eschew the normal method of ''expand''ing the game''. I don't see anyone testing/replicating this so I propose removing it from the list. //Marshall''
|-
! {{Anchor|006F3481|eip}}
| The (elite) secondary weapon (or its warhead) of the object you just selected could not be found (see [[#Broken-reference_Causes|broken-reference causes]], below).
 ''(Marshall retested this and found that the EIP for a missing secondary weapon is actually 006F352E (see above). Not sure what is meant by "you just selected" as the IE will occur the instant the unit is created/promoted. Please can someone else confim that EIP 006F3481 is incorrect and remove this entry if so. Although, it begs the question of where this EIP came from? - it was added by DCoder on 2008-03-04 (id 14195))''
:I'm sorry, I made a mistake analyzing that one. I saw it at [http://www.cannis.net/forum/index.php?s=&showtopic=8560&view=findpost&p=170096 C-GEN] and analyzed it. But in fact it was caused by the ''ElitePrimary'' being wrong, not EliteSecondary. (Though 006F352E in your comment has "ElitePrimary" as the cause as well, I assume you meant 004D5108.) Just cause a certain EIP causes an IE, doesn't mean another EIP cannot cause an IE for the same reason - there are quite a lot of code paths in the game, and under certain circumstances the first EIP doesn't get hit. I just reanalyzed the function which both these EIPs fall under, and I can say this: 006F3481 IEs if (Elite)Secondary is broken, 006F352E - if (Elite)Primary is. The function is responsible for selecting which weapon a unit should use against a certain target in idle mode, the EIP you reported above for (Elite)Secondary (004D5108) is correct, but is only hit if the unit is in Guard mode scanning for targets when promotion happens. [maybe this part should go off to a talk page?] ''//[[User:DCoder|DCoder]]''
''(Just tested this a bit more and got several new EIPs for when the unit was promoted (added in this revision), can't seem to get any consistent results - will need to test this further. //Marshall''
|-
! {{Anchor|?|eip}}
| Setting {{f|CarryOverCap|0|link}}. Default value is -1, positive values do not cause an IE.
 ''I have tested this and couldn't get an IE to occur. Are there any specific circumstances that are required to trigger an IE on a map with CarryOverCap=0? Note that, in FA2YR, CarryOverCap defaults to zero so I would expect this IE to have been seen more often if it was really a problem. //Marshall''
: This setting applies when you progress from one campaign map to another. However, I now see that the default campaigns use 0, so there must be something else amiss. A quick investigation shows that this value is not divided by, so there shouldn't be an exception at all... Will contact Apollo who submitted this as the cause. ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|?|eip}}
| Warheads that are not listed under {{tt|[[Warheads|[Warheads]]]}} have been reported to cause an IE, although the exact details are not established. It is not neccessary for every warhead to be listed (for example, removing the Grand Cannon warhead from the list appears to have no effect on the game), however there is no reason not to list every warhead. '''Validity questionable - if someone can replicate this then please provide an except.txt.'''
''Simply thinking about this, putting warheads on the list should guarantee their position in the internal array, so if there is anywhere that references warheads by internal array position then this is important. However, even if you change an existing weapon's warhead to a non-parsed one in a game mode file, you ''still'' won't get an IE because default warhead values will be used. Because of this, I'm starting to wonder if the reports of un-listed warheads causing an IE are erroneous. If someone can replicate this then please provide an except.txt //Marshall''
: Verified under a debugger - if a weapon exists and links to a warhead that does not, this will not cause an IE, warhead stats will simply remain defaulted. (In other cases, warheads should also remain defaulted but functional. I have not verified every warhead loading location now, but my applicable ini flags tables should indicate whether or not uninited objects cause issues.) ''//[[User:DCoder|DCoder]] 12:44, 11 May 2008 (UTC)''
|-
! {{Anchor|?|eip}}
| If a falling paratrooper (who has nearly reached the ground) is killed by an area-effect mutation weapon. Point based mutations seem to be okay (the falling paratrooper explodes) and the [[Super weapon:Genetic Mutator|Genetic Mutator]] seems incapable of killing falling paratroopers. If you have an area-effect mutation weapon, you should ensure that all paratroopers are immune to it (this also means that you can't have a buildable paradrop plane and an area-effect mutation weapon in the same mod).
|-
! {{Anchor|00000000|eip}}
| Placing two buildings on a map in the map editor so that they overlap, and then destroying or garrisoning one of them in-game. Note that this error is intermittent so may not immediately be noticeable. Use [[FinalAlert]]'s {{tt|Options}} {{arr|r}} {{tt|Show Building Outline}} feature to see the actual areas taken up by buildings, since there are some buildings whose foundation is different from their visual size, and make sure you don't have any buildings that overlap.
Given the unusual EIP value (all zeroes) that has been gathered from testing, it may be a corrupt EIP and not a true indication of the source of the error. Note that this EIP has also been gathered from other 'random-EIP' causes.
:Indeed it is not a true indication, EIP 00000000 can be acquired in several ways. If you can provide an except, I will be able to provide more specific details to look for, like in the case of 0045EC90 . ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|004A2684|eip}}
| Starting a game on any map concludes in a "unable to read scenario" error while loading. The cause of this is an empty uimd.ini file or possibly another empty ini file without any content.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|007564BD|eip}}
| Internal error when starting a game, possibly caused by attempting to load graphics from a corrupt mix file.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|404E0000|eip}}
| Selectable=no on spawned [[AircraftTypes]].
''// [[User:Bbglas007|Bbglas007]]''

This error also occurs if there are overlapping structures and/or overlapping rubble on the map and units try to pathfind over them or one of the buildings is destroyed. Keep in mind that an existing building with Image=none (like for example a nuclear silo) still remains its Bib as it is read from art.ini. So if you give a [NUKE] Image=none it still remains its 3x3 Bib, which counts as an overlapping building. In general don't have overlapping buildings on your map.

''// [[User:DoctorEvil|DoctorEvil]]'' and ~ [[User:RAZER|RAZER]]
|-
! {{Anchor|006E2449|eip}}
| This error occurs when you fire a trigger action 42 (Do explosion at...) at an undefined waypoint.
''// [[User:DoctorEvil|DoctorEvil]]''
|}

===Broken-reference Causes===
*Most of the flags that point to an object type do not verify that the object type exists and will try to invoke it anyway. This includes pointers to weapons, projectiles, warheads, particles, particle systems and infantry/unit/aircraft/building types, among other things.
*All object types must be parsed in order for them to be invoked successfully. For example, a weapon must be parsed by being referenced by a unit in the main rules (weapons used in a game mode that aren't referenced in the main rules will not have been parsed, nor will shrapnel weapons that haven't been referenced by a dummy unit).
*Note that all weapons have to specify a {{f|Warhead|link}} tag and the tag must not be blank otherwise an IE will occur. However if the specified {{f|Warhead|link}} does not exist then that will not cause an IE, as the game will use default warhead settings.
*Your object type may not be 'missing' as such, you may just have mis-spelled its ID (e.g. "MagenticBeam" as opposed to "MagneticBeam"). Always check your typing carefully to make sure you don't  any words out.

===Tank Bunker / Sell Unit IEs===
*There are two IEs that can occur after using a 'Sell Unit' superweapon on a tank-bunkered unit. Both of these IEs can yield seemingly random EIP values (due to the fact that, when the unit is sold, the building's "BunkeredUnit" pointer isn't cleared and so points to garbage memory. Attempts to dereference it will be met with varying levels of failure).
*An IE may occur the instant you sell the unit.
*If an IE does not occur the instant you sell the unit, then the Tank Bunker will have been rendered unusable as the walls are still up. If the 'broken' Tank Bunker is sold or destroyed then an IE will occur (this IE ''does'' always happen). This IE frequently yields EIP 004593BB, although has been known to yield seemingly random EIP values (for the reason stated above).
*The only way to prevent these IEs is to make sure a player never has access to both the Sell Unit superweapon and the Tank Bunker at the same time. (To achieve this, the building that provides the superweapon must be uncapturable and immune to mind-control as must the Tank Bunker. Further more, unless both buildings are country specials, you will need to remove MCVs from crates and make Construction Yards uncapturable and immune to mind-control too.)

==Software used to find Internal Errors==
*[http://dc.strategy-x.com/checker INI Checker] (can check your rules, art and sound files for syntactic errors like typos and missing references)
*[[ExceptChecker]] (primarily for RockPatch-related IEs, it analyzes except.txt, tries to find references to code added by the patch or known routines, and ''might'' then be able give a direction)
*[[Debugger]] (if you know assembler)

==Note==
*After observing [[IE]] for several times, I found that ''' "EIP " ''' that occurs are expressed in categories such as unit errors, image errors, sound errors, configuration + settings errors, etc.

== See also ==
*[[Reconnection Error]]
*[http://forums.renegadeprojects.com/showthread.php?pid=2034#pid2034 Confirmation the Infantry Linking IE also applies to modifications done by maps]

[[Category:Bugs_and_Errors]]

Internal Error

2025-06-03T17:53:26Z

Askhati: Add TS EIP 006428C6

[[Image:Ts_ie.png|thumb|150px|right|Tiberian Sun's Internal Error]]
[[Image:Ra2_ie.png|thumb|150px|right|Red Alert 2's Internal Error]]
[[Image:Yr_ie.png|thumb|150px|right|Yuri Revenge's Internal Error]]
[[Image:Rp_ie.png|thumb|150px|right|RockPatch's Internal Error]]
The '''Internal Error''' (often just written short-hand as '''IE''') is a general error returned by the [[Tiberian Sun]] [[engine]] and its derivates. The message itself gives no information about what the error actually was or what went wrong, thus leaving it to the modder to know what could have caused the error and to find the cause in their mod's changes.

If you experience an Internal Error, you should:
# Check if the EIP reported in your except.txt file matches an EIP for which the IE cause is known (see below).
# Think about whether a distinctive event immediately preceeded the error (e.g. a unit being built, a weapon being fired, etc.). If this was the case then take a look at the changes you applied to that unit/weapon/whatever and see if there are any mistakes. 
# Carefully check your latest modifications, with the help of a diff between the current rules set and the previous, working rules if possible (for this reason, and in case you mess up your code beyond repair, you should always keep recent backups of working code).
Remember that the more code you add at the same time, the more likely it is to introduce multiple bugs and IE causes (and just because you found one mistake in your code, that doesn't mean there can't be another).

==Except.txt==
If your game crashes because of an Internal Error, a file named except.txt is generated in your game folder. This file is a dump of certain runtime-data from the game at the moment the error occurred and could potentially tell you exactly what went wrong ''if'' you knew the engine code. 
Due to his research into the game's binary and his efforts to develop the RockPatch, pd has occasionally been able to indicate the area of the engine where the error occurred (for example, an error occurring in the voxel-loading routines may indicate a problem with a custom voxel).
However, pd has other commitments and should not be treated as the go-to guy for any IEs you may have. Further more, pd may not neccessarily be able to help - without the source code or a comprehensive understanding of the game's binary the file is of little use. (cp. [[SYNCx.txt]])

According to an early version of [[Except.txt]] (which now redirects here), this file includes the full structure and a stack dump of a [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/context_str.asp CONTEXT] element.

IEs that share the same cause also share the same <tt>EIP:</tt> value in except.txt, so knowing that value might help you determine the cause of your IE (see the list of known IE causes (below) which also includes the corresponding EIP). However, it should be noted that some shared IE causes in INI code can yield one of several different EIP values (depending on the circumstance), and that some rare IE causes can actually yield totally random EIP values. As such, if you do have an unexplained IE, you should check all of the known causes.

== Known causes of Internal Errors and their EIPs ==
Since "Internal Error" is the game's response to almost any fatal error, its causes are diverse. Most common are causes related to weapons and warheads, with a missing warhead probably being the most commonly reported cause. Note that some IE causes may be prevented (or at least have certain limits extended (e.g. CellSpread)) by the [[RockPatch]], which in turn has opened up potential for new IE causes ([[RockPatch]]-specific IEs are not listed here).

=== Some useful tips ===
If an integer between {{Tt|0x00812000}} and {{Tt|0x00B78300}} appears in the stack, subtract {{Tt|0x00400000}} from it and look at the resulting address in {{Tt|gamemd.exe}} with a hex editor. If you find some INI flag, you can be almost sure this flag was the one being read when the problem happened and as such its values (or absence thereof) is the problem.


=== Specific game versions ===

==== Yuri's Revenge 1.001 ====

{{:Internal_Error/YR}}

==== Tiberian Sun 2.03 ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00415698|eip}}
| You used a [[TrailerAnim]] on an animation but forgot to set a [[TrailerSeperation]].
|-
! {{Anchor|0042A061|eip}}
| Wall=yes on a normal building.
|-
! {{Anchor|0043541C|eip}}
| Building turret animation has an invalid pointer to an [[AnimTypeClass]] when charging up. See Nod Obelisk of Light for example.
|-
! {{Anchor|00446E61|eip}} {{Anchor|00446F68|eip}}
| Airburst weapon bullet was null. If you have {{f|Airburst|yes|link}} or {{f|Splits|yes|link}} on a [[projectile]], you must also define {{f|AirburstWeapon|link}}.
|-
! {{Anchor|00451C16|eip}}
| {{f|CellAnim|link}} has invalid {{f|Image|link}}.
|-
! {{Anchor|0046C7E2|eip}}
| Fog of War was enabled and crashed the game.
|-
! {{Anchor|004BAEF8|eip}}
| [AI] BuildRefinery= -> one of your factions is missing an entry here, which will cause a crash when the AI tries to use this faction. Will not trigger a crash for human players.
|-
! {{Anchor|004BAF12|eip}}
| [General] HarvesterUnit -> one of the objects in this list is incorrect OR this list has exceeded 127 characters. Commonly triggered when adding new MCV and harvester object codes here when expanding the playable faction list in the TSC 6.00+ builds.
|-
! {{Anchor|004C1680|eip}}
| A house has no buildable {{f|HarvesterUnit|link}}. This crash is typically caused by a [[house]] with an incorrect {{f|ActsLike|link}} setting in a [[map]] when using [https://github.com/CnCNet/ts-patches/blob/9a6440cc921c0941da19e2b1691c45f8d701109d/src/buildconst_harvesterunit_baseunit.asm this patch]. In this case, {{f|ActsLike}} must always point to a house that owns at least one unit listed in {{f|HarvesterUnit}}. Also, make sure all houses listed in the map's {{tt|[Houses]}} list have a valid section. e.g. {{tt|[GDI]}}, defined in the map.
|-
! {{Anchor|004C445E|eip}}
| A unit's Secondary weapon doesn't exist. Check the spelling and cases.
|-
! {{Anchor|004C6428|eip}}
| AI does not have any buildings available for it to build. Check {{f|BuildConst|link}}=, {{f|BuildPower|link}}= etc.
|-
! {{Anchor|004CB997|eip}}
| [[TeamTypes|Team]]'s owner house is invalid. Check if there's a map trigger creating a team whose {{f|House|link}} is invalid or undefined (the house must be one of the houses listed in the map).
|-
! {{Anchor|004D2451|eip}}
| An infantry was about to take damage from a source with no valid [[Warhead]]= set.
|-
! {{Anchor|004D6626|eip}} {{Anchor|004D8BF3|eip}}
| Infantry with missing image in rules.ini (same as missing sequence in art.ini).
|-
!{{Anchor|004F886D|eip}}
| Trying to access colors in header while building radar image; related to the Radar High/Low Colors for terrain tiles.
|-
!{{Anchor|004F8EDD|eip}}
|The number of [[VehicleTypes]] in the [[BaseUnit]] section is incomplete.
|-
! {{Anchor|005A4814|eip}}
| Railgun with wrong particle keys.
|-
! {{Anchor|005A59B4|eip}}
| {{tt|[GasCloudSys]}} with a limited {{f|Lifetime|link}}. This system has hardcoded properties and must exist throughout the game, ergo you must set {{f|Lifetime|-1}} or leave it undefined (it defaults to -1).
|-
! {{Anchor|005A5A83|eip}}
| Invalid {{f|Image|link}} on an [[animation]] attempting to [[SpawnsParticle|spawn particles]] ([[Vinifera]] only). The image must be an existing [[shape]].
|-
! {{Anchor|005A5EB6|eip}}
| {{f|ParticleCap|1|link}} on a {{f|BehavesLike|Spark|link}} particle system.
|-
! {{Anchor|005A640F|eip}}
| {{f|NextParticle|link}} defined on a particle spawned by a {{f|BehavesLike|Smoke|link}} particle system.
|-
! {{Anchor|0062E6F6|eip}}
| It was attempted to use a normal colored house on a multiplayer map.
|-
! {{Anchor|006428C6|eip}}
| [[Trigger]] event had an invalid [[House]] parameter.
|-
! {{Anchor|00649563|eip}}
| A [[trigger]] failed to spring. Look for a trigger with invalid parameters, for example a misspelled or undefined [[house]].
|-
! {{Anchor|006703D4|eip}}
| WaveClass Sonic exception, normally triggered by a unit with a weapon that has IsSonic=yes set, firing to the south of the screen and the user scrolling up. No certain fix for this as we know, although [http://ppmsite.com/forum/viewtopic.php?t=31604 HyperPatch] has been confirmed to fix it at least on some systems. Another fix is disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll], although the fix doesn't work on Windows OS's newer than XP.
|-
! {{Anchor|0067159B|eip}}
| WaveClass Sonic exception. Not sure if this is code related, could be end user.
|-
! {{Anchor|006717CB|eip}}
| WaveClass laser exception. This can be fixed by setting DetailLevel= to 1 or 0 in SUN.ini. In addition, disabling DirectDraw hardware acceleration via either dxdiag or a [http://www.ppmsite.com/forum/viewtopic.php?t=19543 custom ddraw.dll] fixes it, but this fix only works on Windows operating systems older than Vista.
|-
! {{Anchor|0067159B|eip}}
| | You have set {{sl|AudioVisual|ShakeScreen}} to zero.
|-
! {{Anchor|00681363|eip}}
| Missing weedguy hack. (second stage Cluster weapons need to be assigned to a unit, to work)
|-
! {{Anchor|006A877A|eip}}
| LightSize>94 was set on a particlesystem.
|-
! {{Anchor|006B6AE6|eip}}
| Multiple reasons, depending on the stack dump in the except:
* If {{Tt|0066F44F}} appears near the top of the stack dump - A [[Warhead]] whose {{f|Verses|link}} could not be processed. {{Tt|EBP}} value says how many values remained to be parsed when an error occurred - (5 - {{Tt|EBP}}) is the 0-based index of the problematic value.
|-
! {{Anchor|006BB69C|eip}}
| conyard construction as building was canceled in the sidebar.
|-
! {{Anchor|90900004|eip}}
| Generic exception.
|}

==== Unverified / lacking information ====

{| cellpadding="4" border="1" class="table_descrowdesccol anchorcontainer"
! EIP
! Cause
|-
! {{Anchor|00494BCD|eip}}
| (Ares 3.0) A corrupted SHP image was drawn. Check mix files for any .shp files marked by XCC Mixer as 'unknown' under "type".
|-
|-
! {{Anchor|1118A7A5|eip}}
| Probably caused by trying to destroy a tag, but supplying the tag and not a trigger (FA2 offers Triggers, but I hand-typed a tag (among other things). Occams razor suggests this is the culprit.
|-
! {{Anchor|655B4A9C|eip}}
|(Ares 0.E) Setting a [ParticlePart] with 2 BehavesLike= simutaneously (for example , 'both Like=railgun' and 'Like=smoke' exist) may cause an EIP as above . Remove BehavesLike=railgun , and keep Like=smoke here in a [RailgunPart] to avoid this EIP and still gets a railgun with specific SHP-animation rail.
 ''(Two BehavesLike in Ares 0.D is still available , but 0.E not .)''
|-
! {{Anchor|?|eip}}
| Removing a building from the PrerequisitePower= list, while it exists in one of the (GDI/NODRegular/Third)PowerPlant= lists will cause an IE the moment any of your Power buildings get destroyed or sold as long as you own a Construction Yard. YR mods that remove Yuri's side from the game, should not remove YAPOWR from PrerequisitePower=.
 ''(Could not be reproduced thus far.)''
|-
! {{Anchor|?|eip}}
| Calling for an animation that is not listed under {{tt|[[Animations|[Animations]]]}} might trigger an IE.
 ''(That can be caused by multiple issues at various EIPs.)''
|-
! {{Anchor|?|eip}}
| Building a unit in-game whose VXL/SHP was inserted in an original game MIX instead of an expansion MIX.
 ''(Does this really happen? Sounds more like the mix editor crapping up than simply "game should blow up because you changed stock files".)''
 ''Further more, why would anyone eschew the normal method of ''expand''ing the game''. I don't see anyone testing/replicating this so I propose removing it from the list. //Marshall''
|-
! {{Anchor|006F3481|eip}}
| The (elite) secondary weapon (or its warhead) of the object you just selected could not be found (see [[#Broken-reference_Causes|broken-reference causes]], below).
 ''(Marshall retested this and found that the EIP for a missing secondary weapon is actually 006F352E (see above). Not sure what is meant by "you just selected" as the IE will occur the instant the unit is created/promoted. Please can someone else confim that EIP 006F3481 is incorrect and remove this entry if so. Although, it begs the question of where this EIP came from? - it was added by DCoder on 2008-03-04 (id 14195))''
:I'm sorry, I made a mistake analyzing that one. I saw it at [http://www.cannis.net/forum/index.php?s=&showtopic=8560&view=findpost&p=170096 C-GEN] and analyzed it. But in fact it was caused by the ''ElitePrimary'' being wrong, not EliteSecondary. (Though 006F352E in your comment has "ElitePrimary" as the cause as well, I assume you meant 004D5108.) Just cause a certain EIP causes an IE, doesn't mean another EIP cannot cause an IE for the same reason - there are quite a lot of code paths in the game, and under certain circumstances the first EIP doesn't get hit. I just reanalyzed the function which both these EIPs fall under, and I can say this: 006F3481 IEs if (Elite)Secondary is broken, 006F352E - if (Elite)Primary is. The function is responsible for selecting which weapon a unit should use against a certain target in idle mode, the EIP you reported above for (Elite)Secondary (004D5108) is correct, but is only hit if the unit is in Guard mode scanning for targets when promotion happens. [maybe this part should go off to a talk page?] ''//[[User:DCoder|DCoder]]''
''(Just tested this a bit more and got several new EIPs for when the unit was promoted (added in this revision), can't seem to get any consistent results - will need to test this further. //Marshall''
|-
! {{Anchor|?|eip}}
| Setting {{f|CarryOverCap|0|link}}. Default value is -1, positive values do not cause an IE.
 ''I have tested this and couldn't get an IE to occur. Are there any specific circumstances that are required to trigger an IE on a map with CarryOverCap=0? Note that, in FA2YR, CarryOverCap defaults to zero so I would expect this IE to have been seen more often if it was really a problem. //Marshall''
: This setting applies when you progress from one campaign map to another. However, I now see that the default campaigns use 0, so there must be something else amiss. A quick investigation shows that this value is not divided by, so there shouldn't be an exception at all... Will contact Apollo who submitted this as the cause. ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|?|eip}}
| Warheads that are not listed under {{tt|[[Warheads|[Warheads]]]}} have been reported to cause an IE, although the exact details are not established. It is not neccessary for every warhead to be listed (for example, removing the Grand Cannon warhead from the list appears to have no effect on the game), however there is no reason not to list every warhead. '''Validity questionable - if someone can replicate this then please provide an except.txt.'''
''Simply thinking about this, putting warheads on the list should guarantee their position in the internal array, so if there is anywhere that references warheads by internal array position then this is important. However, even if you change an existing weapon's warhead to a non-parsed one in a game mode file, you ''still'' won't get an IE because default warhead values will be used. Because of this, I'm starting to wonder if the reports of un-listed warheads causing an IE are erroneous. If someone can replicate this then please provide an except.txt //Marshall''
: Verified under a debugger - if a weapon exists and links to a warhead that does not, this will not cause an IE, warhead stats will simply remain defaulted. (In other cases, warheads should also remain defaulted but functional. I have not verified every warhead loading location now, but my applicable ini flags tables should indicate whether or not uninited objects cause issues.) ''//[[User:DCoder|DCoder]] 12:44, 11 May 2008 (UTC)''
|-
! {{Anchor|?|eip}}
| If a falling paratrooper (who has nearly reached the ground) is killed by an area-effect mutation weapon. Point based mutations seem to be okay (the falling paratrooper explodes) and the [[Super weapon:Genetic Mutator|Genetic Mutator]] seems incapable of killing falling paratroopers. If you have an area-effect mutation weapon, you should ensure that all paratroopers are immune to it (this also means that you can't have a buildable paradrop plane and an area-effect mutation weapon in the same mod).
|-
! {{Anchor|00000000|eip}}
| Placing two buildings on a map in the map editor so that they overlap, and then destroying or garrisoning one of them in-game. Note that this error is intermittent so may not immediately be noticeable. Use [[FinalAlert]]'s {{tt|Options}} {{arr|r}} {{tt|Show Building Outline}} feature to see the actual areas taken up by buildings, since there are some buildings whose foundation is different from their visual size, and make sure you don't have any buildings that overlap.
Given the unusual EIP value (all zeroes) that has been gathered from testing, it may be a corrupt EIP and not a true indication of the source of the error. Note that this EIP has also been gathered from other 'random-EIP' causes.
:Indeed it is not a true indication, EIP 00000000 can be acquired in several ways. If you can provide an except, I will be able to provide more specific details to look for, like in the case of 0045EC90 . ''//[[User:DCoder|DCoder]]''
|-
! {{Anchor|004A2684|eip}}
| Starting a game on any map concludes in a "unable to read scenario" error while loading. The cause of this is an empty uimd.ini file or possibly another empty ini file without any content.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|007564BD|eip}}
| Internal error when starting a game, possibly caused by attempting to load graphics from a corrupt mix file.
''//[[User:RaVaGe|RaVaGe]]''
|-
! {{Anchor|404E0000|eip}}
| Selectable=no on spawned [[AircraftTypes]].
''// [[User:Bbglas007|Bbglas007]]''

This error also occurs if there are overlapping structures and/or overlapping rubble on the map and units try to pathfind over them or one of the buildings is destroyed. Keep in mind that an existing building with Image=none (like for example a nuclear silo) still remains its Bib as it is read from art.ini. So if you give a [NUKE] Image=none it still remains its 3x3 Bib, which counts as an overlapping building. In general don't have overlapping buildings on your map.

''// [[User:DoctorEvil|DoctorEvil]]'' and ~ [[User:RAZER|RAZER]]
|-
! {{Anchor|006E2449|eip}}
| This error occurs when you fire a trigger action 42 (Do explosion at...) at an undefined waypoint.
''// [[User:DoctorEvil|DoctorEvil]]''
|}

===Broken-reference Causes===
*Most of the flags that point to an object type do not verify that the object type exists and will try to invoke it anyway. This includes pointers to weapons, projectiles, warheads, particles, particle systems and infantry/unit/aircraft/building types, among other things.
*All object types must be parsed in order for them to be invoked successfully. For example, a weapon must be parsed by being referenced by a unit in the main rules (weapons used in a game mode that aren't referenced in the main rules will not have been parsed, nor will shrapnel weapons that haven't been referenced by a dummy unit).
*Note that all weapons have to specify a {{f|Warhead|link}} tag and the tag must not be blank otherwise an IE will occur. However if the specified {{f|Warhead|link}} does not exist then that will not cause an IE, as the game will use default warhead settings.
*Your object type may not be 'missing' as such, you may just have mis-spelled its ID (e.g. "MagenticBeam" as opposed to "MagneticBeam"). Always check your typing carefully to make sure you don't  any words out.

===Tank Bunker / Sell Unit IEs===
*There are two IEs that can occur after using a 'Sell Unit' superweapon on a tank-bunkered unit. Both of these IEs can yield seemingly random EIP values (due to the fact that, when the unit is sold, the building's "BunkeredUnit" pointer isn't cleared and so points to garbage memory. Attempts to dereference it will be met with varying levels of failure).
*An IE may occur the instant you sell the unit.
*If an IE does not occur the instant you sell the unit, then the Tank Bunker will have been rendered unusable as the walls are still up. If the 'broken' Tank Bunker is sold or destroyed then an IE will occur (this IE ''does'' always happen). This IE frequently yields EIP 004593BB, although has been known to yield seemingly random EIP values (for the reason stated above).
*The only way to prevent these IEs is to make sure a player never has access to both the Sell Unit superweapon and the Tank Bunker at the same time. (To achieve this, the building that provides the superweapon must be uncapturable and immune to mind-control as must the Tank Bunker. Further more, unless both buildings are country specials, you will need to remove MCVs from crates and make Construction Yards uncapturable and immune to mind-control too.)

==Software used to find Internal Errors==
*[http://dc.strategy-x.com/checker INI Checker] (can check your rules, art and sound files for syntactic errors like typos and missing references)
*[[ExceptChecker]] (primarily for RockPatch-related IEs, it analyzes except.txt, tries to find references to code added by the patch or known routines, and ''might'' then be able give a direction)
*[[Debugger]] (if you know assembler)

==Note==
*After observing [[IE]] for several times, I found that ''' "EIP " ''' that occurs are expressed in categories such as unit errors, image errors, sound errors, configuration + settings errors, etc.

== See also ==
*[[Reconnection Error]]
*[http://forums.renegadeprojects.com/showthread.php?pid=2034#pid2034 Confirmation the Infantry Linking IE also applies to modifications done by maps]

[[Category:Bugs_and_Errors]]

Cloakable

2025-04-22T07:17:19Z

Askhati: Undo revision 28432 by AuY (talk) - this key does in fact work on buildings too (at least in TS).

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=boolean
|default=no
|types={{Categ|InfantryTypes}},{{Categ|VehicleTypes}},{{Categ|BuildingTypes}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
}}
Specifies whether this object has a cloaking device, which can render it invisible to enemy units without {{f|Sensors|yes|link}}, or [[BuildingTypes|buildings]] without {{f|SensorArray|yes|link}}. This effect also applies to the mini-map, which will only show the revealed (uncloaked) state of the unit.

==In {{ts}}==
Strangely, despite [[TechnoTypes]] lacking {{f|Sensors|yes|link}}, they can still automatically attack units that have <tt>Cloakable=yes</tt> within range, as if there was no cloaking effect.

Unlike in later games, TS (and [[Firestorm]]) support <tt>Cloakable</tt> and [[CloakingSpeed]] tags on buildings, without any problems.

==In {{ra2}}==
Earlier games did not have submarines, and so the cloaking effect only applied to terrestrial units, but in RA2 the cloaking system was repurposed for the Soviet Attack Sub. As such, the sound effects were updated to reflect their aquatic nature, with the splash effect defined by [[CloakSound]] under [AudioVisual], played for both cloaking and decloaking.

The {{f|CloakStop|yes|link}} tag was added to keep a unit like the Attack Sub cloaked when firing or in ambush position.

{{Bugs}}
In RA2, a fully cloaked unit (presumably submarine) might still reveal itself when retaliating (enabled by {{f|CanRetaliate|yes|link}}), or if the target of attack is sufficiently far away from it.

Explicitly set <tt>Cloakable=no</tt> will be overridden if a unit gains the abilities through [[Veterancy|promotion]].

[[SpeedType|Hovering]]/Flying units do not support <tt>Cloakable=yes</tt>, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.
* Ares has removed this hardcode, allowing the definition of the height for determining cloakable, and defaults it to the value of [[HoverHeight]] located under [General], used by hovering units. Therefore by default, just having Ares enables the logic for hovering units, and requires additional configuration to return to vanilla game behaviour.

Cloaked units will not trigger/activate [[Celltags]] on maps. This was an intentional design choice from Westwood, according to analysis of the engine code.

==See also==
[[CloakingStages]]

[[Sensors]]

[[SensorArray]]

[[RadarInvisible]]

EliteAbilities

2025-04-12T10:51:29Z

Askhati:

{{Flag
|name=EliteAbilities
|files={{Categ|Rules(md).ini}}
|values={{Values|stringlist|hardcoded values (see article)}}
|default=none
|types=All {{Categ|TechnoTypes}}: {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, and {{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This flag specifies a list of veterancy bonuses that this object gains when it reaches "Elite" stage. All possible values are hardcoded, and are listed at {{f|VeteranAbilities|link}}.

These values do not stack with {{f|VeteranAbilities|link}}; i.e. you do not get twice the damage reduction from having the {{tt|ARMOR}} statement in both lists.

[[Image:TS_VeteranAbilities_EliteAbilities_demo01.png|thumb|right]]
Abilities listed as {{f|EliteAbilities|link}} will be added in addition to what is listed as {{f|VeteranAbilities|link}} (subject to the no-doubling limit explained above). For example:
* VeteranAbilities=CLOAK
* EliteAbilities=SCATTER
This unit will thus gain CLOAK at Veteran stage, and SCATTER at Elite stage on top of the Veteran CLOAK bonus. Both bonus effects will thus apply in the end.

'''Note''': Contrary to what one might expect, the {{tt|FIREPOWER}} and {{tt|ROF}} bonuses are applied to the object's {{f|Elite|link}} weapon, if any.

== See Also ==
*{{f|VeteranAbilities|link}}

EliteAbilities

2025-04-12T10:50:49Z

Askhati:

{{Flag
|name=EliteAbilities
|files={{Categ|Rules(md).ini}}
|values={{Values|stringlist|hardcoded values (see article)}}
|default=none
|types=All {{Categ|TechnoTypes}}: {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, and {{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This flag specifies a list of veterancy bonuses that this object gains when it reaches "Elite" stage. All possible values are hardcoded, and are listed at {{f|VeteranAbilities|link}}.

These values do not stack with {{f|VeteranAbilities|link}}; i.e. you do not get twice the damage reduction from having the {{tt|ARMOR}} statement in both lists.

[[Image:TS_VeteranAbilities_EliteAbilities_demo01.png|thumb|right]]
Abilities listed as {{f|EliteAbilities|link}} will be added in addition to what is listed as {{f|VeteranAbilities|link}} (subject to the no-doubling limit explained above). For example:
* VeteranAbilities=CLOAK
* EliteAbilities=SCATTER
* This unit will thus gain CLOAK at Veteran stage, and SCATTER at Elite stage on top of the Veteran CLOAK bonus. Both bonus effects will thus apply in the end.

'''Note''': Contrary to what one might expect, the {{tt|FIREPOWER}} and {{tt|ROF}} bonuses are applied to the object's {{f|Elite|link}} weapon, if any.

== See Also ==
*{{f|VeteranAbilities|link}}

EliteAbilities

2025-04-12T10:46:06Z

Askhati:

{{Flag
|name=EliteAbilities
|files={{Categ|Rules(md).ini}}
|values={{Values|stringlist|hardcoded values (see article)}}
|default=none
|types=All {{Categ|TechnoTypes}}: {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, and {{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This flag specifies a list of veterancy bonuses that this object gains when it reaches "Elite" stage. All possible values are hardcoded, and are listed at {{f|VeteranAbilities|link}}.

These values do not stack with {{f|VeteranAbilities|link}}; i.e. you do not get twice the damage reduction from having the {{tt|ARMOR}} statement in both lists.

Abilities listed as {{f|EliteAbilities|link}} will be added in addition to what is listed as {{f|VeteranAbilities|link}} (subject to the no-doubling limit explained above). For example:
* VeteranAbilities=CLOAK
* EliteAbilities=SCATTER
* This unit will thus gain CLOAK at Veteran stage, and SCATTER at Elite stage on top of the Veteran CLOAK bonus. Both bonus effects will thus apply in the end.
<gallery>
TS_VeteranAbilities_EliteAbilities_demo01.png|Visual confirmation of the example above, from Tiberian Sun.
</gallery>

'''Note''': Contrary to what one might expect, the {{tt|FIREPOWER}} and {{tt|ROF}} bonuses are applied to the object's {{f|Elite|link}} weapon, if any.

== See Also ==
*{{f|VeteranAbilities|link}}

File:TS VeteranAbilities EliteAbilities demo01.png

2025-04-12T10:45:11Z

Askhati: An example from TS, where an unit has `VeteranAbilities=CLOAK` and `EliteAbilities=SCATTER`; it is clear to see here that the infantry gained Cloaking at Veteran stage (two bars), and then retained that Cloaking bonus when it reached Elite stage (star).

== Summary ==
An example from TS, where an unit has `VeteranAbilities=CLOAK` and `EliteAbilities=SCATTER`; it is clear to see here that the infantry gained Cloaking at Veteran stage (two bars), and then retained that Cloaking bonus when it reached Elite stage (star).

EliteAbilities

2025-04-12T10:30:41Z

Askhati: Added clarification on how EliteAbilities bonuses stack on top of VeteranAbilities bonuses.

{{Flag
|name=EliteAbilities
|files={{Categ|Rules(md).ini}}
|values={{Values|stringlist|hardcoded values (see article)}}
|default=none
|types=All {{Categ|TechnoTypes}}: {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, and {{Categ|BuildingTypes}}
|ts=yes
|fs=yes
|hp=yes
|ra2=yes
|yr=yes
|ares=yes
}}

This flag specifies a list of veterancy bonuses that this object gains when it reaches "Elite" stage. All possible values are hardcoded, and are listed at {{f|VeteranAbilities|link}}.

These values do not stack with {{f|VeteranAbilities|link}}; i.e. you do not get twice the damage reduction from having the {{tt|ARMOR}} statement in both lists.

Abilities listed as {{f|EliteAbilities|link}} will be added in addition to what is listed as {{f|VeteranAbilities|link}} (subject to the no-doubling limit explained above). For example:
* VeteranAbilities=CLOAK
* EliteAbilities=SCATTER
* This unit will thus gain CLOAK at Veteran stage, and SCATTER at Elite stage on top of the Veteran CLOAK bonus. Both bonus effects will thus apply in the end.

'''Note''': Contrary to what one might expect, the {{tt|FIREPOWER}} and {{tt|ROF}} bonuses are applied to the object's {{f|Elite|link}} weapon, if any.

== See Also ==
*{{f|VeteranAbilities|link}}

Useable Templates for contribution

2025-04-10T13:27:50Z

Askhati:

{{I}} To keep an unique look on every page and to keep the text structured and visualized, there are some templates available:
 
== Flag ==
{{Flag
|files={{Categ|ini=rules}}
|values={{Values|Boolean}}
|default=0
|types={{Categ|BuildingTypes}}
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}

 Code:<pre>
{{Flag
|files={{Categ|ini=rules}}
|values={{Values|Boolean}}
|default=0
|types={{Categ|BuildingTypes}}
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
</pre>
 
This should be used on every Flag on top of the article.
Set games which aren't using that flag to no.
Example: [[IsJuggernaut|IsJuggernaut]]
 
=== Guideheader ===
{{Guideheader
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
 
<pre>{{Guideheader
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}</pre>
For any kinds of tutorials to visualize for which game the guide/tutorial is for.
Example: [[How_to_add_Repair_ring_System|How_to_add_Repair_ring_System]]

===HoriontalBar===
{{HorizontalBar|[[Image:Cc_documentinfo.png‎|24px]] This is a text}}
<pre>{{HorizontalBar|[[Image:Cc_documentinfo.png‎|24px]] This is a text}}</pre>

Image can be replaced with any picture from [[Special:ListFiles]].Pictures with CC at the beginning are recommended for this Template.
24px says, the picture will be shown with a width of 24 pixels.

===BigHorizontalBar===
{{BigHorizontalBar|THIS IS A HEADLINE|Tiberian Sun is the best game in the World}}
<pre>{{BigHorizontalBar|HEADLINE|TEXT}}</pre>

===RedHorizontalBar===
{{RedHorizontalBar|THIS IS A HEADLINE|Tiberian Sun is the best game in the World}}
<pre>{{RedHorizontalBar|HEADLINE|TEXT}}</pre>

===WrongTitle===
{{WrongTitle|[{{PAGENAME}}]}}
<pre>{{WrongTitle|[{{PAGENAME}}]}}</pre>
Example: [[VehicleTypes|VehicleTypes]]

===I===
{{I}}
<pre>{{I}}</pre>

===Arr===
{{Arr|u}} {{Arr|d}} {{Arr|l}} {{Arr|r}}
<pre>{{Arr|x}}
replace x with
u - arrow up
d - arrow down
l - arrow left
r - arrow right</pre>

===NeedsTesting===
{{NeedsTesting}}
<pre>{{NeedsTesting}}
{{NeedsTesting|New Text is also possible}}</pre>

===Strike===
{{Strike|text}}
<pre>{{Strike|text}}</pre>

===Content style consistency===
* When listing multiple items, use proper list formatting: * (asterisk) in front of each list item.
* Sentences should end with a full-stop.
* When quoting text, use single quotes instead of double quotes - e.g. `this phrase' instead of "this phrase".
* When listing two alternates A or B, the following conventions apply:
** if A and B are single words, then 'A/B' (no spaces) - e.g. this/that.
** if A and/or B consist of multiple words, then 'A / B' (spaces before and after slash) - e.g. Global Defense Initiative / Brotherhood of Nod.
** If A and/or B are URL links, use the same 'A / B' convention above to make it more obvious that one or more links are present.

Useable Templates for contribution

2025-04-10T13:16:08Z

Askhati:

{{I}} To keep an unique look on every page and to keep the text structured and visualized, there are some templates available:
 
== Flag ==
{{Flag
|files={{Categ|ini=rules}}
|values={{Values|Boolean}}
|default=0
|types={{Categ|BuildingTypes}}
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}

 Code:<pre>
{{Flag
|files={{Categ|ini=rules}}
|values={{Values|Boolean}}
|default=0
|types={{Categ|BuildingTypes}}
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
</pre>
 
This should be used on every Flag on top of the article.
Set games which aren't using that flag to no.
Example: [[IsJuggernaut|IsJuggernaut]]
 
=== Guideheader ===
{{Guideheader
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}
 
<pre>{{Guideheader
|td=yes
|ra=yes
|ts=yes
|fs=yes
|ra2=yes
|yr=yes
}}</pre>
For any kinds of tutorials to visualize for which game the guide/tutorial is for.
Example: [[How_to_add_Repair_ring_System|How_to_add_Repair_ring_System]]

===HoriontalBar===
{{HorizontalBar|[[Image:Cc_documentinfo.png‎|24px]] This is a text}}
<pre>{{HorizontalBar|[[Image:Cc_documentinfo.png‎|24px]] This is a text}}</pre>

Image can be replaced with any picture from [[Special:ListFiles]].Pictures with CC at the beginning are recommended for this Template.
24px says, the picture will be shown with a width of 24 pixels.

===BigHorizontalBar===
{{BigHorizontalBar|THIS IS A HEADLINE|Tiberian Sun is the best game in the World}}
<pre>{{BigHorizontalBar|HEADLINE|TEXT}}</pre>

===RedHorizontalBar===
{{RedHorizontalBar|THIS IS A HEADLINE|Tiberian Sun is the best game in the World}}
<pre>{{RedHorizontalBar|HEADLINE|TEXT}}</pre>

===WrongTitle===
{{WrongTitle|[{{PAGENAME}}]}}
<pre>{{WrongTitle|[{{PAGENAME}}]}}</pre>
Example: [[VehicleTypes|VehicleTypes]]

===I===
{{I}}
<pre>{{I}}</pre>

===Arr===
{{Arr|u}} {{Arr|d}} {{Arr|l}} {{Arr|r}}
<pre>{{Arr|x}}
replace x with
u - arrow up
d - arrow down
l - arrow left
r - arrow right</pre>

===NeedsTesting===
{{NeedsTesting}}
<pre>{{NeedsTesting}}
{{NeedsTesting|New Text is also possible}}</pre>

===Strike===
{{Strike|text}}
<pre>{{Strike|text}}</pre>

===Content style consistency===
* When listing multiple items, use proper list formatting: * (asterisk) in front of each list item

* When listing two alternates A or B, the following conventions apply:
** if A and B are single words, then "A/B" (no spaces) - e.g. this/that
** if A and/or B consist of multiple words, then "A / B" (spaces before and after slash) - e.g. Global Defense Initiative / Brotherhood of Nod

Cloakable

2025-04-10T12:54:28Z

Askhati:

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values=boolean
|default=no
|types={{Categ|InfantryTypes}},{{Categ|VehicleTypes}},{{Categ|BuildingTypes}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
}}
Specifies whether this object has a cloaking device, which can render it invisible to enemy units without {{f|Sensors|yes|link}}, or [[BuildingTypes|buildings]] without {{f|SensorArray|yes|link}}. This effect also applies to the mini-map, which will only show the revealed (uncloaked) state of the unit.

==In {{ts}}==
Strangely, despite [[TechnoTypes]] lacking {{f|Sensors|yes|link}}, they can still automatically attack units that have Cloakable=yes within range, as if there was no cloaking effect.

Unlike in later games, TS (and [[Firestorm]]) support Cloakable and [[CloakingSpeed]] tags on buildings, without any problems.

==In {{ra2}}==
Earlier games did not have submarines, and so the cloaking effect only applied to terrestrial units, but in RA2 the cloaking system was repurposed for the Soviet Attack Sub. As such, the sound effects were updated to reflect their aquatic nature, with the splash effect defined by [[CloakSound]] under [AudioVisual], played for both cloaking and decloaking.

The {{f|CloakStop|yes|link}} tag was added to keep a unit like the Attack Sub cloaked when firing or in ambush position.

{{Bugs}}
* In RA2, a fully cloaked unit (presumably submarine) might still reveal itself when retaliating (enabled by {{f|CanRetaliate|yes|link}}), or if the target of attack is sufficiently far away from it.

* Explicitly set Cloakable=no will be overridden if a unit gains the abilities through [[Veterancy|promotion]].

* [[SpeedType|Hovering]]/Flying units do not support Cloakable=yes, however granting them cloakability via [[VeteranAbilities]] or [[EliteAbilities]] is possible.
** Ares has removed this hardcode, allowing the definition of the height for determining cloakable, and defaults it to the value of [[HoverHeight]] located under [General], used by hovering units. Therefore by default, just having Ares enables the logic for hovering units, and requires additional configuration to return to vanilla game behaviour.

* Cloaked units will not trigger / activate celltags on maps. This was an intentional design choice from Westwood, as per analysis of the engine code (per Rampastring work).

==See also==
[[CloakingStages]]

[[Sensors]]

[[SensorArray]]

[[RadarInvisible]]

ModEnc²:Community Portal

2025-04-06T22:07:20Z

Askhati:

This page provides links to pages in the community; feel free to add your link to the bottom of the appropriate list. <s>(Remember that this works on a ''first-come-first-served'' basis. Add your link to the ''bottom'' of the list.)</s>
 Update 2025: try to keep the listings alphabetically descending A-Z where possible.

=== Mods - Tiberian Sun / Firestorm ===
Last update: 2025.04.07
* [https://www.moddb.com/mods/tiberian-sun-aftermath/ Aftermath]
* [https://www.moddb.com/mods/the-dawn-of-the-tiberium-age/ Dawn of the Tiberium Age]
* [https://www.moddb.com/mods/fading-dusk/ Fading Dusk]
* [https://www.moddb.com/mods/tiberian-sun-rubicon/ Rubicon]
* [https://www.moddb.com/mods/cc-tiberian-odyssey/ Tiberian Odyssey]
* [https://www.moddb.com/mods/twisted-insurrection/ Twisted Insurrection]

=== Mods - Red Alert 2 / Yuri's Revenge ===
* [http://mo.cncguild.net/ Mental Omega]
* [http://exile.freedomstudios.net/ragen YR: Zero Hour]
* [http://thirdwar.cncguild.net/ The Third War]
* [http://dday.migeater.net/ D-day]

=== Mods - Legacy/ Dead ===
* [http://www.deezire.net/ DeeZire] - The site is dead. Mod is available on [http://commandandconquer.filefront.com/file/RA2_Deezire;34109 FileFront].
* {{co|CannisRules: Balance of Power|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://www.lusitaniaonline.net/cgm/ Mirror 1] and [http://dc.strategy-x.com/mirrors/cgen/ mirror 2].
* {{co|MooMan's Rules/YR²|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://forums.revora.net/index.php?showtopic=59447 Mirror].
* [http://marshall.cannis.net/ump YR Unofficial 1.002 Mini-Patch] - Original site is dead. Available through [[LaunchBase]].
* {{co|AR2 (formerly Allies Revenge 2)|red}} - The site is dead.
* [http://marshall.strategy-x.com/purple Purple Alert] - The site is dead.
* {{co|Terrain Expansion project for Yuri's Revenge|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://www.lusitaniaonline.net/cgm/ Mirror 1] and [http://dc.strategy-x.com/mirrors/cgen/ mirror 2]. Also available through [[LaunchBase]].
* [http://exile.freedomstudios.net/cnc-exile C&C Exile] - Freedom Studios is gone.
* {{co|The Project|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. An older version of this mod is mirrored on the [http://web.archive.org/web/20071109084207/http://project.cannis.net/files/projectbeta60.exe Wayback Machine]
* [http://wbr.strategy-x.com/ Whiteboy's Rules] - Site is dead.
* {{co|Retaliation|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. This has not been mirrored.
* [http://takt.sytes.net/ Taktics (The Awakened Kingdom - The Initial Chaotic Strike)] - The site is dead.

=== Tutorials/[[Tools]] ===
* [http://dc.strategy-x.com/ DCoder's RedUtils]
* [http://www.ppmsite.com/ Project Perfect Mod]
* [http://marshall.strategy-x.com/yrpm YR Playlist Manager]
* {{co|RA2YR Clean Up|red}} - Superseded by [[LaunchBase]].
* [http://xhp.xwis.net/ XCC Utilities]
* [http://exile.freedomstudios.net/ RA2 Awesome] - Freedom Studios is gone.
* [http://finalsun.wagnerma.de/ Final Alert map editor]
* {{co|Kravvitz' FAQ Page|red}} - SavageWar, the site hosting these, is '''dead'''.
* [http://ares.strategy-x.com/ Ares]
* [http://rtb.creativegaming.net/ RockPatch Inofficial Homepage] - Domain for sale.
* [http://marshall.strategy-x.com/LaunchBase YR Launch Base]

=== General Sites ===
* [http://www.cncgames.com/ RADEN] - now leads to the abyss. Do '''not''' click this link.
* [http://www.cncden.com/ CNCDEN] - Domain for sale.
* [http://planetcnc.gamespy.com/ Planet CnC] - Makes you download an INI file.
* [http://commandandconquer.filefront.com/ CnC Files] - no longer functional.
* [http://www.sleipnirstuff.com/ Sleipnir's Stuff] - got nuked to oblivion; assets, threads, everything.
* [http://www.tiberiumweb.com/ TiberiumWeb] - Domain for sale, and https://www.tiberiumweb.net/ gets IPS Driver Error when accessing anything.
* [http://yrarg.cncguild.net/ YR Argentina] - no longer updated, and some assets were lost.

=== Networks ===
* {{co|Cannis Games Editing Network|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''.
* [http://www.ppmsite.com/ Project Perfect Mod]
* [http://www.revora.net/ Revora]
* [http://www.cncguild.net CNC Guild]
* [http://www.ra2diy.com RA2DIY Forum(China)]
* [https://modenc.renegadeprojects.com/Main_Page ModEnc] - ModEnc's old site, established by Renegade. Our '''shattered''' homeland

User talk:Askhati

2025-04-05T18:02:16Z

Askhati:

Let's see how long we survive this time...
- askhati 2025.04.01

== I wanna test this here to be a real WikiMedia Admin ==

Hello Askhati.
How are you? How is the weather in Netherland?

Greetings,
Mark

== Why are you like this ==
- askhati 2025.04.05

User talk:DeathFish

2025-04-04T15:10:34Z

Askhati: Created page with "Cheers for all the cleaning-up work today with the pages marked for deletion. - Askhati, 2025.04.04"

Cheers for all the cleaning-up work today with the pages marked for deletion. 
- [[User:Askhati|Askhati]], 2025.04.04

ModEnc² talk:Community Portal

2025-04-02T16:21:30Z

Askhati: Created page with "Started with a first sweep to update the Mod list. More additions welcome. It would be great if we could implement a version control/ current development status too, per mod. That way our readers can see which mods are done, or in-progress, or abandoned. - askhati 2025.04.02"

Started with a first sweep to update the Mod list. More additions welcome. 

It would be great if we could implement a version control/ current development status too, per mod. That way our readers can see which mods are done, or in-progress, or abandoned. 

- askhati 2025.04.02

ModEnc²:Community Portal

2025-04-02T16:19:10Z

Askhati: Reordered Mod list to split by game type versions (TS/FS, RA2/YR, Legacy/Dead)

This page provides links to pages in the community; feel free to add your link to the bottom of the appropriate list. (Remember that this works on a ''first-come-first-served'' basis. Add your link to the ''bottom'' of the list.)

=== Mods - Tiberian Sun / Firestorm ===
* [https://www.moddb.com/mods/tiberian-sun-aftermath/ Aftermath]
* [https://www.moddb.com/mods/the-dawn-of-the-tiberium-age/ Dawn of the Tiberium Age]
* [https://www.moddb.com/mods/fading-dusk/ Fading Dusk] - currently open Beta
* [https://www.moddb.com/mods/tiberian-sun-rubicon/ Rubicon]
* [https://www.moddb.com/mods/twisted-insurrection/ Twisted Insurrection]

=== Mods - Red Alert 2 / Yuri's Revenge ===
* [http://mo.cncguild.net/ Mental Omega]
* [http://exile.freedomstudios.net/ragen YR: Zero Hour]
* [http://thirdwar.cncguild.net/ The Third War]
* [http://dday.migeater.net/ D-day]

=== Mods - Legacy/ Dead ===
* [http://www.deezire.net/ DeeZire] - The site is dead. Mod is available on [http://commandandconquer.filefront.com/file/RA2_Deezire;34109 FileFront].
* {{co|CannisRules: Balance of Power|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://www.lusitaniaonline.net/cgm/ Mirror 1] and [http://dc.strategy-x.com/mirrors/cgen/ mirror 2].
* {{co|MooMan's Rules/YR²|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://forums.revora.net/index.php?showtopic=59447 Mirror].
* [http://marshall.cannis.net/ump YR Unofficial 1.002 Mini-Patch] - Original site is dead. Available through [[LaunchBase]].
* {{co|AR2 (formerly Allies Revenge 2)|red}} - The site is dead.
* [http://marshall.strategy-x.com/purple Purple Alert] - The site is dead.
* {{co|Terrain Expansion project for Yuri's Revenge|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. [http://www.lusitaniaonline.net/cgm/ Mirror 1] and [http://dc.strategy-x.com/mirrors/cgen/ mirror 2]. Also available through [[LaunchBase]].
* [http://exile.freedomstudios.net/cnc-exile C&C Exile] - Freedom Studios is gone.
* {{co|The Project|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. An older version of this mod is mirrored on the [http://web.archive.org/web/20071109084207/http://project.cannis.net/files/projectbeta60.exe Wayback Machine]
* [http://wbr.strategy-x.com/ Whiteboy's Rules] - Site is dead.
* {{co|Retaliation|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''. This has not been mirrored.
* [http://takt.sytes.net/ Taktics (The Awakened Kingdom - The Initial Chaotic Strike)] - The site is dead.

=== Tutorials/[[Tools]] ===
* [http://dc.strategy-x.com/ DCoder's RedUtils]
* [http://www.ppmsite.com/ Project Perfect Mod]
* [http://marshall.strategy-x.com/yrpm YR Playlist Manager]
* {{co|RA2YR Clean Up|red}} - Superseded by [[LaunchBase]].
* [http://xhp.xwis.net/ XCC Utilities]
* [http://exile.freedomstudios.net/ RA2 Awesome] - Freedom Studios is gone.
* [http://finalsun.wagnerma.de/ Final Alert map editor]
* {{co|Kravvitz' FAQ Page|red}} - SavageWar, the site hosting these, is '''dead'''.
* [http://ares.strategy-x.com/ Ares]
* [http://rtb.creativegaming.net/ RockPatch Inofficial Homepage] - Domain for sale.
* [http://marshall.strategy-x.com/LaunchBase YR Launch Base]

=== General Sites ===
* [http://www.cncgames.com/ RADEN] - now leads to the abyss. Do '''not''' click this link.
* [http://www.cncden.com/ CNCDEN] - Domain for sale.
* [http://planetcnc.gamespy.com/ Planet CnC] - Makes you download an INI file.
* [http://commandandconquer.filefront.com/ CnC Files] - no longer functional.
* [http://www.sleipnirstuff.com/ Sleipnir's Stuff] - got nuked to oblivion; assets, threads, everything.
* [http://www.tiberiumweb.com/ TiberiumWeb] - Domain for sale, and https://www.tiberiumweb.net/ gets IPS Driver Error when accessing anything.
* [http://yrarg.cncguild.net/ YR Argentina] - no longer updated, and some assets were lost.

=== Networks ===
* {{co|Cannis Games Editing Network|red}} - Cannis' site is '''[http://forums.renegadeprojects.com/showthread.php?tid=1183 dead]'''.
* [http://www.ppmsite.com/ Project Perfect Mod]
* [http://www.revora.net/ Revora]
* [http://www.cncguild.net CNC Guild]
* [http://www.ra2diy.com RA2DIY Forum(China)]
* [https://modenc.renegadeprojects.com/Main_Page ModEnc] - ModEnc's old site, established by Renegade. Our '''shattered''' homeland

User:Askhati

2025-04-01T20:25:58Z

Askhati:

Modding TS since about 2001. 
One of the devs of the 'Fading Dusk' mod. 
Old-school voxel artist.

User talk:Askhati

2025-04-01T20:24:44Z

Askhati:

Let's see how long we survive this time...
- askhati 2025.04.01

User:Askhati

2025-04-01T20:23:43Z

Askhati:

Modding TS since about 2001.
One of the devs of the 'Fading Dusk' mod.
Old-school voxel artist.