PROJ TNUM: Difference between revisions
Jump to navigation
Jump to search
Hendricks266 (talk | contribs) m Added category. |
Rasmusthorup (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
The maximum number of trails that an individual projectile can spawn. By default, RPG (non-hitscan) type projectiles will spawn trails even if TNUM is not set. But bullet type (hitscan) projectiles will not spawn any trails unless TNUM is given a non-zero value. | The maximum number of trails that an individual projectile can spawn. By default, RPG (non-hitscan) type projectiles will spawn trails even if TNUM is not set. But bullet type (hitscan) projectiles will not spawn any trails unless TNUM is given a non-zero value. | ||
The way it works, is that if TNUM value is set to 2, then it will spawn 2 of the sprites on the same location. The default value is 1 if a trail is set for the projectile. | |||
[[Category:Projectile_structure_members]] | [[Category:Projectile_structure_members]] | ||
Revision as of 09:30, 2 April 2011
defineprojectile <tile number> PROJ_TNUM <number>
The maximum number of trails that an individual projectile can spawn. By default, RPG (non-hitscan) type projectiles will spawn trails even if TNUM is not set. But bullet type (hitscan) projectiles will not spawn any trails unless TNUM is given a non-zero value.
The way it works, is that if TNUM value is set to 2, then it will spawn 2 of the sprites on the same location. The default value is 1 if a trail is set for the projectile.