PROJ TNUM: Difference between revisions
Jump to navigation
Jump to search
Rasmusthorup (talk | contribs) No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''defineprojectile''' <tilenum> '''PROJ_TNUM''' <trail 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 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. | ||
Revision as of 06:17, 21 February 2020
defineprojectile <tilenum> PROJ_TNUM <trail 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.