Eternity Wiki - User contributions [en]

Polyobject

2026-04-23T17:24:40Z

Printz: /* Creating PolyObjects */

PolyObjects are special sets of one-sided linedefs which, unlike any other lines, can be moved on the map during gameplay. Unlike the Hexen implementation of PolyObjects, Eternity does not restrict these objects to one per subsector, and they are also allowed to move any distance from their spawn point, even across subsector boundaries.

PolyObjects fully clip normal objects such as the player and enemies, optionally doing crushing damage depending upon the type of spawn spot used. They also block bullet tracers and monsters' lines of sight. They do not, however, clip sound propagation, so it may be necessary to use sound blocking lines near areas where PolyObjects are meant to function as a normal wall until they move.

Although Eternity does allow PolyObjects to move between different subsectors, this will only work properly if the subsectors on both sides of a line have the same properties (floor & ceiling heights, light level, and flat). However, since the implementation of [[dynaseg]]s, Eternity does not require a "PolyObject-aware" node builder.

Finally, Eternity allows PolyObjects to be used in DOOM-format maps via the use of [[ExtraData]]. See the subsections below for more information on how to create and move PolyObjects.

{{Backto|Linedef types}}

==Creating PolyObjects==

PolyObjects are a combination of a set of lines, which are typically placed in a "control sector" area outside of the main map, and exactly two mapthings: one spawn spot, and one anchor point. There are two different methods for grouping lines into a PolyObject.

The lines are typically one-sided walls, but two-sided line polyobjects are also possible.

==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===

:The <code>348:Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> special marks the first line in a PolyObject which is made up of a cyclic set of linedefs (that is, each line "points toward" the next line, ending at the first vertex of the first line).

:Diagrammatic Example:
:[[File:Polyobjects_basic.png]]
:Assume that the linedef '''A''' is assigned the <code>Polyobj_StartLine</code> special and has argument #1 set to "1" -- this is its '''PolyObject ID number''', which must be unique amongst all on the map, and must be a number greater than zero.

:Starting from line '''A''', the engine will go from vertex to vertex, adding the first line found which shares the current line's second vertex as its first vertex. In this example, since the object is closed as is required, the process will end at the first vertex of line '''A''', and there will be four lines in the PolyObject (note that unlike Hexen, there is NO limit to the number of lines that can be placed in one PolyObject).

:Now, once the lines are added, it is necessary to define the control objects. Points '''B''' and '''C''' are the two required objects:
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the StartLine's first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the StartLine's first argument and the anchor point's angle field. There must be one and only one of these objects for each PolyObject ID. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:Note that when you use this method, the other lines belonging to the PolyObject can be given their own line specials, including ones which affect the PolyObject itself. When the player presses the PolyObject, the specials will work as expected.

:The complete arguments to <code>Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use [[ExtraData]]. In that case, you must give the line you want to have the Polyobj_StartLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_StartLine and its arguments in its corresponding ExtraData linedef record.

==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===

:The <code>349:Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> special demarcates every line that will be added to a PolyObject and the exact order in which the lines will be added. This affords a bit more flexibility in the construction of PolyObjects at the price of not allowing any other line specials to be placed on the object itself.

:Diagrammatic Example:
:[[File:Polyobjects_adv.png]]
:Assume that the linedefs labeled 1 through 4 are assigned (via [[ExtraData]]) the <code>Polyobj_ExplicitLine</code> special, all have argument '''#1''' set to "1" -- this is its PolyObject ID number (which must be unique amongst all on the map, and must be a number greater than zero), and argument '''#2''' set also to whatever their tag is (in this case again it's ''1'').

:The game engine will search through all linedefs in the entire map for ones with the current '''PolyObject ID''' in argument '''#1''' and a value greater than zero in argument '''#2'''. The lines will be collected and then sorted by the '''LineDef id'''.

:Now, once the lines are added, it is necessary to define the control objects. This is exactly the same as it is for the <code>StartLine(...)</code> special above.
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the <code>ExplicitLines'</code> first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the ExplicitLines' first argument and the anchor point's angle field. There must be one and only one of these objects for each '''PolyObject ID'''. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:The complete arguments to <code>Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''index'' : specifies the order in which the line will be added to the PolyObject. This number should be unique amongst all lines to be added to the same object, and must be a value greater than zero.
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use ExtraData. In that case, you can either give the lines you want to have the Polyobj_ExplicitLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_ExplicitLine and its arguments in all the corresponding ExtraData linedef records; or simply use the line special normally, and specify the ExtraData record number in the linedef's tag, specifying only the arguments inside the ExtraData record.

===Note===
As of EE 3.37.00, thing type 9303 is available, which is similar to the ZDoom damaging polyobject type.

==Moving PolyObjects==

There are two types of basic motion which PolyObjects can currently undergo: translation and rotation. Using "override" actions, it is possible to combine the two to have a PolyObject which rotates while moving in the xy plane.

[[File:Polyobject_rotating.gif]]

===Translating PolyObjects===

To move a PolyObject in the xy plane, use one of the following line specials:
* <code>Polyobj_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>
* <code>Polyobj_OR_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>

Both of these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to intially move. If the object is already moving, nothing will happen unless the action is Polyobj_OR_Move. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the angle of movement for each subsequent mirror.
* ''speed'' : Speed of the motion in eighths of a unit per tic.
* ''angle'' : Byte angle specifying the direction of motion. To convert from degrees to byte angles, use this formula: byteangle = (degrees * 256) / 360. Round or chop the result to an integer. 0 means East, 64 means North, 128 means West, and 192 means South.
* ''dist'' : The total distance to move the object in units.

All PolyObjects will inflict thrust on objects which block them with force proportional to the speed of motion. If the PolyObject was spawned with the EEPolyObjSpawnSpotCrush object (DoomEd num 9302), then if the object does not fit at the location it is being pushed toward, it will be damaged 3 hitpoints per tic (105 damage per second).

===Rotating PolyObjects===

To rotate a PolyObject, use one of the following line specials:
* <code>Polyobj_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>

All these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to initially rotate. If the object is already moving, nothing will happen unless the action is Polyobj_OR_RotateRight or Polyobj_OR_RotateLeft. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the direction of rotation for each subsequent mirror.
* ''aspeed'' : Angular speed of the rotation in byte angles per tic. Same as for the "angle" parameter to Move actions.
* ''adist'' : Angular distance to rotate in byte angles. Same as for aspeed, except with two special caveats:

The byte angle value 0 (zero) means to rotate exactly 360 degrees.

The byte angle value 255 means to rotate perpetually. This type of action never ends and thus only override actions can subsequently be applied to the PolyObject.

===PolyObject Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects.wad PolyObject Demo]====
A demonstration of both rotating and translating PolyObjects. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments. For example this script explains how LineDefs are configured for a manually operated rotating PolyObject:

<pre>
//===============================
//= MANUALLY ROTATING POLYOBJECT
//=============================

// This PolyObject doesn't move unless activated by a a nearby switch.
linedef {
recordnum = 2
special = PolyObj_StartLine
args = { 2 }
}

linedef {
recordnum = 3
extflags = "use player" // Defines how the LineDef action is activated.
// The lack of "repeat" flag means it's a one-time
// action.

special = Polyobj_RotateRight
args = { 2, 2, 255 } // Starts Rotating PolyObject with PolyID: 2
// at a speed of 2 units and angular distance
// of 255 units - which means it'll rotate
// continuously.
} (...)
</pre>

====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects_adv.wad PolyObject Advanced Demo]====
A demonstration of rotating and translating PolyObjects made with <code>PolyObj_ExplicitLine()</code> Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]). It shows how more advanced PolyObjects can be constructed and moved to fake 3D objects. It also includes PolyObject Doors discussed in the next section of this article.

It is recommended that you play go through the first Demo in the series and open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments.

==PolyObject Doors==
There are two distinct types of actions provided to allow PolyObjects to function as doors: swinging and sliding. There are no override versions of door actions, and applying other overrides to currently moving PolyObject doors will most likely cause the doors to malfunction and move erratically.

All PolyObject doors accept a delay parameter, and this specifies the amount of time the door will wait before closing. A door which is closing will reopen if blocked by an object.

===Swinging PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_swingdoor_schema.png|200px]] || [[Image:Poly_swigning_door.gif]]
|-
| PolyObject swinging door schema || PolyObject swinging door
|}

<code>Polyobj_DoorSwing ('''polyobj_id''', '''aspeed''', '''adist''', '''delay''')</code>

This action creates a swinging door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''aspeed'' : Angular speed in byte angles per tic.
:* ''adist'' : Angular distance to rotate when opening, and again but in the opposite direction when closing.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.
Swinging doors currently only rotate left. A right-rotating swinging door special will be added in the near future.

===Sliding PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_slidedoor_schema.png|200px]] || [[Image:Poly_sliding_door.gif|180px]]
|-
| PolyObject sliding door schema || PolyObject sliding door
|}

<code>Polyobj_DoorSlide ('''polyobj_id''', '''speed''', '''angle''', '''dist''', '''delay''')</code>

:This action creates a sliding door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''speed'' : Speed of the door's opening and closing in eighths of a unit per tic.
:* ''angle'' : Byte angle of door's initial motion. This angle is reversed when the door closes.
:* ''dist'' : Distance the door moves when opening, and again when closing, in units.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.

===PolyObject Door Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobj_doors.wad PolyObject Doors Demo]====
A demonstration of both swinging and sliding doors, mirrored and single. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' scripts together with provided comments. For example the first script explains how LineDefs are configured for a single swinging door:

<pre>
//=============================
//= BASIC SINGLE SWINGING DOOR
//===========================
linedef {
recordnum = 1 // corresponds to a LineDef with action: 270, tag: 1

special = PolyObj_StartLine // this defines the current LineDef as a
// starting point for the PolyObject

args = { 1 } // since this is a very basic PolyObj, it requires only one
// argument (it's not to be confused with LineDef / Sector tag)
}

linedef {
recordnum = 2 // corresponds to a LineDef with action: 270, tag: 2

extflags = "use player repeat" // describes how the LineDef is activated

special = PolyObj_DoorSwing
args = { 1,20,64,160 } // swing the door with PolyId: 1, AngularSpeed: 20
// AngularDeistance 64 units (90 deg),
// Delay: 160 tics
} (...)
</pre>

==Polyobjects with portals==
:See [[Linked_portals#Polyobject_portals | Polyobject portals]]

[[category:Editing reference]]

Polyobject

2026-04-23T17:23:18Z

Printz:

PolyObjects are special sets of one-sided linedefs which, unlike any other lines, can be moved on the map during gameplay. Unlike the Hexen implementation of PolyObjects, Eternity does not restrict these objects to one per subsector, and they are also allowed to move any distance from their spawn point, even across subsector boundaries.

PolyObjects fully clip normal objects such as the player and enemies, optionally doing crushing damage depending upon the type of spawn spot used. They also block bullet tracers and monsters' lines of sight. They do not, however, clip sound propagation, so it may be necessary to use sound blocking lines near areas where PolyObjects are meant to function as a normal wall until they move.

Although Eternity does allow PolyObjects to move between different subsectors, this will only work properly if the subsectors on both sides of a line have the same properties (floor & ceiling heights, light level, and flat). However, since the implementation of [[dynaseg]]s, Eternity does not require a "PolyObject-aware" node builder.

Finally, Eternity allows PolyObjects to be used in DOOM-format maps via the use of [[ExtraData]]. See the subsections below for more information on how to create and move PolyObjects.

{{Backto|Linedef types}}

==Creating PolyObjects==

PolyObjects are a combination of a set of 1S lines, which are typically placed in a "control sector" area outside of the main map, and exactly two mapthings: one spawn spot, and one anchor point. There are two different methods for grouping lines into a PolyObject.

==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===

:The <code>348:Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> special marks the first line in a PolyObject which is made up of a cyclic set of linedefs (that is, each line "points toward" the next line, ending at the first vertex of the first line).

:Diagrammatic Example:
:[[File:Polyobjects_basic.png]]
:Assume that the linedef '''A''' is assigned the <code>Polyobj_StartLine</code> special and has argument #1 set to "1" -- this is its '''PolyObject ID number''', which must be unique amongst all on the map, and must be a number greater than zero.

:Starting from line '''A''', the engine will go from vertex to vertex, adding the first line found which shares the current line's second vertex as its first vertex. In this example, since the object is closed as is required, the process will end at the first vertex of line '''A''', and there will be four lines in the PolyObject (note that unlike Hexen, there is NO limit to the number of lines that can be placed in one PolyObject).

:Now, once the lines are added, it is necessary to define the control objects. Points '''B''' and '''C''' are the two required objects:
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the StartLine's first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the StartLine's first argument and the anchor point's angle field. There must be one and only one of these objects for each PolyObject ID. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:Note that when you use this method, the other lines belonging to the PolyObject can be given their own line specials, including ones which affect the PolyObject itself. When the player presses the PolyObject, the specials will work as expected.

:The complete arguments to <code>Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use [[ExtraData]]. In that case, you must give the line you want to have the Polyobj_StartLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_StartLine and its arguments in its corresponding ExtraData linedef record.

==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===

:The <code>349:Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> special demarcates every line that will be added to a PolyObject and the exact order in which the lines will be added. This affords a bit more flexibility in the construction of PolyObjects at the price of not allowing any other line specials to be placed on the object itself.

:Diagrammatic Example:
:[[File:Polyobjects_adv.png]]
:Assume that the linedefs labeled 1 through 4 are assigned (via [[ExtraData]]) the <code>Polyobj_ExplicitLine</code> special, all have argument '''#1''' set to "1" -- this is its PolyObject ID number (which must be unique amongst all on the map, and must be a number greater than zero), and argument '''#2''' set also to whatever their tag is (in this case again it's ''1'').

:The game engine will search through all linedefs in the entire map for ones with the current '''PolyObject ID''' in argument '''#1''' and a value greater than zero in argument '''#2'''. The lines will be collected and then sorted by the '''LineDef id'''.

:Now, once the lines are added, it is necessary to define the control objects. This is exactly the same as it is for the <code>StartLine(...)</code> special above.
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the <code>ExplicitLines'</code> first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the ExplicitLines' first argument and the anchor point's angle field. There must be one and only one of these objects for each '''PolyObject ID'''. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:The complete arguments to <code>Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''index'' : specifies the order in which the line will be added to the PolyObject. This number should be unique amongst all lines to be added to the same object, and must be a value greater than zero.
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use ExtraData. In that case, you can either give the lines you want to have the Polyobj_ExplicitLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_ExplicitLine and its arguments in all the corresponding ExtraData linedef records; or simply use the line special normally, and specify the ExtraData record number in the linedef's tag, specifying only the arguments inside the ExtraData record.

===Note===
As of EE 3.37.00, thing type 9303 is available, which is similar to the ZDoom damaging polyobject type.

==Moving PolyObjects==

There are two types of basic motion which PolyObjects can currently undergo: translation and rotation. Using "override" actions, it is possible to combine the two to have a PolyObject which rotates while moving in the xy plane.

[[File:Polyobject_rotating.gif]]

===Translating PolyObjects===

To move a PolyObject in the xy plane, use one of the following line specials:
* <code>Polyobj_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>
* <code>Polyobj_OR_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>

Both of these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to intially move. If the object is already moving, nothing will happen unless the action is Polyobj_OR_Move. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the angle of movement for each subsequent mirror.
* ''speed'' : Speed of the motion in eighths of a unit per tic.
* ''angle'' : Byte angle specifying the direction of motion. To convert from degrees to byte angles, use this formula: byteangle = (degrees * 256) / 360. Round or chop the result to an integer. 0 means East, 64 means North, 128 means West, and 192 means South.
* ''dist'' : The total distance to move the object in units.

All PolyObjects will inflict thrust on objects which block them with force proportional to the speed of motion. If the PolyObject was spawned with the EEPolyObjSpawnSpotCrush object (DoomEd num 9302), then if the object does not fit at the location it is being pushed toward, it will be damaged 3 hitpoints per tic (105 damage per second).

===Rotating PolyObjects===

To rotate a PolyObject, use one of the following line specials:
* <code>Polyobj_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>

All these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to initially rotate. If the object is already moving, nothing will happen unless the action is Polyobj_OR_RotateRight or Polyobj_OR_RotateLeft. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the direction of rotation for each subsequent mirror.
* ''aspeed'' : Angular speed of the rotation in byte angles per tic. Same as for the "angle" parameter to Move actions.
* ''adist'' : Angular distance to rotate in byte angles. Same as for aspeed, except with two special caveats:

The byte angle value 0 (zero) means to rotate exactly 360 degrees.

The byte angle value 255 means to rotate perpetually. This type of action never ends and thus only override actions can subsequently be applied to the PolyObject.

===PolyObject Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects.wad PolyObject Demo]====
A demonstration of both rotating and translating PolyObjects. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments. For example this script explains how LineDefs are configured for a manually operated rotating PolyObject:

<pre>
//===============================
//= MANUALLY ROTATING POLYOBJECT
//=============================

// This PolyObject doesn't move unless activated by a a nearby switch.
linedef {
recordnum = 2
special = PolyObj_StartLine
args = { 2 }
}

linedef {
recordnum = 3
extflags = "use player" // Defines how the LineDef action is activated.
// The lack of "repeat" flag means it's a one-time
// action.

special = Polyobj_RotateRight
args = { 2, 2, 255 } // Starts Rotating PolyObject with PolyID: 2
// at a speed of 2 units and angular distance
// of 255 units - which means it'll rotate
// continuously.
} (...)
</pre>

====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects_adv.wad PolyObject Advanced Demo]====
A demonstration of rotating and translating PolyObjects made with <code>PolyObj_ExplicitLine()</code> Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]). It shows how more advanced PolyObjects can be constructed and moved to fake 3D objects. It also includes PolyObject Doors discussed in the next section of this article.

It is recommended that you play go through the first Demo in the series and open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments.

==PolyObject Doors==
There are two distinct types of actions provided to allow PolyObjects to function as doors: swinging and sliding. There are no override versions of door actions, and applying other overrides to currently moving PolyObject doors will most likely cause the doors to malfunction and move erratically.

All PolyObject doors accept a delay parameter, and this specifies the amount of time the door will wait before closing. A door which is closing will reopen if blocked by an object.

===Swinging PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_swingdoor_schema.png|200px]] || [[Image:Poly_swigning_door.gif]]
|-
| PolyObject swinging door schema || PolyObject swinging door
|}

<code>Polyobj_DoorSwing ('''polyobj_id''', '''aspeed''', '''adist''', '''delay''')</code>

This action creates a swinging door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''aspeed'' : Angular speed in byte angles per tic.
:* ''adist'' : Angular distance to rotate when opening, and again but in the opposite direction when closing.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.
Swinging doors currently only rotate left. A right-rotating swinging door special will be added in the near future.

===Sliding PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_slidedoor_schema.png|200px]] || [[Image:Poly_sliding_door.gif|180px]]
|-
| PolyObject sliding door schema || PolyObject sliding door
|}

<code>Polyobj_DoorSlide ('''polyobj_id''', '''speed''', '''angle''', '''dist''', '''delay''')</code>

:This action creates a sliding door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''speed'' : Speed of the door's opening and closing in eighths of a unit per tic.
:* ''angle'' : Byte angle of door's initial motion. This angle is reversed when the door closes.
:* ''dist'' : Distance the door moves when opening, and again when closing, in units.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.

===PolyObject Door Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobj_doors.wad PolyObject Doors Demo]====
A demonstration of both swinging and sliding doors, mirrored and single. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' scripts together with provided comments. For example the first script explains how LineDefs are configured for a single swinging door:

<pre>
//=============================
//= BASIC SINGLE SWINGING DOOR
//===========================
linedef {
recordnum = 1 // corresponds to a LineDef with action: 270, tag: 1

special = PolyObj_StartLine // this defines the current LineDef as a
// starting point for the PolyObject

args = { 1 } // since this is a very basic PolyObj, it requires only one
// argument (it's not to be confused with LineDef / Sector tag)
}

linedef {
recordnum = 2 // corresponds to a LineDef with action: 270, tag: 2

extflags = "use player repeat" // describes how the LineDef is activated

special = PolyObj_DoorSwing
args = { 1,20,64,160 } // swing the door with PolyId: 1, AngularSpeed: 20
// AngularDeistance 64 units (90 deg),
// Delay: 160 tics
} (...)
</pre>

==Polyobjects with portals==
:See [[Linked_portals#Polyobject_portals | Polyobject portals]]

[[category:Editing reference]]

CheckSight

2026-04-23T06:06:26Z

Printz:

{{ACSFunction|description=Checks if there is a line of sight between two actors.
|usage=''boolean'' '''CheckSight'''(''int'' ''tid1'', ''int'' ''tid2'', ''flags'')
|parameters=
*''tid1'': [[TID]] of first actor
*''tid2'': [[TID]] of second actor
*''flags'': reserved, must be 0
|notes=This uses the same line of sight rule as the one for monster sights, explosion rays etc. If any of the two actors is completely gone from the game, the function returns 0. It will still return 1 if there's a line of sight if they still exist as corpses or in any way still present in the game.
|id=-35}}

CheckSight

2026-04-23T05:52:57Z

Printz:

CheckSight

2026-04-23T05:51:32Z

Printz: Created page with "{{ACSFunction|description=Checks if there is a line of sight between two actors. |usage=''boolean'' '''CheckSight'''(''int'' ''tid1'', ''int'' ''tid2'', ''flags'') |parameters= *''tid1'': TID of first actor *''tid2'': TID of second actor *''flags'': reserved, must be 0}}"

GetSigilPieces

2026-04-23T05:46:09Z

Printz:

{{ACSFunction|description=Returns the number of Sigil (Strife) pieces.
|usage=int GetSigilPieces(void)
|return=the number of Sigil pieces
|notes=This function only applies for Strife. Currently there is no Sigil in Eternity so this returns 0.
|id=ACS internal}}

EDF item effects and inventory

2026-04-23T05:43:39Z

Printz: /* armoreffect */

Define what happens when an item is picked up and used (and eventually, dropped from the inventory - this is not complete yet). A tutorial on defining each of these can be found at [[Creating a pickup]].

==Thing type based pick-up==
The recommended way to define pick-up effects is by adding the '''pickupeffect''' section in the [[thingtype]] definition of a class.

The fields are as such:

thingtype <name>
{
...
pickupeffect
{
effects <name>, ...
flags <flags>
changeweapon <name>
message <text>
sound <name>
}
...
}
For explanation of the fields, see the sprite-based block definition's corresponding fields.

==Sprite based pick-ups==
===pickupeffect===
Defines what happens when player picks up an item with the '''SPECIAL''' [[Thing type flags|flag]]. Commonly in DOOM and Heretic, pick-up effects are associated with the visual sprites of the things, instead of being mapped directly to the thing class.

In the base game definitions, you can find the pick-up effects defined in sprites.edf.
pickupeffect <name>
{
sprite <name>
effects <name>, ...
flags <flags>
changeweapon <name>
message <text>
sound <name>
}
====Explanation of fields====
*'''sprite'''
:Default: no sprite.
:If set as a four-character sprite name, this will associate any [[thingtype]] with the '''SPECIAL''' [[Thing type flags|flag]] whose current sprite shows as this value to trigger this '''pickupeffect'''.
:Example: <code>sprite BON1</code>
*'''effects'''
:Default: no effect.
:This is a list of effects incurred on player when picking up the item. Each one must be defined in EDF as one of the following: '''ammoeffect''', '''armoreffect''', '''artifact''', '''healtheffect''', '''powereffect''' or '''weapongiver'''.
:Example: <code>effects Berserk, BerserkHealth</code>
*'''flags'''
:Default: no flags.
:This is an optional set of one or more flags, joined together by | (vertical bar). The flags you can use are:
:*'''ALWAYSPICKUP''': item shall always be picked, even if according to the '''effects''', there would be no need for the item. Example: health potions in DOOM.
:*'''LEAVEINMULTI''': if game is multiplayer, keep item on the ground for every players to find it. Commonly used by access keys.
:*'''NOSCREENFLASH''': if picked up, item will not flash player's screen.
:*'''SILENTNOBENEFIT''': only has effect in conjunction with '''ALWAYSPICKUP''': if picked up when unneeded, all user feedback (message, sound, flash) is suppressed.
:*'''COMMERCIALONLY''': only relevant for demo compatibility, marks the item as DOOM 2 (the "commercial" release) specific. The megasphere has this flag. Not needed for new mods.
:*'''GIVESBACKPACKAMMO''': commonly used by the entries with the '''BackpackItem''' in '''effects''' (which doubles player's ammo capacity) to also provide the backpack ammo amount for each available ammo '''artifact''' in the game.
*'''changeweapon'''
:Default: nothing.
:If set, causes the item to change player's current weapon to the designated one whenever picked up. Expects a [[weaponinfo]] definition. This is based on how the [[Doom Wiki:Berserk|Berserk pack]] acts in DOOM.
:Example: <code>changeweapon Fist</code>
*'''message'''
:Default: no message.
:What message to display at the top of the view when picking up the item. This doesn't cover special cases such as the medikit low health message or the special BFG9000 variants.
:Example: <code>message "picked up an item."</code>
*'''sound'''
:Default: none
:Sets the [[sound]] to play when picking up the item.
:Example: <code>sound itemup</code>

Note: the '''pfxname''' field (which you may encounter in the base EDF) is only needed for compatibility with a deprecated feature.

==Effect definitions==
From a '''pickupeffect''''s '''effects''' field, one can add from many different types of item effect definitions:

===Base definitions===

====artifact====
An artifact is an item which, when collected, goes into the player's inventory.

artifact <name>
{
amount <int> // amount gained with one pickup
maxamount <int> // max amount that can be carried in inventory
interhubamount <int> // max amount carryable between levels in different hubs;
// -1 if this field should not apply at all
sortorder <int> // key used for sorting the player's inventory
icon <str> // name of icon graphic for invbar
usesound <str> // sound made when item is used
useeffect <str> // name of item effect to use for activation
useaction <action function> // codepointer and arguments called (e.g. A_GauntletAttack(1))

[+-]undroppable // if +, cannot be dropped from inventory
[+-]invbar // if +, appears in invbar; otherwise, invisible
[+-]keepdepleted // if +, will remain in inventory with amount of zero
[+-]fullamountonly // if +, cannot pickup unless full amount is needed
[+-]noshareware // if +, non-shareware

// artifacttype determines what sort of artifact this is.
artifacttype <str> // "Normal", "Ammo", "Key", "Puzzle", "Power", "Weapon",
// or "Quest"

// The following fields apply only to certain artifact types. They have no
// effect if specified on other types.

// Ammo
ammo.backpackamount <int> // amount of this ammo type given by a Backpack
ammo.backpackmaxamount <int> // max amount after collecting a Backpack

// Autouse health: this applies only for health-effect artifacts.
// If enabled, game will automatically trigger when player is about to die,
// to restore health and keep them alive.

// "none" or "heretic". If "heretic", this is enabled and works like Heretic
autouse.health.mode <option>

// Optional restrictions. If omitted, there is no game restriction. Otherwise,
// it can be a "|"-joined combination of "baby" and "deathmatch". Then the
// autouse will happen IF ANY of the given conditions are met.
autouse.health.restrict <flags>
}

====healtheffect====
A health effect gives the player health in one of many possible ways.
healtheffect <name>
{
amount <int> // amount of health to give
maxamount <int> // max amount this item can health to.
lowmessage <str> // alternate message to give instead of pickupfx message when
// health is less than amount; if starts with $, is a BEX mnemonic.

[+-]alwayspickup // if +, item is picked up even when unneeded (e.g. Health Bonus)
[+-]sethealth // if +, item SETS health rather than adding to it (e.g. Megasphere)
}

====armoreffect====
An armor effect defines the properties of player armor
armoreffect <name>
{
saveamount <int> // amount of armor given
savefactor <int> // numerator of fraction determining save percentage
savedivisor <int> // denominator of fraction determining save percentage
maxsaveamount <int> // max amount his item can give; if player has greater
// armor, the item cannot be picked up at all

[+-]alwayspickup // item is picked up even when unneeded (e.g. Armor Bonus)
[+-]additive // if +, adds to the current amount of armor
[+-]setabsorption // if +, sets absorption values (savefactor & savedivisor)
}

The '''saveamount''' currently worn by a player can be queried at playtime using the ACS function [[PlayerArmorPoints]].

====ammoeffect====
Ammo givers give an Ammo type artifact to the player.
ammoeffect <name>
{
ammo <str> // Name of an Ammo-type artifact definition
amount <int> // Amount to give for an ordinary pickup
dropamount <int> // Amount to give if dropped by an enemy

[+-]ignoreskill // if +, does not double on skills that give double ammo
}
====powereffect====
Power givers buff the player with a temporary or level-permanent effect. They're typical of artifacts such as the radiation suit or the blur sphere.
powereffect <name>
{
duration <int> // Length of time to last in tics
type <str> // Name of power to give

[+-]additivetime // if +, adds to current duration
[+-]permanent // if +, lasts forever
[+-]overridesself // if +, getting the power again while still under its influence is allowed
}

'''Type''' can be any of the following:
*'''PowerAllmap''': Doom computer area map, Heretic map scroll
*'''PowerFlight''': Heretic wings of wrath
*'''PowerGhost''': Heretic shadow sphere
*'''PowerInvulnerable''': Doom invulnerability artifact, Heretic ring of invulnerability
*'''PowerIronFeet''': Doom radiation shielding suit
*'''PowerLightAmp''': Doom light amplification visor
*'''PowerPartialInvisibility''': Doom blur artifact
*'''PowerSilent''': Eternity silencer
*'''PowerStrength''': Doom berserk pack
*'''PowerTorch''': Heretic torch
*'''PowerTotalInvisibility''': Eternity total invisibility
*'''PowerWeaponLevel2''': Heretic tome of power

====weapongiver====
Weapon givers give a Weapon type artifact to the player, and optionally any number of Ammo artifact types.
weapongiver <name>
{
weapon <str> // Name of a weaponinfo to give to the player
// Note that you can specify as many ammogiven properties as you want in a single weapongiver
ammogiven <ammo>, <amount> [, <dropamount> [, <dmamount> [, <coopweaponsstay>]]] // Ammo type artifact given, and the amounts
// given based on how it was picked up. If the
// last three are left blank, only "amount" is used.
}

===Delta structures===
The following can be used to replace already defined effects. They can be cascaded (i.e. any number of loaded mods can change the previous definition and all its deltas). For each of them, the '''name''' field represents the name of the base to modify. They are the following:
healthdelta
{
name <name>
...
}

armordelta
{
name <name>
...
}

ammodelta
{
name <name>
...
}

powerdelta
{
name <name>
...
}

weapongiverdelta
{
name <name>
clearammogiven // if added, removes the "given ammo" definitions
...
}

artifactdelta
{
name <name>
...
}

[[Category:EDF]]

PlayerArmorPoints

2026-04-23T05:42:18Z

Printz:

{{ACSFunction|description=Returns activator's armor points.
|usage=''int'' PlayerArmorPoints()
|return=The value of the armor.
|notes=This only returns the armor value (i.e. what shows up as "percentage" on the status bar in Doom), not also the armor toughness. Only players have armor.
|id=ACS internal
|seealso=
*[[EDF_item_effects_and_inventory#armoreffect|EDF armor effects]]}}

Polyobject

2026-04-21T20:59:47Z

Printz: /* Method 2: The Polyobj_ExplicitLine Special */

PolyObjects are special sets of one-sided linedefs which, unlike any other lines, can be moved on the map during gameplay. Unlike the Hexen implementation of PolyObjects, Eternity does not restrict these objects to one per subsector, and they are also allowed to move any distance from their spawn point, even across subsector boundaries.

PolyObjects fully clip normal objects such as the player and enemies, optionally doing crushing damage depending upon the type of spawn spot used. They also block bullet tracers and monsters' lines of sight. They do not, however, clip sound propagation, so it may be necessary to use sound blocking lines near areas where PolyObjects are meant to function as a normal wall until they move.

Although Eternity does allow PolyObjects to move between different subsectors, this will only work properly if the subsectors on both sides of a line have the same properties (floor & ceiling heights, light level, and flat). However, since the implementation of [[dynaseg]]s, Eternity does not require a "PolyObject-aware" node builder.

Finally, Eternity allows PolyObjects to be used in DOOM-format maps via the use of [[ExtraData]]. See the subsections below for more information on how to create and move PolyObjects.

'''NOTE:''' Polyobjects must be convex, to be rendered properly.

{{Backto|Linedef types}}

==Creating PolyObjects==

PolyObjects are a combination of a set of 1S lines, which are typically placed in a "control sector" area outside of the main map, and exactly two mapthings: one spawn spot, and one anchor point. There are two different methods for grouping lines into a PolyObject.

==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===

:The <code>348:Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> special marks the first line in a PolyObject which is made up of a cyclic set of linedefs (that is, each line "points toward" the next line, ending at the first vertex of the first line).

:Diagrammatic Example:
:[[File:Polyobjects_basic.png]]
:Assume that the linedef '''A''' is assigned the <code>Polyobj_StartLine</code> special and has argument #1 set to "1" -- this is its '''PolyObject ID number''', which must be unique amongst all on the map, and must be a number greater than zero.

:Starting from line '''A''', the engine will go from vertex to vertex, adding the first line found which shares the current line's second vertex as its first vertex. In this example, since the object is closed as is required, the process will end at the first vertex of line '''A''', and there will be four lines in the PolyObject (note that unlike Hexen, there is NO limit to the number of lines that can be placed in one PolyObject).

:Now, once the lines are added, it is necessary to define the control objects. Points '''B''' and '''C''' are the two required objects:
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the StartLine's first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the StartLine's first argument and the anchor point's angle field. There must be one and only one of these objects for each PolyObject ID. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:Note that when you use this method, the other lines belonging to the PolyObject can be given their own line specials, including ones which affect the PolyObject itself. When the player presses the PolyObject, the specials will work as expected.

:The complete arguments to <code>Polyobj_StartLine('''polyobj_id''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use [[ExtraData]]. In that case, you must give the line you want to have the Polyobj_StartLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_StartLine and its arguments in its corresponding ExtraData linedef record.

==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===

:The <code>349:Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> special demarcates every line that will be added to a PolyObject and the exact order in which the lines will be added. This affords a bit more flexibility in the construction of PolyObjects at the price of not allowing any other line specials to be placed on the object itself.

:Diagrammatic Example:
:[[File:Polyobjects_adv.png]]
:Assume that the linedefs labeled 1 through 4 are assigned (via [[ExtraData]]) the <code>Polyobj_ExplicitLine</code> special, all have argument '''#1''' set to "1" -- this is its PolyObject ID number (which must be unique amongst all on the map, and must be a number greater than zero), and argument '''#2''' set also to whatever their tag is (in this case again it's ''1'').

:The game engine will search through all linedefs in the entire map for ones with the current '''PolyObject ID''' in argument '''#1''' and a value greater than zero in argument '''#2'''. The lines will be collected and then sorted by the '''LineDef id'''.

:Now, once the lines are added, it is necessary to define the control objects. This is exactly the same as it is for the <code>StartLine(...)</code> special above.
:* '''B''': This is the PolyObject's anchor point (type EEPolyObjAnchor with DoomEd #9300). It defines the point relative to which all the lines in the PolyObject will be translated to the spawn point. This object's angle must be set to the same value as the <code>ExplicitLines'</code> first argument (the '''PolyObject ID'''). There must be one and only one of these objects for each '''PolyObject ID'''.
:* '''C''': This is the PolyObject's spawn point (one of EEPolyObjSpawnSpot [9301] or EEPolyObjSpawnSpotCrush [9302]). It defines the point where the PolyObject will initially spawn on the map. The anchor point will be translated to this exact location, and all lines in the PolyObject will maintain their relative positions to it. This object must also have its angle field set to the same value as both the ExplicitLines' first argument and the anchor point's angle field. There must be one and only one of these objects for each '''PolyObject ID'''. Use 9302 to cause the PolyObject to do crushing damage to things that block it while it is in motion.

:The complete arguments to <code>Polyobj_ExplicitLine('''polyobj_id''', '''index''', '''mirror_id''')</code> are as follows:
:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
:* ''index'' : specifies the order in which the line will be added to the PolyObject. This number should be unique amongst all lines to be added to the same object, and must be a value greater than zero.
:* ''mirror_id'' : the ID number of a PolyObject that you want to mirror every action that affects this PolyObject. This number cannot be the same as the PolyObject's own ID.

:In order to use this line special in a DOOM-format map, it is necessary to use ExtraData. In that case, you can either give the lines you want to have the Polyobj_ExplicitLine special the ExtraData linedef control special (#270) instead, and then specify Polyobj_ExplicitLine and its arguments in all the corresponding ExtraData linedef records; or simply use the line special normally, and specify the ExtraData record number in the linedef's tag, specifying only the arguments inside the ExtraData record.

===Note===
As of EE 3.37.00, thing type 9303 is available, which is similar to the ZDoom damaging polyobject type.

==Moving PolyObjects==

There are two types of basic motion which PolyObjects can currently undergo: translation and rotation. Using "override" actions, it is possible to combine the two to have a PolyObject which rotates while moving in the xy plane.

[[File:Polyobject_rotating.gif]]

===Translating PolyObjects===

To move a PolyObject in the xy plane, use one of the following line specials:
* <code>Polyobj_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>
* <code>Polyobj_OR_Move('''polyobj_id''', '''speed''', '''angle''', '''dist''')</code>

Both of these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to intially move. If the object is already moving, nothing will happen unless the action is Polyobj_OR_Move. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the angle of movement for each subsequent mirror.
* ''speed'' : Speed of the motion in eighths of a unit per tic.
* ''angle'' : Byte angle specifying the direction of motion. To convert from degrees to byte angles, use this formula: byteangle = (degrees * 256) / 360. Round or chop the result to an integer. 0 means East, 64 means North, 128 means West, and 192 means South.
* ''dist'' : The total distance to move the object in units.

All PolyObjects will inflict thrust on objects which block them with force proportional to the speed of motion. If the PolyObject was spawned with the EEPolyObjSpawnSpotCrush object (DoomEd num 9302), then if the object does not fit at the location it is being pushed toward, it will be damaged 3 hitpoints per tic (105 damage per second).

===Rotating PolyObjects===

To rotate a PolyObject, use one of the following line specials:
* <code>Polyobj_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateRight('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>
* <code>Polyobj_OR_RotateLeft('''polyobj_id''', '''aspeed''', '''adist''')</code>

All these line specials use the same arguments:
* ''polyobj_id'' : Specifies which PolyObject to initially rotate. If the object is already moving, nothing will happen unless the action is Polyobj_OR_RotateRight or Polyobj_OR_RotateLeft. If this object has a mirror, the same action will be recursively applied to every mirror PolyObject, reversing the direction of rotation for each subsequent mirror.
* ''aspeed'' : Angular speed of the rotation in byte angles per tic. Same as for the "angle" parameter to Move actions.
* ''adist'' : Angular distance to rotate in byte angles. Same as for aspeed, except with two special caveats:

The byte angle value 0 (zero) means to rotate exactly 360 degrees.

The byte angle value 255 means to rotate perpetually. This type of action never ends and thus only override actions can subsequently be applied to the PolyObject.

===PolyObject Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects.wad PolyObject Demo]====
A demonstration of both rotating and translating PolyObjects. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments. For example this script explains how LineDefs are configured for a manually operated rotating PolyObject:

<pre>
//===============================
//= MANUALLY ROTATING POLYOBJECT
//=============================

// This PolyObject doesn't move unless activated by a a nearby switch.
linedef {
recordnum = 2
special = PolyObj_StartLine
args = { 2 }
}

linedef {
recordnum = 3
extflags = "use player" // Defines how the LineDef action is activated.
// The lack of "repeat" flag means it's a one-time
// action.

special = Polyobj_RotateRight
args = { 2, 2, 255 } // Starts Rotating PolyObject with PolyID: 2
// at a speed of 2 units and angular distance
// of 255 units - which means it'll rotate
// continuously.
} (...)
</pre>

====[https://s3-eu-west-1.amazonaws.com/eternity/polyobjects_adv.wad PolyObject Advanced Demo]====
A demonstration of rotating and translating PolyObjects made with <code>PolyObj_ExplicitLine()</code> Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]). It shows how more advanced PolyObjects can be constructed and moved to fake 3D objects. It also includes PolyObject Doors discussed in the next section of this article.

It is recommended that you play go through the first Demo in the series and open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' and '''ACS''' scripts together with provided comments.

==PolyObject Doors==
There are two distinct types of actions provided to allow PolyObjects to function as doors: swinging and sliding. There are no override versions of door actions, and applying other overrides to currently moving PolyObject doors will most likely cause the doors to malfunction and move erratically.

All PolyObject doors accept a delay parameter, and this specifies the amount of time the door will wait before closing. A door which is closing will reopen if blocked by an object.

===Swinging PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_swingdoor_schema.png|200px]] || [[Image:Poly_swigning_door.gif]]
|-
| PolyObject swinging door schema || PolyObject swinging door
|}

<code>Polyobj_DoorSwing ('''polyobj_id''', '''aspeed''', '''adist''', '''delay''')</code>

This action creates a swinging door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''aspeed'' : Angular speed in byte angles per tic.
:* ''adist'' : Angular distance to rotate when opening, and again but in the opposite direction when closing.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.
Swinging doors currently only rotate left. A right-rotating swinging door special will be added in the near future.

===Sliding PolyObject Door===
{| class="wikitable"
|-
| [[Image:Poly_slidedoor_schema.png|200px]] || [[Image:Poly_sliding_door.gif|180px]]
|-
| PolyObject sliding door schema || PolyObject sliding door
|}

<code>Polyobj_DoorSlide ('''polyobj_id''', '''speed''', '''angle''', '''dist''', '''delay''')</code>

:This action creates a sliding door from a PolyObject and takes the following arguments:
:* ''polyobj_id'' : The ID number of PolyObject to affect. Mirroring works for doors as well and is the most common use for PolyObject mirroring.
:* ''speed'' : Speed of the door's opening and closing in eighths of a unit per tic.
:* ''angle'' : Byte angle of door's initial motion. This angle is reversed when the door closes.
:* ''dist'' : Distance the door moves when opening, and again when closing, in units.
:* ''delay'' : Amount of time before the door attempts to close after fully opening in tics. If the door is forced to reopen due to being blocked, it will also wait this amount of time before once again closing.

===PolyObject Door Examples===
====[https://s3-eu-west-1.amazonaws.com/eternity/polyobj_doors.wad PolyObject Doors Demo]====
A demonstration of both swinging and sliding doors, mirrored and single. Plays on '''Doom 2''' / '''Map01'''. The map is linked to an [[ExtraData]] lump (via [[EMAPINFO]]).

It is recommended that you open the Demo WAD in a WAD manager program like '''SLADE3''' or '''XWE''' to read the '''ExtraData''' scripts together with provided comments. For example the first script explains how LineDefs are configured for a single swinging door:

<pre>
//=============================
//= BASIC SINGLE SWINGING DOOR
//===========================
linedef {
recordnum = 1 // corresponds to a LineDef with action: 270, tag: 1

special = PolyObj_StartLine // this defines the current LineDef as a
// starting point for the PolyObject

args = { 1 } // since this is a very basic PolyObj, it requires only one
// argument (it's not to be confused with LineDef / Sector tag)
}

linedef {
recordnum = 2 // corresponds to a LineDef with action: 270, tag: 2

extflags = "use player repeat" // describes how the LineDef is activated

special = PolyObj_DoorSwing
args = { 1,20,64,160 } // swing the door with PolyId: 1, AngularSpeed: 20
// AngularDeistance 64 units (90 deg),
// Delay: 160 tics
} (...)
</pre>

==Polyobjects with portals==
:See [[Linked_portals#Polyobject_portals | Polyobject portals]]

[[category:Editing reference]]

UMAPINFO

2026-04-05T14:49:17Z

Printz:

Eternity supports the common UMAPINFO lump, a standard defined in PrBoom+um. See its [https://github.com/kraflab/umapinfo/blob/master/docs/spec.md specification]. Make sure to adhere to the strict standard if you want the maps to be playable on all implementing ports. Otherwise, if you make the mod for Eternity, [[EMAPINFO]] is more recommended, since it contains the entire feature set.

==UMAPINFO - EMAPINFO equivalence table==
{|class="wikitable sortable"
!UMAPINFO property
!EMAPINFO equivalent
|-
||'''levelname''', '''label'''||Both of these influence '''levelname''' and '''inter-levelname'''
|-
||'''levelpic'''||'''levelpic'''
|-
||'''next'''||'''nextlevel'''. Beware that omitting '''next''' in UMAPINFO will reset '''nextlevel''' to the next numbered map (if following the ExMy/MAPxy format).
|-
||'''nextsecret'''||'''nextsecret'''. Same situations as with UMAPINFO '''next'''.
|-
||'''skytexture'''||'''skyname'''. For more advanced sky effects, you need EMAPINFO.
|-
||'''music'''||'''music'''. Beware that in UMAPINFO you must specify the entire lump length (including D_ or MUS_, based on game).
|-
||'''exitpic'''||'''interpic'''
|-
||'''enterpic'''||'''enterpic'''
|-
||'''partime'''||'''partime'''
|-
||'''endgame = false'''||
:'''finaletype text'''
:'''endofgame false'''
:'''finale-early false'''
|-
||'''endgame = true'''||Effect depends on the current episode (if map lump is named in a standard manner).
|-
||'''endpic'''||
:'''endofgame false'''
:'''finaletype endpic'''
:'''endpic''' ''lump''
It also enables the finale for both the normal and secret exits.
|-
||'''endbunny = true'''||
:'''endofgame false'''
:'''finaletype doom_bunny'''
It also enables the finale for both the normal and secret exits.
|-
||'''endcast = true'''||
:'''endofgame true'''
:'''finaletype text'''
|-
||'''nointermission'''||'''finale-early'''
|-
||'''intertext''', '''intertextsecret''''||Like '''intertext''' and '''intertext-secret''' but gets the text directly from UMAPINFO. It also sets or clears '''finale-normal''' and '''finale-secret'''.
|-
||'''interbackdrop'''||'''inter-backdrop'''
|-
||'''intermusic'''||'''intermusic'''
|-
||'''episode'''||[[EDF menu reference]]. See '''mn_episode''' in particular. If mod has this EDF menu defined, it takes priority over UMAPINFO.
|-
||'''bossaction'''||'''levelaction-bossdeath'''. However, the UMAPINFO always uses classic specials, whereas the EMAPINFO version uses UDMF parameterized specials. Clearing '''bossaction''' is like setting EMAPINFO '''boss-specials 0'''.
|}
==See also==
*[[EMAPINFO]]

Accelerative scrolling

2026-04-04T19:09:41Z

Printz: Redirected page to Scroller linedef types#Accelerative Scrollers

#REDIRECT [[Scroller_linedef_types#Accelerative_Scrollers]]

Displacement scrolling

2026-04-04T19:09:10Z

Printz: Redirected page to Scroller linedef types#Displacement Scrollers

#REDIRECT [[Scroller_linedef_types#Displacement_Scrollers]]

Scroll Floor

2026-04-04T19:08:23Z

Printz: Created page with "{{LineSpecial|description=This is the parameterized scrolling special for the floor. |usage='''Scroll_Floor'''(''tag'', ''flags'', ''type'', ''x'', ''y'') |parameters= *''tag'': tag of sectors whose floors to scroll; *''flags'': zero or a sum of the following values: :*1: set displacement scrolling :*2: set accelerative scrolling. This overrides displacement scrolling if both flags are set. :*4: use linedef vector to direct the scrolling (scrolling will happen wh..."

{{LineSpecial|description=This is the parameterized scrolling special for the floor.
|usage='''Scroll_Floor'''(''tag'', ''flags'', ''type'', ''x'', ''y'')
|parameters=
*''tag'': tag of sectors whose floors to scroll;
*''flags'': zero or a sum of the following values:
:*1: set [[displacement scrolling]]
:*2: set [[accelerative scrolling]]. This overrides displacement scrolling if both flags are set.
:*4: use linedef vector to direct the scrolling (scrolling will happen wherever the linedef points on the map). Divide the length of the line by 32 to obtain the scrolling velocity. Parameters ''x'' and ''y'' will be ignored.
*''type'': type of scroller. Can be:
:*0: scroll only the texture;
:*1: only carry the things, without animating the texture;
:*2: both scroll the texture and carry things.
*''x'', ''y'': if ''flags'' doesn't include 4, then these parameters control the scrolling direction. Please see in '''Notes''' about how they're scaled.
|notes=This special acts ''static'' when set on a linedef: it triggers at map startup, not when activated by player or others. But it can also be called from [[ACS]].
|udmf=223
|extradata=484

Scales of ''x'' and ''y'' differ between map placement and ACS:
*on the map, due to Hexen format legacy, you need to subtract 128 from the parameter, then divide by 32, to obtain the actual direction.
*in ACS: multiply by 10, then divide by 32.}}

WeaponReady

2026-04-04T15:17:55Z

Printz:

{{codepointer|description=WeaponReady is a player weapon codepointer. This codepointer readies the player's gun to fire or to change to another weapon. It should be called from any weapon's ready state.
|usage='''A_WeaponReady'''(''flags'')
|parameters=
*''flags'': optional, can be '''WRF_NOBOB''' if mentioned. Disables weapon bobbing.
|examples=
<code>A_WeaponReady</code>

<code>A_WeaponReady(WRF_NOBOB)</code>
|notes=This pointer also plays the chainsaw's idle sound, as determined by [[weaponinfo]] '''readysound'''.
|seealso=
*[[Lower]]
*[[Raise]]
}}

SetWeapon

2026-04-04T11:25:14Z

Printz: Created page with "{{ACSFunction|description=Changes activator's current weapon. |usage=''boolean'' '''SetWeapon'''(''str weapon'') |parameters= *''weapon'': name of weapon to switch to. This name is one defined by an EDF weaponinfo block, which for the base games is stored in '''player.edf'''. |return='''TRUE''' if the weapon was successfully selected or was already active, '''FALSE''' otherwise. |examples= <code>int result = SetWeapon("Crossbow"); // will return TRUE if player..."

{{ACSFunction|description=Changes activator's current weapon.
|usage=''boolean'' '''SetWeapon'''(''str weapon'')
|parameters=
*''weapon'': name of weapon to switch to. This name is one defined by an [[EDF]] [[weaponinfo]] block, which for the base games is stored in '''player.edf'''.
|return='''TRUE''' if the weapon was successfully selected or was already active, '''FALSE''' otherwise.
|examples=

<code>int result = SetWeapon("Crossbow"); // will return TRUE if player has and can use crossbow</code>

|notes=
This function only works if activator is a player.

This will not allow selecting a weapon missing from activator's [[playerclass]] '''weaponslot''' items (i.e. weapons not allowed for the given character class), even if the player holds it in the inventory.

If Heretic tome of power (from [[powereffect]] '''type''' '''PowerWeaponLevel2''') is active, it will always choose the powered type even if you specify the unpowered '''weaponinfo''' definition name.
|id=(ACS internal)}}

Powereffect

2026-04-04T11:23:45Z

Printz: Changed redirect target from EDF item effects and inventory to EDF item effects and inventory#powereffect

#REDIRECT [[EDF item effects and inventory#powereffect]]

Powereffect

2026-04-04T11:23:26Z

Printz: Redirected page to EDF item effects and inventory

#REDIRECT [[EDF item effects and inventory]]

EDF item effects and inventory

2026-03-27T18:16:45Z

Printz: /* weapongiver */

Define what happens when an item is picked up and used (and eventually, dropped from the inventory - this is not complete yet). A tutorial on defining each of these can be found at [[Creating a pickup]].

==Thing type based pick-up==
The recommended way to define pick-up effects is by adding the '''pickupeffect''' section in the [[thingtype]] definition of a class.

The fields are as such:

thingtype <name>
{
...
pickupeffect
{
effects <name>, ...
flags <flags>
changeweapon <name>
message <text>
sound <name>
}
...
}
For explanation of the fields, see the sprite-based block definition's corresponding fields.

==Sprite based pick-ups==
===pickupeffect===
Defines what happens when player picks up an item with the '''SPECIAL''' [[Thing type flags|flag]]. Commonly in DOOM and Heretic, pick-up effects are associated with the visual sprites of the things, instead of being mapped directly to the thing class.

In the base game definitions, you can find the pick-up effects defined in sprites.edf.
pickupeffect <name>
{
sprite <name>
effects <name>, ...
flags <flags>
changeweapon <name>
message <text>
sound <name>
}
====Explanation of fields====
*'''sprite'''
:Default: no sprite.
:If set as a four-character sprite name, this will associate any [[thingtype]] with the '''SPECIAL''' [[Thing type flags|flag]] whose current sprite shows as this value to trigger this '''pickupeffect'''.
:Example: <code>sprite BON1</code>
*'''effects'''
:Default: no effect.
:This is a list of effects incurred on player when picking up the item. Each one must be defined in EDF as one of the following: '''ammoeffect''', '''armoreffect''', '''artifact''', '''healtheffect''', '''powereffect''' or '''weapongiver'''.
:Example: <code>effects Berserk, BerserkHealth</code>
*'''flags'''
:Default: no flags.
:This is an optional set of one or more flags, joined together by | (vertical bar). The flags you can use are:
:*'''ALWAYSPICKUP''': item shall always be picked, even if according to the '''effects''', there would be no need for the item. Example: health potions in DOOM.
:*'''LEAVEINMULTI''': if game is multiplayer, keep item on the ground for every players to find it. Commonly used by access keys.
:*'''NOSCREENFLASH''': if picked up, item will not flash player's screen.
:*'''SILENTNOBENEFIT''': only has effect in conjunction with '''ALWAYSPICKUP''': if picked up when unneeded, all user feedback (message, sound, flash) is suppressed.
:*'''COMMERCIALONLY''': only relevant for demo compatibility, marks the item as DOOM 2 (the "commercial" release) specific. The megasphere has this flag. Not needed for new mods.
:*'''GIVESBACKPACKAMMO''': commonly used by the entries with the '''BackpackItem''' in '''effects''' (which doubles player's ammo capacity) to also provide the backpack ammo amount for each available ammo '''artifact''' in the game.
*'''changeweapon'''
:Default: nothing.
:If set, causes the item to change player's current weapon to the designated one whenever picked up. Expects a [[weaponinfo]] definition. This is based on how the [[Doom Wiki:Berserk|Berserk pack]] acts in DOOM.
:Example: <code>changeweapon Fist</code>
*'''message'''
:Default: no message.
:What message to display at the top of the view when picking up the item. This doesn't cover special cases such as the medikit low health message or the special BFG9000 variants.
:Example: <code>message "picked up an item."</code>
*'''sound'''
:Default: none
:Sets the [[sound]] to play when picking up the item.
:Example: <code>sound itemup</code>

Note: the '''pfxname''' field (which you may encounter in the base EDF) is only needed for compatibility with a deprecated feature.

==Effect definitions==
From a '''pickupeffect''''s '''effects''' field, one can add from many different types of item effect definitions:

===Base definitions===

====artifact====
An artifact is an item which, when collected, goes into the player's inventory.

artifact <name>
{
amount <int> // amount gained with one pickup
maxamount <int> // max amount that can be carried in inventory
interhubamount <int> // max amount carryable between levels in different hubs;
// -1 if this field should not apply at all
sortorder <int> // key used for sorting the player's inventory
icon <str> // name of icon graphic for invbar
usesound <str> // sound made when item is used
useeffect <str> // name of item effect to use for activation
useaction <action function> // codepointer and arguments called (e.g. A_GauntletAttack(1))

[+-]undroppable // if +, cannot be dropped from inventory
[+-]invbar // if +, appears in invbar; otherwise, invisible
[+-]keepdepleted // if +, will remain in inventory with amount of zero
[+-]fullamountonly // if +, cannot pickup unless full amount is needed
[+-]noshareware // if +, non-shareware

// artifacttype determines what sort of artifact this is.
artifacttype <str> // "Normal", "Ammo", "Key", "Puzzle", "Power", "Weapon",
// or "Quest"

// The following fields apply only to certain artifact types. They have no
// effect if specified on other types.

// Ammo
ammo.backpackamount <int> // amount of this ammo type given by a Backpack
ammo.backpackmaxamount <int> // max amount after collecting a Backpack

// Autouse health: this applies only for health-effect artifacts.
// If enabled, game will automatically trigger when player is about to die,
// to restore health and keep them alive.

// "none" or "heretic". If "heretic", this is enabled and works like Heretic
autouse.health.mode <option>

// Optional restrictions. If omitted, there is no game restriction. Otherwise,
// it can be a "|"-joined combination of "baby" and "deathmatch". Then the
// autouse will happen IF ANY of the given conditions are met.
autouse.health.restrict <flags>
}

====healtheffect====
A health effect gives the player health in one of many possible ways.
healtheffect <name>
{
amount <int> // amount of health to give
maxamount <int> // max amount this item can health to.
lowmessage <str> // alternate message to give instead of pickupfx message when
// health is less than amount; if starts with $, is a BEX mnemonic.

[+-]alwayspickup // if +, item is picked up even when unneeded (e.g. Health Bonus)
[+-]sethealth // if +, item SETS health rather than adding to it (e.g. Megasphere)
}

====armoreffect====
An armor effect defines the properties of player armor
armoreffect <name>
{
saveamount <int> // amount of armor given
savefactor <int> // numerator of fraction determining save percentage
savedivisor <int> // denominator of fraction determining save percentage
maxsaveamount <int> // max amount his item can give; if player has greater
// armor, the item cannot be picked up at all

[+-]alwayspickup // item is picked up even when unneeded (e.g. Armor Bonus)
[+-]additive // if +, adds to the current amount of armor
[+-]setabsorption // if +, sets absorption values (savefactor & savedivisor)
}
====ammoeffect====
Ammo givers give an Ammo type artifact to the player.
ammoeffect <name>
{
ammo <str> // Name of an Ammo-type artifact definition
amount <int> // Amount to give for an ordinary pickup
dropamount <int> // Amount to give if dropped by an enemy

[+-]ignoreskill // if +, does not double on skills that give double ammo
}
====powereffect====
Power givers buff the player with a temporary or level-permanent effect. They're typical of artifacts such as the radiation suit or the blur sphere.
powereffect <name>
{
duration <int> // Length of time to last in tics
type <str> // Name of power to give

[+-]additivetime // if +, adds to current duration
[+-]permanent // if +, lasts forever
[+-]overridesself // if +, getting the power again while still under its influence is allowed
}

'''Type''' can be any of the following:
*'''PowerAllmap''': Doom computer area map, Heretic map scroll
*'''PowerFlight''': Heretic wings of wrath
*'''PowerGhost''': Heretic shadow sphere
*'''PowerInvulnerable''': Doom invulnerability artifact, Heretic ring of invulnerability
*'''PowerIronFeet''': Doom radiation shielding suit
*'''PowerLightAmp''': Doom light amplification visor
*'''PowerPartialInvisibility''': Doom blur artifact
*'''PowerSilent''': Eternity silencer
*'''PowerStrength''': Doom berserk pack
*'''PowerTorch''': Heretic torch
*'''PowerTotalInvisibility''': Eternity total invisibility
*'''PowerWeaponLevel2''': Heretic tome of power

====weapongiver====
Weapon givers give a Weapon type artifact to the player, and optionally any number of Ammo artifact types.
weapongiver <name>
{
weapon <str> // Name of a weaponinfo to give to the player
// Note that you can specify as many ammogiven properties as you want in a single weapongiver
ammogiven <ammo>, <amount> [, <dropamount> [, <dmamount> [, <coopweaponsstay>]]] // Ammo type artifact given, and the amounts
// given based on how it was picked up. If the
// last three are left blank, only "amount" is used.
}

===Delta structures===
The following can be used to replace already defined effects. They can be cascaded (i.e. any number of loaded mods can change the previous definition and all its deltas). For each of them, the '''name''' field represents the name of the base to modify. They are the following:
healthdelta
{
name <name>
...
}

armordelta
{
name <name>
...
}

ammodelta
{
name <name>
...
}

powerdelta
{
name <name>
...
}

weapongiverdelta
{
name <name>
clearammogiven // if added, removes the "given ammo" definitions
...
}

artifactdelta
{
name <name>
...
}

[[Category:EDF]]

EDF puff type reference

2026-02-28T19:03:32Z

Printz: /* Explanation of fields */

Puffs are special effects spawned at hitscan attack impact points. Hitscan attacks are those 'projectiles' which travel instantly, which includes all gunshots from Doom and the elven wand and dragon claw from Heretic. The syntax is as follows:
pufftype <name> [ : <base> ]
{
thingtype <name>
sound <name>
hitsound <name>
hitpufftype <name>
nobloodpufftype <name>
upspeed <floating-point value>
zspread <floating-point value>
punchhack <frame name>
particles <number>
+|-PUFFONACTORS
+|-BLOODLESS
+|-LOCALTHRUST
+|-RANDOMTICS
+|-TARGETSHOOTER
}
==Explanation of fields==
*'''base'''
:Optional ancestor puff type whose attributes to inherit. If you don't want inheritance, remove both ':' and the base name.
*'''thingtype'''
:[[Thingtype|Class of thing]] to spawn when puff is produced. Can be omitted if no visible thing is intended.
*'''sound'''
:Optional sound to play when puff is spawned. Only works if '''thingtype''' is set. Example: the Heretic staff puff has this.
*'''hitsound'''
:Alternate sound to play if the hitscan hits a shootable thing, and if the puff is not replaced by a blood splat. Example: the dragon claw hit puff has this.
*'''hitpufftype'''
:If this one is set and a shootable thing is hit, use this alternate puff type instead of the one defined here. Example: the dragon claw spark has this. Important: this is a pufftype, not a thingtype.
*'''nobloodpufftype'''
:Optional alternate puff type when hitting things with the '''NOBLOOD''' flag. Note that this has priority over '''hitpufftype''' but only against '''NOBLOOD''' targets. Important: this is a pufftype, not a thingtype.
*'''upspeed'''
:Default: 0
:Speed by which the puff thing moves up.
*'''zspread'''
:Default: 4
:Vertical spread by which spawned things are randomly created.
*'''punchhack'''
:Limited use special handler for DOOM fist puff's special behaviour of switching to a different frame (as given by this field) when using the fist attack codepointer. New mods should use dedicated puff types for custom melee attacks.
*'''particles'''
:Optional number of smoke particles to spawn when enabled in the settings. Does not spawn if '''punchhack''' is active and player uses fist.
===Flags===
Prefix these with + or - to add or remove them.
*'''PUFFONACTORS''': make sure to spawn puff even when hitting a bleeding target. Common with Heretic hitscans.
*'''BLOODLESS''': avoid showing blood when hitting a bleeding target.
*'''LOCALTHRUST''': when hitting shootable things, make sure to thrust them from wherever the puff appears, not from attacker.
*'''RANDOMTICS''': if set, the spawned thing will have its first frame duration randomized
*'''TARGETSHOOTER''': sets puff thing's "target" (originator) to the shooter. In effect, it will act like a projectile explosion, and any codepointer such as [[DetonateEx]] or [[BFGSpray]] from the puff thing will use the shooter as an originator for damage purposes.

==Delta structure==
You can use <code>puffdelta</code> to modify an already defined '''pufftype'''. The syntax is:
puffdelta
{
name <puff name>
<fields>
}
The ''fields'' are the same as those from '''pufftype''', modifying anything already defined in a <code>pufftype <puff name></code> block.
==Tips==
*If you use the '''TARGETSHOOTER''' flag and intend to turn the puff into an explosion, beware that, as with all thing types, the explosion will fail if it's triggered from the very first spawn state. Make sure to use the second one onwards.
[[Category:EDF]]
[[Category:Editing]]

Polyobj MoveTo

2026-02-28T18:16:40Z

Printz: Created page with "{{template:LineSpecial|description=Moves a polyobject to given coordinates. |usage='''Polyobj_MoveTo(''po'', ''speed'', ''x'', ''y'') |parameters= *''po'': polyobject ID to move *''speed'': movement speed in eighths of unit per tic *''x'', ''y'': coordinates, in integer map units |examples= '''Polyobj_MoveTo(1, 8, -1024, 4192) |notes=This linedef special moves the targeted polyobject to a given location in coordinates, instead of using a map spot thing. Be careful, if in..."

{{template:LineSpecial|description=Moves a polyobject to given coordinates.
|usage='''Polyobj_MoveTo(''po'', ''speed'', ''x'', ''y'')
|parameters=
*''po'': polyobject ID to move
*''speed'': movement speed in eighths of unit per tic
*''x'', ''y'': coordinates, in integer map units
|examples=
'''Polyobj_MoveTo(1, 8, -1024, 4192)
|notes=This linedef special moves the targeted polyobject to a given location in coordinates, instead of using a map spot thing. Be careful, if in ACS, not to use fixed-point numbers (which internally are multiples of 65536).
|udmf=88
|extradata=497
}}

DeHackEd / BEX Reference/Eternity Extension: SOUNDS Block

2026-02-19T06:32:00Z

Printz: /* Syntax */

The SOUNDS block can change the name of any sound.
{{backto|DeHackEd / BEX Reference}}
==Syntax==
[SOUNDS]
<mnemonic> = <string>
The <mnemonic> to use is the EDF sound mnemonic defined for the sound you wish to replace. The string to provide is the new lump name for that sound. If you want to rename the sound that's normally named PISTOL, you use the mnemonic PISTOL. Changing the sound lump names will not change their corresponding mnemonics. <string> must be from 1 to 8 characters long, or the substitution will not occur.
[[category:dehacked]]
===DSDHacked extension===
If you have <code>Doom version = 2021</code> in the DEHACKED patch header, you can also use this syntax:
<number> = <lump_name>
where <number> is the Dehacked number of a possibly new sound entry (thus allowing you to declare new sounds), and <lump_name> is the name of the sound entry in the WAD.

DeHackEd / BEX Reference/Thing Block

2026-02-19T05:47:24Z

Printz: /* Syntax */

The DeHackEd Thing block allows you to edit the properties of DOOM's map object types. Map objects are what comprise anything you see with a sprite in DOOM, including enemies, powerups, missiles, decorations, and invisible control objects.

Eternity provides several extensions to the DeHackEd thing block, some of which are considered part of the BEX standard specification. Extended fields will be noted as such in their descriptions.
{{backto|DeHackEd / BEX Reference}}

==Syntax==
A brief explanation of the syntax description:

Items in angle brackets (< >) are required.

Items in square brackets ([ ]) are optional.

All fields in the block are optional. If a field is not provided, that value of the thing being edited will not change.

A || symbol means that the field can have one of the two listed types of values.

Thing <dehacked number> [(thing type name)]
ID # = <number>
Initial frame = <frame number>
Hit points = <number>
First moving frame = <frame number>
Alert sound = <sound number>
Reaction time = <number>
Attack sound = <sound number>
Injury frame = <frame number>
Pain chance = <number>
Pain sound = <sound number>
Close attack frame = <frame number>
Far attack frame = <frame number>
Death frame = <frame number>
Exploding frame = <frame number>
Death sound = <sound number>
Speed = <number>
Width = <number>
Height = <number>
Mass = <number>
Missile damage = <number>
Action sound = <sound number>
# The ability to provide flag lists is a BEX extension
Bits = <number || flag list>
Respawn frame = <frame number>
# The below fields are Eternity Engine extensions
Bits2 = <number || flag list>
Bits3 = <number || flag list>
Translucency = <number>
Blood color = <number>
Dropped item = <>
MBF21 Bits = <>
Fast speed = <>
Splash group = <>
Projectile group = <>
Infighting group = <>
Melee range = <>
Rip sound = <>

Explanation of special information:

'''dehacked number''' is the DeHackEd number of the thing type that this block edits. The DeHackEd number for a thing type is given in its EDF thingtype definition.

NOTE: for DSDHacked patches (annotated at the beginning with <code>Doom version = 2021</code>), new thing types can be defined which do not exist in EDF, by having a new '''dehacked number''', outside the normal range and missing from EDF thingtype definitions. Those new thing types will have EDF names in the form of <code>_AddDehThing###</code>, where <code>###</code> is this '''dehacked number'''. You can use such a name on the '''summon''' console command, for example.

'''(thing type name)''' is an optional string which gives a descriptive name to this block. This field is NOT used by Eternity, and can be left off. Its only purpose is to serve as a comment letting you better know which thing type you are editing.

==Fields==

====ID # = <number>====
Sets the id, or "doomednum", used to identify this thing type in maps. For example, when a map calls for a thing with id 2003, the game engine will find the thing type which has that number in this field. Every thing that will be spawned on maps must have a unique ID number. Things which are not spawned on maps, such as fireballs, can be given an ID of -1.

====Initial frame = <frame number>====
Sets the frame which a thing starts in when it is spawned. Monsters generally use this frame to stand still and look for targets. <frame number> must be a valid frame DeHackEd number.

====Hit points = <number>====
Sets a thing's maximum amount of life. It is only used for things which can be shot.

====First moving frame = <frame number>====
Sets the frame which a monster will jump to when it sees or hears a target. Also called walking frames.

====Alert sound = <sound number>====
Sets the sound that a monster will play when it awakens. This sound is also played by missiles when they are shot. <sound number> must be a valid sound number. See the sound number table for details.

====Reaction time = <number>====
Sets an amount of time that a thing must wait under certain circumstances. Monsters use this value as a means to control their rate of attack. This value is also used as an internal field for varying purposes, but those uses are not editable.

====Attack sound = <sound number>====
Sets a sound used by some monster attacks, including the Lost Soul's charge.

====Injury frame = <frame number>====
Sets the frame a thing may randomly enter when it has been injured.

====Pain chance = <number>====
Sets the chance out of 255 that this thing will enter its pain state when it is injured. A thing with 0 pain chance will never feel pain, whereas a thing with 255 pain chance will always feel pain. If a thing has a pain chance greater than zero, it should have a valid Injury frame, otherwise it will disappear forever.

====Pain sound = <sound number>====
Sets the sound played by the Pain codepointer when this thing uses it. Monsters and the player always call Pain from their Injury frames.

====Close attack frame = <frame number>====
If this frame is non-zero, monsters chasing a target will attempt to close to melee range quickly. When they determine they are within 64 units of their target, they may randomly enter this frame to perform a melee attack.

====Far attack frame = <frame number>====
If this frame is non-zero, monsters chasing a target will randomly enter it to perform a missile attack.

====Death frame = <frame number>====
When a thing dies normally, it will enter this state. If the state is zero, the thing will disappear forever.

====Exploding frame = <frame number>====
If a thing dies by taking enough damage that its health is equal to its negated Hit points value, it will enter this frame instead of its Death frame. This is also known as gibbing, or extreme death. If this frame is zero, the thing will always die normally.

====Death sound = <sound number>====
Sound played by the Scream codepointer. Used to play monster death sounds.

====Speed = <number>====
Value used by monsters as a movement delta per walking frame. The monster will move by an amount relative to this value each time it uses the Chase codepointer. For missiles, this value is a fixed-point number (multiplied by 65536), and represents a constant speed by which the missile advances every game tic. Missile speed is not affected by the missile frame durations, whereas monster walking speed is.

====Width = <number>====
Fixed-point value (multiplied by 65536) that represents the radius of this thing type. A thing can fit into corridors which are at least as wide as this value times two, plus one unit (ie a thing with radius 32 can fit into a 65-wide hallway). The maximum value this field *should* have is 2097152, which is equal to 32 units. However, the game breaks its own rule here, giving several monsters radii up to 128 units. These monsters, which include the mancubus, arachnotron, and spider demon, exhibit clipping errors which enable other things to walk into them, and which can cause some moving sectors to malfunction. Avoid giving things radii larger than this to remain absolutely safe.

====Height = <number>====
Fixed-point value that represents the height of this thing type. A thing can fit into areas which are of this exact height or taller. Note that in DOOM, this value is only used to see where a monster can fit. For purposes of clipping, monsters are considered to be infinitely tall. However, Eternity's extended 3D object clipping enables this field to also be used to allow or disallow things to pass over, under, or stand on this thing.

====Mass = <number>====
Normal integer value that serves as a mass factor for this object. Mass affects the amount of thrust an object is given when it is damaged, the amount of effect an archvile's attack can have on it, and for bouncing objects, the rate at which they fall.

====Missile damage = <number>====
This number is used as a damage multiplier when a missile hits a thing. The damage formula used is:
damage = ((rnd % 8) + 1) * missiledamage

This field is also used as a parameter by some new, parameterized codepointers, including BetaSkullAttack and Detonate.

====Action sound = <sound number>====
Sets the sound used by a thing when it is wandering around. A thing is given a 3 out of 256 chance (1.17%) of making this sound every time it calls the Chase codepointer. There are some new Bits3 flags which can alter the behavior of this sound.

====Bits = <number || flag list>====
This field controls a number of thing type properties using bit flags, where each bit in the field stands for some effect, and has the value of being either on or off. In old DeHackEd patches, this field is an integer number. BEX Extensions allow a human-readable string of flag values to be provided instead. See the flag field lists below for more information.

====Bits2 = <number || flag list>====
Similar to Bits but takes a different set of values with different meanings. This field is an Eternity extension. See below for more information.

====Bits3 = <number || flag list>====
Similar to Bits but takes a different set of values with different meanings. This field is an Eternity extension. See below for more information.

====Respawn frame = <frame number>====
If this frame is non-zero, an Archvile can perform a resurrection on this creature. When this occurs, the creature will enter this frame.

====Translucency = <number>====
This field is an Eternity extension which allows fine, customizable control over a thing's translucency. The value of this field may range from 0 to 65536, with 0 being completely invisible, and 65536 being normal. Consider the following example:
Thing 2 (Trooper)
Translucency = 32768

Trooper objects will be 50% translucent in this example, since 32768 is half of 65536. Note this effect is mutually exclusive of BOOM-style translucency. If this value is not 65536, and the BOOM translucency flag is turned on, the flag will be turned off at run-time, and this field will take precedence.

====Blood color = <number>====
This field is an Eternity extension. Allows this thing type to have differently colored blood when particle blood effects are enabled (this does not currently have any effect on blood sprites). Currently available blood color values are as follows:
Blood color Number
--------------------------
Red (normal) 0
Grey 1
Green 2
Blue 3
Yellow 4
Black 5
Purple 6
White 7
Orange 8
--------------------------

====Dropped item = <number>====
Sets the dropped item to the thingtype identified by given dehacked number.

====MBF21 Bits = <number or flag set>====
Applies the following bits from MBF21, possibly replacing existing Eternity flags. It can either be a sum of the numbers or |, ",", + joined list of the following bits:
*LOGRAV (1): low gravity
*SHORTMRANGE (2): short missile range
*DMGIGNORED (4): other things ignore its attacks
*NORADIUSDMG (8): doesn't take splash damage
*FORCERADIUSDMG (16): causes splash damage even if target immune
*HIGHERMPROB (32): higher missile attack probability
*RANGEHALF (64): use half distance for missile attack probability
*NOTHRESHOLD (128): no targeting threshold
*LONGMELEE (256): revenant proximity shyness
*BOSS (512): full volume see / death sound + splash immunity
*MAP07BOSS1 (1024): tag 666 "boss" on DOOM 2 MAP07
*MAP07BOSS2 (2048): tag 667 "boss" on DOOM 2 MAP07
*E1M8BOSS (4096)
*E2M8BOSS (8192)
*E3M8BOSS (16384)
*E4M6BOSS (32768)
*E4M8BOSS (65536)
*RIP (131072): projectile rips through targets
*FULLVOLSOUND (262144): full volume see / death sound

====Fast speed = <number>====
Sets a thing's fast speed, such as for Nightmare! mode projectiles.

====Melee range = <number>====
Sets a thing's melee attack range.

====Rip sound = <number>====
A projectile's sound as it rips through targets.

====Splash group = <number>====
Adds this thing to a [[thinggroup]] identified by a unique number with flag '''NOSPLASHDAMAGE'''. Objects with this value will not take any radius (explosion) damage from any inflictor objects with the same value. For example: monsters and rockets.

====Infighting group = <number>====
Adds this thing to a [[thinggroup]] identified by a unique number with flag '''DAMAGEIGNORE'''. In addition, it gets '''NOSPECIESINFIGHT''' thingtype flag. This makes this monster never enter infights with its own kind an none other species sharing this value.

====Projectile group = <number>====
If <number> is 0 or positive: adds this thing to a [[thinggroup]] identified by a unique number with flag '''PROJECTILEALLIANCE'''. All monsters sharing this value will be immune to projectiles shot by any other monsters.

If <number> is negative, then it gets the '''HARMSPECIESMISSILE''' flag, which means the monster gets affected by projectiles from same species.

==BEX Extension: Thing Flag Lists==
This is actually something you can use to hack your DeHackEd file to be more understandable and modifiable. Note that once you do this you won't be able to bring it back into DeHackEd.

If you've altered a thing's bits at all, you'll see a line like:
Bits = 205636102
That horrible number is why we are providing some mnemonics instead. All you need to do is to put the appropriate ones of the following mnemonics on the line where the big number is, and it'll be read in and converted to the number for you. Some valid example lines:
Bits = SOLID+SHOOTABLE+NOBLOOD
...
Bits = NOBLOCKMAP | NOGRAVITY
...
Bits = SPECIAL, COUNTITEM
which converts to Bits = 524294 but you didn't have to figure that part out. Just use a plus, '|', comma, or whitespace between the mnemonics. Below are mnemonic lists, along with a bit of explanation of each, and the phrase that's used in Dehacked to describe them. If there are any disagreements between the 2 definitions, ours wins.

==Bits Mnemonics==
Mnemonic Bit mask Meaning / Dehacked phrase
------------------------------------------------------------------
SPECIAL 0x00000001 - Object is a collectable item.
"Can be picked up"
SOLID 0x00000002 - Blocks other objects.
"Obstacle"
SHOOTABLE 0x00000004 - Can be targetted and hit with bullets, missiles.
"Shootable"
NOSECTOR 0x00000008 - Invisible but still clipped -- see notes.
"Total invisibility"
NOBLOCKMAP 0x00000010 - Inert but displayable; can hit but cannot be hit.
"Can't be hit"
AMBUSH 0x00000020 - Deaf monster.
"Semi-deaf"
JUSTHIT 0x00000040 - Internal, monster will try to attack immediately; see notes.
"In pain"
JUSTATTACKED 0x00000080 - Internal, monster takes at least 1 step before attacking; see notes.
"Steps before attack"
SPAWNCEILING 0x00000100 - Thing spawns hanging from the ceiling of its sector.
"Hangs from ceiling"
NOGRAVITY 0x00000200 - Thing is not subject to gravity.
"No Gravity"
DROPOFF 0x00000400 - Thing can walk over tall dropoffs (> 24 units).
"Travels over cliffs"
PICKUP 0x00000800 - Thing can pick up items -- see notes.
"Picks up items"
NOCLIP 0x00001000 - Thing is not clipped, can walk through walls.
"No clipping"
SLIDE 0x00002000 - No effect -- see notes.
"Slides along walls"
FLOAT 0x00004000 - Monster may move to any height; is flying.
"Floating"
TELEPORT 0x00008000 - Don't cross lines or look at teleport heights.
"Semi-no clipping"
MISSILE 0x00010000 - Thing is a missile, explodes and inflicts damage when blocked.
"Projectiles"
DROPPED 0x00020000 - Internal, item was dropped by a creature and won't respawn.
"Disappearing weapon"
SHADOW 0x00040000 - Use fuzz draw effect like spectres, also causes aiming inaccuracy.
"Partial invisibility"
NOBLOOD 0x00080000 - Object puffs instead of bleeds when shot.
"Puffs (vs. bleeds)"
CORPSE 0x00100000 - Internal, object is dead and will slide down steps.
"Sliding helpless"
INFLOAT 0x00200000 - Internal, monster is floating but not to target height -- see notes.
"No auto-leveling"
COUNTKILL 0x00400000 - Can be targetted, adds 1 to kill percent when it dies -- see notes.
"Affects Kill %"
COUNTITEM 0x00800000 - Item adds 1 to item percent when collected.
"Affects Item %"
SKULLFLY 0x01000000 - Internal, special handling for flying skulls -- see notes.
"Running"
NOTDMATCH 0x02000000 - Thing will not be spawned at level start when in Deathmatch.
"Not in deathmatch"
TRANSLATION1 0x04000000 - Use translation table for color (players)'.
(aka TRANSLATION) "Color 1 (gray/red)"

TRANSLATION2 0x08000000 - Second bit for color translation;
(aka UNUSED1) "Color 2 (brown/red)"

TOUCHY 0x10000000 - Thing dies on contact with any solid object of another species;
(aka UNUSED2) MBF Extension, see notes.

BOUNCES 0x20000000 - Thing may bounce off walls and ceilings;
(aka UNUSED3) MBF Extension, see notes.

FRIEND 0x40000000 - All things of this type are allied with player;
(aka UNUSED4) MBF Extension.

TRANSLUCENT 0x80000000 - Apply BOOM-style translucency to sprite;
BOOM Extension, see notes.
------------------------------------------------------------------
Notes on Bits values:

====NOSECTOR:====
This flag has some odd side effects. For a pure total invisibility effect, use the new DONTDRAW flag in the Bits2 field.
====JUSTHIT:====
This flag is for internal AI use, applying it to a thing will have more or less no effect.
==== JUSTATTACKED:====
As above.
==== PICKUP:====
Only the player should possess this flag. If monsters try to pick up items, results will be undefined. This may change in the future.
==== SLIDE:====
This flag has absolutely no effect and is never used anywhere. For compatibility, it must remain this way. A new flag, SLIDE, in the Bits3 field, DOES have this effect, however, and is used by the player object and Heretic pods, by default.
==== INFLOAT:====
This flag is for internal AI use only.
==== COUNTKILL:====
This flag actually has two effects. If a monster does not have the COUNTKILL flag, other monsters may ignore it, and some other engine features will not work properly for it. This is generally undesirable. A new Bits3 flag KILLABLE, used by the Lost Soul by default, allows monsters to behave normally even without having this flag.
==== SKULLFLY:====
This flag is for internal AI use only.
==== TOUCHY:====
This new MBF extension allows things to instantly die if any solid thing of a differing species touches it. Note that for purposes of this effect, Lost Souls and Pain Elementals are considered to be the same species.
==== BOUNCES:====
This flag declares that the thing is bouncy. The exact behavior of the thing can be modified by combining this with other flags in the following manners:
==== BOUNCES + MISSILE:====
Object bounces off of floors and ceilings only.
==== BOUNCES + NOGRAVITY:====
Object bounces off all surfaces without losing momentum, unless its also a missile.
==== BOUNCES + FLOAT:====
Without NOGRAVITY, allows monsters to jump to reach their target.
==== BOUNCES + FLOAT + DROPOFF:====
Allows even higher bouncing / jumping.
==== BOUNCES:====
When the flag is alone, without MISSILE, it allows the object to bounce off all surfaces, losing momentum at each contact. It can also roll up and down steps. This is highly realistic.
==== TRANSLUCENT:====
This thing will use the global BOOM translucency level for its sprite. If general translucency is off, it will draw normally. This effect is mutually exclusive with the new Eternity extension for translucency. If the latter is enabled, this flag will be turned off by the game at run-time.

==Bits2 Mnemonics (Eternity extension)==
Mnemonic Bit mask Meaning
------------------------------------------------------------------
LOGRAV 0x00000001 - Thing experiences low gravity; see notes.

NOSPLASH 0x00000002 - Thing cannot trigger TerrainTypes.

NOSTRAFE 0x00000004 - Thing never uses advanced strafing logic.

NORESPAWN 0x00000008 - Thing will not respawn in nightmare mode.

ALWAYSRESPAWN 0x00000010 - Thing will respawn at any difficulty level.

REMOVEDEAD 0x00000020 - Thing removes itself shortly after death; see notes.

NOTHRUST 0x00000040 - Thing is unaffected by push/pull, wind, current, or conveyors.

NOCROSS 0x00000080 - Thing cannot trigger crossable special lines.

JUMPDOWN 0x00000100 - Thing, when friendly, can jump down to follow player.

PUSHABLE 0x00000200 - Thing is pushable by other moving things.

MAP07BOSS1 0x00000400 - Thing must be dead for MAP07 tag 666 special.

MAP07BOSS2 0x00000800 - Thing must be dead for MAP07 tag 667 special.

E1M8BOSS 0x00001000 - Thing must be dead for E1M8 tag 666 special.

E2M8BOSS 0x00002000 - Thing must be dead for E2M8 end-level special.

E3M8BOSS 0x00004000 - Thing must be dead for E3M8 end-level special.

BOSS 0x00008000 - Thing is a boss; roars loud and is invincible to blast radii.

E4M6BOSS 0x00010000 - Thing must be dead for E4M6 tag 666 special.

E4M8BOSS 0x00020000 - Thing must be dead for E4M8 tag 666 special.

FOOTCLIP 0x00040000 - Thing lowers when on liquid terrain.

FLOATBOB 0x00080000 - Thing floats up and down on z axis.

DONTDRAW 0x00100000 - Thing is totally invisible; enemies cannot see player.

SHORTMRANGE 0x00200000 - Thing has a shorter than normal missile range.

LONGMELEE 0x00400000 - Thing has a longer than normal melee range.

RANGEHALF 0x00800000 - Thing considers itself to be half as far from target.

HIGHERMPROB 0x01000000 - Thing has a higher missile attack probability.

CANTLEAVEFLOORPIC
0x02000000 - Thing can only move into sectors with the same flat.

SPAWNFLOAT 0x04000000 - Thing spawns with a randomized z coordinate.

INVULNERABLE 0x08000000 - Thing is invulnerable to damage less than 10000 points.

DORMANT 0x10000000 - Thing is invulnerable and inert until activated by script; see notes.

SEEKERMISSILE 0x20000000 - Indicates that this thing may be used as a homing missile; see notes.

DEFLECTIVE 0x40000000 - When paired with REFLECTIVE, thing will reflect at a wide angle.

REFLECTIVE 0x80000000 - Thing reflects missile projectiles; see notes.
------------------------------------------------------------------
Notes on Bits2 values:

==== LOGRAV:====
Has no effect on BOUNCY things
==== REMOVEDEAD:====
Things with this flag also cannot respawn in Nightmare mode. Do not give the player this flag.
==== DORMANT:====
Does not function as expected unless a thing is spawned on the map at startup with the DORMANT mapthing flag set in the level itself. It cannot be switched on and off freely.
==== SEEKERMISSILE:====
This flag is used by reflection code to check if a missile is being used as a homing missile. When a homing missile with this flag is reflected, its tracer target will be set to the thing that fired it, so that it will properly home on its originator instead of its original target.
==== REFLECTIVE:====
Does not impart invulnerability, and unless paired with that flag, the object will take damage before bouncing the projectile back.
==Bits3 Mnemonics (Eternity extension)==
Mnemonic Bit mask Meaning
------------------------------------------------------------------
GHOST 0x00000001 - Thing is a Heretic-style ghost; enemies may not see player.

THRUGHOST 0x00000002 - Missiles with this flag pass through GHOST objects.

NODMGTHRUST 0x00000004 - Things aren't thrusted when damaged by this thing.

ACTSEESOUND 0x00000008 - Thing may make see sound instead of active sound; 50% chance.

LOUDACTIVE 0x00000010 - Thing makes its active sound at full volume.

E5M8BOSS 0x00000020 - Thing is a boss on Heretic level E5M8.

DMGIGNORED 0x00000040 - Other things will not fight this thing if damaged by it.

BOSSIGNORE 0x00000080 - Things won't fight other species with this flag.

SLIDE 0x00000100 - Thing can slide against walls; see notes.

TELESTOMP 0x00000200 - Thing can telefrag other things.

WINDTHRUST 0x00000400 - Thing is affected by Heretic-style wind sectors; see notes.

FIREDAMAGE 0x00000800 - Reserved; currently has no effect.

KILLABLE 0x00001000 - Thing doesn't count for kill %, but is still an enemy; see notes.

DEADFLOAT 0x00002000 - Flying thing won't drop to the ground when killed.

NOTHRESHOLD 0x00004000 - Thing has no threshold for acquiring a new target.

FLOORMISSILE 0x00008000 - Missile can step up/down any height changes when on ground.

SUPERITEM 0x00010000 - Item respawns only if the "super items respawn" DMFLAG is on.

NOITEMRESP 0x00020000 - Item never respawns, and will not be crushed.

SUPERFRIEND 0x00040000 - Thing never attacks other friends when friendly.

INVULNCHARGE 0x00080000 - Thing is invulnerable when SKULLFLY flag is set.

EXPLOCOUNT 0x00100000 - Missile will not explode if Counter 1 < Counter 2.
Counter 1 will be incremented at each explosion attempt.

CANNOTPUSH 0x00200000 - Thing cannot push things with the PUSHABLE flag.

TLSTYLEADD 0x00400000 - Thing uses additive translucency style.

SPACMONSTER 0x00800000 - Thing can activate parameterized line specials which bear
the MONSTER activation flag.

SPACMISSILE 0x01000000 - Thing can activate parameterized line specials which bear
the MISSILE activation flag.

NOFRIENDDMG 0x02000000 - Thing will not be damaged by things with the FRIEND flag.

3DDECORATION 0x04000000 - Thing is a decoration which, when 3D object clipping is
active, will NOT use its corrected height, even if one
is specified in its EDF thingtype definition.

ALWAYSFAST 0x08000000 - Thing has -fast/Nightmare mode attack speed behavior in
any difficulty level.

PASSMOBJ 0x10000000 - Thing is fully treated with respect to 3D object clipping.
All monsters and other moving solid things should have this
flag.

DONTOVERLAP 0x20000000 - This thing type prefers not to overlap with other things
vertically when possible.
------------------------------------------------------------------
Notes on Bits3 values:

====SLIDE:====
As noted in the documentation for Bits flag SLIDE, it does nothing. This flag, however, actually works, and is used by the player and by Heretic pods.
==== WINDTHRUST:====
This controls only which things are affected by the new Heretic wind special, controlled by control linedef type 293. Any thing type with this flag will experience thrust relative to the angle and magnitude of the control linedef when it is anywhere within a tagged sector.
==== KILLABLE:====
As noted in the documentation for Bits flag COUNTKILL, enemies without that flag normally suffer severe side-effects. This new flag generalizes what was previously a special case for the Lost Soul, and allows enemies which don't count toward the kill percentage to be otherwise normal.
[[Category:dehacked]]

A BulletAttack

2026-02-16T16:14:31Z

Printz:

{{codepointer|description=Powerful codepointer which allows construction of custom monster bullet attacks. This pointer is capable of emulating any of the built-in player or monster bullet attacks, as well creating many completely new ones (including a super shotgun attack for monsters).|usage='''BulletAttack'''(''sound'', ''accuracy'', ''number'', ''factor'', ''modulus'', ''pufftype'')
|parameters=*sound = name or Dehacked number of sound to play (default of 0 = no sound)
*accuracy = Select accuracy (default of 0 = 1)
**1 or '''ba_always''' = Always accurate
**2 or '''ba_never''' = Never accurate (moderate horizontal spread with no vertical error)
**3 or '''ba_ssg''' = Super Shotgun accuracy (wide horizontal spread with moderate vertical error)
**4 or '''ba_monster''' = Monster accuracy (very wide horizontal spread)
*number = Number of bullet tracers to fire (default of 0 = 0)
*factor = Damage factor (Damage formula is: <code>factor * (rnd() % modulus + 1)</code>)
*modulus = Damage modulus (Forced into range of 1 to 256)
*pufftype = name of EDF [[pufftype]] to use when hitting walls. Default type is the one designated for the game.
|notes=The accuracy parameter for this pointer differs slightly from the Args2 parameter to the [[FireCustomBullets]] player codepointer. The value which allows "first fire only" accuracy is not available for monsters.

This codepointer is specific for Eternity. For the one from the MBF21 standard, see [[MonsterBulletAttack]].
|seealso=
*[[MissileAttack]]
*[[MonsterBulletAttack]]}}

A BulletAttack

2026-02-16T16:14:05Z

Printz:

{{codepointer|description=Powerful codepointer which allows construction of custom monster bullet attacks. This pointer is capable of emulating any of the built-in player or monster bullet attacks, as well creating many completely new ones (including a super shotgun attack for monsters).|usage='''BulletAttack'''(''sound'', ''accuracy'', ''number'', ''factor'', ''modulus'', ''pufftype'')
|parameters=*sound = name or Dehacked number of sound to play (default of 0 = no sound)
*accuracy = Select accuracy (default of 0 = 1)
**1 or '''ba_always''' = Always accurate
**2 or '''ba_never''' = Never accurate (moderate horizontal spread with no vertical error)
**3 or '''ba_ssg''' = Super Shotgun accuracy (wide horizontal spread with moderate vertical error)
**4 or '''ba_monster''' = Monster accuracy (very wide horizontal spread)
*number = Number of bullet tracers to fire (default of 0 = 0)
*factor = Damage factor (Damage formula is: <code>factor * (rnd() % modulus + 1)</code>)
*modulus = Damage modulus (Forced into range of 1 to 256)
*pufftype = name of EDF [[pufftype]] to use when hitting walls. Default type is the one designated for the game.
|notes=The accuracy parameter for this pointer differs slightly from the Args2 parameter to the [[FireCustomBullets]] player codepointer. The value which allows "first fire only" accuracy is not available for monsters.

This codepointer is specific for Eternity. For the one from the MBF21, see [[MonsterBulletAttack]].
|seealso=
*[[MissileAttack]]
*[[MonsterBulletAttack]]}}

MonsterBulletAttack

2026-02-16T16:12:34Z

Printz:

{{codepointer|
description=Generic monster bullet attack. This is from the MBF21 standard.
|usage='''MonsterBulletAttack(''horizontal_spread'', ''vertical_spread'', ''number_of_bullets'', ''base_damage'', ''random_multiplier'')
|parameters=
*''horizontal_spread'': in degrees (accepts decimal point). Default: 0 (perfectly precise horizontally)
*''vertical_spread'': in degrees (accepts decimal point). Default: 0 (perfectly precise vertically)
*''number_of_bullets'': how many bullet tracers to fire. Default: 1
*''base_damage'': base damage of attack, which will be multiplied by 1 up to ''random_multiplier'' inclusive. Default: 3
*''random_multiplier'': maximum multiplier of ''base_damage''. Default: 5. Must not be 0.
|notes=
The damage formula is ''base_damage'' * random(1, ''random_multiplier'').
|seealso=
*[[BulletAttack]]}}

A BulletAttack

2026-02-16T16:11:27Z

Printz:

{{codepointer|description=Powerful codepointer which allows construction of custom monster bullet attacks. This pointer is capable of emulating any of the built-in player or monster bullet attacks, as well creating many completely new ones (including a super shotgun attack for monsters).|usage='''BulletAttack'''(''sound'', ''accuracy'', ''number'', ''factor'', ''modulus'', ''pufftype'')
|parameters=*sound = name or Dehacked number of sound to play (default of 0 = no sound)
*accuracy = Select accuracy (default of 0 = 1)
**1 or '''ba_always''' = Always accurate
**2 or '''ba_never''' = Never accurate (moderate horizontal spread with no vertical error)
**3 or '''ba_ssg''' = Super Shotgun accuracy (wide horizontal spread with moderate vertical error)
**4 or '''ba_monster''' = Monster accuracy (very wide horizontal spread)
*number = Number of bullet tracers to fire (default of 0 = 0)
*factor = Damage factor (Damage formula is: <code>factor * (rnd() % modulus + 1)</code>)
*modulus = Damage modulus (Forced into range of 1 to 256)
*pufftype = name of EDF [[pufftype]] to use when hitting walls. Default type is the one designated for the game.
|notes=The accuracy parameter for this pointer differs slightly from the Args2 parameter to the [[FireCustomBullets]] player codepointer. The value which allows "first fire only" accuracy is not available for monsters.
|seealso=
*[[MonsterBulletAttack]]
*[[MissileAttack]]}}

UDMF

2026-02-15T18:28:05Z

Printz: /* Explanation of fields */

UDMF is the extensible format that replaces the classic Doom format and [[ExtraData]]. Each level, instead of being defined by the classic lumps (THINGS, LINEDEFS, SIDEDEFS etc.) is defined by a human-readable lump named TEXTMAP, and can have associated lumps (e.g. ZNODES, BLOCKMAP, REJECT if needed) and other lumps, until a marker lump named ENDMAP.

TEXTMAP has a well-defined language. Check the UDMF article at doomwiki.org. Each game and port has its own namespace(s), for example we have these namespaces: "doom", "heretic", "hexen", "strife", "zdoom" and others. Eternity has the "eternity" namespace.

At its core, UDMF is made of many blocks, each titled "vertex", "sector", "sidedef", "linedef", "thing" and containing several properties, some mandatory, others optional. Each game or port namespace can define its own set, which is typically hard-coded, though it's also possible for the user to add their own fields (which have to be preceded by a safe prefix, to avoid conflicts with the standard).

Maps designed in UDMF no longer need ExtraData.

The standard was defined by James "Quasar" Haley and has also been successfully implemented in Vavoom, ZDoom and the ZDoom-derivative ports.

* See also the [https://www.doomworld.com/eternity/engine/stuff/udmf11.txt base UDMF specifications]

==Basics==

Eternity supports the "doom" and "eternity" namespaces. In the rest of this article, we'll detail the "eternity" namespace. See the [https://www.doomworld.com/eternity/engine/stuff/udmf11.txt base UDMF specifications] for the options not detailed in this document.

A TEXTMAP for Eternity must start with this:
namespace = "eternity";

===Eternity compatibility===
You can also add the following field in UDMF TEXTMAP:
ee_compat = true;
which, no matter the namespace used (e.g. "zdoom"), assumes the map is going to work in Eternity. In other words, it is equivalent to setting namespace as "eternity". Any fields not supported by Eternity, however, may make the mod fail.

===Node format===

Nodes for UDMF use the uncompressed GL-nodes format under the ZNODES name. Tools such as ZDBSP should build such a lump upon detecting a TEXTMAP lump.

==Linedefs==
linedef
{
blocklandmonsters = <boolean>;
blockplayers = <boolean>;

polycross = <boolean>;
monstershoot = <boolean>;

midtex3d = <boolean>;
firstsideonly = <boolean>;
blockeverything = <boolean>;
zoneboundary = <boolean>;
clipmidtex = <boolean>;
midtex3dimpassible = <boolean>;
lowerportal = <boolean>;
upperportal = <boolean>;

portal = <integer>;

alpha = <floating-point>; // default 1.0
renderstyle = <string>;
tranmap = <string>;
}
===Explanation of fields===
*'''blocklandmonsters'''
:If true, linedef blocks walking monsters but allows fliers to pass. Players can pass anyway.
*'''blockplayers'''
:If true, linedef blocks players but allows monsters and projectiles to pass.
*'''polycross'''
:If true, linedef is activated when a polyobject's center point crosses it.
*'''monstershoot'''
:If true, linedef is activated when a monster fires hitscan on it.
*'''midtex3d'''
:If true, this linedef's middle texture uses [[3DMidTex_tutorial|3dmidtex]] physics.
*'''firstsideonly'''
:Linedef can only be activated from front side.
*'''blockeverything'''
:Linedef blocks all objects, acting like an external solid wall
*'''zoneboundary'''
:Linedef acts like a boundary for [[EDF_sound_reference#Sound_environments|reverb]] effects.
*'''clipmidtex'''
:Middle texture is clipped against the floor or ceiling as if a light change took place.
*'''midtex3dimpassible'''
:Treat the 3dmidtex line as a classic impassable middle texture, with regards to projectiles (i.e. they will pass through, just like hitscans).
*'''lowerportal''', '''upperportal'''
:Apply [[edge portals|edge portal]] on the lower or upper part of this linedef, copying back sector's floor or ceiling portal into it.
*'''portal'''
:The ID of the portal to apply on this linedef, as defined from [[Portal_Define]]
*'''alpha''' (default: 1.0)
:Opacity of this line.
*'''renderstyle'''
:Either "translucent" or "add". Default is "".
*'''tranmap'''
:Boom [[translucency map]]. Mutually exclusive with alpha and renderstyle.

==Sidedefs==
sidedef
{
offsetx = <floating-point>;
offsety = <floating-point>;
offsetx_top = <floating-point>;
offsety_top = <floating-point>;
offsetx_mid = <floating-point>;
offsety_mid = <floating-point>;
offsetx_bottom = <floating-point>;
offsety_bottom = <floating-point>;

light = <integer>;
lightabsolute = <boolean>;
light_top = <integer>;
lightabsolute_top = <boolean>;
light_mid = <integer>;
lightabsolute_mid = <boolean>;
light_bottom = <integer>;
lightabsolute_bottom = <boolean>;

skew_top_type = <string>;
skew_middle_type = <string>;
skew_bottom_type = <string>;
}

===Explanation of fields===
*'''offsetx''', '''offsety'''
:Overall horizontal and vertical offsets for the top, middle, and bottom textures of this sidedef.
*'''offsetx_top''', '''offsety_top''', '''offsetx_mid''', '''offsety_mid''', '''offsetx_bottom''', '''offsety_bottom'''
:Horizontal and vertical offsets for the individual top, middle, and bottom portions of this sidedef.
*'''light''', '''light_top''', '''light_mid''', '''light_bottom''', '''lightabsolute''', '''lightabsolute_top''', '''lightabsolute_mid''', '''lightabsolute_bottom'''
:Brightness for the whole, and the individual top, middle, and bottom portions of this sidedef. By default the values are additive to the inherited brightness. If the "absolute" properties are set to "true" the values are not additive anymore, but absolute.
*'''skew_top_type''', '''skew_bottom_type''', '''skew_middle_type'''
:The type of skewing that the a given texture of this sidedef has. This skew starts at the left side of the sidedef (if viewing the sidedef straight-on) and conforms to either the slope on the front or back side of the line the sidedef is on. Either the floor or ceiling slope can be picked as the slope for the skewing to conform to. Values are "none", "front_floor", "front_ceiling", "back_floor", and "back_ceiling", with "none" being the default.

==Vertices==
No change yet from the base "doom" namespace.
==Sectors==
sector
{
heightfloor = <floating-point>;
heightceiling = <floating-point>;

xpanningfloor = <floating-point>;
ypanningfloor = <floating-point>;
xpanningceiling = <floating-point>;
ypanningceiling = <floating-point>;

xscalefloor = <floating-point>;
yscalefloor = <floating-point>;
xscaleceiling = <floating-point>;
yscaleceiling = <floating-point>;
rotationfloor = <floating-point>;
rotationceiling = <floating-point>;

secret = <boolean>;
friction = <integer>;

leakiness = <integer>;
damageamount = <integer>;
damageinterval = <integer>;
damage_endgodmode = <boolean>;
damage_exitlevel = <boolean>;
damageterraineffect = <boolean>;
damagetype = <string>;

floorterrain = <string>;
ceilingterrain = <string>;

lightfloor = <integer>;
lightceiling = <integer>;
lightfloorabsolute = <boolean>;
lightceilingabsolute = <boolean>;

phasedlight = <boolean>;
lightsequence = <boolean>;
lightseqalt = <boolean>;

colormaptop = <string>;
colormapmid = <string>;
colormapbottom = <string>;

scroll_ceil_x = <floating-point>;
scroll_ceil_y = <floating-point>;
scroll_ceil_type = <string>;
scroll_floor_x = <floating-point>;
scroll_floor_y = <floating-point>;
scroll_floor_type = <string>;

floorid = <integer>;
ceilingid = <integer>;
attachfloor = <integer>;
attachceiling = <integer>;

soundsequence = <string>;

portalfloor = <integer>;
portalceiling = <integer>;

portal_floor_disabled = <boolean>;
portal_floor_norender = <boolean>;
portal_floor_nopass = <boolean>;
portal_floor_blocksound = <boolean>;
portal_floor_useglobaltex = <boolean>;
portal_floor_overlaytype = <string>;
alphafloor = <floating-point>;
portal_floor_attached = <boolean>;

portal_ceil_disabled = <boolean>;
portal_ceil_norender = <boolean>;
portal_ceil_nopass = <boolean>;
portal_ceil_blocksound = <boolean>;
portal_ceil_useglobaltex = <boolean>;
portal_ceil_overlaytype = <string>;
alphaceiling = <floating-point>;
portal_ceil_attached = <boolean>;
}

=== Explanation of fields ===
*'''heightfloor''', '''heightceiling''' (mandatory)
:Unlike the base field from the core specs, these ones allow floating-point values.
*'''xpanningfloor''', '''ypanningfloor''', '''xpanningceiling''', '''ypanningceiling'''
:These properties control the panning of the floor or ceiling flat.
*'''xscalefloor''', '''yscalefloor''', '''xscaleceiling''', '''yscaleceiling''' (default: 1.0)
:These properties control the scaling of the floor or ceiling flat. Greater values result in smaller textures.
*'''rotationfloor''', '''rotationceiling'''
:These properties control the clockwise rotation of the floor or ceiling flat, in degrees.
*'''secret'''
:If true, the sector counts as a secret when visited by player.
*'''friction''' (default: -1)
:This one controls the friction of movement on the floor. The value of this field is equivalent to the length of a horizontal linedef with the classic Boom friction special. Default value: -1 (use usual Doom friction).
*'''leakiness'''
:This one controls the probability that, if this sector is also damaging, it will leak damage through the radiation suit. As reference, the classic Doom 20% sector has 5 leakiness. For damage which always goes through the suit, use 256.
*'''damageamount'''
:Damage per hit for players on the floor.
*'''damageinterval'''
:Time between hits. The classic Doom damaging floors use a 32 period.
*'''damage_endgodmode'''
:If true, it will cause the damaging floor to disable the godmode cheat.
*'''damage_exitlevel'''
:If true, it will cause the damaging floor to exit the level in victory if the player has too little health.
*'''damageterraineffect'''
:If true, then each damage hit will produce a splash, like the Heretic lava.
*'''damagetype''' (default: "Unknown")
:The [[damagetype|damage type]] of the floor. For Doom damaging floors you can use "Slime".
*'''floorterrain''' (default: "@flat")
:The [[terrain]] effect of the floor.
*'''ceilingterrain''' (default: "@flat")
:The [[terrain]] effect of the ceiling. Currently used for particle recolouring.
*'''lightfloor''', '''lightceiling'''
:The light amount to add to the floor or ceiling, relative to the designated light level.
*'''lightfloorabsolute''', '''lightceilingabsolute'''
:If true, then '''lightfloor''' or '''lightceiling''' just overrides the light.
* phasedlight = <boolean>;
:Equivalent to ExtraData flag.
* lightsequence = <boolean>;
:Equivalent to ExtraData flag.
* lightseqalt = <boolean>;
:Equivalent to ExtraData flag.
*'''colormaptop''', '''colormapmid''', '''colormapbottom''' (default: "@default")
:The colormap to set for the top, normal or bottom part of a Boom sector with fake flats. Or for any normal part, if it's '''colormapmid'''. Use a lump from between '''C_START''' and '''C_END'''. "WATERMAP" and "LAVAMAP" are provided by Eternity.
*'''scroll_ceil_x''', '''scroll_ceil_y''', '''scroll_floor_x''', '''scroll_floor_y'''
:These fields make the sector ceiling or floor scroll at startup. The values you input there are the equivalents of a Boom trigger linedef length divided by 10. So to emulate a linedef pointing east of length 64 having a scroll trigger, set value 6.4 on '''scroll_ceil_x''' or '''scroll_floor_x'''.
*'''scroll_ceil_type''', '''scroll_floor_type''' (default: "none")
:These fields control the kind of scrolling for each surface and can be: "none" (no scrolling enabled), "visual" (only scroll the texture), "physical" (only carry the things), "both" (both scroll and carry). For now, '''scroll_ceil_type''' only supports "none" or "visual".
*'''floorid''', '''ceilingid'''
:ID of the floor or ceiling of this sector to use for [[attached surfaces]]. Use this id in '''attachfloor''' and '''attachceiling'''.
*'''attachfloor''', '''attachceiling'''
:Makes the floor or ceiling of this sector move whenever sectors with '''floorid''' or '''ceilingid''' with the same number move their respective surfaces. If you want this sector's floor or ceiling to move in opposite direction, use the negative value.
*'''soundsequence'''
:Name of the [[soundsequence]] to use for the movement of this sector. It will only work if said soundsequence has an '''id'''. It can also be a number (the sound sequence '''id''') surrounded by quotes.
*'''portalfloor''', '''portalceiling'''
:Portal ID to use on the floor or ceiling of this sector, using the same value as the one set in [[Portal_Define]]. For two-way portals, use the negative number for the opposite portal (i.e. one way uses portal ''n'', and the other way uses -''n'').
*'''portal_floor_disabled''', '''portal_ceil_disabled'''
:If true, the portal is disabled (has no effect).
*'''portal_floor_norender''', '''portal_ceil_norended'''
:If true, the portal is not rendered but may have effects.
*'''portal_floor_nopass''', '''portal_ceil_nopass'''
:If true, it disables any linked portals interaction.
*'''portal_floor_blocksound''', '''portal_ceil_blocksound'''
:If true, it blocks sounds from monsters listening for alerts.
*'''portal_floor_useglobaltex''', '''portal_ceil_useglobaltex'''
:Reserved.
*'''portal_floor_overlaytype''', '''portal_ceil_overlaytype''' (default: "none")
:Can be "none", "translucent" or "additive". Controls the rendering of portal overlays.
*'''alphafloor''', '''alphaceiling''' (default: 1.0)
:Alpha of the portal overlay. 1.0 makes it fully visible, 0.0 is invisible.
*'''portal_floor_attached''', '''portal_ceil_attached'''
:If true, and the sector has a linked portal on the floor or ceiling, the portal will move along with the floor or ceiling surface, instead of remaining at the same height as default. This is useful for easily moving platforms vertically.

==Things==
thing
{
health = <floating-point>;
}
===Explanation of fields===
*'''health'''
:Health modifier. Works like in ZDoom: 0 means no change from [[EDF]], positive values multiply the initial spawn health, and negative values change the absolute spawn health.

EDF player reference

2026-02-15T07:15:39Z

Printz: /* Explanation of fields */

== Player class ==
playerclass ''name''
{
defaultskin ''name''
thingtype ''name''
altattackstate ''name''
initialhealth ''number'' // default: 100
maxhealth ''number''
superhealth ''number''
viewheight ''floating_point_number''

speedwalk ''number'' // default: 25
speedrun ''number'' // default: 50
speedstrafe ''number'' // default: 24
speedstraferun ''number'' // default: 40
speedturn ''number'' // default: 640
speedturnfast ''number'' // default: 1280
speedturnslow ''number'' // default: 320
speedlookslow ''number'' // default: 450
speedlookfast ''number'' // default: 512
speedjump ''floating_point_number'' // default: 8.0

speedfactor ''floating_point_number'' // default: 1.0

default ''boolean'' // default: false

clearrebornitems

rebornitem ''name'', ''amount''
...

+AlwaysJump
+ChickenTwitch
+NoBob
+NoHealthAutoUse

weaponslot 1 { clear }
weaponslot 2 { weapons: Chainsaw, Fist }
...
}

By default, under the base folder, in the root player.edf, there are two classes defined: DoomMarine (only if game is Doom) and Corvus (only if game is Heretic). Any of these classes may be redefined in mods. So if you want to change the player speed and initial health, you can do so in mods by redefining game's default class.

You can also define a new player class and make it the default by setting '''default true'''.

===Explanation of fields===
*'''defaultskin'''
:Required. The default skin (sprite and sounds) associated with the player class. It works as a reskin on the '''thingtype''' specification. See the '''skin''' definition.
*'''thingtype'''
:Required. The avatar [[thingtype]] associated with the player class. It's usually the "player" thing of the game, with states supporting movement, attacks, pain and death.
*'''altattackstate'''
:Default: '''thingtype''''s '''missilestate'''. This is the state to go into when the weapon is in the flashing state, which is usually separate from '''thingtype''''s '''missilestate'''. By default it will use that state. Doom works based on this principle of a separate firing state to that of the missile state.
*'''initialhealth'''
:Default: 100. This is the health the player starts in this class. It doesn't need to be the same as the max health.
*'''maxhealth'''
:Default: 100. This is the maximum health to which this player can be healed by items with the '''@maxhealth''' placeholder and by actions such as [[HealThing]] and the powered Heretic gauntlets.
*'''superhealth'''
:Default: '''maxhealth'''. This is the bonus maximum health to which this player can be healed by items with the '''@superhealth''' placeholder and by [[HealThing]] when set to go past the normal maximum health. By default it's the same as '''maxhealth''' but it's common to want a higher value for it.
*'''viewheight'''
:Default: 41.0. This is the "camera" height relative to ground when playing as this class.
*'''speedwalk'''
:Default: 25. This is the walking forward/backward speed, when using the simple keyboard actions.
*'''speedrun'''
:Default: 50. This is the running forward/backward speed, when using the keyboard actions with the "run" modifier pressed. It also works as a mouse movement limiter.
*'''speedstrafe'''
:Default: 24. This is the walking sideways speed, when using the keyboard actions with the "strafe" modifier pressed.
*'''speedstraferun'''
:Default: 40. This is the running sideways speed, when using the keyboard actions with the "strafe" and "run" modifiers pressed.
*'''speedturn'''
:Default: 640. This is the normal turning speed with the keyboard.
*'''speedturnfast'''
:Default: 1280. This is the running turning speed with the keyboard.
*'''speedturnslow'''
:Default: 320. This is the turning speed during the first few tics of pressing the keyboard.
*'''speedlookslow'''
:Default: 450. This is the looking speed with the keyboard when not running.
*'''speedlook'''
:Default: 512. This is the looking speed with the keyboard when looking.
*'''speedjump'''
:Default: 8.0. This is the jumping speed. If you want the class to always be able to jump regardless of compatibility settings, make sure to also set '''+AlwaysJump'''.
*'''speedfactor'''
:Default: 1.0. This is a speed multiplier. This can be used for a more precise control, such as needed by the Heretic chicken morphed player.
*'''default'''
:Default: '''false'''. If '''true''', causes this class to be the default you start in the new game.
*'''clearrebornitems'''
:Default: omitted. If present, this marker causes the class to remove any startup items from previous definitions. This is only useful in '''playerdelta''' sections.
*'''rebornitem'''
:This is a list of 0 or more items to start with in a fresh game. Each item is an [[EDF item effects and inventory|artifact]] followed optionally by a comma and a list of how many such items to give (if applicable).
*'''+AlwaysJump'''
:Default: omitted. If present, this flag allows the player to jump all the time. Use this for any class where jumping is expected. Currently the Doom marine and Heretic hero don't have it, even though they have '''jumpspeed'''. For them, you need to enable jumping in the compatibility settings. Future games like Hexen and Strife will have their base classes with '''+AlwaysJump'''. When using '''playerdelta''', you can remove this flag by putting '''-AlwaysJump'''.
*'''+ChickenTwitch'''
:Default: omitted. If present, this flag causes the player to occasionally change view direction, jump and make the pain sound. Typical for Heretic chicken players.
*'''+NoBob'''
:Default: omitted. Disables player weapon and view bobbing.
*'''+NoHealthAutoUse'''
:Default: omitted. Disables Heretic inventory health item autousing.
*'''weaponslot'''
:This is a list of 1 or more weapon slots associated with each selection key. A weapon may appear on more than one slot. A slot can have multiple weapons, with the most superior first in the list. When using '''playerdelta''', instead of '''weapons:''' ''list'' you can put '''clear''' to remove that slot.
:Important: add <code>setdialect("ALFHEIM")</code> at the beginning of the EDFROOT lump or edf file to be able to use the '''weapons:''' syntax.

===Player class delta structure===
You can use the '''playerdelta''' section to change an already defined player class. The syntax is as follows:
playerdelta
{
name ''playerclass_name''
''any_fields_from_playerclass''
}
''any_fields_from_playerclass'' means that you can list any of the settings from the base class here, with modified values, using the same syntax as in '''playerclass'''. See '''playerclass''' for explanations of the fields.

== Player skin ==
skin ''name''
{
sprite ''name'' // default: PLAY
faces ''prefix'' // default: STF
sounds
{
pain ''name'' // default: plpain
diehi ''name'' // default: pdiehi
oof ''name'' // default: oof
gib ''name'' // default: slop
punch ''name'' // default: punch
radio ''name'' // default: radio
die ''name'' // default: pldeth
fall ''name'' // default: plfall
feet ''name'' // default: plfeet
fallhit ''name'' // default: fallht
plwdth ''name'' // default: plwdth
noway ''name'' // default: noway
}
}

Skins are options for the player to appear differently. Despite the "skin" name, it means changing both the graphics and sounds, just without changing the player class (behaviour).

Any skin you define will appear in the menu in the "Player Setup" section as an option.

The default skins are "marine" for Doom and "corvus" for Heretic. You can redefine your own "marine" or "corvus" skin in your mod's EDF and it will replace the default player skin. Do this if you want to change the sprite and sound of the protagonist.

The fields are:
*'''sprite'''
:Sprite to replace the default player's with.
*'''faces'''
:DOOM status bar graphics lump prefix replacement.
*'''sounds'''
:Optional replacement sounds for common player sounds. Use EDF [[sound]] names.
===See also===
*[[S_SKIN]]: cross-port non-EDF alternative format

EDF player reference

2026-02-15T07:15:00Z

Printz: /* Explanation of fields */

== Player class ==
playerclass ''name''
{
defaultskin ''name''
thingtype ''name''
altattackstate ''name''
initialhealth ''number'' // default: 100
maxhealth ''number''
superhealth ''number''
viewheight ''floating_point_number''

speedwalk ''number'' // default: 25
speedrun ''number'' // default: 50
speedstrafe ''number'' // default: 24
speedstraferun ''number'' // default: 40
speedturn ''number'' // default: 640
speedturnfast ''number'' // default: 1280
speedturnslow ''number'' // default: 320
speedlookslow ''number'' // default: 450
speedlookfast ''number'' // default: 512
speedjump ''floating_point_number'' // default: 8.0

speedfactor ''floating_point_number'' // default: 1.0

default ''boolean'' // default: false

clearrebornitems

rebornitem ''name'', ''amount''
...

+AlwaysJump
+ChickenTwitch
+NoBob
+NoHealthAutoUse

weaponslot 1 { clear }
weaponslot 2 { weapons: Chainsaw, Fist }
...
}

By default, under the base folder, in the root player.edf, there are two classes defined: DoomMarine (only if game is Doom) and Corvus (only if game is Heretic). Any of these classes may be redefined in mods. So if you want to change the player speed and initial health, you can do so in mods by redefining game's default class.

You can also define a new player class and make it the default by setting '''default true'''.

===Explanation of fields===
*'''defaultskin'''
:Required. The default skin (sprite and sounds) associated with the player class. It works as a reskin on the '''thingtype''' specification. See the '''skin''' definition.
*'''thingtype'''
:Required. The avatar [[thingtype]] associated with the player class. It's usually the "player" thing of the game, with states supporting movement, attacks, pain and death.
*'''altattackstate'''
:Default: '''thingtype''''s '''missilestate'''. This is the state to go into when the weapon is in the flashing state, which is usually separate from '''thingtype''''s '''missilestate'''. By default it will use that state. Doom works based on this principle of a separate firing state to that of the missile state.
*'''initialhealth'''
:Default: 100. This is the health the player starts in this class. It doesn't need to be the same as the max health.
*'''maxhealth'''
:Default: 100. This is the maximum health to which this player can be healed by items with the '''@maxhealth''' placeholder and by actions such as [[HealThing]] and the powered Heretic gauntlets.
*'''superhealth'''
:Default: '''maxhealth'''. This is the bonus maximum health to which this player can be healed by items with the '''@superhealth''' placeholder and by [[HealThing]] when set to go past the normal maximum health. By default it's the same as '''maxhealth''' but it's common to want a higher value for it.
*'''viewheight'''
:Default: 41.0. This is the "camera" height relative to ground when playing as this class.
*'''speedwalk'''
:Default: 25. This is the walking forward/backward speed, when using the simple keyboard actions.
*'''speedrun'''
:Default: 50. This is the running forward/backward speed, when using the keyboard actions with the "run" modifier pressed. It also works as a mouse movement limiter.
*'''speedstrafe'''
:Default: 24. This is the walking sideways speed, when using the keyboard actions with the "strafe" modifier pressed.
*'''speedstraferun'''
:Default: 40. This is the running sideways speed, when using the keyboard actions with the "strafe" and "run" modifiers pressed.
*'''speedturn'''
:Default: 640. This is the normal turning speed with the keyboard.
*'''speedturnfast'''
:Default: 1280. This is the running turning speed with the keyboard.
*'''speedturnslow'''
:Default: 320. This is the turning speed during the first few tics of pressing the keyboard.
*'''speedlookslow'''
:Default: 450. This is the looking speed with the keyboard when not running.
*'''speedlook'''
:Default: 512. This is the looking speed with the keyboard when looking.
*'''speedjump'''
:Default: 8.0. This is the jumping speed. If you want the class to always be able to jump regardless of compatibility settings, make sure to also set '''+AlwaysJump'''.
*'''speedfactor'''
:Default: 1.0. This is a speed multiplier. This can be used for a more precise control, such as needed by the Heretic chicken morphed player.
*'''default'''
:Default: '''false'''. If '''true''', causes this class to be the default you start in the new game.
*'''clearrebornitems'''
:Default: omitted. If present, this marker causes the class to remove any startup items from previous definitions. This is only useful in '''playerdelta''' sections.
*'''rebornitem'''
:This is a list of 0 or more items to start with in a fresh game. Each item is an [[EDF item effects and inventory|artifact]] followed optionally by a comma and a list of how many such items to give (if applicable).
*'''+AlwaysJump'''
:Default: omitted. If present, this flag allows the player to jump all the time. Use this for any class where jumping is expected. Currently the Doom marine and Heretic hero don't have it, even though they have '''jumpspeed'''. For them, you need to enable jumping in the compatibility settings. Future games like Hexen and Strife will have their base classes with '''+AlwaysJump'''. When using '''playerdelta''', you can remove this flag by putting '''-AlwaysJump'''.
*'''+ChickenTwitch'''
:Default: omitted. If present, this flag causes the player to occasionally change view direction, jump and make the pain sound. Typical for Heretic chicken players.
*'''+NoBob'''
:Default: omitted. Disables player weapon and view bobbing.
*'''+NoHealthAutoUse'''
:Default: omitted. Disables Heretic inventory health item autousing.
*'''weaponslot'''
:This is a list of 1 or more weapon slots associated with each selection key. A weapon may appear on more than one slot. A slot can have multiple weapons, with the most superior first in the list. When using '''playerdelta''', instead of '''weapons:''' ''list'' you can put '''clear''' to remove that slot.
:Important: add <code>setdialect("ALFHEIM")</code> at the beginning of the EDFROOT or edf file to be able to use the '''weapons:''' syntax.

===Player class delta structure===
You can use the '''playerdelta''' section to change an already defined player class. The syntax is as follows:
playerdelta
{
name ''playerclass_name''
''any_fields_from_playerclass''
}
''any_fields_from_playerclass'' means that you can list any of the settings from the base class here, with modified values, using the same syntax as in '''playerclass'''. See '''playerclass''' for explanations of the fields.

== Player skin ==
skin ''name''
{
sprite ''name'' // default: PLAY
faces ''prefix'' // default: STF
sounds
{
pain ''name'' // default: plpain
diehi ''name'' // default: pdiehi
oof ''name'' // default: oof
gib ''name'' // default: slop
punch ''name'' // default: punch
radio ''name'' // default: radio
die ''name'' // default: pldeth
fall ''name'' // default: plfall
feet ''name'' // default: plfeet
fallhit ''name'' // default: fallht
plwdth ''name'' // default: plwdth
noway ''name'' // default: noway
}
}

Skins are options for the player to appear differently. Despite the "skin" name, it means changing both the graphics and sounds, just without changing the player class (behaviour).

Any skin you define will appear in the menu in the "Player Setup" section as an option.

The default skins are "marine" for Doom and "corvus" for Heretic. You can redefine your own "marine" or "corvus" skin in your mod's EDF and it will replace the default player skin. Do this if you want to change the sprite and sound of the protagonist.

The fields are:
*'''sprite'''
:Sprite to replace the default player's with.
*'''faces'''
:DOOM status bar graphics lump prefix replacement.
*'''sounds'''
:Optional replacement sounds for common player sounds. Use EDF [[sound]] names.
===See also===
*[[S_SKIN]]: cross-port non-EDF alternative format

Parameterized linedef specials

2025-12-13T10:10:27Z

Printz: /* Exits */

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*Ceiling_ToHighestInstant''' ( tag, change, crush )
*Ceiling_RaiseToNearest''' ( tag, speed, change )
*Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*Ceiling_RaiseToLowest''' ( tag, speed, change )
*Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*Ceiling_RaiseByTexture''' ( tag, speed, change )
*Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*Ceiling_RaiseByValue''' ( tag, speed, height, change )
*Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*Ceiling_RaiseInstant''' ( tag, height, change )
*Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

Parameterized linedef specials

2025-12-13T10:07:08Z

Printz: /* Teleportation */

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*Ceiling_ToHighestInstant''' ( tag, change, crush )
*Ceiling_RaiseToNearest''' ( tag, speed, change )
*Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*Ceiling_RaiseToLowest''' ( tag, speed, change )
*Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*Ceiling_RaiseByTexture''' ( tag, speed, change )
*Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*Ceiling_RaiseByValue''' ( tag, speed, height, change )
*Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*Ceiling_RaiseInstant''' ( tag, height, change )
*Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*400:'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*447:'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*448:'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*449:'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*462:'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

Parameterized linedef specials

2025-12-13T10:05:43Z

Printz: /* Things */

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*Ceiling_ToHighestInstant''' ( tag, change, crush )
*Ceiling_RaiseToNearest''' ( tag, speed, change )
*Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*Ceiling_RaiseToLowest''' ( tag, speed, change )
*Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*Ceiling_RaiseByTexture''' ( tag, speed, change )
*Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*Ceiling_RaiseByValue''' ( tag, speed, height, change )
*Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*Ceiling_RaiseInstant''' ( tag, height, change )
*Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*444:'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*445:'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*446:'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*400:'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*447:'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*448:'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*449:'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*462:'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

Parameterized linedef specials

2025-12-13T10:04:54Z

Printz: /* Lights */

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*Ceiling_ToHighestInstant''' ( tag, change, crush )
*Ceiling_RaiseToNearest''' ( tag, speed, change )
*Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*Ceiling_RaiseToLowest''' ( tag, speed, change )
*Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*Ceiling_RaiseByTexture''' ( tag, speed, change )
*Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*Ceiling_RaiseByValue''' ( tag, speed, height, change )
*Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*Ceiling_RaiseInstant''' ( tag, height, change )
*Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*402:'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*403:'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*421:'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*426:'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*427:'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*428:'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*478:'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*469:'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*444:'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*445:'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*446:'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*400:'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*447:'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*448:'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*449:'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*462:'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

Parameterized linedef specials

2025-12-13T10:00:50Z

Printz: /* Ceiling movement */ More misleading useless number removal

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*Ceiling_ToHighestInstant''' ( tag, change, crush )
*Ceiling_RaiseToNearest''' ( tag, speed, change )
*Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*Ceiling_RaiseToLowest''' ( tag, speed, change )
*Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*Ceiling_RaiseByTexture''' ( tag, speed, change )
*Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*Ceiling_RaiseByValue''' ( tag, speed, height, change )
*Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*Ceiling_RaiseInstant''' ( tag, height, change )
*Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*368:'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*369:'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*370:'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*371:'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*372:'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*373:'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*374:'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*463:'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*473:'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*461:'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*402:'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*403:'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*421:'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*426:'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*427:'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*428:'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*478:'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*469:'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*444:'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*445:'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*446:'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*400:'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*447:'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*448:'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*449:'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*462:'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

Parameterized linedef specials

2025-12-13T09:55:58Z

Printz: /* Floor movement, earthquake */ Removed misleading incomplete redundant info

The parameterized linedefs types are Hexen-like action specials with arguments, whose purpose is to be more customizable than the Boom generalized types. When mapping in UDMF, you have to use these parameterized specials instead of the classic parameter-less ones. They're also used in Hexen format maps (which is necessary when Hexen is going to be supported in Eternity), though Hexen format is not recommended or fully supported for other maps than vanilla Hexen in Eternity. To use parameterized specials in classic (Doom) format maps, provide an [[ExtraData]] lump by attaching it via [[MapInfo|EMAPINFO]] to the map. [[ACS]] scripts can also call parameterized specials. They're meant to be as compatible as possible with the ZDoom implementation, so minimal changes to zspecial.acs are needed, though Eternity may have extensions of its own. Most likely however the base zspecial.acs is going to be updated for Eternity. Parameters are only limited to 0-255 in the Hexen format (and some specials may have some legacy workarounds for that interval), but otherwise they're in the normal integer range for other environments (UDMF, ExtraData, ACS). Some specials have never been added to ExtraData, because of their mere purpose being to work under the limits of the Hexen map format.

Each parameterized line special has a name and two associated numbers: one for UDMF, ACS and Hexen formats, and another one for ExtraData support, set this way to avoid conflicts with classic Boom specials (since it's possible to use their number in the editor instead of the 270 "ExtraData special"). If you only see one number mentioned in the documentation, then it's the UDMF number (for ExtraData it's preferred to use the names).

'''IMPORTANT''': all ''reserved'' parameters must be set to 0. Failure to do so will result in your maps being broken in later Eternity versions! Also, for "flag" arguments, do not add or provide other values than in the intended range, for the same reason.

{{Backto|Linedef types}}
==General info==
All sector tags, unless otherwise specified, have a special meaning if 0: that means to affect the sector behind the trigger linedef (like regular doors in vanilla Doom).

Thing tags (TIDs) have special meaning for values 0 and negative: 0 means activator, and -1 to -4 mean to affect players 1 to 4 (if present). '''Consider other negative values reserved''' and do not use them in your maps.
==Specials==
===Doors===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Args
! Summary
|-
|| 10 || 302 || [[Door_Close]] || ''tag'', ''speed'', ''light_tag'' || Closes a door.
|-
|| 11 || 301 || [[Door_Open]] || ''tag'', ''speed'', ''light_tag'' || Opens a door.
|-
|| 12 || 300 || [[Door_Raise]] || ''tag'', ''speed'', ''delay'', ''light_tag'' || Opens a door temporarily.
|-
|| 13 || 429 || [[Door_LockedRaise]] || ''tag'', ''speed'', ''delay'', ''lock'', ''light_tag'' || Opens a locked door.
|-
|| 105 || 304 || [[Door_WaitRaise]] || ''tag'', ''speed'', ''delay'', ''timeoffset'', ''light_tag'' || Opens a door temporarily after a delay.
|-
|| 106 || 305 || [[Door_WaitClose]] || ''tag'', ''speed'', ''timeoffset'', ''light_tag'' || Closes a door after a delay.
|-
|| 249 || 303 || [[Door_CloseWaitOpen]] || ''tag'', ''speed'', ''delay_octics'', ''light_tag'' || Closes a door, waits a bit, then opens it back.
|}
:''tag'': Tag of sector to affect. If it's 0, then the sector behind the linedef will be activated, if applicable.
:''speed'': How fast, in eights of units per tic, the door should move. Doom normal doors are as fast as 16, and blazing doors are 64.
:''delay'': Time in tics (1/35 seconds) for the door before it returns to its opposite movement.
:''delay_octics'': Delay, but expressed in octics, which is eighths of second (i.e. 8 octics = 1 second).
:''timeoffset'': Time in tics before the door activates.
:''light_tag'': Sector tag to receive light changes to maximum or minimum neighbor depending on whether the door is closed or opened.
:''lock'': One of the [[lock identifiers]] to specify the key or set of keys.

===Floor movement, earthquake===
{|class="wikitable sortable"
! UDMF #
! ExtraData #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 20 || 318 || [[Floor_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 21 || 309 || [[Floor_LowerToLowest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 22 || 311 || [[Floor_LowerToNearest]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 23 || 317 || [[Floor_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 24 || 306 || [[Floor_RaiseToHighest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 25 || 310 || [[Floor_RaiseToNearest]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 28 || 451 || [[Floor_RaiseAndCrush]] || tag || speed || crush || ||
|-
|| 35 || - || [[Floor_RaiseByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' || ''crush''
|-
|| 36 || - || [[Floor_LowerByValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''change'' ||
|-
|| 37 || 319 || [[Floor_MoveToValue]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 46 || 452 || [[Floor_CrushStop]] || ''tag'' || || || || || Stops crushing floor movement.
|-
|| 66 || 321 || [[Floor_LowerInstant]] || ''tag'' || - || ''height'' || ''change'' || || Lowers floor instantly.
|-
|| 67 || 320 || [[Floor_RaiseInstant]] || ''tag'' || - || ''height'' || ''change'' || ''crush'' || Raises floor instantly.
|-
|| 68 || - || [[Floor_MoveToValueTimes8]] || ''tag'' || ''speed'' || ''height'' || ''neg'' || ''change''
|-
|| 120 || 375 || [[Radius_Quake]] || intensity || duration || damage radius || tremor radius || foci tid
|-
|| 138 || 397 || [[Floor_Waggle]] || tag || height || speed || offset || timer
|-
|| 200 || 464 || [[Generic_Floor]] || tag || speed || height || target || flags || Boom-like generalized floor.
|-
|| 228 || 475 || [[Plat_RaiseAndStayTx0]] || tag || speed || lock out || || || Variation of [[Floor_RaiseToNearest]].
|-
|| 230 || 476 || [[Plat_UpByValueStayTx]] || tag || speed || height || || || Variation of [[Floor_RaiseByValue]]
|-
|| 231 || 487 || [[Plat_ToggleCeiling]] || tag || || || || || Toggles floor between ceiling and initial position.
|-
|| 235 || 466 || [[Floor_TransferTrigger]] || ''tag'' || || || ||
|-
|| 236 || 467 || [[Floor_TransferNumeric]] || ''tag'' || || || ||
|-
|| 238 || 312 || [[Floor_RaiseToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap''
|-
|| 240 || 315 || [[Floor_RaiseByTexture]] || ''tag'' || ''speed'' || ''change'' || ''crush'' ||
|-
|| 242 || 416 || [[Floor_LowerToHighest]] || ''tag'' || ''speed'' || ''adjust'' || ''force_adjust'' ||
|-
|| 250 || 431 || [[Floor_Donut]] || pillar tag || pillar speed || pool speed || ||
|-
|| 256 || 307 || [[Floor_LowerToHighestEE]] || ''tag'' || ''speed'' || ''change'' || ||
|-
|| 257 || 308 || [[Floor_RaiseToLowest]] || ''tag'' || ''change'' || ''crush'' || || || Instantly lower floor to lowest neighbour.
|-
|| 258 || 313 || [[Floor_LowerToLowestCeiling]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor to lowest ceiling.
|-
|| 259 || 314 || [[Floor_RaiseToCeiling]] || ''tag'' || ''speed'' || ''change'' || ''crush'' || ''gap'' || Raise floor to ceiling.
|-
|| 260 || 322 || [[Floor_ToCeilingInstant]] || ''tag'' || ''change'' || ''crush'' || ''gap'' || || Raise floor to ceiling instantly.
|-
|| 261 || 316 || [[Floor_LowerByTexture]] || ''tag'' || ''speed'' || ''change'' || || || Lower floor by shortest lower texture.
|-
|}
*'''Floor_Waggle''' ( tag, height, speed, offset, timer )
:This special implements the sinusoidal floor motion from Hexen. Its tag and speed parameters bear similar properties to the other floor specials, but -
:*height - waggle amplitude in 1/8 units
:*offset - phase offset; how much to delay the waggle in relation to others (0 to 63, in byte angles)
:*timer - time in seconds the waggle lasts. Zero means permanent
*'''Radius_Quake''' (intensity, duration, damageradius, quakeradius, tid)
:This special implements the earthquake effect, centred on the map spot with the given ''tid'', with user-selectable intensity, duration and separate thing damage radius and tremor radius (both being multiplied with 64).
*'''Floor_RaiseAndCrush'''(''tag'', ''speed'', ''crush'')
:This one is for Hexen compatibility. Please use '''Floor_RaiseToCeiling''' or '''Floor_RaiseToLowestCeiling''' instead.
====See also====
*[[Floor movement classic specials]]: for the Doom format variants.

===Plats, lifts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
! Description
|-
|| 60 || 410 || [[Plat_PerpetualRaise]] || tag || speed || delay || || || Perpetual lift with lip of 8
|-
|| 61 || 411 || [[Plat_Stop]] || tag || stop_mode || || ||
|-
|| 62 || 412 || [[Plat_DownWaitUpStay]] || tag || speed || delay || ||
|-
|| 63 || 413 || [[Plat_DownByValue]] || tag || speed || delay || height ||
|-
|| 64 || 414 || [[Plat_UpWaitDownStay]] || tag || speed || delay || ||
|-
|| 65 || 415 || [[Plat_UpByValue]] || tag || speed || delay || height ||
|-
|| 203 || 501 || [[Generic_Lift]] || tag || speed || delay || type || height ||
|-
|| 206 || 488 || [[Plat_DownWaitUpStayLip]] || tag || speed || delay || lip ||
|-
|| 207 || 489 || [[Plat_PerpetualRaiseLip]] || tag || speed || delay || lip ||
|}
*207 (489) '''Plat_PerpetualRaiseLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_PerpetualRaise''', but lets you choose a "lip" (distance from lowest adjacent floor to move down to). If ''lip'' is 0, it will work like classic Doom perpetual plats.
*61 (411) '''Plat_Stop'''(''tag'', ''stop_mode'')
:Pauses or stops a perpetual platform from moving. The behavior depends on ''stop_mode'':
:*1: the platform will be merely suspended. It will only be retriggerable by other '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' (or in Doom-format maps, by similar specials), continuing from the exact same state it stopped.
:*2: the platform movement will be stopped at the current position. It will be retriggerable by any other special. If restarted by '''Plat_PerpetualRaise''' or '''Plat_PerpetualRaiseLip''' it may not remember the last state.
:*0 (default): will act based on compatibility with current game mode. On Doom/Heretic/Hexen, it will act like mode 1, while in Hexen it will act like mode 2.
*62 (412) '''Plat_DownWaitUpStay'''(''tag'', ''speed'', ''delay'')
:Lowers the plat as a lift to the lowest adjacent floor '''plus 8 units'''. Use '''Plat_DownWaitUpStayLip''' with 0 lip if you want classic Doom-like lifts.
*206 (488) '''Plat_DownWaitUpStayLip'''(''tag'', ''speed'', ''delay'', ''lip'')
:Like '''Plat_DownWaitUpStay''' but with settable ''lip''.
*63 (413) '''Plat_DownByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Lowers a lift by an absolute ''height'', '''multiplied by 8'''. It will rise back after ''delay'' tics.
*64 (414) '''Plat_UpWaitDownStay'''(''tag'', ''speed'', ''delay'')
:Raises a lift to the highest neighbor floor. It will lower back after ''delay'' tics.
*65 (415) '''Plat_UpByValue'''(''tag'', ''speed'', ''delay'', ''height'')
:Raises a lift by an absolute ''height'', '''multiplied by 8'''. It will lower back after ''delay'' tics.
*231 (487) '''Plat_ToggleCeiling'''(''tag'')
:Toggles a floor between the default position and touching the ceiling. It will be left busy after that.

===Elevators===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 95 || 453 || [[FloorAndCeiling_LowerByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 96 || 454 || [[FloorAndCeiling_RaiseByValue]] || ''tag'' || ''speed'' || ''height'' || ||
|-
|| 245 || 458 || [[Elevator_RaiseToNearest]] || ''tag'' || ''speed'' || || ||
|-
|| 246 || 460 || [[Elevator_MoveToFloor]] || ''tag'' || ''speed'' || || ||
|-
|| 247 || 459 || [[Elevator_LowerToNearest]] || ''tag'' || ''speed'' || || ||
|}

===Ceiling movement===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 38 || 500 || [[Ceiling_Waggle]] || tag || height || speed || offset || timer
|-
|| 40 || 336 || [[Ceiling_LowerByValue]] || tag || speed || height || change || crush
|-
|| 41 || 335 || [[Ceiling_RaiseByValue]] || tag || speed || height || change ||
|-
|| 42 || 432 || [[Ceiling_CrushAndRaise]] || tag || speed || crush || crush mode ||
|-
|| 43 || 435 || [[Ceiling_LowerAndCrush]] || tag || speed || crush || crush mode ||
|-
|| 44 || 433 || [[Ceiling_CrushStop]] || tag || stop mode || || ||
|-
|| 45 || 434 || [[Ceiling_CrushRaiseAndStay]] || tag || speed || crush || crush mode ||
|-
|| 47 || 337 || [[Ceiling_MoveToValue]] || tag || speed || height || negate || change
|-
|| 69 || - || [[Ceiling_MoveToValueTimes8]] || tag || speed || height || negate || change
|-
|| 97 || 436 || [[Ceiling_LowerAndCrushDist]] || tag || speed || crush || gap || crush mode
|-
|| 104 || 441 || [[Ceiling_CrushAndRaiseSilentDist]] || tag || gap || speed || damage || crush mode
|-
|| 168 || 437 || [[Ceiling_CrushAndRaiseDist]] || tag || gap || speed || damage || crush mode
|-
|| 192 || 330 || [[Ceiling_LowerToHighestFloor]] || tag || speed || change || crush || gap to floor
|-
|| 193 || 339 || [[Ceiling_LowerInstant]] || tag || - || height * 8 || change || crush
|-
|| 194 || 338 || [[Ceiling_RaiseInstant]] || tag || - || height * 8 || change ||
|-
|| 195 || 438 || [[Ceiling_CrushRaiseAndStayA]] || tag || down speed || up speed || damage || crush mode
|-
|| 196 || 439 || [[Ceiling_CrushAndRaiseA]] || tag || down speed || up speed || damage || crush mode
|-
|| 197 || 440 || [[Ceiling_CrushAndRaiseSilentA]] || tag || down speed || up speed || damage || crush mode
|-
|| 198 || - || [[Ceiling_RaiseByValueTimes8]] || tag || speed || height * 8 || change ||
|-
|| 199 || - || [[Ceiling_LowerByValueTimes8]] || tag || speed || height * 8 || change || crush
|-
|| 201 || 465 || [[Generic_Ceiling]] || tag || speed || height || target || flags
|-
|| 205 || 443 || [[Generic_Crusher]] || tag || down speed || up speed || silent || damage
|-
|| 252 || 325 || [[Ceiling_RaiseToNearest]] || tag || speed || change || ||
|-
|| 253 || 328 || [[Ceiling_LowerToLowest]] || tag || speed || change || crush ||
|-
|| 254 || 332 || [[Ceiling_LowerToFloor]] || tag || speed || change || crush || gap
|-
|| 255 || 442 || [[Ceiling_CrushRaiseAndStaySilA]] || tag || down speed || up speed || damage || crush mode
|-
|| 262 || 323 || [[Ceiling_RaiseToHighest]] || tag || speed || change || ||
|-
|| 263 || 324 || [[Ceiling_ToHighestInstant]] || tag || change || crush || ||
|-
|| 264 || 326 || [[Ceiling_LowerToNearest]] || tag || speed || change || crush ||
|-
|| 265 || 327 || [[Ceiling_RaiseToLowest]] || tag || speed || change || ||
|-
|| 266 || 329 || [[Ceiling_RaiseToHighestFloor]] || tag || speed || change || ||
|-
|| 267 || 331 || [[Ceiling_ToFloorInstant]] || tag || change || crush || gap ||
|-
|| 268 || 333 || [[Ceiling_RaiseByTexture]] || tag || speed || change || ||
|-
|| 269 || 334 || [[Ceiling_LowerByTexture]] || tag || speed || change || crush ||
|}
*323:'''Ceiling_RaiseToHighest''' ( tag, speed, change )
*324:'''Ceiling_ToHighestInstant''' ( tag, change, crush )
*325:'''Ceiling_RaiseToNearest''' ( tag, speed, change )
*326:'''Ceiling_LowerToNearest''' ( tag, speed, change, crush )
*327:'''Ceiling_RaiseToLowest''' ( tag, speed, change )
*328:'''Ceiling_LowerToLowest''' ( tag, speed, change, crush )
*329:'''Ceiling_RaiseToHighestFloor''' ( tag, speed, change )
*330:'''Ceiling_LowerToHighestFloor''' ( tag, speed, change, crush, gap )
*331:'''Ceiling_ToFloorInstant''' ( tag, change, crush, gap )
*332:'''Ceiling_LowerToFloor''' ( tag, speed, change, crush, gap )
*333:'''Ceiling_RaiseByTexture''' ( tag, speed, change )
*334:'''Ceiling_LowerByTexture''' ( tag, speed, change, crush )
*335:'''Ceiling_RaiseByValue''' ( tag, speed, height, change )
*336:'''Ceiling_LowerByValue''' ( tag, speed, height, change, crush )
*337:'''Ceiling_MoveToValue''' ( tag, speed, height, change, crush )
*338:'''Ceiling_RaiseInstant''' ( tag, height, change )
*339:'''Ceiling_LowerInstant''' ( tag, height, change, crush )
:Values for these specials:
:*tag: Tag of the sector(s) to affect. A tag of zero means to affect the sector on the second side of the line.
:*speed: Speed of ceiling in eighths of a unit per tic.
:*change: This parameter takes the following values:
::0 : No texture or type change.
::1 : Copy texture, zero type; trigger model.
::2 : Copy texture, zero type; numeric model.
::3 : Copy texture, preserve type; trigger model.
::4 : Copy texture, preserve type; numeric model.
::5 : Copy texture and type; trigger model.
::6 : Copy texture and type; numeric model.
:*crush: Amount of crushing damage ceiling inflicts at each crushing event (when gametic % 4 = 0). If this amount is less than or equal to zero, no crushing damage is done.
:*height: An integer number of units, either the amount to move the floor by or the exact z coordinate to move the floor toward. Negative numbers are valid for the latter case.
:*gap: Distance to keep from the destination. Useful if crush is nonzero
*465:'''Generic_Ceiling'''(''tag'', ''speed'', ''height'', ''target'', ''flag'')
:See '''Generic_Floor''' for an explanation of parameters.

====Crushing ceilings====
There are some crushing ceilings available now. Some originate from Hexen while others are extensions from ZDoom. ZDoom compatibility is considered where relevant. For all specials where it applies, ''crushmode'' can take one of these values:
*0: compatibility. Act like it would do in ZDoom. This means that in Doom the crusher keeps pushing into the things it crushes, while in Hexen it stays on position while dealing damage. And if the game is Doom, the special has "Dist" in the name and the speed is set to 8, it will also slow down to speed 1 when crushing.
*1: Doom mode without slowdown. Same as classic Doom's fast crushers.
*2: Hexen mode. It will rest in position while crushing.
*3: Doom mode with slowdown. Same as classic Doom's slow crushers. Currently the crushing speed is hardcoded to 1.
The specials are the following. Take care that Ceiling_CrushAndRaise is mainly for Hexen compatibility: it will rise at half the speed it lowers. For Doom-like crushers use Ceiling_CrushAndRaiseA (all "A" crushers let you specify the rising speed) or Ceiling_CrushAndRaiseDist (all "Dist" crushers rise at the same speed as they lower, but instead let you specify the gap size to the ground). Finally, Generic_Crusher aims to act like the Boom crushers, having the following particularities: it will slow down when crushing if speed is less than 24, and it will be totally silent if specified in the parameter (won't even make clunk noises).
*432: Ceiling_CrushAndRaise(tag, speed, damage, crushmode)
*439: Ceiling_CrushAndRaiseA(tag, down_speed, up_speed, damage, crushmode)
*440: Ceiling_CrushAndRaiseSilentA(tag, down_speed, up_speed, damage, crushmode)
*437: Ceiling_CrushAndRaiseDist(tag, ground_distance, speed, damage, crushmode)
*441: Ceiling_CrushAndRaiseSilentDist(tag, ground_distance, speed, damage, crushmode)
*434: Ceiling_CrushAndRaiseAndStay(tag, speed, damage, crushmode)
*438: Ceiling_CrushAndRaiseAndStayA(tag, down_speed, up_speed, damage, crushmode)
*442: Ceiling_CrushAndRaiseAndStaySilA(tag, down_speed, up_speed, damage, crushmode)
*435: Ceiling_LowerAndCrush(tag, speed, damage, crushmode)
*436: Ceiling_LowerAndCrushDist(tag, speed, damage, ground_distance, crushmode)
*433: Ceiling_CrushStop(tag, stop_mode)
:*stop_mode can be: 0 (compatibility), 1 (Doom: pause crusher), 2 (Hexen: remove crusher and release the ceiling)
*443: Generic_Crusher(tag, down_speed, up_speed, silent, damage)

===Stair building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 204 || 502 || [[Generic_Stairs]] || ''tag'' || ''speed'' || ''height'' || ''flags'' || ''reset''
|-
|| 217 || 340 || [[Stairs_BuildUpDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 270 || 341 || [[Stairs_BuildDownDoom]] || ''tag'' || ''speed'' || ''stepsize'' || ''delay'' || ''reset''
|-
|| 271 || 342 || [[Stairs_BuildUpDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|-
|| 272 || 343 || [[Stairs_BuildDownDoomSync]] || ''tag'' || ''speed'' || ''stepsize'' || ''reset'' ||
|}
------------------------------------------------------------------------------
* Synchronized stairs have each step move at a different speed so that all the
steps reach the destination height at the same time. This stair building
style is only available with these parameterized line types.

Values
---------------------------------------------------------------
tag : Tag of first sector to raise or lower as a step.
When the stair building method is DOOM, subsequent
steps are found by searching across two-sided
lines where the first side belongs to the current
sector and the floor texture is the same. The
Hexen stair building method is not yet supported.
speed : Speed of steps in eights of a unit per tic. If the
build style is synchronized, only the first step
moves at this speed. Other steps will move at a
speed which allows them to reach their
destination height at the same time.
stepsize : Step size in units.
delay : Delay time in tics between steps
reset : If greater than zero, the stairs will wait this
amount of time in tics after completely building
and will then reset by repeating the same stair
building action but in the reverse direction. If
zero, the stairs will never reset.
------------------------------------------------------------------------------

===Polyobjects===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 1 || 348 || [[Polyobj_StartLine]] || id || mirror id || sound sequence || ||
|-
|| 2 || 356 || [[Polyobj_RotateLeft]] || id || speed || rotation || ||
|-
|| 3 || 354 || [[Polyobj_RotateRight]] || id || speed || rotation || ||
|-
|| 4 || 352 || [[Polyobj_Move]] || id || speed || angle || distance ||
|-
|| 5 || 349 || [[Polyobj_ExplicitLine]] || id || line index || mirror id || sound sequence ||
|-
|| 6 || - || [[Polyobj_MoveTimes8]] || id || speed || angle || distance ||
|-
|| 7 || 351 || [[Polyobj_DoorSwing]] || id || speed || rotation || delay ||
|-
|| 8 || 350 || [[Polyobj_DoorSlide]] || id || speed || angle || distance || delay
|-
|| 59 || 499 || [[Polyobj_OR_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 86 || 496 || [[Polyobj_MoveToSpot]] || id || speed || [[TID]] || ||
|-
|| 87 || 474 || [[Polyobj_Stop]] || id || || || ||
|-
|| 88 || 497 || [[Polyobj_MoveTo]] || id || speed || x || y ||
|-
|| 89 || 498 || [[Polyobj_OR_MoveTo]] || id || speed || x || y ||
|-
|| 90 || 357 || [[Polyobj_OR_RotateLeft]] || id || speed || rotation || ||
|-
|| 91 || 355 || [[Polyobj_OR_RotateRight]] || id || speed || rotation || ||
|-
|| 92 || 353 || [[Polyobj_OR_Move]] || id || speed || angle || distance ||
|-
|| 93 || - || [[Polyobj_OR_MoveTimes8]] || id || speed || angle || distance ||
|}
*1 (348) '''Polyobj_StartLine'''(''id'', ''mirror_id'', ''sequence_id'')
*5 (349) '''Polyobj_ExplicitLine(''id'', ''linenum'', ''mirror_id'', ''sequence_id'')
:There are two different methods of creating a polyobject. In the first, the "first" line is given the '''Polyobj_StartLine''' special, and subsequent lines are added to the PolyObject by following segs from vertex to vertex. To use this, all the lines around the polyobject must run in the same direction, and the last line must end at the same vertex which starts the first line (in other words, it must be closed).

:With the second method, every line to be included must be given the '''Polyobj_ExplicitLine''' special and must be given a ''linenum'' param which is unique amongst all lines that will added to that polyobject. Polyobjects of this sort should also be closed for proper rendering, but the game engine cannot and will not verify that this is the case.

:Only polyobjects created with the '''Polyobj_StartLine''' method can have other line specials on the polyobject's lines themselves.

:''Mirror_id'' is the ID number of a PolyObject that wants to mirror every action that this PolyObject makes. This number cannot refer to the self-same PolyObject, nor should PolyObjects attempt to mirror each other in a cycle since this will create problems with override actions. Angle of motion is always reversed when applying an action to a mirroring PolyObject. If a mirror is already in motion for a non-override action, the mirror will not be affected even if the main object was moved. Mirror polyobjects can themselves define a mirror, and an action will affect all mirroring polyobjects in the chain.
*4 (352) '''Polyobj_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Slides a polyobject in the direction given in ''angle'' by ''distance''.
*6 '''Polyobj_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''' but with ''distance'' multiplied by 8. Needed only for the Hexen format and supported for legacy reasons.
*2 (356) '''Polyobj_RotateLeft'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject counterclockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*3 (354) '''Polyobj_RotateRight'''(''id'', ''speed'', ''distance'')
:Rotates a polyobject clockwise by the ''distance'' [[byte angle]] difference. If ''distance'' is 0, it means 360 degrees. If ''distance'' is 255, it means perpetual spinning.
*92 (353) '''Polyobj_OR_Move'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_Move''', but overrides the current movement.
*93 '''Polyobj_OR_MoveTimes8'''(''id'', ''speed'', ''angle'', ''distance'')
:Like '''Polyobj_MoveTimes8''', but overrides the current movement.
*90 (357) '''Polyobj_OR_RotateLeft'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateLeft''', but overrides the current movement.
*91 (355) '''Polyobj_OR_RotateRight'''(''id'', ''speed'', ''distance'')
:Like '''Polyobj_RotateRight''', but overrides the current movement.
*8 (350) '''Polyobj_DoorSlide'''(''id'', ''speed'', ''angle'', ''distance'', ''delay'')
:Slides a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed.
*7 (351) '''Polyobj_DoorSwing'''(''id'', ''speed'', ''distance'', ''delay'')
:Swings a polyobject like a door which closes after a ''delay'' and deflects if it gets jammed. There are no special behaviors for setting ''distance'' to 0 or 255, unlike '''Polyobj_RotateLeft''' and derivatives.
*87 (474) '''Polyobj_Stop'''(''id'')
:Stops a polyobject from movement. It will then be free for other activations.

===Pillar building===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 29 || 362 || [[Pillar_Build]] || tag || speed || height || ||
|-
|| 30 || 364 || [[Pillar_Open]] || tag || speed || floor dist || ceil dist ||
|-
|| 94 || 363 || [[Pillar_BuildAndCrush]] || tag || speed || height || damage ||
|-
|| 251 || 468 || [[FloorAndCeiling_LowerRaise]] || tag || floor speed || ceiling speed || Boom emulation ||
|}
------------------------------------------------------------------------------
# Function ExtraData Name

362 Build pillar Pillar_Build
363 Build pillar and crush Pillar_BuildAndCrush
364 Open pillar Pillar_Open

Parameters
---------------------------------------------------------------
Pillar_Build tag, speed, height
Pillar_BuildAndCrush tag, speed, height, crush
Pillar_Open tag, speed, fdist, cdist

Values
---------------------------------------------------------------
tag : Tag of sector to close or open as a pillar. For the
action to succeed, neither surface may have an
action running on it already. If the tag is zero,
the sector on the backside of a 2S line with this
special will be used.
speed : Speed of the surface with the greatest distance to
move in eights of a unit per tic. The other surface
will move at a speed which causes it to reach its
destination at the same time.
height : For Build and BuildAndCrush types, this is the
height relative to the floor where the floor and
ceiling should meet. If this value is zero, the
floor and ceiling will meet exactly half-way.
crush : For BuildAndCrush type only, this specifies the
amount of damage to inflict per crush event.
fdist : For Open type only, this is the distance the floor
should move down. If this value is zero, the floor
will move to its lowest neighboring floor.
cdist : For Open type only, this is the distance the
ceiling should move up. If this value is zero, the
ceiling will move to its highest neighboring
ceiling.
------------------------------------------------------------------------------
*[[FloorAndCeiling_LowerRaise]]

===ACS Scripts===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 80 || 365 || [[ACS_Execute]] || script || map || arg1 || arg2 || arg3
|-
|| 81 || 366 || [[ACS_Suspend]] || script || map || || ||
|-
|| 82 || 367 || [[ACS_Terminate]] || script || map || || ||
|-
|| 83 || 430 || [[ACS_LockedExecute]] || script || map || arg1 || arg2 || lock id
|-
|| 84 || 420 || [[ACS_ExecuteWithResult]] || script || arg1 || arg2 || arg3 || arg4
|-
|| 85 || 490 || [[ACS_LockedExecuteDoor]] || script || map || arg1 || arg2 || lock id
|-
|| 226 || 477 || [[ACS_ExecuteAlways]] || script || map || arg1 || arg2 || arg3
|}
{{zdoomwiki}}
Eternity supports ACS script calling.
*365:'''ACS_Execute'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Executes the specified script. A map value of zero indicates that the script is on the current map. If the script is on a different map, then the execution of the script will be delayed until the player enters the map that contains it. Only one copy of a script can be running at a time when started with this special.
:If the specified script was previously executed but then suspended, then execution will begin at the point immediately after where it was suspended instead of starting over again at the beginning.
:The number of usable arguments is limited to 3.
*477:'''ACS_ExecuteAlways'''(''scriptnum'', ''mapnum'', ''arg0'', ''arg1'', ''arg2'')
:Same as ACS_Execute, but will not be blocked if an instance of ''scriptnum'' is already running.
*366:'''ACS_Suspend'''(''scriptnum'', ''mapnum'')
:Suspends execution of a script until an ACS_Execute special resumes it.
*367:'''ACS_Terminate'''(''scriptnum'', ''mapnum'')
:Terminates the script.
*430:'''ACS_LockedExecute'''(''scriptnum'', ''mapnum'', ''arg1'', ''arg2'', ''lock'') ''(since Feb 25 2016)''
:This one executes a script that requires the player to have a key or more. See [[Lock identifiers]] for info on what to put for the ''lock'' argument.

===Lights===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 110 || 368 || [[Light_RaiseByValue]] || tag || level || || ||
|-
|| 111 || 369 || [[Light_LowerByValue]] || tag || level || || ||
|-
|| 112 || 370 || [[Light_ChangeToValue]] || tag || level || || ||
|-
|| 113 || 371 || [[Light_Fade]] || tag || dest value || tics || ||
|-
|| 114 || 372 || [[Light_Glow]] || tag || max || min || tics ||
|-
|| 115 || 373 || [[Light_Flicker]] || tag || max || min || ||
|-
|| 116 || 374 || [[Light_Strobe]] || tag || max value || min value || max time || min time
|-
|| 232 || 463 || [[Light_StrobeDoom]] || tag || max time || min time || ||
|-
|| 233 || 473 || [[Light_MinNeighbor]] || ''tag'' || || || ||
|-
|| 234 || 461 || [[Light_MaxNeighbor]] || ''tag'' || || || ||
|-
|}
If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
* '''Light_MinNeighbor''' sets the lights in tagged sectors to their minimum neighbors' values.
* '''Light_MaxNeighbor''' sets the lights in tagged sectors to their maximum neighbors' values.

Eternity supports the following light level controlling parameterized linedef specials. If ''tag'' is 0, any such parameterized special will affect the sector behind the linedef, if applicable.
*368:'''Light_RaiseByValue'''(''tag'', ''lvl'')
:Adds the ''lvl'' value to the light levels of tagged sectors, capping them to 255.
*369:'''Light_LowerByValue'''(''tag'', ''lvl'')
:Substracts the ''lvl'' value from the light levels of tagged sectors, limiting them to 0.
*370:'''Light_ChangeToValue'''(''tag'', ''lvl'')
:Sets the ''lvl'' value for the light level of tagged sectors, and caps it between 0 and 255 inclusive.
*371:'''Light_Fade'''(''tag'', ''destvalue'', ''tics'')
:Makes the light level of tagged sectors gradually go to ''destvalue'', for the given amount of tics. ''tics'' must be greater than 0.
*372:'''Light_Glow'''(''tag'', ''maxval'', ''minval'', ''tics'')
:Enables periodic glowing light effect on tagged sectors. ''tics'' is the duration between the extreme light levels and must be positive. The sequence starts by fading down.
*373:'''Light_Flicker'''(''tag'', ''maxval'', ''minval'')
:Enables flickering light effect on tagged sectors.
*374:'''Light_Strobe'''(''tag'', ''maxval'', ''minval'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors. Light will periodically flash, staying at ''maxval'' level for ''maxtime'' tics and at ''minval'' level for ''mintime'' tics.
*463:'''Light_StrobeDoom'''(''tag'', ''maxtime'', ''mintime'')
:Enables strobing light effect on tagged sectors, using Doom's logic of choosing the minimum and maximum light levels.
*473:'''Light_MinNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their minimum neighbors' values
*461:'''Light_MaxNeighbor'''(''tag'')
:Sets the lights in tagged sectors to their maximum neighbors' values

===Things===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 17 || 422 || [[Thing_Raise]] || tid || || || ||
|-
|| 19 || 423 || [[Thing_Stop]] || tid || || || ||
|-
|| 72 || 424 || [[ThrustThing]] || angle || speed || - || tid ||
|-
|| 73 || 426 || [[DamageThing]] || damage || mod || || ||
|-
|| 119 || 427 || [[Thing_Damage]] || tid || damage || mod || ||
|-
|| 128 || 425 || [[ThrustThingZ]] || tid || speed || up or down || set or add ||
|-
|| 130 || 404 || [[Thing_Activate]] || tid || || || ||
|-
|| 131 || 405 || [[Thing_Deactivate]] || tid || || || ||
|-
|| 132 || 478 || [[Thing_Remove]] || tid || || || ||
|-
|| 133 || 428 || [[Thing_Destroy]] || tid || - || sector tag || ||
|-
|| 134 || 402 || [[Thing_Projectile]] || tid || type || angle || speed || vertical speed
|-
|| 135 || 398 || [[Thing_Spawn]] || tid || type || angle || new_tid ||
|-
|| 136 || 403 || [[Thing_ProjectileGravity]] || tid || type || angle || speed || vertical speed
|-
|| 137 || 399 || [[Thing_SpawnNoFog]] || tid || type || angle || new_tid ||
|-
|| 176 || 421 || [[Thing_ChangeTID]] || oldtid || newtid || || ||
|-
|| 248 || 469 || [[HealThing]] || amount || max health || || ||
|}
*402:'''Thing_Projectile'''(tid, type, angle, speed, verticalspeed)
:Throws a projectile from a map spot. Can also be used to throw a flying monster. Like in Thing_Spawn, ''type'' is an '''acs_spawndata num'''. Note that ''speed'' and ''verticalspeed'' are in eighths (units per 8 tics). Up is positive for ''verticalspeed''.
*403:'''Thing_ProjectileGravity'''(tid, type, angle, speed, verticalspeed)
:Same as above, but the thrown projectile or monster will be subject to gravity.
*421:'''Thing_ChangeTID'''(oldtid, newtid) ''(since Nov 14 2015)''
:Sets the TID of all things which currently have ''oldtid'' to the value ''newtid''. If ''oldtid'' is zero, it will change the TID of the activator.
*426:'''DamageThing'''(damage, mod) ''(since Feb 24 2016)''
:Damages the activator. ''Mod'' is a means-of-death ([[damagetype]]), which can be used for custom obituaries and damage resistances. If ''damage'' is 0, it will actually do 10000 (gibbing) damage.
*427:'''Thing_Damage'''(tid, damage, mod) ''(since Feb 24 2016)''
:Same as '''DamageThing''', but with the possibility to select TID (where 0 will mean the activator). It's done this way for ZDoom compatibility. Unlike '''DamageThing''', it will not cause 10000 damage if ''damage'' is 0.
*428:'''Thing_Destroy'''(tid, reserved, sectortag) ''(since Feb 24 2016)''
:Causes 10000 damage to all things tagged ''tid''. Beware that, in accordance to Hexen, ''tid'' 0 will NOT affect the activator; for that use '''DamageThing'''. ''Reserved'' must be set to 0. ''Sectortag'' can be used to only kill things inside sectors with given tag.
*478:'''Thing_Remove'''(tid)
:Directly removes objects tagged ''tid'' from the game.
*469:'''HealThing'''(amount, maxhealth)
:Heals the activator by ''amount''. ''Maxhealth'' influences maximum health and only affects player activators. For monsters and other objects, the maximum health is always the spawn health. On players, ''maxhealth'' has the following meanings:
:*If 0, it will heal the player up to the initial health (such as the maximum medikit health in default Doom).
:*If 1, it will heal the player up to the soulsphere maximum health (in default Doom) or the initial health + 100 (if no soulsphere is defined in current game mode)
:*Otherwise, it will heal the player up to ''maxhealth''.
*227 (480) '''PointPush_SetForce'''(''tag'', ''tid'', ''amount'', ''use_line'')
:Enables and sets wind for Boom push/pull source things. If ''tag'' is non-zero, it looks for such things inside a tagged sector. Only one push/pull thing will be used for each tagged sector. If ''tag'' is zero, it will enable pushing for things tagged ''tid''. ''Amount'' is the force, and depending on thing type, it will be attractive or repulsive. If ''use_line'' is 1, it will use the linedef length as amount, not the ''amount'' argument. Either the tagged sector (if ''tag'' is non-zero) or the sectors containing the ''tid'' things must have the Boom generalized wind special.

===Sectors===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 48 || 482 || yes || [[Sector_Attach3dMidtex]] || line id || optional sector tag || use ceiling || ||
|-
|| 54 || 503 || || [[Sector_ChangeFlags]] || tag || setflags || clearflags || ||
|-
|| 140 || 495 || || [[Sector_ChangeSound]] || tag || sequence id || || ||
|-
|| 185 || 470 || || [[Sector_SetRotation]] || tag || floor angle || ceiling angle || ||
|-
|| 186 || 472 || || [[Sector_SetCeilingPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 187 || 471 || || [[Sector_SetFloorPanning]] || tag || x integer || x fractional || y integer || y fractional
|-
|| 190 || 481 || yes || [[Static_Init (sky transfer)]] || tag || 255 || flip sky || ||
|}
*470:'''Sector_SetRotation'''(tag, floor_angle, ceiling_angle)
:Sets the floor and ceiling texture rotation of tagged sectors to the given values in degrees (0-360).
*471:'''Sector_SetFloorPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Sets the floor texture panning of tagged sectors to given X and Y values. A value is calculated as x_int + 0.01 * x_frac.
*472:'''Sector_SetCeilingPanning'''(tag, x_int, x_frac, y_int, y_frac)
:Same as Sector_SetFloorPanning, but for the ceiling texture.
*'''Sector_SetFriction'''(tag, amount)
:Sets friction in the target sectors. Those sectors must have the Boom generalized friction special enabled to work. ''Amount'' is an optional argument. If 0, it will use the length of the linedef to specify friction. Otherwise, the friction will be settable by ''amount''. As a rule, smaller values than 100 mean sludge (high friction) and greater than 100 mean slippery surface (low friction).
*218 (457) '''Sector_SetWind'''(''tag'', ''strength'', ''angle'', ''flags'')
:Creates wind in the tagged sectors, which, if Boom-style, must have the wind generalized special set. ''Flags'' can be the sum of the following values:
:*1: if added, it will cause the wind to be defined by the linedef's length and direction, instead of the ''strength'' and ''angle'' ([[byte angle]]) parameters;
:*2: if added, it will use Heretic-style winds, which have a slightly different behavior and scale, and will not require the Boom wind sector special to be set.
*220 (479) '''Sector_SetCurrent'''(''tag'', ''strength'', ''angle'', ''flags'')
:Similar to '''Sector_SetWind''', but meant for water flow setup, not air wind.

===Slopes===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 118 || 493 || [[Plane_Copy]] || front floor tag || front ceiling tag || back floor tag || back ceiling tag || share slope
|-
|| 181 || 455 || [[Plane_Align]] || floor || ceiling || || ||
|}

===Teleportation===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 70 || 444 || [[Teleport]] || tid || sector tag || || ||
|-
|| 71 || 445 || [[Teleport_NoFog]] || tid || use angle || sector tag || keep height ||
|-
|| 215 || 446 || [[Teleport_Line]] || - || dest_id || flip || ||
|}
*444:'''Teleport'''(tid, sector_tag, reserved)
:Teleports the activator. Depending on whether ''tid'' or ''sector_tag'' is nonzero, the behavior will be Hexen or Doom compatible. If ''tid'' is zero, then it will teleport like in Doom, into the first teleport destination found on sectors tagged ''sector_tag''.
:If ''tid'' is non-zero, it will teleport to one random target thing (doesn't matter the type) among the ones tagged ''tid''. If in this case ''sector_tag'' is also non-zero, it will only seek a destination thing located in these tagged sectors. This behavior is based on the Hexen teleporters.
*445:'''Teleport_NoFog'''(tid, use_angle, sector_tag, keep_height)
:Teleports the activator silently, without fog and without holding it. ''Tid'' and ''sector_tag'' are used the same as in '''Teleport'''.
:''Use_angle'' sets how the activator angle should be set after teleportation, and can take one of the following values:
:*0: default Hexen behavior. The thing won't change its angle at all during teleportation.
:*1: set thing's angle to the same angle as the one of the destination spot
:*2: use Boom's original, buggy behavior: shift angle ''opposite'' to that of the difference between destination spot's angle and the line normal's angle
:*3: use Boom's supposedly intended behavior: shift angle by the difference between destination spot's angle and line normal's angle.
:If ''use_angle'' is 2 or 3 and the special is not triggered from a linedef, then it will work like mode 1.
:''Keep_height'': setting this to 1 will make the thing preserve its distance to the floor after teleporting. If it's 0, the thing will be teleported on the floor, like in Hexen.
*446:'''Teleport_Line'''(reserved, dest_id, flip)
:Encapsulates the Boom line-teleporting functions. ''Dest_id'' is the tag of the target line. ''Flip'' will cause the user to rotate 180 degrees after teleporting.

===Portals===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 9 || 450 || [[Line_Horizon]] || || || || ||
|-
|| 300 || 492 || [[Portal_Define]] || portal id || type || anchor line id || z parameter || flipped anchor
|-
|| 301 || 491 || [[Line_QuickPortal]] || visual-only || || || ||
|}
*'''Line_Horizon'''
:Simple linedef specials which converts the middle part with a horizon portal which uses front sector's floor and ceiling.
*'''Portal_Define'''
:See the [[Portal_Define|linked article]] for its description.

*'''Line_QuickPortal'''(''non-interactive'')
:Convenience linedef special to quickly create a portal between two areas, through a linedef's middle part. The two lines must be of equal length, and of opposite angles (if linked/interactive) or any angle if not linked. They must have the same, unique tag and the same ''non-interactive'' value, which is 0 for linked portals and 1 for two-way non-linked portals.

*'''Sector_SetPortal'''(''tag'', ''type'', ''plane'', ''misc'')
:'''Only needed for easily converting old maps with portals'''. You can skip this part if you're designing a new UDMF map.
:Only activates on map starts, this one sets a sector portal on floor and/or ceiling on the ''tag''ged sectors. See [[Portal]] for visual examples.
:''Plane'' can be 0 (display portal on floor), 1 (display portal on ceiling), 2 (display portal on both);
:''Type'' can be:
:*0: anchored portal. This line must correspond to another line named "anchor", whose first 3 parameters are the same with this one, except that ''misc'' is 0 for the anchor, while the source line has ''misc'' 1.
:*2: skybox portal. Uses the skybox camera object as a source, and displays the skybox (view of this camera) in tagged sectors.
:*3: plane portal. Renders the ceiling texture of line's front sector at a fixed camera distance.
:*4: horizon portal. Renders the floor and ceiling textures of line's front sector at relative camera distance, useful for infinite horizontal planes such as seas.
:*6: linked portal. Interactive anchored portals (through which gameplay passes seamlessly). Has the same rule as anchored portals with regard to anchor lines. Requires consistent offsets if there are multiple linked portals in the map, otherwise linked portals are disabled.
:''Type'' can also be used for copying already placed portals:
:*1: copy the portal from a sector tagged with ''misc'' into the tagged sectors if ''tag'' is nonzero, or to the front sector if ''tag'' is 0.
:*5: copy the portal from a sector tagged with ''misc'' into the tagged lines if ''tag'' is nonzero, or to the current line if ''tag'' is 0.
:''Misc'' has values depending on the ''type'' chosen. It makes sense for anchored and linked portals (with 0 meaning source line, and 1 meaning anchor line) and it also has a meaning for the copy types (1 and 5) where it specifies the tag of the sector with portals to copy.

===Binary format specific===
*378:'''Line_SetIdentification'''(id)
:Sets the linedef identification number (separate from tag) to ''id''. Useful for various specials that use the line id. Do not use in UDMF.

===Property transfer===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Static
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 209 || 242 || yes || [[Transfer_Heights]] || tag || || || ||
|-
|| 210 || 213 || yes || [[Transfer_FloorLight]] || tag || || || ||
|-
|| 211 || 261 || yes || [[Transfer_CeilingLight]] || tag || || || ||
|}
*'''Transfer_FloorLight'''(tag)
*'''Transfer_CeilingLight'''(tag)
:These two are the same as the Boom special, but applicable in parameterized namespaces.
*'''Transfer_Heights'''(tag, reserved)
:This also acts like the Boom special 242. Argument ''reserved'' must be 0.
*190 (481) '''Static_Init'''(''tag'', ''type'', ''flip_or_ceiling'', ''move_type'')
:This is a multi-purpose special encapsulating several static specials from MBF and Boom. ''Tag'' is the tag of the target sector(s). ''Type'' can be 255 for MBF sky transfers. If ''flip_or_ceiling'' is 1, the sky will be flipped horizontally. If ''type'' is 255, ''move_type'' must be 0.

===Scrollers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 100 || 406 || [[Scroll_Texture_Left]] || amount || || || ||
|-
|| 101 || 407 || [[Scroll_Texture_Right]] || amount || || || ||
|-
|| 102 || 408 || [[Scroll_Texture_Up]] || amount || || || ||
|-
|| 103 || 409 || [[Scroll_Texture_Down]] || amount || || || ||
|-
|| 222 || 485 || [[Scroll_Texture_Model]] || line id || kind || || ||
|-
|| 223 || 484 || [[Scroll_Floor]] || tag || kind || move things || x || y
|-
|| 224 || 483 || [[Scroll_Ceiling]] || tag || kind || - || x || y
|-
|| 225 || ExtraData only || [[Scroll_Texture_Offsets]]
|}
*223 (484) '''Scroll_Floor'''(''tag'', ''kind'', ''scroll_things'', ''x'', ''y'')
*224 (483) '''Scroll_Ceiling'''(''tag'', ''kind'', ''unused'', ''x'', ''y'')
*222 (485) '''Scroll_Texture_Model'''(''line_id'', ''kind'')
:These specials do standard Boom scrolling. ''Kind'' specifies if it's a static scroller (0), displacement scroller (1) or accelerative scroller (2), and 4 can be added to it to discard arguments ''x'' and ''y'' and instead use the linedef's vertex coordinates do determine the scrolling vector. ''Scroll_things'' only apples for '''Scroll_Floor''' and means simple visual scrolling (0), thing movement with static floor (1) or thing movement with floor (2). ''X'' and ''y'' are the velocity components with which to scroll, if ''kind'' is less than 4 (otherwise the line's size is used).

:'''Scroll_Texture_Model''' does wall texture scrolling according to line's vector relative to the target lines.

===Pushers===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 218 || 457 || [[Sector_SetWind]] || tag || force || angle || flags ||
|-
|| 219 || 223 || [[Sector_SetFriction]] || tag || || || ||
|-
|| 220 || 479 || [[Sector_SetCurrent]] || tag || force || angle || flags ||
|-
|| 227 || 480 || [[PointPush_SetForce]] || tag || tid || force || use line ||
|}

===Exits===
{|class="wikitable sortable"
! UDMF #
! DOOM Format #
! Name
! Arg1
! Arg2
! Arg3
! Arg4
! Arg5
|-
|| 74 || 449 || [[Teleport_NewMap]] || level number || || || ||
|-
|| 75 || 400 || [[Teleport_EndGame]] || || || || ||
|-
|| 179 || 462 || [[ChangeSkill]] || skill || || || ||
|-
|| 243 || 447 || [[Exit_Normal]] || || || || ||
|-
|| 244 || 448 || [[Exit_Secret]] || || || || ||
|}
*400:'''Teleport_EndGame'''
:Ends the entire game in victory. This triggers the current game's assigned ending cutscene and the player can only choose to start a new game.
*447:'''Exit_Normal'''(reserved)
:Exits to a normal destination level. The argument is reserved and must be 0.
*448:'''Exit_Secret'''(reserved)
:Exits to the secret destination level. The argument is reserved and must be 0.
*449:'''Teleport_NewMap'''(level_number, reserved, reserved)
:Exits to the given map. The last two arguments are reserved and must be 0.
*462:'''ChangeSkill'''(''skill'')
:Changes the current difficulty level, where ''skill'' is from 0 (I'm too young to die) to 4 inclusive (Nightmare!).

==See also==
*[[ACS functions]]

[[Category:Editing]]
[[Category:Editing reference]]

List of maps and mods made for Eternity

2025-12-07T11:01:30Z

Printz: /* Maps */

This is a list of maps and mods designed to work with Eternity. They're either exclusively for Eternity or made to work both with Eternity and another advanced port (e.g. ZDoom). All the Boom-compatible wads are not listed here.

NOTE: the list may be incomplete, check if anything new was added in the meantime.
==Maps==
{|class="wikitable sortable"
! Name
! Author
! Notes
|-
|| [https://www.doomworld.com/idgames/levels/doom2/Ports/a-c/cc-cod Caverns of Darkness] || Chaos Crew ([https://doomwiki.org/wiki/Caverns_of_Darkness Doom wiki link]) || '''actually uses a modified version of old DOS Eternity.''' You can load it with DOSBox or similar emulators, but you may need extra setup.
|-
||[https://www.doomworld.com/forum/topic/111787-cubic-worlds-wip-a-mapset-for-eternity-with-original-music-6-maps-done/ Cubic Worlds] || [[Doom Wiki:stewboy|stewboy]] ||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/p-r/rf_kerkr De Kerker (The Dungeon)] || ravage ||
|-
||[https://doomwiki.org/wiki/DOOM_PSX:_Damnation_of_Eternity Doom PSX: Damnation of Eternity] || [https://doomwiki.org/wiki/Andrey_Skochko_(DRON12261) Andrey Skochko] ||
|-
||[https://www.doomworld.com/idgames/levels/doom/Ports/j-l/lostepis Doom: The Lost Episode] || [[Doom Wiki:Xaser|Xaser]] et al. || designed for ZDoom and Eternity.
|-
||[https://www.doomworld.com/forum/topic/122483-dread-moon-map02-released/ Dread Moon]||Gwarl||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/megawads/dsv4_rvltinE DSV Episode 4: The Revolution]|| [[Doom Wiki:Samuel Villarreal|Samuel Villarreal]] et al. || '''does not work with modern Eternity''' due to using FraggleScript)
|-
||[https://www.doomworld.com/forum/topic/120175-heartland-an-episode-for-the-eternity-engine-rc2-out-lots-of-bugfixes/ Heartland] || [[Doom Wiki:skillsaw|skillsaw]] ||
|-
||[https://www.doomworld.com/forum/topic/117985-in-search-eternity-engine-map-demo/ In search] || [[Doom Wiki:Misty|Misty]] ||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/g-i/igaite It goes away in the end] || Misty ||
|-
||[https://www.doomworld.com/forum/topic/123344-light-pollution-a-map-for-the-eternity-engine-update/ Light Pollution]|| NokturnuS ||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/d-f/e2l11 Maniac Ridge] || [[Doom Wiki:Max Waine (Altazimuth)|Max "Altazimuth" Waine]] ||
|-
||[https://doomwiki.org/wiki/MAYhem_2023 MAYhem 2023] || various || [https://doomwiki.org/wiki/James_Caldwell_(Obsidian) James Caldwell] maintainer
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/m-o/mothership Mothership] || Albatross ||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/m-o/opf Ogro Power Facility] || Stephen "[[Doom Wiki:SoM|SoM]]" McGranahan ||
|-
||[https://www.doomworld.com/idgames/levels/doom2/Ports/s-u/solid solid.pke] || [[Doom Wiki:anotak|anotak]] ||
|-
||[https://www.doomworld.com/forum/topic/122115-megawad-tarnsmans-projectile-hell-rcf/ Tarnsman's Projectile Hell]||Tarnsman||
|-
||[https://doomwiki.org/wiki/Testing_Pool Testing Pool] || [https://doomwiki.org/wiki/Zan-zan-zawa-veia Zan-zan-zawa-veia] ||
|-
||Vaporware Demo: [http://esselfortium.net/wasd/vaprdemo.zip direct download link] || [[Doom wiki:esselfortium|esselfortium]] ||
|-
||[https://www.doomworld.com/idgames/levels/doom/Ports/v-z/wastevat Waste Vats] || stewboy ||
|}

==Mods==
*[https://www.doomworld.com/idgames/combos/e_bskull The beta lost soul]: '''redundant now''' because the beta lost soul is included with Eternity.
*[https://www.doomworld.com/forum/topic/114640-colander-10-interloper-released/ Colander] by _sink
*[https://www.doomworld.com/idgames/combos/swad SWAD Pack 1: Stock CounterStrike Weapons]
*[https://www.doomworld.com/idgames/combos/swad2 SWAD Pack 2: Custom CounterStrike Weapons]

WeaponMeleeAttack

2025-10-11T18:48:27Z

Printz: Created page with "{{codepointer|description=Generic weapon melee attack, from MBF21. |usage='''A_WeaponMeleeAttack'''(''baseDamage'', ''randomMultiplier'', ''berserkMultiplier'', ''hitSound'', ''range'') |parameters= * ''baseDamage'': base damage of attack; if not set, defaults to 2 * ''randomMultiplier'': attack damage random multiplier; if not set, defaults to 10 * ''berserkMultiplier'': berserk damage multiplier; if not set, defaults to 1.0 * ''hitSound'': sound index to play if at..."

{{codepointer|description=Generic weapon melee attack, from [[MBF21]].
|usage='''A_WeaponMeleeAttack'''(''baseDamage'', ''randomMultiplier'', ''berserkMultiplier'', ''hitSound'', ''range'')
|parameters=
* ''baseDamage'': base damage of attack; if not set, defaults to 2
* ''randomMultiplier'': attack damage random multiplier; if not set, defaults to 10
* ''berserkMultiplier'': berserk damage multiplier; if not set, defaults to 1.0
* ''hitSound'': sound index to play if attack hits
* ''range'' attack range; if not set, defaults to player mobj's melee range property
|examples=
This is an example for a "plasma lance" which deals damage and noise like the plasma shot (5-40) at double range, but only has 2x berserk multiplication (because it is farther from the berserker's body).
Fire:
LANC B 4
LANC C 4 A_WeaponMeleeAttack(5, 8, 2.0, "firxpl", 128.0)
LANC D 5
LANC C 4
LANC B 5 A_ReFire
goto Ready
|notes=This is the [[MBF21]] standard implementation equivalent of [[CustomPlayerMelee]]. Check that function too for feature comparison.
|seealso=
*[[CustomPlayerMelee]]
}}

List of codepointers

2025-10-11T18:40:22Z

Printz: /* Parameterized */

This '''list of codepointers''' is a list of all the action routines which can be performed by [[thingtype|things]] from [[EDF]] [[frame]]s. They are common for all games, so for example Heretic codepointers can be used in Doom.

You can specify the codepointers with or without their internal A_ prefix, even inside [[DECORATE state syntax]]. For simplicity, they will be referred in this wiki without the prefix.

Note that some codepointers, inherited from MBF, use the '''misc1''' and '''misc2''' frame properties, instead of the more general '''args''' list. Side effects aside, this also means that in the DECORATE syntax they will have to use the '''offset'''(''misc1'', ''misc2'') specifier. They all have DECORATE-friendly equivalents however.

'''IMPORTANT:''' Do not provide more nonzero arguments to the codepointers than specified in the reference. Doing so may break forward compatibility with versions of Eternity that implement new functionality to codepointers.

{{backto|EDF state reference}}
{{backto|Eternity Engine}}

==Player guns==
===Weapon maintenance===
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[CheckAmmo]]||MBF21 ammo check against value||MBF21
|-
||[[CheckReload]]||Super shotgun reload check.||Doom 2
|-
||[[CheckReloadEx]]||Extended version of [[CheckReload]] that allows counter comparison.||Eternity
|-
||[[ConsumeAmmo]]||MBF21 codepointer to use ammo||MBF21
|-
||[[GunFlash]]||Produces a gun flash sprite without firing anything at the current moment.||Doom
|-
||[[GunFlashTo]]||Generic weapon muzzle flash||MBF21
|-
||[[JumpIfNoAmmo]]||Jumps to a state if ammo is gone.||ZDoom
|-
||[[Light0]]||Resets the gun flash light level.||Doom
|-
||[[Light1]]||Sets the gun flash light level to 1.||Doom
|-
||[[Light2]]||Sets the gun flash light level to 2.||Doom
|-
||[[Lower]]||Action during a weapon's lowering sequence.||Doom
|-
||[[Raise]]||Action during a weapon's raise sequence.||Doom
|-
||[[ReFire]]||Skip frame if shooting is sustained (e.g. for plasma rifle's cooldown effect).||Doom
|-
||[[RefireTo]]||Change to a given frame if shooting is sustained||MBF21
|-
||[[SubtractAmmo]]||Consumes one ammo unit without firing.||Eternity
|-
||[[WeaponAlert]]||Alerts monsters from the weapon frame||MBF21
|-
||[[WeaponReady]]||Action during a weapon's idle sequence.||Doom
|-
||[[WeaponSound]]||Play sound from a weapon frame.||MBF21
|}

===Player attacks===
====Classic Doom====
{|class="wikitable sortable"
! Name
! Description
! Specifics
! First game it appeared
|-
||[[BFGsound]]||Plays the BFG charge-up sound effect.||BFG||Doom
|-
||[[CloseShotgun2]]||Plays the super shotgun closing sound effect. Also includes [[ReFire]].||Super shotgun||Doom 2
|-
||[[FireBFG]]||BFG9000 attack.||BFG||Doom
|-
||[[FireCGun]]||Chaingun attack.||||Doom
|-
||[[FireMissile]]||Rocket launcher attack.||||Doom
|-
||[[FireOldBFG]]||Alpha Doom BFG attack (made available since [[MBF]]).||||Doom
|-
||[[FirePistol]]||Pistol attack.||||Doom
|-
||[[FirePlasma]]||Plasma rifle attack.||||Doom
|-
||[[FireShotgun]]||Shotgun attack.||||Doom
|-
||[[FireShotgun2]]||Super shotgun attack.||Super shotgun||Doom 2
|-
||[[LoadShotgun2]]||Plays the super shotgun loading sound effect.||Super shotgun||Doom 2
|-
||[[OpenShotgun2]]||Plays the super shotgun opening sound effect.||Super shotgun||Doom 2
|-
||[[Punch]]||Fist attack.||||Doom
|-
||[[Saw]]||Chainsaw attack.||||Doom
|}
====Classic Heretic====
These exist to support the vanilla Doom and Heretic player attacks.
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[FireBlasterPL1]]||Dragon claw attack.||Heretic
|-
||[[FireBlasterPL2]]||Dragon claw powered attack.||Heretic
|-
||[[FireCrossbowPL1]]||Ethereal crossbow attack.||Heretic
|-
||[[FireCrossbowPL2]]||Ethereal crossbow attack with Tome of Power.||Heretic
|-
||[[FireGoldWandPL1]]||Elven wand attack.||Heretic
|-
||[[FireGoldWandPL2]]||Elven wand attack with Tome of Power.||Heretic
|-
||[[FireMacePL1]]||Fire mace attack.||Heretic
|-
||[[FireMacePL2]]||Fire mace attack with Tome of Power.||Heretic
|-
||[[FirePhoenixPL1]]||[[Doom Wiki:Phoenix Rod|Phoenix Rod]] attack.||Heretic
|-
||[[FirePhoenixPL2]]||Phoenix rod attack with Tome of Power.||Heretic
|-
||[[FireSkullRodPL1]]||[[Doom Wiki:Hellstaff|Hellstaff]] attack.||Heretic
|-
||[[FireSkullRodPL2]]||[[Doom Wiki:Hellstaff|Hellstaff]] attack with Tome of Power.||Heretic
|-
||[[GauntletAttack]]||Gauntlets of the Necromancer attack.||Heretic
|-
||[[InitPhoenixPL2]]||Heretic Tome of Power Phoenix Rod startup.||Heretic
|-
||[[StaffAttackPL1]]||Heretic staff.||Heretic
|-
||[[StaffAttackPL2]]||Heretic powered staff||Heretic
|-
||[[ViewThrust]]||Heretic beak thrust||Heretic
|}

====Parameterized====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[CustomPlayerMelee]]||Configurable player melee attack.||Eternity
|-
||[[EjectCasing]]||Used for the effect of throwing casing.||Eternity
|-
||[[FireCustomBullets]]||Configurable player bullet (hitscan) attack.||Eternity
|-
||[[FirePlayerMissile]]||Configurable player projectile attack.||Eternity
|-
||[[PlayerThunk]]||{{deprecated}} Run monster-specific codepointers as weapon actions.||Eternity
|-
||[[WeaponBulletAttack]]||Generic weapon hitscan attack||MBF21
|-
||[[WeaponMeleeAttack]]||Generic weapon melee attack||MBF21
|-
||[[WeaponProjectile]]||Generic weapon projectile attack||MBF21
|}

===Weapon frame scripting===
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[PlayerStartScript]]||Starts map script, as from a player weapon.||Eternity
|-
||[[WeaponCopyCtr]]||Copy counter value to another counter.||Eternity
|-
||[[WeaponCtrOp]]||Computer operation between two counters, storing result into another counter.||Eternity
|-
||[[WeaponCtrJump]]||Change to a given state, based on a counter's value.||Eternity
|-
||[[WeaponCtrSwitch]]||Change to a state from a given list, depending on a counter's value.||Eternity
|-
||[[WeaponJump]]||Weapon frame compatible random frame change||MBF21
|-
||[[WeaponSetCtr]]||Assign value to a counter.||Eternity
|-
||[[WeaponSetTics]]||Set weapon frame duration.||Eternity 4.4.0
|}

==Map objects==
===Simple movement===
These operations perform simple effects on thing's direction, position or velocity. The available codepointers are:
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[Face]]||Face a specified angle.||MBF
|-
||[[Stop]]||Set velocity to 0.||MBF beta emulation
|-
||[[Turn]]||Turn around by a specified angle.||MBF
|-
||[[TurnProjectile]]||Turn around and update velocity to direction.||Eternity 4.2.0
|}

===Explosions and flames===
====BFG9000====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BFG11KHit]]||[[SMMU]] BFG variant.||SMMU
|-
||[[BFGBurst]]||Produces a burst of smaller plasma projectiles.||MagDOOM by Cephaler
|-
||[[BFGSpray]]||Original Doom BFG explosion damage-inflicting afterglow.||Doom
|-
||[[BouncingBFG]]||SMMU bouncing BFG.||SMMU
|}

====DOOM 2 Final boss====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BrainExplode]]||Brain perpetual explosion controller.||Doom 2
|-
||[[BrainScream]]||Giant demon wall explosion sequence.||Doom 2
|-
||[[SpawnFly]]||Spawn cube controller.||Doom 2
|}

====Explosions====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[Detonate]]||Thing damage controlled explosion.||MBF
|-
||[[DetonateEx]]||Parameterized detonate action.||Eternity
|-
||[[Explode]]||Rocket/barrel splash damage.||Doom
|-
||[[Mushroom]]||[[MBF]]-style mushroom explosion.||MBF
|-
||[[MushroomEx]]||Extended mushroom explosion codepointer.||Eternity
|-
||[[Nailbomb]]||[[SMMU]]-style explosion with shrapnels.||SMMU
|-
||[[RadiusDamage]]||MBF21 explosion: allows separate radius and damage values.||MBF21
|}
=====Heretic=====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[DeathBallImpact]]||Heretic super firemace sphere impact.||Heretic
|-
||[[HticExplode]]||Heretic-compatible explosion.||Heretic
|-
||[[MaceBallImpact]]||Heretic small firemace sphere impact.||Heretic
|-
||[[MaceBallImpact2]]||Heretic medium firemace sphere impact.||Heretic
|}

====Homing projectiles====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[ClearTracer]]||Stop seeking current target.||MBF21
|-
||[[FindTracer]]||Homing target search and lock.||MBF21
|-
||[[GenTracer]]||Generic homing projectile.||Eternity
|-
||[[HticTracer]]||Heretic nitrogolem homing projectile (generalized).||Heretic
|-
||[[MummyFX1Seek]]||Heretic nitrogolem homing projectile (particular).||Heretic
|-
||[[SeekerMissile]]||ZDoom-based generic homing missile.||ZDoom
|-
||[[SeekTracer]]||Generic seeker missile function.||MBF21
|-
||[[SkullRodPL2Seek]]||Powered hellstaff projectile seek||Heretic
|-
||[[Tracer]]||Revenant homing projectile.||Doom 2
|}

====Others====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[Fire]]||Stick on the face of attacker's target, like the archvile's fire effect.||Doom 2
|}
=====Heretic specific=====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AddPlayerRain]]||Powered hellstaff hellrain maintenance||Heretic
|-
||[[FlameEnd]]||Phoenix rod flame rising.||Heretic
|-
||[[FloatPuff]]||Phoenix rod flame hitting wall.||Heretic
|-
||[[BeastPuff]]||Weredragon fire projectile smoke.||Heretic
|-
||[[BoltSpark]]||Ethereal arrow trail.||Heretic
|-
||[[BlueSpark]]||Create a blue D'sparil attack projectile.||Heretic
|-
||[[GenWizard]]||Spawn a disciple of D'sparil.||Heretic
|-
||[[LichFireGrow]]||Expand the iron lich fire column projectile.||Heretic
|-
||[[LichIceImpact]]||Explode iron lich ice globe into shards.||Heretic
|-
||[[MacePL1Check]]||Small Heretic mace sphere maintenance.||Heretic
|-
||[[MntrFloorFire]]||Used by the maulotaur ground fire projectile.||Heretic
|-
||[[PhoenixPuff]]||Phoenix rod missile trail.||Heretic
|-
||[[PodPain]]||Special effect when pod is damaged.||Heretic
|-
||[[RainImpact]]||Hell rain fall impact.||Heretic
|-
||[[SkullRodStorm]]||Spawn hellrain drop||Heretic
|-
||[[SpawnRippers]]||Powered dragon claw impact spawning of ripping balls||Heretic
|-
||[[VolcBallImpact]]||Heretic volcano lava ball impact.||Heretic
|-
||[[WhirlwindSeek]]||Homing behaviour used by iron lich tornado projectiles.||Heretic
|}

===AI===
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AlertMonsters]]||Shout so other monsters chase the player.||ZDoom
|-
||[[Chase]]||Pursue a target and check for attacks||Doom
|-
||[[CPosRefire]]||Go to '''seestate''' if target is out of sight.||Doom 2
|-
||[[FaceTarget]]||Turn to target, looking around it if it's partially invisible.||Doom
|-
||[[GenRefire]]||Customizable refire control.||Eternity
|-
||[[HealChase]]||Parameterized version of VileChase.||MBF21
|-
||[[KeepChasing]]||pursue target without attacking.||Eternity
|-
||[[Look]]||Stand in guard, looking for targets.||Doom
|-
||[[NoiseAlert]]||MBF21 version of AlertMonsters||MBF21
|-
||[[RandomWalk]]||Random wandering for inactive enemies.||Eternity
|-
||[[Sor1Chase]]||D'sparil's mount specific chase.||Heretic
|-
||[[Sor1Pain]]||D'sparil's mount specific twitch. Calls Pain.||Heretic
|-
||[[SpidRefire]]||Like CPosRefire, slightly modified.||Doom
|-
||[[VileChase]]||Same as Chase, but resurrects encountered cadavres.||Doom 2
|}

===AI attacks===
====Parameterized====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BetaSkullAttack]]||Remote melee attack, as used by the Doom alpha lost souls (available since [[MBF]]).||MBF beta emulation
|-
||[[BulletAttack]]||Generic bullet (hitscan) shooting.||Eternity
|-
||[[MissileAttack]]||Generic projectile shooting.||Eternity
|-
||[[MissileSpread]]||'''MissileAttack''' variation, supports shooting in spread patterns.||Eternity
|-
||[[MonsterBulletAttack]]||MBF21 variant of BulletAttack||MBF21
|-
||[[MonsterMeleeAttack]]||MBF21 variant of Scratch||MBF21
|-
||[[MonsterProjectile]]||MBF21 variant of MissileAttack||MBF21
|-
||[[SargAttack12]]||Old Doom 1.2 style monster melee attack which uses hitscan similar to player's fist.||Doom v1.2
|-
||[[Scratch]]||Generic melee attack.||MBF
|-
||[[ThingSummon]]||Generic creature summoning.||Eternity
|}

====Original Doom====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BrainSpit]]||cube spawn||Doom 2
|-
||[[BruisAttack]]||baron/knight of hell||Doom
|-
||[[BspiAttack]]||arachnotron||Doom 2
|-
||[[CPosAttack]]||pistol attack w/ shotgn noise||Doom 2
|-
||[[CyberAttack]]||rocket launching||Doom
|-
||[[FatAttack1]]||mancubus left attack||Doom 2
|-
||[[FatAttack2]]||mancubus right attack||Doom 2
|-
||[[FatAttack3]]||mancubus front attack||Doom 2
|-
||[[HeadAttack]]||cacodemon||Doom
|-
||[[PainAttack]]||elemental||Doom 2
|-
||[[PainDie]]||elemental death (3 souls)||Doom 2
|-
||[[PosAttack]]||former human||Doom
|-
||[[SargAttack]]||demon bite||Doom
|-
||[[SkelFist]]||revenant punch||Doom 2
|-
||[[SkelMissile]]||revenant missile||Doom 2
|-
||[[SkullAttack]]||flying skull||Doom
|-
||[[SPosAttack]]||sergeant||Doom
|-
||[[TroopAttack]]||imp||Doom
|-
||[[VileAttack]]||arch vile toss||Doom 2
|-
||[[VileTarget]]||spawn a vile fire effect on target||Doom 2
|}

====Heretic====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BeastAttack]]||weredragon||Heretic
|-
||[[ClinkAttack]]||sabreclaw||Heretic
|-
||[[ImpChargeAtk]]||gargoyle charge||Heretic
|-
||[[ImpMeleeAtk]]||gargoyle scratch||Heretic
|-
||[[ImpMissileAtk]]||gargoyle fire||Heretic
|-
||[[KnightAttack]]||undead warrior||Heretic
|-
||[[LichAttack]]||iron lich random attack **only one which includes ice globes**||Heretic
|-
||[[LichFire]]||iron lich fire column||Heretic
|-
||[[LichWhirlwind]]||iron lich tornado||Heretic
|-
||[[MinotaurAtk1]]||maulotaur melee damage||Heretic
|-
||[[MinotaurAtk2]]||spreadshot||Heretic
|-
||[[MinotaurAtk3]]||straight flame snake||Heretic
|-
||[[MinotaurCharge]]||maulotaur charge||Heretic
|-
||[[MinotaurDecide]]||maulotaur ranged attack choosing||Heretic
|-
||[[MummyAttack]]||golem melee||Heretic
|-
||[[MummyAttack2]]||nitrogolem range||Heretic
|-
||[[SnakeAttack]]||ophidian blue spark||Heretic
|-
||[[SnakeAttack2]]||ophidian yellow shot||Heretic
|-
||[[Srcr1Attack]]||d'sparil mount attack||Heretic
|-
||[[Srcr2Attack]]||d'sparil sorcerer attack||Heretic
|-
||[[Srcr2Decide]]||d'sparil decide whether to teleport||Heretic
|-
||[[VolcanoBlast]]||volcano burst||Heretic
|-
||[[WizardAtk3]]||disciple tri-ball||Heretic
|}

===Alterations===
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AddFlags]]||Add flags (MBF21 style)||MBF21
|-
||[[BossDeath]]||special monster death functions (such as Baron death in E1M8)||Doom
|-
||[[BrainDie]]||exits the level||Doom 2
|-
||[[CasingThrust]]||movement for ejected casing||Eternity
|-
||[[Die]]||causes suicide||MBF
|-
||[[Fall]]||remove SOLID flag (used on dying monsters)||Doom
|-
||[[KeenDie]]||open 666-tagged doors on death of all like-named monsters||Doom 2
|-
||[[KillChildren]]||destroy all summoned things||ZDoom
|-
||[[LineEffect]]||activate a tag using a special||MBF
|-
||[[PainNukeSpec]]||Pain elemental nuke cheat handler.||Eternity
|-
||[[RemoveFlags]]||MBF21 codepointer to remove flags||MBF21
|-
||[[RestoreArtifact]]||Adds the SPECIAL flag back to an object, sets the object back into its spawnstate, and plays the object's seesound.||Heretic
|-
||[[RestoreSpecialThing1]]||Removes the DONTDRAW flag from an object. If the object defines the itemrespawnat property, it will at this time be moved to a random spot if any such spots exist on the map (otherwise the item will remain where it spawned originally). The item will play its seesound.||Heretic
|-
||[[RestoreSpecialThing2]]||Adds the SPECIAL flag back to an object and sets the object back into its spawnstate.||Heretic
|-
||[[SelfDestruct]]||Projectile-compatible counterpart to '''Die'''.||Eternity
|-
||[[SetFlags]]||alter flags||Eternity
|-
||[[SetSpecial]]||alter thing's special and args||ZDoom
|-
||[[ShowMessage]]||display text message||Eternity
|-
||[[Spawn]]||create another object on top of this one||MBF
|-
||[[SpawnEx]]||enhanced spawn variant||Eternity
|-
||[[SpawnObject]]||MBF21 spawn variant||MBF21
|-
||[[SteamSpawn]]||create steam effects||Eternity
|-
||[[UnSetFlags]]||alter flags||Eternity
|}
====Visual====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[ClearSkin]]||Removes the sprite skin.||Eternity
|-
||[[FadeIn]]||increments alpha||ZDoom
|-
||[[FadeOut]]||decrements alpha, DOESN'T destroy the thing||ZDoom
|-
||[[HideThing]]||Sets DONTDRAW flag on an object||ZDoom
|-
||[[SetTranslucent]]||modify alpha amount; setup additiveness or fuzziness||ZDoom
|-
||[[UnHideThing]]||Unsets DONTDRAW flag on an object||ZDoom
|-
|}
====Heretic====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AccelGlitter]]||accelerate upwards||Heretic
|-
||[[DripBlood]]||spawn heretic blood||Heretic
|-
||[[Feathers]]||make feathers fly||Heretic
|-
||[[GhostOff]]||Remove the ghost effect||Heretic
|-
||[[HideInCeiling]]||moves above ceiling level||Heretic
|-
||[[HticBossDeath]]||special monster death functions for Heretic||Heretic
|-
||[[Fall|HticDrop]]||{{deprecated}} same thing as [[Fall]]||Heretic
|-
||[[ImpDeath]]||special death for gargoyle||Heretic
|-
||[[ImpExplode]]||crash for gargoyle||Heretic
|-
||[[ImpXDeath1]]||special extreme death for gargoyle, stage 1||Heretic
|-
||[[ImpXDeath2]]||special extreme death for gargoyle, stage 2||Heretic
|-
||[[InitKeyGizmo]]||Heretic key lock orb statue maintenance||Heretic
|-
||[[MakePod]]||generate a pod||Heretic
|-
||[[MummySoul]]||create raising soul||Heretic
|-
||[[PlayerSkull]]||player death effect, when the skull tosses in air||Heretic
|-
||[[RemovePod]]||notifies the generator that this pod was destroyed||Heretic
|-
||[[Sor2DthInit]]||d'sparil death maintenance||Heretic
|-
||[[Sor2DthLoop]]||d'sparil death maintenance||Heretic
|-
||[[SorcererRise]]||d'sparil waking up after mount crash||Heretic
|-
||[[SorcNukeSpec]]||D'sparil handling of the nuke cheat.||Heretic
|-
||[[SpawnAbove]]||spawns above the summoner||Heretic
|-
||[[SpawnGlitter]]||create teleportation sparkle||Heretic
|-
||[[SpawnTeleGlitter]]||Heretic teleport glitter object spawner.||Heretic
|-
||[[SpawnTeleGlitter2]]||Heretic exit glitter object spawner.||Heretic
|-
||[[VolcanoSet]]||Set volcano tic duration||Heretic
|-
||[[WizardAtk1]]||face target and clear GHOST flag||Heretic
|-
||[[WizardAtk2]]||face target and set GHOST flag||Heretic
|}

===Sound effects===
====Generic====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AmbientThinker]]||ambient sound maintenance||Eternity
|-
||[[Pain]]||play pain sound||Doom
|-
||[[PlayerScream]]||player-specific, health-dependent (death) sound||Doom
|-
||[[PlaySound]]||custom sound||MBF
|-
||[[PlaySoundEx]]||extended custom sound||ZDoom
|-
||[[Scream]]||play death sound||Doom
|-
||[[XScream]]||extreme death gut noise||Doom
|}
====Game specific====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BrainAwake]]||loud bossit sound effect||Doom 2
|-
||[[BrainPain]]||loud bospn sound effect||Doom 2
|-
||[[ContMobjSound]]||Heretic knight axe and nitrogolem missile sounds||Heretic
|-
||[[ESound]]||Heretic water and wind ambiend sounds||Heretic
|-
||[[FlameSnd]]||Heretic player burning death sound||Heretic
|-
||[[RavenPlayerScream]]||Heretic player scream||Heretic
|-
||'''SorDBon'''||Plays sound 329 ('''ht_sordbon''')||Heretic
|-
||'''SorDExp'''||Plays sound 328 ('''ht_sordexp''')||Heretic
|-
||'''SorDSph'''||Plays sound 327 ('''ht_sordsph''')||Heretic
|-
||'''SorRise'''||Plays sound 322 ('''ht_sorrise''')||Heretic
|-
||'''SorSightSnd'''||Plays sound 323 ('''ht_sorsit''')||Heretic
|-
||'''SorZap'''||Plays sound 321 ('''ht_sorzap''')||Heretic
|-
||[[StartFire]]||flamst sound effect — also includes "Fire" action!||Doom 2
|-
||[[VileStart]]||archvile heat-up noise||Doom 2
|}
=====Combined=====
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[BabyMetal]]||bspwlk sound effect — also includes Chase!||Doom 2
|-
||[[FatRaise]]||mancubus warning — also includes FaceTarget||Doom 2
|-
||[[FireCrackle]]||flame sound effect — also includes "Fire" action!||Doom 2
|-
||[[Hoof]]||cyberdemon hoof sound — also includes Chase!||Doom
|-
||[[Metal]]||metal sound effect — also includes Chase!||Doom
|-
||[[SkelWhoosh]]||revenant swing noise — also includes FaceTarget||Doom 2
|-
||[[SpawnSound]]||boscub sound effect — also includes SpawnFly||Doom 2
|}

===Frame scripting===
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[AproxDistance]]||assign distance from target to a variable||Eternity
|-
||[[CheckPlayerDone]]||jump to a frame if not under player control||ZDoom
|-
||[[CopyCounter]]||copy a variable to another variable||Eternity
|-
||[[CounterDiceRoll]]||set a variable to the result of a damage calculation||Eternity
|-
||[[CounterJump]]||counter-based next frame||Eternity
|-
||[[CounterJumpEx]]||DECORATE-compatible counter-based next frame||Eternity
|-
||[[CounterOp]]||set a variable to an operation of another 2 variables||Eternity
|-
||[[CounterSwitch]]||counter-based set of frames||Eternity
|-
||[[CounterSwitchEx]]||DECORATE-compatible counter-based set of states||Eternity
|-
||[[HealthJump]]||health-based next frame||Eternity
|-
||[[JumpIfFlagsSet]]||jump if flags set||MBF21
|-
||[[JumpIfHealthBelow]]||jump to frame if health is below threshold||MBF21
|-
||[[JumpIfTargetInLOS]]||jump to frame if target is in the field of view||ZDoom
|-
||[[JumpIfTargetInSight]]||MBF21 target sight and field of view test.||MBF21
|-
||[[JumpIfTargetCloser]]||Jump if target is closer than threshold||MBF21
|-
||[[JumpIfTracerInSight]]||Jump if projectile seeking target is in sight||MBF21
|-
||[[JumpIfTracerCloser]]||Jump if projectile seeking target is closer than threshold||MBF21
|-
||[[RandomJump]]||random next frame||MBF
|-
||[[Jump]]||Decorate-compatible alternative to RandomJump.||ZDoom
|-
||[[SetCounter]]||set a variable||Eternity
|-
||[[SetTics]]||set frame duration||Eternity
|-
||[[StartScript]]||run map script (such as [[ACS]])||Eternity
|-
||[[StartScriptNamed]]||run named map script||Eternity
|-
||[[TargetJump]]||go to designated frame if having a target||Eternity
|}

===Powerup use===
These are triggered from [[EDF_item_effects_and_inventory#artifact|artifact]]'s '''useaction''' field, not from states.
{|class="wikitable sortable"
! Name
! Description
! First game it appeared
|-
||[[HticArtiTele]]||Chaos Device action||Heretic
|-
||[[HticMorphOvum]]||Morph Ovum action||Heretic
|-
||[[HticSpawnFireBomb]]||Time Bomb of the Ancients action||Heretic
|}

[[Category:Codepointers|*]]
[[Category:EDF]]

Generalized sector types

2025-10-04T18:22:05Z

Printz: /* Introduced with MBF21 */

Eternity provides generalized sector types, based on bit fields, that allow several sector type properties to be independently specified for a sector. Texture change linedefs can be used to switch some or all of these properties dynamically, outside lighting.

{{Backto|Sector types}}

'''For classic non-UDMF format only''': Bits 0 to 4 specify the lighting type in the sector, the same codes that DOOM used are employed:

Dec Bits 4-0 Description
-------------------------------------------------------------------
0 00000 Normal lighting
1 00001 random off
2 00010 blink 0.5 second
3 00011 blink 1.0 second
4 00100 -10/20% health AND light blink 0.5 second
8 01000 light oscillates
12 01100 blink 0.5 second, synchronized
13 01101 blink 1.0 second, synchronized
17 10001 flickers on and off randomly

'''For UDMF''': bits 0 to 7 are the same as in [[Regular sector types]], the UDMF section.

'''IMPORTANT for UDMF''': to use the following values in UDMF, you need to multiply them by 8 first. The components from 0 to 255 apply te

All decimal values listed below can be added from each category to obtain the generalized sector effects.

Bits 5 and 6 set the damage type of the sector, with the usual 5/10/20 damage units per second.

Dec UDMF dec Bits 6-5 / 9-8 Description
-------------------------------------------------------------------
0 0 00 No damage
32 256 01 5 units damage per sec (halve damage in TYTD skill)
64 512 10 10 units damage per sec
96 768 11 20 units damage per sec
Bit 7 makes the sector count towards the secrets total at game end

Dec UDMF dec Bit 7 / 10 Description
-------------------------------------------------------------------
0 0 0 Sector is not secret
128 1024 1 Sector is secret
Bit 8 enables the ice/mud effect controlled by linedef 223

Dec UDMF dec Bit 8 / 11 Description
-------------------------------------------------------------------
0 0 0 Sector friction disabled
256 2048 1 Sector friction enabled
Bit 9 enables the wind effects controlled by linedefs 224-226

Dec UDMF dec Bit 9 / 12 Description
-------------------------------------------------------------------
0 0 0 Sector wind disabled
512 4096 1 Sector wind enabled
== Introduced with SMMU ==

Bits 10 and 11 are now implemented as of SMMU v3.21.
Bit 10 suppresses all sounds within the sector, while Bit 11 disables any sounds due to floor or ceiling motion by the sector. Bit 11 is especially useful in silencing constructs such as pseudo-3D bridges, which give off an undesirable plat sound when they move.

Dec UDMF dec Bit 10 / 13 Description
-------------------------------------------------------------------
0 0 0 Sounds made in sector function normally
1024 8192 1 Sounds made in sector are suppressed

Dec UDMF dec Bit 11 / 14 Description
-------------------------------------------------------------------
0 0 0 Sounds made by sector floor/ceiling movement normal
2048 16384 1 Sounds made by sector floor/ceiling movement suppressed

== Introduced with MBF21 ==
These new bits are added since the MBF21 editing standard.

===Instant death sector===
A new bit is added in MBF21, bit 12 under classic format and bit 15 under UDMF. When this bit is set, bits 5-6 (classic) or 8-9 (UDMF) change their meaning from "sector damage" to different variations of this instant death sector type, as shown in the following table:

{|class="wikitable sortable"
! Dec
! Hex
! UDMF dec
! UDMF hex
! Description
|-
||4096||1000||32768||8000||Player dies instantly when on sector floor (unless wearing radiation suit or invulnerability)
|-
||4128||1020||33024||8100||Player dies instantly when on sector floor (even if wearing suit or invulnerability)
|-
||4160||1040||33280||8200||Kill all players and exit to next level (useful for forcing pistol start)
|-
||4192||1060||33536||8300||Kill all players and exit to the secret level (useful for forcing pistol start)
|}

===Kill grounded monsters===
Bit 13, i.e. value 8192, if added to a sector, causes monsters on the ground to die.

[[Category:Editing reference]]

BFGSpray

2025-08-23T20:32:57Z

Printz:

{{codepointer|description=BFGSpray is a codepointer which causes a BFG explosion effect.|usage='''BFGSpray'''(''sprayType'', ''numRays'', ''damageCount'', ''fov'', ''maxDist'')
|parameters=
*''sprayType'': name of thing type to spawn on hit targets. Default is the thingtype with dehackednum 43, which in Doom is BFGFlash.
*''numRays'': number of rays. Default: 40.
*''damageCount'': how many times to add the random 1-8 damage for each ray. Default: 15.
*''fov'': angle in degrees of the spread. Default: 90.
*''maxDist'': range of each ray. Default: 1024.
|notes=
The effect differs depending on the player's selected type of BFG:

*Normal BFG: ''numRays'' tracers will emanate from the object which fired the projectile in the general direction in which the projectile was fired, each doing damage that is the sum of ''damageCount'' rolls of an 8-sided die.
*BFG11K: Control is transferred to the [[BFG11KHit]] codepointer.
*Bouncing BFG: Control is transferred to the [[BouncingBFG]] codepointer.
*Plasma Burst BFG: Control is transferred to the [[BFGBurst]] codepointer.

Note: this will not trigger the Doom beta BFG attack if its gameplay setting is enabled. There is a separate set of frames for the classic BFG that replace the normal BFG9000.|seealso=
*[[BFG11KHit]]
*[[BFGBurst]]
*[[BouncingBFG]]|examples=
{{example|description=From base\doom\frames.edf:|code=<nowiki>frame S_BFGLAND3 { cmp = "BFE1|2|T|8|BFGSpray|@next"; dehackednum = 119 }</nowiki>}}}}

Eternity Engine

2025-08-23T17:30:55Z

Printz: /* Version 4.05 */

The Eternity Engine is [[Doom Wiki:Team Eternity|Team Eternity]]'s advanced [[Doom Wiki:Doom|Doom]] [[Doom Wiki:Source port|source port]] and the primary subject of this Wiki. It is meant as a versatile feature port which keeps gameplay compatibility with its roots (DOOM, [[BOOM]], [[MBF]] and so on) while advancing with powerful features such as new ways to design levels ([[linked portals]], [[3DMidTex]], [[polyobjects]] etc.) and modding capabilities (using the [[EDF]] definition language). Every new feature we add is tested not to affect anything that exists so far.

==History==
The Eternity Engine began in 1998 as a simple modification of [[Doom Wiki:Boom|Boom]] meant to power [[Doom Wiki:Eternity TC|Eternity TC]], which was at that time a new and active project. When [[Doom Wiki:Lee Killough|Lee Killough]] began the [[MBF]] project, [[Doom Wiki:James_Haley_(Quasar)|James "Quasar" Haley]] became a beta tester after emailing Lee with questions about the early Doom alpha versions. The Eternity project moved to an MBF code base after that port's first release.

In late 1999, [[Doom Wiki:Simon "Fraggle" Howard|Fraggle]] released v3.10 of his MBF-based source port [[SMMU]], which contained support for the new [[Doom Wiki:FraggleScript|FraggleScript]] scripting language. Although activity in the Eternity TC project by editors had steadily dropped to almost nothing, Quasar was still interested in developing the code associated with it. Needing features such as scripting and the [[console]], he then moved the Eternity project's code into SMMU.

Despite this long history of jumping between Boom-based ports, no public release of Eternity based on any port other than SMMU was ever made. The first private alpha, released to a select few beta testers, was derived from SMMU 3.21 with selected modifications from 3.30. Because of this, Eternity began at version 3.29.

After the release of the [[Doom Wiki:Caverns_of_Darkness|Caverns of Darkness]] project, which used a customized version of Eternity Engine v3.29 Development Beta 5, the project began to attract more attention. A second programmer, [[Doom Wiki:Stephen_McGranahan_(SoM)|Steven "SoM" McGranahan]], joined the project and immediately set to work porting the code to use [[Wikipedia:Simple_DirectMedia_Layer|SDL]], making it capable of running on many operating systems, including [[Wikipedia:Microsoft Windows|Windows]].

Now it has [[Universal Doom Map Format|UDMF]] support and a dynamic weapon and inventory system. It supports linked portals for full room-over-room gameplay. Current major goals for the engine include completing support for [[Doom Wiki:Heretic|Heretic]].

==Getting started==
You can download Eternity either from [https://www.doomworld.com/forum/25-eternity/ Doomworld] (as official releases) or from [https://devbuilds.drdteam.org/eternity/ DRDTeam] (as "beta quality" development builds, which in practice are generally stable, and may be needed for some modding features listed on this wiki).

Eternity's goal that makes it different from feature ports such as [[Doom Wiki:GZDoom|GZDoom]] is demo compatibility similar to that of [[Doom Wiki:PrBoom+|PrBoom+]], kept specifically to ensure that every new feature we add fits seamlessly with what exists so far, and that we don't stray from the bases made so far in the DOOM gameplay.

Support for [[Doom Wiki:Heretic|Heretic]] is growing, though still under way. While we don't support vanilla Heretic demos for playback yet, a possibility exists in the horizon.

===Playing Eternity===
When run directly, Eternity tries to find the DOOM, DOOM 2 or Final DOOM megawads in some standard locations. If it can't find them, it will let you know. If it finds several of them, it will start with a picker screen, letting you choose.

On [[Wikipedia:Windows|Windows]] you can use the drag-and-drop feature of Explorer by moving WADs and PKEs into Eternity's executable. Or you can use Powershell or Command Prompt in a manner similar to starting [[Doom Wiki:Vanilla Doom|vanilla DOOM]]. See [[list of command line parameters]]. For more advanced cases, you can use [[GFS]] files to quickly load multiple files and settings together.

The [[Wikipedia:macOS|macOS]] version of Eternity also comes with a visual dialog-box launcher, hiding the complexity behind starting a terminal.

For advanced technical stuff, cheating and testing maps, Eternity has a [[console]] similar to [[Wikipedia:Quake|Quake's]].

====Loading main game WADs====
Eternity looks for the main game WADs (IWADs), e.g. doom2.wad, at these locations:
* IWAD file paths in user/system.cfg;
* the -iwad command-line parameter;
* the [[Doom Wiki:Environment variables|'''DOOMWADDIR''' or '''DOOMWADPATH''' environment variables]];
* the IWAD in the working directory;
* the IWAD file under the appropriate game folder of the base directory, which can be found using the -game parameter.

====Loading Master Levels for DOOM II====
Eternity offers a menu for conveniently loading each WAD from the Master Levels. To start the Master Levels:
# Start Eternity with DOOM II;
# Go to the Options menu, under the Game Files section, select WAD Options;
# Under the Master Levels section, you may need to specify Master Levels Dir to the path with the WADs;
# Once the path is configured, enter Play Master Levels.
Once the Master Levels Dir is configured, entering New Game from the menu will give you the choice to start the Master Levels.

===Making mods for Eternity===
The editors [[Doom Wiki:Doom Builder X|Doom Builder X]], [[Doom Wiki:GZDoom Builder|GZDoom Builder]], [[Doom Wiki:Eureka|Eureka]] and [[Doom Wiki:SLADE|SLADE]] have Eternity level editing support of varying degrees. For [[UDMF]] (modern advanced format) you can use Doom Builder X, GZDoom Builder or SLADE. However, if you lack access to a UDMF-capable editor or don't want the complexity it brings, you can also use the classic DOOM format, combined with [[ExtraData]]

For general modding, Eternity relies on [[EDF]], its own content definition language. For level definitions in particular it uses [[EMAPINFO]]. Eternity also has growing support for some lumps from [[Doom Wiki:GZDoom|GZDoom]] and [[Doom Wiki:Hexen|Hexen]] such as [[ANIMDEFS]], thus increasing the support for cross-port mods.

Eternity can load [[PKE]] archives, not just [[Doom Wiki:WAD|WADs]]. It can also load unarchived folders structured the same as PKE archives (you can use the -file command-line parameter on folders), facilitating project work. You can use powerful editors such as [[Wikipedia:Visual Studio Code|Visual Studio Code]] on such folders to edit your EDF modifications.

See [[Editing reference|all editing reference]] to get started on modding.

==Major Features==

===Cardboard engine===
[[Cardboard]] is a floating-point rendering engine created by [[Doom Wiki:Stephen_McGranahan_(SoM)|SoM]] that fixes several problems inherent with the classic fixed-point [[Doom Wiki:Doom rendering engine|Doom rendering engine]].

===EDF===
[[EDF]], which stands for Eternity Definition Files, is a textual input language that allows specification of almost all the static game data which was once contained inside the executable. This includes [[thingtype|thing types]], [[frame|frames]], sprites, terrain definitions, and more. EDF has a relaxed [[Wikipedia:C programming language|C]]-like syntax and can be used from both files and [[WAD]] lumps.

===ExtraData===
[[ExtraData]] is another EDF-like data specification language that allows the Doom map format to be extended with any kind of data. Use of special thing, line, and sector types within a map allows the editor to attach ExtraData records to those objects. Special data for the objects is then given inside the script.

===Linked portals===
[[Linked portals]] are surfaces that, like regular [[portals]], connect different areas of the map, but in addition can be walked through, thus allowing multistory maps to be designed in Doom.

===[[MapInfo]]===
Eternity expands SMMU's level info system significantly, allowing dozens of new properties to be specified, and allowing cascading global EMAPINFO lumps as an alternative to inserting MapInfo data into level headers. Among other things, MapInfo is used to tie ExtraData and ACS scripts to the maps that use them.

==Releases==
A complete list of Eternity's release history follows. You can find most of these releases on the [https://www.doomworld.com/forum/25-eternity/ Doomworld Eternity forum], on the [https://github.com/team-eternity/eternity/releases GitHub Eternity repository] and the older releases on the [http://eternity.mancubus.net/ee-old/ Eternity Mancubus website]. Most of the releases are Windows only, but the most recent ones are also available on macOS.

For finer grained non-official releases, see also the [[Eternity Engine#Development builds|development builds]] below.

===Version 3.29===
* 3.29 Private Alpha - September 14, 2000
* 3.29 Public Beta 1 - January 8, 2001
* 3.29 Public Beta 2 - January 9, 2001
* 3.29 Public Beta 3 - May 10, 2001
* 3.29 Public Beta 4 - June 30, 2001
* 3.29 Development Beta 5 - October 2, 2001
* 3.29 "Gamma" - July 4, 2002

===Version 3.31===
* 3.31 Public Beta 1 - September 11, 2002
* 3.31 Public Beta 2 - March 5, 2003
* 3.31 Public Beta 3 - August 8, 2003
* 3.31 Public Beta 4 - November 29, 2003
* 3.31 Public Beta 5 - December 17, 2003
* 3.31 Public Beta 6 - February 29, 2004
* 3.31 Public Beta 7 - April 11, 2004
* 3.31 "Delta" Pre-Release Alpha 1 - August 23, 2004
* 3.31 "Delta" Pre-Release Alpha 2 - November 11, 2004
* 3.31.10 "Delta" - January 19, 2005

===Version 3.33===
* 3.33.00 "Genesis" - May 26, 2005
* 3.33.01 "Outcast" - June 24, 2005
* 3.33.02 "Warrior" - October 1, 2005
* 3.33.33 "Paladin" - May 17, 2006
* 3.33.50 "Phoenix" - October 23, 2006

===Version 3.35===
* [http://www.doomworld.com/vb/eternity/45146-eternity-engine-v3-35-90-simorgh/ 3.35.90] "Simorgh" - January 11, 2009
* [http://www.doomworld.com/vb/eternity/45757-eternity-engine-3-35-92-nekhbet/ 3.35.92] "Nekhbet" - March 22, 2009

===Version 3.37===
* [http://www.doomworld.com/vb/eternity/49268-eternity-engine-3-37-00-sekhmet/ 3.37.00] "Sekhmet" - January 1, 2010

===Version 3.39===
* [http://www.doomworld.com/vb/eternity/52873-eternity-engine-v3-39-20-resheph/ 3.39.20] "Resheph" - October 10, 2010

===Version 3.40===
* [http://www.doomworld.com/vb/eternity/53944-eternity-engine-v3-40-00-rebirth/ 3.40.00] "Rebirth" - January 8, 2011
* [http://www.doomworld.com/vb/eternity/55219-announcing-the-blue-box-ee-3-40-11-and-vaporware-demo/ 3.40.11] "Aasgard" - May 2, 2011
* [http://www.doomworld.com/vb/eternity/55874-eternity-engine-3-40-15-wodanaz/ 3.40.15] "Wodanaz" - June 22, 2011
* [http://www.doomworld.com/vb/eternity/58281-eternity-engine-v3-40-20-mjolnir/ 3.40.20] "Mjolnir" - December 26, 2011
* [http://www.doomworld.com/vb/eternity/61245-eternity-engine-3-40-25-midgard/ 3.40.25] "Midgard" - August 27, 2012
* [http://www.doomworld.com/vb/eternity/62087-eternity-engine-3-40-30-alfheim/ 3.40.30] "Alfheim" - November 4, 2012
* [http://www.doomworld.com/vb/eternity/64382-eternity-engine-3-40-37-gungnir/ 3.40.37] "Gungnir" - May 27, 2013
* [http://www.doomworld.com/vb/eternity/67069-eternity-engine-3-40-46-bifrost/ 3.40.46] "Bifröst" - January 19, 2014 - ''first one with a macOS release''

===Version 3.42===
* [https://www.doomworld.com/forum/topic/94046-eternity-engine-34202-heimdal-files-documentation-buglist/ 3.42.02] "Heimdal" - May 7, 2017
* [https://www.doomworld.com/forum/topic/95351-eternity-engine-34203a-heimdal-release-2-hotfix/ 3.42.03a] "Heimdal" release 2 - August 2, 2017

===Version 4.00===
* [https://www.doomworld.com/forum/topic/99957-eternity-engine-40000-v%C3%B6lusp%C3%A1/ 4.00.00] "Völuspá" - March 17, 2018

===Version 4.01===
* [https://www.doomworld.com/forum/topic/117429-eternity-engine-40100-tyrfing/ 4.01.00] "Tyrfing" - October 13, 2020

===Version 4.02===
* [https://www.doomworld.com/forum/topic/119425-eternity-engine-40200-forseti/ 4.02.00] "Forseti" - January 27, 2021

===Version 4.04===
* [https://www.doomworld.com/forum/topic/148678-eternity-engine-40400-glitnir/ 4.04.00] "Glitnir" - October 12, 2024
* [https://www.doomworld.com/forum/topic/148678-eternity-engine-40401-glitnir-update-1/ 4.04.01] "Glitnir" Update 1 - October 20, 2024
* [https://www.doomworld.com/forum/topic/148678-eternity-engine-40402-glitnir-update-2/ 4.04.02] "Glitnir" Update 2 - November 18, 2024

===Version 4.05===
* [https://www.doomworld.com/forum/topic/154848-eternity-engine-40504-citadel/ 4.05.04] "Citadel" - August 23, 2025

==Cross-platform development==
Eternity is built by using the [[Wikipedia:CMake|CMake]] utility. You can download the Eternity [[Wikipedia:source code|source code]] from [[Wikipedia:GitHub|GitHub]] and execute CMake. Eternity's source code repository, as well as the latest releases, are located [https://github.com/team-eternity/eternity/ here].

==Development builds==
Development builds ("beta" releases) for Eternity are available for Windows and macOS at [http://devbuilds.drdteam.org/eternity/ DRDTeam's website]. They are recommended if you encounter serious bugs with any of the official releases, or if you want to test brand new features that didn't exist in the latest official releases. Due to their beta status, they may be untested and have other problems. However, due to the sometimes sporadic release cycles, it's often recommended to just try the development builds. The only problem is that by upgrading Eternity often, savegames tend to become unusable, so exercise caution before upgrading Eternity if you rely on games with saves.

==System features==
*[[Cardboard engine]]
*[[List of command line parameters]]
*[[Console]]
*[[List of cheat codes]]
*[[GFS|GFS files]]
*[[ZIP|ZIP mods]]

==Gameplay and modding features==
*[[DeHackEd / BEX Reference]]
*[[List of codepointers]]
*[[EDF|EDF files]]
*[[Editing reference]]
*[[OPTIONS|OPTIONS lump]]
*[[MapInfo]]
*[[SMMU|Features inherited from SMMU]]
*[[ExtraData]]
*[[Hexen format SNDINFO]]

[[Category:Source ports]]

Template:Latest

2025-08-23T17:30:30Z

Printz:

[https://www.doomworld.com/forum/topic/154848-eternity-engine-40504-citadel/ 4.05.04]

DECORATE state syntax

2025-08-23T17:13:48Z

Printz: /* Labels */

EDF allows using a concise ZDoom DECORATE-style state syntax for [[thingtype|thing types]], by using the '''states''' field, followed by a heredoc (multiline string). The syntax is based on the one from ZDoom, described [http://zdoom.org/wiki/Actor_states here], in the ZDoom wiki.

Note that DECORATE errors in Eternity will trigger warnings at startup which can only be observed with -edfout or -edf-show-warnings during the text-mode part of the program initialization. You can press the ''Pause'' key during that sequence to read the warning messages. Usually in these cases, the DECORATE state definition is fully disabled.
{{Backto|EDF state reference}}
==Syntax==
The DECORATE grammar is defined as such (source: Eternity source code comment):
<labeledunit> := <labelblock><frameblock><labeledunit> | nil
<labelblock> := <label><eol><labelblock>
<label> := [A-Za-z0-9_]+('.'[A-Za-z0-9_]+)?':'
<eol> := '\n'
<frameblock> := <frame><frameblock> | <frame>
<frame> := <keyword><eol> | <frame_token_list><eol>
<keyword> := "stop" | "wait" | "loop" | "goto" <jumplabel>
<jumplabel> := <jlabel> | <jlabel> '+' number
<jlabel> := [A-Za-z0-9_:]+('.'[A-Za-z0-9_]+)?
<frame_token_list> := <sprite><frameletters><tics><flagslist><action>
<sprite> := [A-Z0-9][A-Z0-9][A-Z0-9][A-Z0-9]
<frameletters> := [A-Z\[\\\]]+
<tics> := [0-9]+
<flagslist> := <flag><flagslist>
<flag> := "bright" | "fast" | "offset" '(' <x> ',' <y> [',' "interpolate"] ')' | nil
<action> := <name>
| <name> '(' <arglist> ')'
| nil
<name> := [A-Za-z0-9_]+
<arglist> := <arg> ',' <arglist> | <arg> | nil
<arg> := "string" | number
Here's an example, the Sergeant's DECORATE state (from base/doom/things.edf):
states
@"
Spawn:
SPOS AB 10 A_Look
loop
See:
SPOS AABBCCDD 3 A_Chase
loop
Missile:
SPOS E 10 A_FaceTarget
SPOS F 10 bright A_SPosAttack
SPOS E 10
goto See
Pain:
SPOS G 3
SPOS G 3 A_Pain
goto See
Death:
SPOS H 5
SPOS I 5 A_Scream
SPOS J 5 A_Fall
SPOS K 5
SPOS L -1
stop
XDeath:
SPOS M 5
SPOS N 5 A_XScream
SPOS O 5 A_Fall
SPOS PQRST 5
SPOS U -1
stop
Raise:
SPOS LKJIH 5
goto See
"@
Here we can see three kinds of units: labels, frames and keywords.
===Labels===
Labels are the '''Spawn:''', '''See:''', '''Missile:''' and other lines ended with colons. They designate starting points for special thing states, equivalent to non-DECORATE EDF [[thingtype]] '''spawnstate''', '''seestate''', '''missilestate''' and so on. You can also create your own labels, which will be reachable using keywords like '''goto''', as well as state-jumping [[List of codepointers|codepointers]]. Labels are case-insensitive. The following labels are used natively by Eternity:

*'''Spawn''': equivalent of '''spawnstate''': state the thing is spawned at;
*'''See''': equivalent of '''seestate''': state the monster goes into after seeing a target;
*'''Melee''': equivalent of '''meleestate''': state the monster goes into after getting close to the target;
*'''Missile''': equivalent of '''missilestate''': state the monster goes into when deciding to shoot the target;
*'''Pain''': equivalent of '''painstate''': state the thing goes into when hit;
*'''Death''': equivalent of '''deathstate''': state the thing goes into when killed or otherwise destroyed;
*'''XDeath''': equivalent of '''xdeathstate''': optional state the thing goes into when killed with very high damage;
*'''Raise''': equivalent of '''raisestate''': optional state the corpse goes into when raised by an archvile;
*'''Heal''' (since Feb 21 2016): equivalent of '''healstate''': state to jump to if during [[VileChase]] it encounters a corpse. If not set, it will just go into S_VILE_HEAL1.
*'''Crash''': equivalent of '''crashstate''': optional state for a corpse to go into when falling and hitting the floor;
*'''Active''': equivalent of '''activestate''': optional state to go into when triggered by [[Detailed parameterized linedef specification#Things|Thing_Activate]];
*'''Inactive''': equivalent of '''inactivestate''': optional state to go into when triggered by [[Detailed parameterized linedef specification#Things|Thing_Deactivate]];
*'''Pickup.Respawn''': state to jump to when the gettable item thing has the '''RAVENRESPAWN''' flag and is picked up, after which it waits to respawn;
*'''Pickup.Remove''': state to jump to when the gettable item thing has the '''RAVENRESPAWN''' flag and is picked up, after which it is removed permanently without respawning. This applies for items which for any reasons must not respawn, such as individual dropped items. It's a property of the particular item, not of the entire thingtype class, so be sure to also include a '''Pickup.Respawn''' state.
*'''Crunch''' or '''Crush''': equivalent of '''crunchstate''': optional state to go into when crushed as a dead body by a door or any other sector type. Default depends on game mode. It may be nothing if game mode doesn't specify anything, in which case there's no transition.
====Damage type pain and death states====
You can also add labels for means-of-death (damage type) specific pain and death states. They're equivalent to the '''dmg_painstates''' and '''dmg_deathstates''' thingype fields. You formulate them as such:
*'''Pain'''.''damage_type'': for non-death pain states to go into when hit by specific kinds of damage;
*'''Death'''.''damage_type'': for death states when hit by specific kinds of damage.
The built-in damage types are defined in base/things.edf, and you can add your own. Example: define '''Pain.Pistol''', '''Death.Pistol''' states when the thing is hit by player pistol bullets and has to react specifically to this kind of damage.

===Frames===
A frame has the following syntax:
:''sprite'' ''frame_letters'' ''tics'' [''flags_list''] [''action'']
*''sprite'': this is a four letter code corresponding to the sprite lump stem. In Doom, for example, imps have TROO, zombiemen have POSS and so on. For the invisible sprite, use TNT1.
*''frame_letters'': this is one or more letters corresponding to the sprite frame index. Include more than one letter if you want a sequence of frames with the same properties (duration, flags and action).
*''tics'': the duration, in tics (1/35 seconds), of each frame. Do not use value 0 in loops. Setting value -1 will cause the thing to stop at that frame, without going forward.
*''flags_list'': zero or more flags, separated by spaces. The flags can be:
**'''bright''': causes the sprite to be full bright in any place;
**'''fast''': makes the frame take half as long on fast skill levels (used in Doom by the demons);
**'''offset'''(''x'', ''y''[, '''interpolate''']): useful for weapon HUD sprites, causes the image to be offset by the exact amount of ''x'' and ''y'' from the center-bottom, overriding the current bob amount. Under Doom, ''x'' must be nonzero for both offsets to have effect; under other games, each of them needs to be nonzero for each of them to have effect — otherwise the offset will be preserved from the previous frame. You can override the 0 condition choice (Doom/non-Doom) in [[gameproperties]]. Beware that ''y'' has the origin at 32. An offset of (0, 32) keeps the weapon at the origin, but because of Doom's rules, you may need to have (1, 32) or (-1, 32) instead. Do note that this '''offset''' vector has been available in vanilla Doom as well, modifiable under [[DeHackEd]], and it is the same thing as the '''misc1''' and '''misc2''' [[frame]] fields, which means these work as parameters for several [[MBF]] [[codepointers]]. However, currently you cannot use strings or other expressions in ''x'' and ''y'', unlike when using the full '''frame''' section or the '''cmp''' specifier. In the classic games original designs, only Hexen has used '''offset''', in order to animate its melee weapons.
::If '''interpolate''' is added, it causes the movement between offsets to be smooth. By default interpolation is disabled when '''offset''' is specified.
*''action'': this can be a [[List of codepointers|codepointer]], optionally followed by a list of arguments enclosed by parentheses. Make sure to include strings in double quotes (""). Conventionally, from ZDoom, and based on the Doom source code in general, codepointers are prefixed with '''A_''', but it is not required here.

====Using state-switching codepointers with DECORATE====
Some codepointers, such as [[CounterJump]], [[Jump]] and so on let the calling thing jump to specific frames. For the frame name parameter, just use the label name.

The MBF-based [[RandomJump]] uses the '''misc1''' and '''misc2''' frame fields as parameters. Since the DECORATE style syntax currently only supports '''misc1''' and '''misc2''' through the '''offset''' specifier, you are better off using [[Jump]], which uses args, is based on ZDoom's implementation and only works for DECORATE state syntax. Other codepointers, such as [[CounterJump]], work well both for non-DECORATE and DECORATE syntax. Certain codepointers such as [[CounterSwitch]] aren't designed for DECORATE state syntax however.

===Keywords===
These are placed at the end of a state, before other labels. They are:
*'''stop''': this is equivalent to setting next frame to 0. If the last frame in the state has a finite (different from -1) duration, it will disappear. Otherwise it's commonly used after -1 duration frames when nothing is expected to follow.
*'''wait''': this causes the last frame to loop back into itself. If the duration is 0, it will be adjusted to 1.
*'''loop''': this causes the last frame to loop back to where its label points.
*'''goto''' ''jump_label'': sets the next frame of the last frame to the one designated by the label.

==Differences from ZDoom's DECORATE==
* The frame after a '''goto''' line must be labelled in Eternity. Of course, labels can be native (spawn, see, pain etc.) or user-defined.

[[category:EDF]]

EDF thing reference

2025-08-23T17:12:38Z

Printz: /* States */

Thing types define monsters, lamps, control points, items, etc -- anything that moves, occupies space, can display a sprite, or is useful for singling out locations. Things have unique names, or mnemonics, for easy identification. They're referenced in several places by their name, such as the console command ''Summon'', or [[List of codepointers|action functions]] dealing with spawning things (such as [[Spawn]] or [[MissileAttack]]).

If a thing type's mnemonic is not unique, the latest definition of a thing type with that mnemonic replaces any earlier ones. Like most other identifiers in EDF (but not lump names or subnames), thing type mnemonics are completely case-insensitive.

New objects, created via EDF files or wad lumps, can be later tweaked with Dehacked (BEX) patches, if they're given a unique '''dehackednum''' entry. For forward compatibility, the '''dehackednum''' has to be greater than or equal to 10000.

For placing the thing on the map, an integer field called '''doomednum''' must be specified. For forward compatibility it has to be greater than or equal to 20000 or in the 3000-3999 range. Due to how binary WAD files format their THINGS lumps, '''doomednum''' values have to be less than 32767, though textmode representations such as [[ExtraData]] or UDMF solve this limit.

If you want to know the base game thing types from Doom, you can look on the [https://github.com/team-eternity/eternity/blob/master/base/doom/things.edf list of Doom thing types].

{{See|Thing type flags}}
{{See|thinggroup}}. Some of the customization should be set in '''thinggroup''' blocks, which group multiple things. Most notably, infighting control. There are also flags and '''damagefactor''' "immune" (see this page) settings.
{{Backto|EDF}}

==Eternity Alfheim syntax==
For versions of Eternity from Alfheim up, EDF thingtypes support the following syntax. Make sure to add:
setdialect("ALFHEIM")
before using this syntax:
thingtype <unique name> : <inherited thingtype>, <doomednum>, <dehackednum>
{
<other attributes>
}
===Header properties===
* ''<inherited thingtype>'' must be a value, even if the thingtype doesn't inherit from anything else. In that case, it must be '''Mobj''', which is a placeholder value belonging to no real thingtype.
* ''<doomednum>'' and ''<dehackednum>'' can be -1 if not used. If both are -1, they can be omitted, leaving just this:
thingtype <unique name> : <inherited thingtype> {<attributes>}
* If header properties are used, the pre-Alfheim '''inherits''', '''doomednum''' and '''dehackednum''' attributes are not used.

==Syntax==
thingtype <unique name> [: <parent type> [, <doomednum> [, <dehackednum>]]]
{
doomednum <number>
dehackednum <unique number>
inherits <thingtype>
compatname <name>
basictype <basic type qualifier>

// NOTE: for this section, see the "states" field below and use it instead of these.
spawnstate <frame>
seestate <frame>
painstate <frame>
dmg_painstates {<damage type>, <frame>, ...}
dmg_painstates.add {<damage type>, <frame>, ...}
dmg_painstates.remove {<damage type>, ...}
meleestate <frame>
missilestate <frame>
deathstate <frame>
dmg_deathstates {<damage type>, <frame>, ...}
dmg_deathstates.add {<damage type>, <frame>, ...}
dmg_deathstates.remove {<damage type>, ...}
xdeathstate <frame>
raisestate <frame>
healstate <frame> // since Feb 21 2016
crashstate <frame>
activestate <frame>
inactivestate <frame>
crunchstate <frame>

seesound <sound>
attacksound <sound>
painsound <sound>
deathsound <sound>
activesound <sound>
activatesound <sound>
deactivatesound <sound>
ripsound <sound>

spawnhealth <number>
gibhealth <number>
reactiontime <number>
painchance <number>
speed <number OR floating-point number>
fastspeed <number OR floating-point number>
radius <floating-point number>
height <floating-point number>
correct_height <floating-point number>
mass <number>
respawntime <number>
respawnchance <number>

damage <number>
damagemod <number>
dmgspecial <dmgspecial name>
missiletype <option>
aimshift <number>

meleerange <floating-point number>
missileheight <floating-point number>
bulletzoffset <floating-point number>

damagefactor <damage type>, <floating point number>|immune[, rounded]
damagefactor <damage type>, <floating point number>|immune[, rounded]
...
damagefactor.remove <damage type>
cleardamagefactors

topdamage <number>
topdamagemask <number>
mod <MOD name OR number>
obituary_normal <string>
obituary_melee <string>

bloodcolor <number>
nukespecial <BEX codepointer mnemonic>
droptype <thing type mnemonic>

bloodbehavior <action>, <behavior>
clearbloodbehaviors
bloodtype.normal <name>
bloodtype.impact <name>
bloodtype.rip <name>
bloodtype.crush <name>

cleardropitems
dropitem <type>, [, <chance> [, <amount> [, <toss>]]]
dropitem.remove <type>
collectionspawn <thingtype> [, <spchance> [, <coopchance> [, <dmchance>]]]
itemrespawnat <thingtype>

cflags <flag list>
addflags <flag list>
remflags <flag list>
flags <flag list>
flags2 <flag list>
flags3 <flag list>
flags4 <flag list>
flags5 <flag list>
particlefx <particle effect flag list>

translucency <number OR percentage>
translation <number OR translation table lump name>
tranmap <lump name>
skinsprite <sprite>
defaultsprite <sprite>
alphavelocity <floating-point number>
xscale <floating-point number>
yscale <floating-point number>

trail.type <thing type>
trail.zoffset <floating-point number>
trail.spawnchance <number>
trail.sparsity <number>

acs_spawndata {num <number> modes <mnemonic>}

pickupeffect
{
effects <effect1>, ...
changeweapon <weapon>
message <text>
sound <sound>
flags <flags>
}
clearpickupeffect

firstdecoratestate <frame>
states <[[DECORATE state syntax]] heredoc>
}
===Explanation of fields===
====ID / Type Info====
*'''doomednum'''
:Default = -1
:The identification number, which makes this actor type placeable in maps. Zombieman monsters for example have '''doomednum''' 3004. Objects which don't need to be placed on the map can have '''doomednum''' -1. For EDF, recommended numbers are in the ranges 3000-3999 and 20000 up. Other numbers may be used by future versions of Eternity, so they're not safe to use.
:NOTE: you can just use the first number following the inherited class, in the title. Just remember to start the script with <code>setdialect("alfheim")</code>.
*'''dehackednum'''
:Default = -1
:Fake array index number, for Dehacked patch (BEX or DEH file) compatibility. It has to be an unique number if not -1. Safe numbers are from 10000 up.
:NOTE: you can use the second number following the inherited class in the title. For this, you also need <code>setdialect("alfheim")</code>.
*'''inherits'''
:Default = (nothing)
:Sets the thing type from which this will copy properties. All of the properties except '''dehackednum''' will be copied from the base actor type.
:NOTE: you can use the class in the title properties after the colon, instead of '''inherits''' in the '''thingtype''' body. You also need <code>setdialect("alfheim")</code>.
*'''compatname'''
:Default = (nothing)
:Sets a "compatible name" useful for [[ACS]] scripts copied from GZDoom mods or for cross-port usage. Typically the need for this is because of ACS scripts assuming thingtype names from GZDoom, and in the base Eternity definitions, '''compatname''' is set to names which GZDoom uses for its thingtypes.
:Setting this flag is not needed and shouldn't be done in mods.
*'''basictype'''
:Default = (nothing)
:'''Basictype''' is a list of common flags used in Doom and derived games. Using '''basictype''' instead of setting individual flags is encouraged, in order to keep up with Eternity engine updates. Other flags may be subsequently added or removed with '''addflags''' or '''remflags'''. See the [[Thing type flags]] page for a full list. The '''basictype''' mnemonics follow:
:*''Monster''
::An ordinary walking monster with no fancy features.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+FOOTCLIP+SPACMONSTER+PASSMOBJ"

:*''FlyingMonster''
::An ordinary flying monster.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+NOGRAVITY+FLOAT+SPACMONSTER+PASSMOBJ"

:*''FriendlyHelper''
::A player helper with maximum friendliness options.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+FRIEND+JUMPDOWN+FOOTCLIP+WINDTHRUST+SUPERFRIEND+SPACMONSTER+PASSMOBJ"

:*''Projectile''
::A standard projectile.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS"

:*''PlayerProjectile''
::A projectile for use by players.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS+SPACMISSILE"

:*''Seeker''
::A missile prepared to be fired by homing missile codepointers.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS+SEEKERMISSILE"

:*''SolidDecor''
::A solid decorative item.
::'''cflags''' SOLID

:*''HangingDecor''
::A hanging decorative item that is passable even without 3D object clipping.
::'''cflags''' "SPAWNCEILING+NOGRAVITY"

:*''SolidHangingDecor''
::A solid hanging decorative item.
::'''cflags''' "SOLID+SPAWNCEILING+NOGRAVITY"

:*''ShootableDecor''
::A shootable decorative item.
::'''cflags''' "SOLID+SHOOTABLE+NOBLOOD"

:*''Fog''
::A fog item such as telefog or item fog.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+TRANSLUCENT+NOSPLASH"

:*''Item''
::A collectable item. Doesn't count towards the item score.
::'''cflags''' SPECIAL

:*''ItemCount''
::A collectable item. Counts for item score.
::'''cflags''' "SPECIAL+COUNTITEM"

:*''TerrainBase''
::A TerrainTypes base item.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+NOSPLASH"

:*''TerrainChunk''
::A TerrainTypes chunk item.
::'''cflags''' "NOBLOCKMAP+DROPOFF+MISSILE+LOGRAV+NOSPLASH+NOCROSS+CANNOTPUSH"

:*''ControlPoint''
::An inert control point.
::'''cflags''' "NOBLOCKMAP+NOSECTOR+NOGRAVITY"
::'''spawnstate''' S_TNT1

:*''ControlPointGrav''
::An control point that is subject to gravity. Because of this, it's not considered inert.
::'''cflags''' "DONTDRAW+NOSPLASH"
::'''spawnstate''' S_TNT1

====States====
*'''firstdecoratestate'''
:Sets the first frame in a sequential list of dummy frames that use the internal Decorate-style defined '''states''' of this actor for [[EDF delta structures|framedelta]] compatibility. It's not required unless the intention is to make the Decorate states of this thing accessible from other thing types. Default games' (Doom, Heretic) thing types use externalized frames for all thing types, for compatibility.
*'''states'''
{{see|DECORATE state syntax}}
:Default = nothing
:Defines frames using [http://zdoom.org/wiki/DECORATE DECORATE]-style state definitions. This means it won't be necessary to define separate [[frame]] blocks for each individual frame. See the DECORATE reference at the ZDoom wiki for documentation on its syntax. Using the '''states''' field instead of any of the ones below results in more concise text, but also the newly created frames won't be accessible from outside (other thingtypes, Dehacked patches or delta structures), unless you use the '''firstdecoratestate''' field as well. Like normally, [[List of codepointers|codepointers]] may or may not be preceded by '''A_'''. The DECORATE code has to be implemented via a heredoc: a text string that spans on multiple lines. Unlike a regular string which uses quotation marks, the heredoc is marked by @" and "@ respectively. Example on an imp-like monster (the '=' sign is optional):
states =
@"
Spawn:
TROO AB 10 A_Look
loop
See:
TROO AABBCCDD 3 A_Chase
loop
Pain:
TROO H 2
TROO H 2 A_Pain
goto See
Melee:
Missile:
TROO EF 8 A_FaceTarget
TROO G 6 A_TroopAttack
goto See
Death:
TROO I 8
TROO J 8 A_Scream
TROO K 6
TROO L 6 A_Fall
TROO M -1
stop
XDeath:
TROO N 5
TROO O 5 A_XScream
TROO P 5
TROO Q 5 A_Fall
TROO RST 5
TROO U -1
stop
Raise:
TROO ML 8
TROO KJI 6
goto See
"@
:A "fast" flag is now allowed between the tics and action function of DECORATE states (along with the pre-existing "bright" flag) which determines if that state halves its "tics" value when the game is in -fast or Nightmare skill. Example (from demon's states):
states
@"
See:
SARG AABBCCDD 2 fast A_Chase
loop
Melee:
SARG EF 8 fast A_FaceTarget
SARG G 8 fast A_SargAttack
goto See
Pain:
SARG H 2 fast
SARG H 2 fast A_Pain
goto See
"@
*'''spawnstate'''
:Default = S_NULL
:Sets the frame which a thing starts in when it is spawned. Monsters generally use this frame to stand still and look for targets. If the object is supposed to have any dynamic purpose or be visible, do not leave the '''spawnstate''' at S_NULL.
*'''seestate'''
:Default = S_NULL
:Sets the frame which a monster will jump to when it sees or hears a target during a [[Look]] (monster standing unawakened) check. If an object is alive and has a seestate, it is considered ''sentient'' by certain game mechanics.
*'''painstate'''
:Default = S_NULL
:Sets the frame a thing may randomly enter when it has been injured. If set to S_NULL, the creature will be removed instantly from the game if the random check succeeds.
*'''dmg_painstates'''
:Default = (nothing)
:This is a list of one or more damagetype/frame pairs, enclosed in braces. For example:
dmg_painstates
{
Fire, S_HPLAY_FPAIN1,
Lava, S_HPLAY_LPAIN1
}
makes the actor go to frame S_HPLAY_FPAIN1 when damaged by fire, or to S_HPLAY_LPAIN1 when harmed by lava. It defaults to its '''painstate''' if the damage is of another nature. The damage type of an actor is set up through the '''mod''' field.
*'''dmg_painstates.add'''
*'''dmg_painstates.remove'''
:Can be used for derived actor types, who can have more or fewer specialized pain states than their ancestors. ''Dmg_painstates.add'' has the same format as ''dmg_painstates'', but ''dmg_painstates.remove'' only lists the damagetypes. For example:
dmg_painstates.remove
{
Fire, lava
}
makes them get hurt normally from fire or lava, without going to special pain states.
*'''meleestate'''
:Default = S_NULL
:If this frame is not S_NULL, monsters will have a slightly lower range attack probability and when they are within about 64 units of their target, they will enter this frame to perform a melee attack.
*'''missilestate'''
:Default = S_NULL
:If this frame is not S_NULL, monsters chasing a target will randomly enter it to perform a missile attack.
*'''deathstate'''
:Default = S_NULL
:When a thing dies normally, it will enter this state. If the state is S_NULL, the thing will disappear forever.
*'''dmg_deathstates'''
*'''dmg_deathstates.add'''
*'''dmg_deathstates.remove'''
:Defaults = (nothing)
:These three properties work similar to ''dmg_painstates*'', in that they allow the object to enter special frames depending on the damage type suffered, but if they die. The formats are the same.
*'''xdeathstate'''
:Default = S_NULL
:If a thing dies by taking enough damage that its health is equal to its negated spawnhealth value (or negated 0.5 spawnhealth value in Heretic), it will enter this frame instead of its deathstate. If this frame is S_NULL, the thing will always die normally.
*'''raisestate'''
:Default = S_NULL
:If this frame is not S_NULL, a creature running [[VileChase]] codepointers can perform a resurrection on this actor. When this occurs, the actor will enter this frame along with being restored.
*'''healstate''' (since Feb 21 2016)
:Default = S_NULL
:Sets the frame to jump to if, during a [[VileChase]] frame, the thing encounters a corpse and raises it. If not set (or set to S_NULL), it will actually default to S_VILE_HEAL1, same as in Doom.
*'''crashstate'''
:Default = S_NULL
:When a thing with this state dies and then subsequently hits the ground, it will enter this state. If this state S_NULL, it is not used.
*'''activestate'''
:Default = S_NULL
:State to enter when triggered by the '''Thing_Activate''' parameterized special.
*'''inactivestate'''
:Default = S_NULL
:State to enter when triggered by the '''Thing_Deactivate''' parameterized special.
*'''crunchstate'''
:State, if specified, to enter when crushed as a dead body by a sector (door, crusher etc.). If unspecified, it depends on game mode, and it's the pool of blood (S_GIBS) in Doom. NOTE: for DECORATE-style syntax, it's the Crunch: or Crush: label.

====Sounds====
*'''seesound'''
:Default = none
:Sets the sound that a monster will play when it awakens. This sound is also played by missiles when they are shot. (Note: "none" is a special mnemonic for no sound)
*'''attacksound'''
:Default = none
:Sets a sound used by some monster attacks, including the Lost Soul's charge, or melee attacks.
*'''painsound'''
:Default = none
:Sets the sound played by the Pain codepointer when this thing uses it.
*'''deathsound'''
:Default = none
:Sound played by the Scream codepointer. Used to play monster death sounds.
*'''activesound'''
:Default = none
:Sets the sound used by a thing when it is wandering around. A thing is given a 3 out of 256 chance (1.17%) of making this sound every time it calls the Chase codepointer. There are some new flags3 flags which can alter the behavior of this sound.
*'''activatesound'''
:Default = none
:Sound to play when triggered by the '''Thing_Activate''' parameterized special.
*'''deactivatesound'''
:Default = none
:Sound to play when triggered by the '''Thing_Deactivate''' parameterized special.
*'''ripsound'''
:Default = none
:Sound to play if it's a projectile using the '''RIP''' flag and it's moving and ripping through shootable targets. This is for example used by the Heretic powered-up Dragon Claw secondary "spiked ball" projectiles when they pass through enemies.

====Basic Stats====
*'''spawnhealth'''
:Default = 1000
:Sets a thing's maximum amount of life.
*'''gibhealth''' ''number''
:gibhealth overrides the gamemode default behavior for determining the negative amount of health at which a thing uses its "extreme" death state rather than its normal one. This is ordinarily defined in terms of the spawnhealth (Doom and Strife thingtypes gib at -spawnhealth; Heretic and Hexen thingtypes gib at -(spawnhealth/2).
:If an inheriting thingtype changes its spawnhealth, it will "lose" the inherited definition of gibhealth from its parent. If changing spawnhealth when inheriting from a thingtype that customizes gibhealth, be sure to re-customize the gibhealth in the inheriting thingtype.
*'''reactiontime'''
:Default = 8
:Sets an amount of time that a thing must wait under certain circumstances. Monsters use this value as a means to control their rate of attack. This value is also used as an internal field for varying purposes, but those uses are not editable.
*'''painchance'''
:Default = 0
:Sets the chance out of 255 that this thing will enter its painstate when it is injured. A thing with 0 painchance will never feel pain, whereas a thing with 255 painchance will always feel pain. If a thing has a painchance greater than zero, it should have a valid painstate, otherwise it will disappear forever.
*'''speed'''
:Default = 0
:Value used by monsters as a movement delta per walking frame. The monster will move by an amount relative to this value each time it uses the Chase codepointer. For missiles, this value is a fixed-point number (multiplied by 65536), and represents a constant speed by which the missile advances every game tic. Missile speed is not affected by the missile frame durations, whereas monster walking speed is.
:This field also supports floating-point values. When a floating-point value is provided, it will be translated into the corresponding fixed-point value. This means that a value of 10.0 is equivalent to the integer value 655360 (10*65536). It is NOT equivalent to 10. This distinction is very important. Small integer speed values are appropriate for monsters, whereas floating-point values will be suitable only for missiles.
*'''fastspeed'''
:Default = 0
:When the game is switched into Nightmare difficulty or -fast mode is active, all thing types with a non-zero fastspeed will have their speed fields changed to their fastspeed value. This enables editing of the -fast speed of projectiles and monsters. For detailed information on speed, see the speed field itself above. Note: as of EDF 1.2, this field also supports floating-point numbers, with the same meaning as that for the speed field.
*'''radius'''
:Default = 20.0
:Floating-point value that represents the radius of this thing type. A thing can fit into corridors which are at least as wide as this value times two, plus one unit (ie a thing with radius 32 can fit into a 65-wide hallway). The maximum value this field *should* have is 64.0 units. However, the game breaks its own rule here, giving several monsters radii up to 128 units. These monsters, which include the Mancubus, Arachnotron, and Spider Demon, exhibit clipping errors which enable other things to walk into them, and which can cause some moving sectors to malfunction. Avoid giving things radii larger than 64.0 to remain absolutely safe.
*'''height'''
:Default = 16.0
:Floating-point value that represents the height of this thing type. A thing can fit into areas which are of this exact height or taller. Note that in DOOM, this value is only used to see where a monster can fit relative to walls and floor/ceiling heights. For purposes of clipping against other things, monsters were considered to be infinitely tall. However, Eternity's extended 3D object clipping enables this field to also be used to allow or disallow things to pass over, under, or stand on this thing.
*'''correct_height'''
:Default = 0.0
:Floating-point value that represents a height for this thing type which is corrected for 3D object clipping. When 3D object clipping is enabled and the comp_theights variable is set to off, objects which have a non-zero correct_height field will begin to use this value for their height instead of the normal height field. If an object has the 3DDECORATION flags3 bit set, it will still clip missiles at its original height instead of at this value, so that playability of old maps is not altered. This field will generally only be necessary for old DOOM objects, which have now been assigned correct_height values in the default things.edf module. Use for new objects is discouraged; instead, set the height field above to the proper value.
*'''mass'''
:Default = 100
:Normal integer value that serves as a mass factor for this object. Mass affects the amount of thrust an object is given when it is damaged, the amount of effect an archvile's attack can have on it, and for bouncing objects, the rate at which they fall. Objects with a mass less than 10 will cause small terrain hits when landing on terrain that supports small splashes.
*'''respawntime'''
:Default = 420
:Sets the number of gametics before the monster may respawn. A tic is 1/35 of a second.
*'''respawnchance'''
:Default = 4
:Sets the chance out of 255 that the monster may respawn after respawntime has passed. The check is done for each tic that the monster isn't blocked.
====Damage Properties====
*'''damage'''
:Default = 0
:This number is used as a damage multiplier when a [[Thing type flags|MISSILE]] or SKULLFLY actor hits a SHOOTABLE. The damage formula used for impact damage is:
((rnd % damagemod) + 1) * damage
:This field is also used as a parameter by some parameterized codepointers, including [[Scratch]], [[BetaSkullAttack]] and [[Detonate]]. See '''damagemod''' field's description for the <code>damagemod</code> parameter.
*'''damagemod'''
:Default = 8
:This is the damage modulus to use when computing projectile damage. This is the maximum multiplier of '''damage''' for a projectile impact. For Doom projectiles, it's typically 8. To have constant impact damage, you can set it to 1. Do not set it to 0.
*'''dmgspecial'''
:Default = "none"
:The dmgspecial field allows specification of a special action that will be taken when this object is involved in damaging another object as the inflictor (an inflictor is the object actually doing the damage, and not necessarily the object that is blamed for the damage). Supported values and their meanings are as follows:
:*''none''
::This is the default value. No special action is taken; the object is normal when damaging other things.

:*''MinotaurCharge''
::If the thing is flying like a skull (has flags bit SKULLFLY set), it will inflict a large amount of thrust on the target along the vector of the impact, will hit it directly for ((rnd % 8) + 1) * 6 damage, and if the target is a player, the player's controls will be frozen for 14 + (rnd % 8) gametics. When the thing is not in SKULLFLY mode, normal damage is done by all attacks.

:*''Whirlwind''
::The target will have its angle and x/y momenta modified by random amounts. If the current level time has the 5th bit (value 16) set and the target is not a boss (possesses the BOSS flag), the target will be given randomized z momentum up to but no greater than 12 units per tic. When the level time is divisible by 8, the target will be hit directly for 3 damage.

:*''PoweredMaceBall''
::Behavior specific to the powered mace projectile. Beware that it has behavior specific to some Heretic thing type targets, and it can even cause a target player to use the Chaos Device.

:*''PoweredPhoenixFire''
::Causes players to be occasionally stunned.

:*''BossTeleport''
::Causes monsters with properties similar to dismounted D'Sparil to teleport away on impact.

*'''missiletype'''
:Default = '''Default'''
:Type of movement if this thingtype is a projectile. It can be '''Default''' or '''RavenFast'''. The '''Default''' type is usual, allowing speeds up to about 35 (but in practice the limit is around 25, after which it becomes inaccurate). The '''RavenFast''' type is for very fast projectiles, as happening to some types in the Heretic and Hexen games, which can be very fast and still being accurate. Do mind that '''RavenFast''' works only and strictly with projectiles, and can't be used with other types of actors, as they're severely limited on their interactions with the environment.

*'''aimshift''' ''number''
:If in the range of 0 to 24, this value overrides the "shift" amount that enemies of this object experience while trying to aim at it due to effects like SHADOW, GHOST, and TOTALINVISIBLE. A larger number in this field makes enemies more inaccurate when aiming at this creature. The default value of -1 means that no aiming inaccuracy is experienced *except* what may be incurred from what flags this monster has. A value larger than 24 will, on the other hand, override the creature's flags and cause enemies to experience no inaccuracy due to to those flags (so for example a creature inheriting from Spectre and setting its aimshift to 25 will behave as though it does not have the SHADOW flag other than for rendering purposes). Values of 20 and 21 are used by the various built-in flag effects.

*'''meleerange'''
:Default = 64.0
:Sets the close attack distance for this monster, allowing initiation of attack to start at a different distance from default.

*'''missileheight'''
:Default = 32.0
:Height relative to thing's feet to spawn new projectiles if no other changes are implied in the codepointer.

*'''bulletzoffset'''
:Default = 8.0
:Height relative to thing's middle to source bullet (hitscan) rays.

*'''damagefactor'''
:This sets up the monster's resistance to various [[EDF damagetype reference|damage types]] ("means of death"). 0 means invincible (''but still suffering pain''), 1 full damage. This property has a distinct syntax: there may be as many ''DamageFactor'' lines as damage resistances. Note that setting the factor to 0 won't prevent monster retaliation. Example of usage:
damagefactor fire, 0.3
damagefactor lava, 0.2
:As seen above, no braces are used, and the arguments are separated by commas.
:You can also use the '''immune''' keyword to make a thingtype truly immune to certain damage types, preventing any reaction or infighting. Example:
damagefactor fire, immune
:A third optional argument is possible, called '''rounded'''. It was needed to support the various Heretic boss damage resistances. Its presence has the following effects:
:*The reduction of damage is rounded to the nearest, instead of down.
:*If there ends up being no damage, the target won't react as if in pain.
:Example:
damagefactor lava, 0.25, rounded

*'''damagefactor.remove'''
:Removes the given '''damagefactor''' specification if it already exists from an inherited thingtype, or in a delta structure of an existing one.

*'''cleardamagefactors'''
:Removes all already existing '''damagefactor''' specifications.

*'''topdamage'''
:Default = 0
:This number is a constant amount of damage inflicted on any shootable object that stands on top of this object when 3D object clipping is active. This is useful for objects such as torches and flaming barrels. The frequency of damage is determined by the topdamagemask field.
*'''topdamagemask'''
:Default = 0
:This number determines how often a thing with a non-zero topdamage field burns objects that are standing on top of it. This number should be a power of two minus 1 to work properly, such as 1, 3, 7, 15, or 31 (31 would be approximately once per second and is used by DOOM's nukage sector types). New to EDF 1.7.
*'''mod'''
:Default = UNKNOWN (0)
:Originally standing for "Means of Death", this field allows you to associate a '''[[damagetype]]''' to an inflictor (such as projectile) thing type. Then, you'll be able to make other thing types resistant to the given damage type by using the '''damagefactor''' field. You can give them specific pain or death states as well. Damage types also have the role in multiplayer to specify what obituaries are shown depending on which weapon the player uses.
:The mnemonics were initially hard-coded, but are now available inside ''base\things.edf'' as '''damagetype''' blocks. Notice that the default damage types (means of death) have been differentiated for each player attack, as well as for the various slime types and whatnot, so as to have the obituaries differentiated. Monsters don't need new damage types to have new obituaries, because these are defined within the '''thingtype''' block. See the two fields below.
*'''obituary_normal'''
:Default = empty
:Defines the obituary seen by players when killed by a projectile or other miscellaneous attack by a monster. If the obituary is not defined for this type, it will simply read that the player died. Note that you are only allowed to specify an obituary starting immediately after the player's name. If you want an obituary to say "Player was flamed", then simply make the obituary read "was flamed".
:You can also use a $-prefixed Dehacked string for this.
*'''obituary_melee'''
:Default = empty
:Defines the obituary seen by players when killed by a monster's melee attack. If the obituary is not defined for this type, it will simply read that the player died. Note that you are only allowed to specify an obituary starting immediately after the player's name. If you want an obituary to say "Player was stabbed mercilessly", then simply make the obituary read "was stabbed mercilessly".
:You can also use a $-prefixed Dehacked string for this.

====Pain/Death Properties====
*'''nukespecial'''
:Default = NULL
:This field is the name of a special codepointer to call when the player uses the KILLEM cheat to kill all monsters. Currently only two special pointers are provided for this purpose, PainNukeSpec and SorcNukeSpec. These enable monsters with spawn-on-death actions to either spawn enemies early, or not at all. See the Eternity Engine Definitive Codepointer Reference for detailed information.
*'''droptype'''
:Default = NONE
:This field allows the type of thing that is dropped by this thing when it dies to be edited. This field should either be a valid thing type mnemonic, or the special value NONE.
*'''cleardropitems'''
:The '''cleardropitems''' flag, if present, removes ALL dropitems from a thingtype. This is applied *before* any dropitem or droptype fields defined within this thingtype itself. This allows removing all inherited dropitems at once. This field is a flag and does not accept any value. Its presence in a thingtype is not inheritable (things which inherit from this type must again specify cleardropitems if they want to in turn remove any items this type added).
*'''dropitem ''type'', [, ''chance'' [, ''amount'' [, ''toss'']]]'''
:dropitem defines a Doom- or Heretic-style drop item; any number of dropitems can be defined. All are dropped when an enemy dies, subject to possible randomization.
:*''type'': name of EDF thing type to spawn
:*''chance'': If specified, chance between 0 and 255 to spawn this drop, 0 being no chance and 255 being 100%.
:*''amount'': If specified, overrides the '''dropamount''' field of an '''ammoeffect''' definition. Does not affect any other item effect type. If zero, this field is ignored.
:*''toss'': Flag value. If specified as +toss, the item is a Heretic-style item drop which will be thrown out during the A_Fall action function with randomized velocity. If this flag is not specified, or is specified as -toss, the item is a Doom-style drop item which will be spawned on the floor as soon as the dying thing has reached 0 health.
:Note: The older '''droptype''' field is still supported, and defines a Doom-style dropitem (100% chance, no dropamount override, and never tossed).
*'''dropitem.remove'''
:removes from this thingtype's dropitem list the named EDF thingtype. Useful when inheriting.
*'''collectionspawn''' ''thingtype'' [, ''spchance'' [, ''coopchance'' [, ''dmchance'']]]
:collectionspawn defines a thingtype at which THIS thingtype will select one instance out of all instances on the map at which to spawn itself at level start. This attribute is used by the Heretic Fire Mace. See the example in [https://github.com/team-eternity/eternity/blob/master/base/heretic/things.edf#L3213 Heretic's things.edf] on how it's used.
:Explanation of collectionspawn multivalue properties:
:*''thingtype'': Name of the EDF thingtype at which to spawn at random. If this is invalid, this collectionspawn definition will be disregarded.
:*''spchance'': if specified, chance this item will spawn at all in single player, from 0 to 255. Default is 255.
:*''coopchance'': if specified, chance this item will spawn at all in coop mode, from 0 to 255. Default is 255.
:*''dmchance'': if specified, chance this item will spawn at all in deathmatch mode, from 0 to 255. Default is 255.
*'''itemrespawnat''' ''thingtype''
:itemrespawnat defines an EDF thingtype at which this thingtype will respawn if it becomes subject to Heretic-style item respawning.

=====Blood properties=====
*'''bloodcolor'''
:Default = 0
:Allows this thing type to have differently colored blood when particle blood effects are enabled (this does not currently have any effect on blood sprites). Currently available blood color values are as follows:
Blood color Number
--------------------------
Red (normal) 0
Grey 1
Green 2
Blue 3
Yellow 4
Black 5
Purple 6
White 7
Orange 8
--------------------------

*'''bloodbehavior'''
:Syntax: '''bloodbehavior''' ''action'', ''behavior''
:A '''thingtype''' can have one or more of these entries. ''Action'' can be one of: '''shot''', '''impact''', '''rip''' or '''crush'''. ''Behavior'' can be one of: '''Doom''', '''Heretic''', '''HereticRip''', '''Hexen''', '''HexenRip''', '''Strife''' or '''crush'''. Setting this will override game's default settings, which for Doom are respectively ('''Doom''', '''Heretic''', '''HereticRip''', '''crush''') and for Heretic are ('''Heretic''', '''Heretic''', '''HereticRip''', '''crush'''). Due to Doom having no innate impact or rip attacks, it borrows the behaviors from Heretic. The meanings of the actions are as such:
:*'''shot''': from bullet (hitscan) attacks.
:*'''impact''': from projectiles with the '''DRAWSBLOOD''' flag (Heretic projectiles commonly have this).
:*'''rip''': from projectiles with the '''RIP''' flag (Heretic's powered dragonclaw attack has this).
:*'''crush''': from crushing surfaces (except for polyobjects).
:The behaviors assigned to each action can be:
:*'''Doom''': spawns the given blood objects with a small vertical speed of 2 and lowers the tic count of the first frame. If damage is less than 9, it will jump to Decorate state '''Blood3''' (or if missing, '''dehackednum''' 92). If damage is between 9 and 12, it will jump to Decorate state '''Blood2''' (or if missing, '''dehackednum''' 91).
:*'''Heretic''': similar to the '''Doom''' behavior, but without the state transition or randomization, and with a random horizontal spread.
:*'''HereticRip''': spawns the blood object at a slight distance away from inflictor or (if missing) target, clears it of gravity and propels it in a direction of inflictor/target's speed. It will also randomly increase the duration of the first state by 0-3.
:*'''Hexen''': like '''Heretic''' but with even more spread.
:*'''HexenRip''': like '''HereticRip''' but with gravity (won't add '''NOGRAVITY''').
:*'''Strife''': similar to Doom but with no duration randomization and with transitions to '''Blood2''', '''Blood1''', '''Blood0''' for damages 0-6, 7-9 or 10-13 respectively.
:*'''crush''': blood splat will be spread horizontally.

====Flags====
*'''cflags'''
:Default = ""
:This field allows specification of all the thing's flag values in one single flag list. When this field is defined, flags, flags2, flags3 and flags4 are ignored. The only caveat to this field is that the '''flags''' bit "SLIDE", which has no effect, cannot be specified in this field. If SLIDE is used, it will activate the '''flags3''' bit with the same name, which has the expected effect. All other flags will be assigned to their appropriate internal fields as normal. See the [[Thing type flags]] for their descriptions.

*'''addflags'''
:Default = ""
:This field specifies a combined list of flags to be added to the thing's existing flags values (this works the same as the cflags field above). Flags in this list are "turned on" in the thing. If flags are listed here which are already "on," there is no effect on those flags. This field is most useful within thingdelta sections and in concert with thing type inheritance.
*'''remflags'''
:Default = ""
:This field specifies a combined list of flags to be subtracted from the thing's existing flags values (this works the same as the cflags field above). Flags in this list are "turned off" in the thing, as if they had never been listed. If flags are listed here which are not already "on," there is no effect on those flags. This field is most useful within thingdelta sections and in concert with thing type inheritance. This field will be applied '''AFTER''' the addflags field is applied, so it could potentially turn off flags turned on by that field.

*'''flags'''
:Default = ""
:This field controls a number of thing type properties using bit flags, where each bit in the field stands for some effect, and has the value of being either on or off. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags2'''
:Default = ""
:Similar to flags but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags3'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags4'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags5'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''particlefx'''
:Default = 0
:This field is a flag field with syntax identical to the flags, flags2, and flags3 fields, but which accepts the following values which control what persistent particle effects are associated with objects of this type:
Flag name Hex Value Effect
--------------------------------------------------------
ROCKET 0x00000001 Rocket trail
GRENADE 0x00000002 Grenade trail
FLIES 0x00000004 Swarm of flies w/ sound
BFG 0x00000008 BFG particle swarm
FLIESONDEATH 0x00000010 Flies when object dies
DRIP 0x00000020 Parameterized drip effect
REDFOUNTAIN 0x00010000 Red fountain
GREENFOUNTAIN 0x00020000 Green fountain
BLUEFOUNTAIN 0x00030000 Blue fountain
YELLOWFOUNTAIN 0x00040000 Yellow fountain
PURPLEFOUNTAIN 0x00050000 Purple fountain
BLACKFOUNTAIN 0x00060000 Black fountain
WHITEFOUNTAIN 0x00070000 White fountain
--------------------------------------------------------
:Note that the fountain flag values cannot be combined with each other. Doing so will simply result in another one of the existing fountain colors.
:The DRIP effect requires parameters to be specified in a thing's [[ExtraData]] mapthing block. The parameters to this effect are as follows:
:*args 0: color (palette index from 0 to 255)
:*args 1: particle width/height in pixels
:*args 2: frequency in gametics
:*args 3: if 1, particles cause terrain hits
:*args 4: if 1, particles are fullbright
:Examples:
# a single effect
particlefx = ROCKET

# multiple effects
particlefx = BFG+GREENFOUNTAIN

# if there are spaces or disallowed characters, you must use quotations
particlefx = "BFG + GREENFOUNTAIN"

====Graphic Properties====
*'''translucency'''
:Default = 65536 (100%)
:This field allows fine, customizable control over a thing's translucency. This field accepts two types of values. First, it may be given an integer value in the range of 0 to 65536, with 0 being completely invisible, and 65536 being normal. Alternatively, beginning with EDF 1.3, you can provide a percentage value to this field indicating the amount of the foreground sprite that is blended with the background. A percentage value must be a base 10 integer between 0 and 100, with the final digit followed immediately by a '%' character (percent sign).

:Note this effect is mutually exclusive of BOOM-style translucency. If this value is not 65536 (or 100%), and the BOOM translucency flag is turned on for the same thing type, the flag will be turned off at run-time, and this field will take precedence.

*'''translation'''
:Default = 0
:Sets a translation for the thing's sprite. Translation tables are 256-byte lumps which can be used to remap any range of colors in a sprite. When this field defaults, no translation will be used. Otherwise, you may either provide a number to access one of the internal player translation tables, or you may provide the name of a translation lump, which must be found either inside the '''translations''' folder inside a [[PKE]], or between T_START and T_END markers inside a [[Doom Wiki:WAD|wad]]. Numeric values for player translations are as follows. All of the player translations remap the pure green range:
:*1: indigo
:*2: brown
:*3: red
:*4: tomato
:*5: dirt
:*6: blue
:*7: gold
:*8: sea
:*9: black
:*10: purple
:*11: orange
:*12: pink
:*13: cream
:*14: white

*'''tranmap'''
:Default: not used
:This is a [[translucency map]] lump name to use to render the thing. NOTE: it should NOT be between T_START and T_END. Useful if you want custom translucency effects, not easily available with simple parameterized means.

*'''skinsprite'''
:Default = "noskin"
:The skinsprite field defines a sprite that will be used to override the sprite value in any frame a thing of this type enters. This allows the creation of thingtypes which behave identically but look different without the creation of any new frames. Note that when things are crushed into gibs, the skinsprite is cleared at that time. If an Archvile resurrects such a thing, the proper skinsprite is then restored.
:NOTE: for any use of '''skinsprite''', you need to add the sprite to the '''spritenames''' list, e.g. <code>spritenames += { SPRT }</code> (for a sprite named <code>SPRT</code>)
*'''defaultsprite'''
:Default = the object's first spawn state's sprite
:Controls the remapping behavior of skins for objects that use more than one sprite. Any frame not using the defaultsprite is ignored for remapping by the skin. If not set, the defaultsprite is adapted from the object's first spawn state.
*'''alphavelocity'''
:Default = 0.0
:If nonzero, the thing's opacity (alpha value) will raise up to full solidity, or lower to full invisibility, depending on '''alphavelocity''''s sign and quantity per tic. If the '''CYCLEALPHA''' [[Thing type flags|flag]] is set, the thing will cycle between visibility and invisibility with this speed.
*'''xscale'''
:Default = 1.0
:Sets how much the horizontal component of the sprite is to be scaled.
*'''yscale'''
:Default = 1.0
:Sets how much the vertical component of the sprite is to be scaled.

*'''trail.type'''
:If specified, is the thing type of trail to spawn when moving as a '''RavenFast''' projectile.

*'''trail.zoffset'''
:Default = -8.0
:Vertical offset where to spawn the trail object.

*'''trail.spawnchance'''
:Default = 256
:Chance out of 256 to spawn a trail object.

*'''trail.sparsity'''
:Default = 0
: How sparsely to spawn the trail objects. Be careful that this uses the counter of 0 (commonly used in frame scripting [[codepointers]]). 1 or less means all the time, larger values reduce the amount of sparkles.

====Pick-up effect====
*'''pickupeffect'''
:You can define the details of an item with the '''SPECIAL''' [[Thing type flags|flag]] in this block. See the [[pickupeffect|standalone block definition]] for explanation of the available fields.
*'''clearpickupeffect'''
:If added, it will clear the previous '''pickupeffect''' definition from an inherited '''thingtype''' or when using a '''thingdelta'''. By default it will be copied.

====ACS Spawn Data Sub-Block====
*'''acs_spawndata'''
:Default = (nothing)
:This specifies the identification number for various parameterized specials, such as [[Thing_Spawn]] or [[Thing_SpawnNoFog]]. It also limits the number to a game namespace. For example, by default the Zombieman has
acs_spawndata { num 4; modes doom }
:Heretic objects will use '''modes heretic''' instead of '''modes doom'''. To make it work for any game mode, use '''modes all''' or simply omit it. You shouldn't need to use '''modes''' in any custom mod unless it's available for more than one game.
:'''num''' must be between 0 and 255 inclusive.
[[category:EDF]]

==References==
This document has content from:
*New Bifrost features, on Eternity website: http://eternity.mancubus.net/text/bifrost_docs.txt
*Old documentation

EDF thing reference

2025-08-23T17:11:34Z

Printz: /* Syntax */

Thing types define monsters, lamps, control points, items, etc -- anything that moves, occupies space, can display a sprite, or is useful for singling out locations. Things have unique names, or mnemonics, for easy identification. They're referenced in several places by their name, such as the console command ''Summon'', or [[List of codepointers|action functions]] dealing with spawning things (such as [[Spawn]] or [[MissileAttack]]).

If a thing type's mnemonic is not unique, the latest definition of a thing type with that mnemonic replaces any earlier ones. Like most other identifiers in EDF (but not lump names or subnames), thing type mnemonics are completely case-insensitive.

New objects, created via EDF files or wad lumps, can be later tweaked with Dehacked (BEX) patches, if they're given a unique '''dehackednum''' entry. For forward compatibility, the '''dehackednum''' has to be greater than or equal to 10000.

For placing the thing on the map, an integer field called '''doomednum''' must be specified. For forward compatibility it has to be greater than or equal to 20000 or in the 3000-3999 range. Due to how binary WAD files format their THINGS lumps, '''doomednum''' values have to be less than 32767, though textmode representations such as [[ExtraData]] or UDMF solve this limit.

If you want to know the base game thing types from Doom, you can look on the [https://github.com/team-eternity/eternity/blob/master/base/doom/things.edf list of Doom thing types].

{{See|Thing type flags}}
{{See|thinggroup}}. Some of the customization should be set in '''thinggroup''' blocks, which group multiple things. Most notably, infighting control. There are also flags and '''damagefactor''' "immune" (see this page) settings.
{{Backto|EDF}}

==Eternity Alfheim syntax==
For versions of Eternity from Alfheim up, EDF thingtypes support the following syntax. Make sure to add:
setdialect("ALFHEIM")
before using this syntax:
thingtype <unique name> : <inherited thingtype>, <doomednum>, <dehackednum>
{
<other attributes>
}
===Header properties===
* ''<inherited thingtype>'' must be a value, even if the thingtype doesn't inherit from anything else. In that case, it must be '''Mobj''', which is a placeholder value belonging to no real thingtype.
* ''<doomednum>'' and ''<dehackednum>'' can be -1 if not used. If both are -1, they can be omitted, leaving just this:
thingtype <unique name> : <inherited thingtype> {<attributes>}
* If header properties are used, the pre-Alfheim '''inherits''', '''doomednum''' and '''dehackednum''' attributes are not used.

==Syntax==
thingtype <unique name> [: <parent type> [, <doomednum> [, <dehackednum>]]]
{
doomednum <number>
dehackednum <unique number>
inherits <thingtype>
compatname <name>
basictype <basic type qualifier>

// NOTE: for this section, see the "states" field below and use it instead of these.
spawnstate <frame>
seestate <frame>
painstate <frame>
dmg_painstates {<damage type>, <frame>, ...}
dmg_painstates.add {<damage type>, <frame>, ...}
dmg_painstates.remove {<damage type>, ...}
meleestate <frame>
missilestate <frame>
deathstate <frame>
dmg_deathstates {<damage type>, <frame>, ...}
dmg_deathstates.add {<damage type>, <frame>, ...}
dmg_deathstates.remove {<damage type>, ...}
xdeathstate <frame>
raisestate <frame>
healstate <frame> // since Feb 21 2016
crashstate <frame>
activestate <frame>
inactivestate <frame>
crunchstate <frame>

seesound <sound>
attacksound <sound>
painsound <sound>
deathsound <sound>
activesound <sound>
activatesound <sound>
deactivatesound <sound>
ripsound <sound>

spawnhealth <number>
gibhealth <number>
reactiontime <number>
painchance <number>
speed <number OR floating-point number>
fastspeed <number OR floating-point number>
radius <floating-point number>
height <floating-point number>
correct_height <floating-point number>
mass <number>
respawntime <number>
respawnchance <number>

damage <number>
damagemod <number>
dmgspecial <dmgspecial name>
missiletype <option>
aimshift <number>

meleerange <floating-point number>
missileheight <floating-point number>
bulletzoffset <floating-point number>

damagefactor <damage type>, <floating point number>|immune[, rounded]
damagefactor <damage type>, <floating point number>|immune[, rounded]
...
damagefactor.remove <damage type>
cleardamagefactors

topdamage <number>
topdamagemask <number>
mod <MOD name OR number>
obituary_normal <string>
obituary_melee <string>

bloodcolor <number>
nukespecial <BEX codepointer mnemonic>
droptype <thing type mnemonic>

bloodbehavior <action>, <behavior>
clearbloodbehaviors
bloodtype.normal <name>
bloodtype.impact <name>
bloodtype.rip <name>
bloodtype.crush <name>

cleardropitems
dropitem <type>, [, <chance> [, <amount> [, <toss>]]]
dropitem.remove <type>
collectionspawn <thingtype> [, <spchance> [, <coopchance> [, <dmchance>]]]
itemrespawnat <thingtype>

cflags <flag list>
addflags <flag list>
remflags <flag list>
flags <flag list>
flags2 <flag list>
flags3 <flag list>
flags4 <flag list>
flags5 <flag list>
particlefx <particle effect flag list>

translucency <number OR percentage>
translation <number OR translation table lump name>
tranmap <lump name>
skinsprite <sprite>
defaultsprite <sprite>
alphavelocity <floating-point number>
xscale <floating-point number>
yscale <floating-point number>

trail.type <thing type>
trail.zoffset <floating-point number>
trail.spawnchance <number>
trail.sparsity <number>

acs_spawndata {num <number> modes <mnemonic>}

pickupeffect
{
effects <effect1>, ...
changeweapon <weapon>
message <text>
sound <sound>
flags <flags>
}
clearpickupeffect

firstdecoratestate <frame>
states <[[DECORATE state syntax]] heredoc>
}
===Explanation of fields===
====ID / Type Info====
*'''doomednum'''
:Default = -1
:The identification number, which makes this actor type placeable in maps. Zombieman monsters for example have '''doomednum''' 3004. Objects which don't need to be placed on the map can have '''doomednum''' -1. For EDF, recommended numbers are in the ranges 3000-3999 and 20000 up. Other numbers may be used by future versions of Eternity, so they're not safe to use.
:NOTE: you can just use the first number following the inherited class, in the title. Just remember to start the script with <code>setdialect("alfheim")</code>.
*'''dehackednum'''
:Default = -1
:Fake array index number, for Dehacked patch (BEX or DEH file) compatibility. It has to be an unique number if not -1. Safe numbers are from 10000 up.
:NOTE: you can use the second number following the inherited class in the title. For this, you also need <code>setdialect("alfheim")</code>.
*'''inherits'''
:Default = (nothing)
:Sets the thing type from which this will copy properties. All of the properties except '''dehackednum''' will be copied from the base actor type.
:NOTE: you can use the class in the title properties after the colon, instead of '''inherits''' in the '''thingtype''' body. You also need <code>setdialect("alfheim")</code>.
*'''compatname'''
:Default = (nothing)
:Sets a "compatible name" useful for [[ACS]] scripts copied from GZDoom mods or for cross-port usage. Typically the need for this is because of ACS scripts assuming thingtype names from GZDoom, and in the base Eternity definitions, '''compatname''' is set to names which GZDoom uses for its thingtypes.
:Setting this flag is not needed and shouldn't be done in mods.
*'''basictype'''
:Default = (nothing)
:'''Basictype''' is a list of common flags used in Doom and derived games. Using '''basictype''' instead of setting individual flags is encouraged, in order to keep up with Eternity engine updates. Other flags may be subsequently added or removed with '''addflags''' or '''remflags'''. See the [[Thing type flags]] page for a full list. The '''basictype''' mnemonics follow:
:*''Monster''
::An ordinary walking monster with no fancy features.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+FOOTCLIP+SPACMONSTER+PASSMOBJ"

:*''FlyingMonster''
::An ordinary flying monster.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+NOGRAVITY+FLOAT+SPACMONSTER+PASSMOBJ"

:*''FriendlyHelper''
::A player helper with maximum friendliness options.
::'''cflags''' "SOLID+SHOOTABLE+COUNTKILL+FRIEND+JUMPDOWN+FOOTCLIP+WINDTHRUST+SUPERFRIEND+SPACMONSTER+PASSMOBJ"

:*''Projectile''
::A standard projectile.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS"

:*''PlayerProjectile''
::A projectile for use by players.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS+SPACMISSILE"

:*''Seeker''
::A missile prepared to be fired by homing missile codepointers.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+DROPOFF+MISSILE+NOCROSS+SEEKERMISSILE"

:*''SolidDecor''
::A solid decorative item.
::'''cflags''' SOLID

:*''HangingDecor''
::A hanging decorative item that is passable even without 3D object clipping.
::'''cflags''' "SPAWNCEILING+NOGRAVITY"

:*''SolidHangingDecor''
::A solid hanging decorative item.
::'''cflags''' "SOLID+SPAWNCEILING+NOGRAVITY"

:*''ShootableDecor''
::A shootable decorative item.
::'''cflags''' "SOLID+SHOOTABLE+NOBLOOD"

:*''Fog''
::A fog item such as telefog or item fog.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+TRANSLUCENT+NOSPLASH"

:*''Item''
::A collectable item. Doesn't count towards the item score.
::'''cflags''' SPECIAL

:*''ItemCount''
::A collectable item. Counts for item score.
::'''cflags''' "SPECIAL+COUNTITEM"

:*''TerrainBase''
::A TerrainTypes base item.
::'''cflags''' "NOBLOCKMAP+NOGRAVITY+NOSPLASH"

:*''TerrainChunk''
::A TerrainTypes chunk item.
::'''cflags''' "NOBLOCKMAP+DROPOFF+MISSILE+LOGRAV+NOSPLASH+NOCROSS+CANNOTPUSH"

:*''ControlPoint''
::An inert control point.
::'''cflags''' "NOBLOCKMAP+NOSECTOR+NOGRAVITY"
::'''spawnstate''' S_TNT1

:*''ControlPointGrav''
::An control point that is subject to gravity. Because of this, it's not considered inert.
::'''cflags''' "DONTDRAW+NOSPLASH"
::'''spawnstate''' S_TNT1

====States====
*'''firstdecoratestate'''
:Sets the first frame in a sequential list of dummy frames that use the internal Decorate-style defined '''states''' of this actor for [[EDF delta structures|framedelta]] compatibility. It's not required unless the intention is to make the Decorate states of this thing accessible from other thing types. Default games' (Doom, Heretic) thing types use externalized frames for all thing types, for compatibility.
*'''states'''
{{see|DECORATE state syntax}}
:Default = nothing
:Defines frames using [http://zdoom.org/wiki/DECORATE DECORATE]-style state definitions. This means it won't be necessary to define separate [[frame]] blocks for each individual frame. See the DECORATE reference at the ZDoom wiki for documentation on its syntax. Using the '''states''' field instead of any of the ones below results in more concise text, but also the newly created frames won't be accessible from outside (other thingtypes, Dehacked patches or delta structures), unless you use the '''firstdecoratestate''' field as well. Like normally, [[List of codepointers|codepointers]] may or may not be preceded by '''A_'''. The DECORATE code has to be implemented via a heredoc: a text string that spans on multiple lines. Unlike a regular string which uses quotation marks, the heredoc is marked by @" and "@ respectively. Example on an imp-like monster (the '=' sign is optional):
states =
@"
Spawn:
TROO AB 10 A_Look
loop
See:
TROO AABBCCDD 3 A_Chase
loop
Pain:
TROO H 2
TROO H 2 A_Pain
goto See
Melee:
Missile:
TROO EF 8 A_FaceTarget
TROO G 6 A_TroopAttack
goto See
Death:
TROO I 8
TROO J 8 A_Scream
TROO K 6
TROO L 6 A_Fall
TROO M -1
stop
XDeath:
TROO N 5
TROO O 5 A_XScream
TROO P 5
TROO Q 5 A_Fall
TROO RST 5
TROO U -1
stop
Raise:
TROO ML 8
TROO KJI 6
goto See
"@
:A "fast" flag is now allowed between the tics and action function of DECORATE states (along with the pre-existing "bright" flag) which determines if that state halves its "tics" value when the game is in -fast or Nightmare skill. Example (from demon's states):
states
@"
See:
SARG AABBCCDD 2 fast A_Chase
loop
Melee:
SARG EF 8 fast A_FaceTarget
SARG G 8 fast A_SargAttack
goto See
Pain:
SARG H 2 fast
SARG H 2 fast A_Pain
goto See
"@
*'''spawnstate'''
:Default = S_NULL
:Sets the frame which a thing starts in when it is spawned. Monsters generally use this frame to stand still and look for targets. If the object is supposed to have any dynamic purpose or be visible, do not leave the '''spawnstate''' at S_NULL.
*'''seestate'''
:Default = S_NULL
:Sets the frame which a monster will jump to when it sees or hears a target during a [[Look]] (monster standing unawakened) check. If an object is alive and has a seestate, it is considered ''sentient'' by certain game mechanics.
*'''painstate'''
:Default = S_NULL
:Sets the frame a thing may randomly enter when it has been injured. If set to S_NULL, the creature will be removed instantly from the game if the random check succeeds.
*'''dmg_painstates'''
:Default = (nothing)
:This is a list of one or more damagetype/frame pairs, enclosed in braces. For example:
dmg_painstates
{
Fire, S_HPLAY_FPAIN1,
Lava, S_HPLAY_LPAIN1
}
makes the actor go to frame S_HPLAY_FPAIN1 when damaged by fire, or to S_HPLAY_LPAIN1 when harmed by lava. It defaults to its '''painstate''' if the damage is of another nature. The damage type of an actor is set up through the '''mod''' field.
*'''dmg_painstates.add'''
*'''dmg_painstates.remove'''
:Can be used for derived actor types, who can have more or fewer specialized pain states than their ancestors. ''Dmg_painstates.add'' has the same format as ''dmg_painstates'', but ''dmg_painstates.remove'' only lists the damagetypes. For example:
dmg_painstates.remove
{
Fire, lava
}
makes them get hurt normally from fire or lava, without going to special pain states.
*'''meleestate'''
:Default = S_NULL
:If this frame is not S_NULL, monsters will have a slightly lower range attack probability and when they are within about 64 units of their target, they will enter this frame to perform a melee attack.
*'''missilestate'''
:Default = S_NULL
:If this frame is not S_NULL, monsters chasing a target will randomly enter it to perform a missile attack.
*'''deathstate'''
:Default = S_NULL
:When a thing dies normally, it will enter this state. If the state is S_NULL, the thing will disappear forever.
*'''dmg_deathstates'''
*'''dmg_deathstates.add'''
*'''dmg_deathstates.remove'''
:Defaults = (nothing)
:These three properties work similar to ''dmg_painstates*'', in that they allow the object to enter special frames depending on the damage type suffered, but if they die. The formats are the same.
*'''xdeathstate'''
:Default = S_NULL
:If a thing dies by taking enough damage that its health is equal to its negated spawnhealth value (or negated 0.5 spawnhealth value in Heretic), it will enter this frame instead of its deathstate. If this frame is S_NULL, the thing will always die normally.
*'''raisestate'''
:Default = S_NULL
:If this frame is not S_NULL, a creature running [[VileChase]] codepointers can perform a resurrection on this actor. When this occurs, the actor will enter this frame along with being restored.
*'''healstate''' (since Feb 21 2016)
:Default = S_NULL
:Sets the frame to jump to if, during a [[VileChase]] frame, the thing encounters a corpse and raises it. If not set (or set to S_NULL), it will actually default to S_VILE_HEAL1, same as in Doom.
*'''crashstate'''
:Default = S_NULL
:When a thing with this state dies and then subsequently hits the ground, it will enter this state. If this state S_NULL, it is not used.
*'''activestate'''
:Default = S_NULL
:State to enter when triggered by the '''Thing_Activate''' parameterized special.
*'''inactivestate'''
:Default = S_NULL
:State to enter when triggered by the '''Thing_Deactivate''' parameterized special.
*'''crunchstate'''
:State, if specified, to enter when crushed as a dead body by a sector (door, crusher etc.). If unspecified, it depends on game mode, and it's the pool of blood in Doom.

====Sounds====
*'''seesound'''
:Default = none
:Sets the sound that a monster will play when it awakens. This sound is also played by missiles when they are shot. (Note: "none" is a special mnemonic for no sound)
*'''attacksound'''
:Default = none
:Sets a sound used by some monster attacks, including the Lost Soul's charge, or melee attacks.
*'''painsound'''
:Default = none
:Sets the sound played by the Pain codepointer when this thing uses it.
*'''deathsound'''
:Default = none
:Sound played by the Scream codepointer. Used to play monster death sounds.
*'''activesound'''
:Default = none
:Sets the sound used by a thing when it is wandering around. A thing is given a 3 out of 256 chance (1.17%) of making this sound every time it calls the Chase codepointer. There are some new flags3 flags which can alter the behavior of this sound.
*'''activatesound'''
:Default = none
:Sound to play when triggered by the '''Thing_Activate''' parameterized special.
*'''deactivatesound'''
:Default = none
:Sound to play when triggered by the '''Thing_Deactivate''' parameterized special.
*'''ripsound'''
:Default = none
:Sound to play if it's a projectile using the '''RIP''' flag and it's moving and ripping through shootable targets. This is for example used by the Heretic powered-up Dragon Claw secondary "spiked ball" projectiles when they pass through enemies.

====Basic Stats====
*'''spawnhealth'''
:Default = 1000
:Sets a thing's maximum amount of life.
*'''gibhealth''' ''number''
:gibhealth overrides the gamemode default behavior for determining the negative amount of health at which a thing uses its "extreme" death state rather than its normal one. This is ordinarily defined in terms of the spawnhealth (Doom and Strife thingtypes gib at -spawnhealth; Heretic and Hexen thingtypes gib at -(spawnhealth/2).
:If an inheriting thingtype changes its spawnhealth, it will "lose" the inherited definition of gibhealth from its parent. If changing spawnhealth when inheriting from a thingtype that customizes gibhealth, be sure to re-customize the gibhealth in the inheriting thingtype.
*'''reactiontime'''
:Default = 8
:Sets an amount of time that a thing must wait under certain circumstances. Monsters use this value as a means to control their rate of attack. This value is also used as an internal field for varying purposes, but those uses are not editable.
*'''painchance'''
:Default = 0
:Sets the chance out of 255 that this thing will enter its painstate when it is injured. A thing with 0 painchance will never feel pain, whereas a thing with 255 painchance will always feel pain. If a thing has a painchance greater than zero, it should have a valid painstate, otherwise it will disappear forever.
*'''speed'''
:Default = 0
:Value used by monsters as a movement delta per walking frame. The monster will move by an amount relative to this value each time it uses the Chase codepointer. For missiles, this value is a fixed-point number (multiplied by 65536), and represents a constant speed by which the missile advances every game tic. Missile speed is not affected by the missile frame durations, whereas monster walking speed is.
:This field also supports floating-point values. When a floating-point value is provided, it will be translated into the corresponding fixed-point value. This means that a value of 10.0 is equivalent to the integer value 655360 (10*65536). It is NOT equivalent to 10. This distinction is very important. Small integer speed values are appropriate for monsters, whereas floating-point values will be suitable only for missiles.
*'''fastspeed'''
:Default = 0
:When the game is switched into Nightmare difficulty or -fast mode is active, all thing types with a non-zero fastspeed will have their speed fields changed to their fastspeed value. This enables editing of the -fast speed of projectiles and monsters. For detailed information on speed, see the speed field itself above. Note: as of EDF 1.2, this field also supports floating-point numbers, with the same meaning as that for the speed field.
*'''radius'''
:Default = 20.0
:Floating-point value that represents the radius of this thing type. A thing can fit into corridors which are at least as wide as this value times two, plus one unit (ie a thing with radius 32 can fit into a 65-wide hallway). The maximum value this field *should* have is 64.0 units. However, the game breaks its own rule here, giving several monsters radii up to 128 units. These monsters, which include the Mancubus, Arachnotron, and Spider Demon, exhibit clipping errors which enable other things to walk into them, and which can cause some moving sectors to malfunction. Avoid giving things radii larger than 64.0 to remain absolutely safe.
*'''height'''
:Default = 16.0
:Floating-point value that represents the height of this thing type. A thing can fit into areas which are of this exact height or taller. Note that in DOOM, this value is only used to see where a monster can fit relative to walls and floor/ceiling heights. For purposes of clipping against other things, monsters were considered to be infinitely tall. However, Eternity's extended 3D object clipping enables this field to also be used to allow or disallow things to pass over, under, or stand on this thing.
*'''correct_height'''
:Default = 0.0
:Floating-point value that represents a height for this thing type which is corrected for 3D object clipping. When 3D object clipping is enabled and the comp_theights variable is set to off, objects which have a non-zero correct_height field will begin to use this value for their height instead of the normal height field. If an object has the 3DDECORATION flags3 bit set, it will still clip missiles at its original height instead of at this value, so that playability of old maps is not altered. This field will generally only be necessary for old DOOM objects, which have now been assigned correct_height values in the default things.edf module. Use for new objects is discouraged; instead, set the height field above to the proper value.
*'''mass'''
:Default = 100
:Normal integer value that serves as a mass factor for this object. Mass affects the amount of thrust an object is given when it is damaged, the amount of effect an archvile's attack can have on it, and for bouncing objects, the rate at which they fall. Objects with a mass less than 10 will cause small terrain hits when landing on terrain that supports small splashes.
*'''respawntime'''
:Default = 420
:Sets the number of gametics before the monster may respawn. A tic is 1/35 of a second.
*'''respawnchance'''
:Default = 4
:Sets the chance out of 255 that the monster may respawn after respawntime has passed. The check is done for each tic that the monster isn't blocked.
====Damage Properties====
*'''damage'''
:Default = 0
:This number is used as a damage multiplier when a [[Thing type flags|MISSILE]] or SKULLFLY actor hits a SHOOTABLE. The damage formula used for impact damage is:
((rnd % damagemod) + 1) * damage
:This field is also used as a parameter by some parameterized codepointers, including [[Scratch]], [[BetaSkullAttack]] and [[Detonate]]. See '''damagemod''' field's description for the <code>damagemod</code> parameter.
*'''damagemod'''
:Default = 8
:This is the damage modulus to use when computing projectile damage. This is the maximum multiplier of '''damage''' for a projectile impact. For Doom projectiles, it's typically 8. To have constant impact damage, you can set it to 1. Do not set it to 0.
*'''dmgspecial'''
:Default = "none"
:The dmgspecial field allows specification of a special action that will be taken when this object is involved in damaging another object as the inflictor (an inflictor is the object actually doing the damage, and not necessarily the object that is blamed for the damage). Supported values and their meanings are as follows:
:*''none''
::This is the default value. No special action is taken; the object is normal when damaging other things.

:*''MinotaurCharge''
::If the thing is flying like a skull (has flags bit SKULLFLY set), it will inflict a large amount of thrust on the target along the vector of the impact, will hit it directly for ((rnd % 8) + 1) * 6 damage, and if the target is a player, the player's controls will be frozen for 14 + (rnd % 8) gametics. When the thing is not in SKULLFLY mode, normal damage is done by all attacks.

:*''Whirlwind''
::The target will have its angle and x/y momenta modified by random amounts. If the current level time has the 5th bit (value 16) set and the target is not a boss (possesses the BOSS flag), the target will be given randomized z momentum up to but no greater than 12 units per tic. When the level time is divisible by 8, the target will be hit directly for 3 damage.

:*''PoweredMaceBall''
::Behavior specific to the powered mace projectile. Beware that it has behavior specific to some Heretic thing type targets, and it can even cause a target player to use the Chaos Device.

:*''PoweredPhoenixFire''
::Causes players to be occasionally stunned.

:*''BossTeleport''
::Causes monsters with properties similar to dismounted D'Sparil to teleport away on impact.

*'''missiletype'''
:Default = '''Default'''
:Type of movement if this thingtype is a projectile. It can be '''Default''' or '''RavenFast'''. The '''Default''' type is usual, allowing speeds up to about 35 (but in practice the limit is around 25, after which it becomes inaccurate). The '''RavenFast''' type is for very fast projectiles, as happening to some types in the Heretic and Hexen games, which can be very fast and still being accurate. Do mind that '''RavenFast''' works only and strictly with projectiles, and can't be used with other types of actors, as they're severely limited on their interactions with the environment.

*'''aimshift''' ''number''
:If in the range of 0 to 24, this value overrides the "shift" amount that enemies of this object experience while trying to aim at it due to effects like SHADOW, GHOST, and TOTALINVISIBLE. A larger number in this field makes enemies more inaccurate when aiming at this creature. The default value of -1 means that no aiming inaccuracy is experienced *except* what may be incurred from what flags this monster has. A value larger than 24 will, on the other hand, override the creature's flags and cause enemies to experience no inaccuracy due to to those flags (so for example a creature inheriting from Spectre and setting its aimshift to 25 will behave as though it does not have the SHADOW flag other than for rendering purposes). Values of 20 and 21 are used by the various built-in flag effects.

*'''meleerange'''
:Default = 64.0
:Sets the close attack distance for this monster, allowing initiation of attack to start at a different distance from default.

*'''missileheight'''
:Default = 32.0
:Height relative to thing's feet to spawn new projectiles if no other changes are implied in the codepointer.

*'''bulletzoffset'''
:Default = 8.0
:Height relative to thing's middle to source bullet (hitscan) rays.

*'''damagefactor'''
:This sets up the monster's resistance to various [[EDF damagetype reference|damage types]] ("means of death"). 0 means invincible (''but still suffering pain''), 1 full damage. This property has a distinct syntax: there may be as many ''DamageFactor'' lines as damage resistances. Note that setting the factor to 0 won't prevent monster retaliation. Example of usage:
damagefactor fire, 0.3
damagefactor lava, 0.2
:As seen above, no braces are used, and the arguments are separated by commas.
:You can also use the '''immune''' keyword to make a thingtype truly immune to certain damage types, preventing any reaction or infighting. Example:
damagefactor fire, immune
:A third optional argument is possible, called '''rounded'''. It was needed to support the various Heretic boss damage resistances. Its presence has the following effects:
:*The reduction of damage is rounded to the nearest, instead of down.
:*If there ends up being no damage, the target won't react as if in pain.
:Example:
damagefactor lava, 0.25, rounded

*'''damagefactor.remove'''
:Removes the given '''damagefactor''' specification if it already exists from an inherited thingtype, or in a delta structure of an existing one.

*'''cleardamagefactors'''
:Removes all already existing '''damagefactor''' specifications.

*'''topdamage'''
:Default = 0
:This number is a constant amount of damage inflicted on any shootable object that stands on top of this object when 3D object clipping is active. This is useful for objects such as torches and flaming barrels. The frequency of damage is determined by the topdamagemask field.
*'''topdamagemask'''
:Default = 0
:This number determines how often a thing with a non-zero topdamage field burns objects that are standing on top of it. This number should be a power of two minus 1 to work properly, such as 1, 3, 7, 15, or 31 (31 would be approximately once per second and is used by DOOM's nukage sector types). New to EDF 1.7.
*'''mod'''
:Default = UNKNOWN (0)
:Originally standing for "Means of Death", this field allows you to associate a '''[[damagetype]]''' to an inflictor (such as projectile) thing type. Then, you'll be able to make other thing types resistant to the given damage type by using the '''damagefactor''' field. You can give them specific pain or death states as well. Damage types also have the role in multiplayer to specify what obituaries are shown depending on which weapon the player uses.
:The mnemonics were initially hard-coded, but are now available inside ''base\things.edf'' as '''damagetype''' blocks. Notice that the default damage types (means of death) have been differentiated for each player attack, as well as for the various slime types and whatnot, so as to have the obituaries differentiated. Monsters don't need new damage types to have new obituaries, because these are defined within the '''thingtype''' block. See the two fields below.
*'''obituary_normal'''
:Default = empty
:Defines the obituary seen by players when killed by a projectile or other miscellaneous attack by a monster. If the obituary is not defined for this type, it will simply read that the player died. Note that you are only allowed to specify an obituary starting immediately after the player's name. If you want an obituary to say "Player was flamed", then simply make the obituary read "was flamed".
:You can also use a $-prefixed Dehacked string for this.
*'''obituary_melee'''
:Default = empty
:Defines the obituary seen by players when killed by a monster's melee attack. If the obituary is not defined for this type, it will simply read that the player died. Note that you are only allowed to specify an obituary starting immediately after the player's name. If you want an obituary to say "Player was stabbed mercilessly", then simply make the obituary read "was stabbed mercilessly".
:You can also use a $-prefixed Dehacked string for this.

====Pain/Death Properties====
*'''nukespecial'''
:Default = NULL
:This field is the name of a special codepointer to call when the player uses the KILLEM cheat to kill all monsters. Currently only two special pointers are provided for this purpose, PainNukeSpec and SorcNukeSpec. These enable monsters with spawn-on-death actions to either spawn enemies early, or not at all. See the Eternity Engine Definitive Codepointer Reference for detailed information.
*'''droptype'''
:Default = NONE
:This field allows the type of thing that is dropped by this thing when it dies to be edited. This field should either be a valid thing type mnemonic, or the special value NONE.
*'''cleardropitems'''
:The '''cleardropitems''' flag, if present, removes ALL dropitems from a thingtype. This is applied *before* any dropitem or droptype fields defined within this thingtype itself. This allows removing all inherited dropitems at once. This field is a flag and does not accept any value. Its presence in a thingtype is not inheritable (things which inherit from this type must again specify cleardropitems if they want to in turn remove any items this type added).
*'''dropitem ''type'', [, ''chance'' [, ''amount'' [, ''toss'']]]'''
:dropitem defines a Doom- or Heretic-style drop item; any number of dropitems can be defined. All are dropped when an enemy dies, subject to possible randomization.
:*''type'': name of EDF thing type to spawn
:*''chance'': If specified, chance between 0 and 255 to spawn this drop, 0 being no chance and 255 being 100%.
:*''amount'': If specified, overrides the '''dropamount''' field of an '''ammoeffect''' definition. Does not affect any other item effect type. If zero, this field is ignored.
:*''toss'': Flag value. If specified as +toss, the item is a Heretic-style item drop which will be thrown out during the A_Fall action function with randomized velocity. If this flag is not specified, or is specified as -toss, the item is a Doom-style drop item which will be spawned on the floor as soon as the dying thing has reached 0 health.
:Note: The older '''droptype''' field is still supported, and defines a Doom-style dropitem (100% chance, no dropamount override, and never tossed).
*'''dropitem.remove'''
:removes from this thingtype's dropitem list the named EDF thingtype. Useful when inheriting.
*'''collectionspawn''' ''thingtype'' [, ''spchance'' [, ''coopchance'' [, ''dmchance'']]]
:collectionspawn defines a thingtype at which THIS thingtype will select one instance out of all instances on the map at which to spawn itself at level start. This attribute is used by the Heretic Fire Mace. See the example in [https://github.com/team-eternity/eternity/blob/master/base/heretic/things.edf#L3213 Heretic's things.edf] on how it's used.
:Explanation of collectionspawn multivalue properties:
:*''thingtype'': Name of the EDF thingtype at which to spawn at random. If this is invalid, this collectionspawn definition will be disregarded.
:*''spchance'': if specified, chance this item will spawn at all in single player, from 0 to 255. Default is 255.
:*''coopchance'': if specified, chance this item will spawn at all in coop mode, from 0 to 255. Default is 255.
:*''dmchance'': if specified, chance this item will spawn at all in deathmatch mode, from 0 to 255. Default is 255.
*'''itemrespawnat''' ''thingtype''
:itemrespawnat defines an EDF thingtype at which this thingtype will respawn if it becomes subject to Heretic-style item respawning.

=====Blood properties=====
*'''bloodcolor'''
:Default = 0
:Allows this thing type to have differently colored blood when particle blood effects are enabled (this does not currently have any effect on blood sprites). Currently available blood color values are as follows:
Blood color Number
--------------------------
Red (normal) 0
Grey 1
Green 2
Blue 3
Yellow 4
Black 5
Purple 6
White 7
Orange 8
--------------------------

*'''bloodbehavior'''
:Syntax: '''bloodbehavior''' ''action'', ''behavior''
:A '''thingtype''' can have one or more of these entries. ''Action'' can be one of: '''shot''', '''impact''', '''rip''' or '''crush'''. ''Behavior'' can be one of: '''Doom''', '''Heretic''', '''HereticRip''', '''Hexen''', '''HexenRip''', '''Strife''' or '''crush'''. Setting this will override game's default settings, which for Doom are respectively ('''Doom''', '''Heretic''', '''HereticRip''', '''crush''') and for Heretic are ('''Heretic''', '''Heretic''', '''HereticRip''', '''crush'''). Due to Doom having no innate impact or rip attacks, it borrows the behaviors from Heretic. The meanings of the actions are as such:
:*'''shot''': from bullet (hitscan) attacks.
:*'''impact''': from projectiles with the '''DRAWSBLOOD''' flag (Heretic projectiles commonly have this).
:*'''rip''': from projectiles with the '''RIP''' flag (Heretic's powered dragonclaw attack has this).
:*'''crush''': from crushing surfaces (except for polyobjects).
:The behaviors assigned to each action can be:
:*'''Doom''': spawns the given blood objects with a small vertical speed of 2 and lowers the tic count of the first frame. If damage is less than 9, it will jump to Decorate state '''Blood3''' (or if missing, '''dehackednum''' 92). If damage is between 9 and 12, it will jump to Decorate state '''Blood2''' (or if missing, '''dehackednum''' 91).
:*'''Heretic''': similar to the '''Doom''' behavior, but without the state transition or randomization, and with a random horizontal spread.
:*'''HereticRip''': spawns the blood object at a slight distance away from inflictor or (if missing) target, clears it of gravity and propels it in a direction of inflictor/target's speed. It will also randomly increase the duration of the first state by 0-3.
:*'''Hexen''': like '''Heretic''' but with even more spread.
:*'''HexenRip''': like '''HereticRip''' but with gravity (won't add '''NOGRAVITY''').
:*'''Strife''': similar to Doom but with no duration randomization and with transitions to '''Blood2''', '''Blood1''', '''Blood0''' for damages 0-6, 7-9 or 10-13 respectively.
:*'''crush''': blood splat will be spread horizontally.

====Flags====
*'''cflags'''
:Default = ""
:This field allows specification of all the thing's flag values in one single flag list. When this field is defined, flags, flags2, flags3 and flags4 are ignored. The only caveat to this field is that the '''flags''' bit "SLIDE", which has no effect, cannot be specified in this field. If SLIDE is used, it will activate the '''flags3''' bit with the same name, which has the expected effect. All other flags will be assigned to their appropriate internal fields as normal. See the [[Thing type flags]] for their descriptions.

*'''addflags'''
:Default = ""
:This field specifies a combined list of flags to be added to the thing's existing flags values (this works the same as the cflags field above). Flags in this list are "turned on" in the thing. If flags are listed here which are already "on," there is no effect on those flags. This field is most useful within thingdelta sections and in concert with thing type inheritance.
*'''remflags'''
:Default = ""
:This field specifies a combined list of flags to be subtracted from the thing's existing flags values (this works the same as the cflags field above). Flags in this list are "turned off" in the thing, as if they had never been listed. If flags are listed here which are not already "on," there is no effect on those flags. This field is most useful within thingdelta sections and in concert with thing type inheritance. This field will be applied '''AFTER''' the addflags field is applied, so it could potentially turn off flags turned on by that field.

*'''flags'''
:Default = ""
:This field controls a number of thing type properties using bit flags, where each bit in the field stands for some effect, and has the value of being either on or off. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags2'''
:Default = ""
:Similar to flags but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags3'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags4'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''flags5'''
:Default = ""
:Similar to flags, but takes a different set of values with different meanings. See the [[Thing type flags]] List, for the values which can be used in this field. Remember that if whitespace or disallowed characters are used, this field's value must be enclosed in quotation marks.
*'''particlefx'''
:Default = 0
:This field is a flag field with syntax identical to the flags, flags2, and flags3 fields, but which accepts the following values which control what persistent particle effects are associated with objects of this type:
Flag name Hex Value Effect
--------------------------------------------------------
ROCKET 0x00000001 Rocket trail
GRENADE 0x00000002 Grenade trail
FLIES 0x00000004 Swarm of flies w/ sound
BFG 0x00000008 BFG particle swarm
FLIESONDEATH 0x00000010 Flies when object dies
DRIP 0x00000020 Parameterized drip effect
REDFOUNTAIN 0x00010000 Red fountain
GREENFOUNTAIN 0x00020000 Green fountain
BLUEFOUNTAIN 0x00030000 Blue fountain
YELLOWFOUNTAIN 0x00040000 Yellow fountain
PURPLEFOUNTAIN 0x00050000 Purple fountain
BLACKFOUNTAIN 0x00060000 Black fountain
WHITEFOUNTAIN 0x00070000 White fountain
--------------------------------------------------------
:Note that the fountain flag values cannot be combined with each other. Doing so will simply result in another one of the existing fountain colors.
:The DRIP effect requires parameters to be specified in a thing's [[ExtraData]] mapthing block. The parameters to this effect are as follows:
:*args 0: color (palette index from 0 to 255)
:*args 1: particle width/height in pixels
:*args 2: frequency in gametics
:*args 3: if 1, particles cause terrain hits
:*args 4: if 1, particles are fullbright
:Examples:
# a single effect
particlefx = ROCKET

# multiple effects
particlefx = BFG+GREENFOUNTAIN

# if there are spaces or disallowed characters, you must use quotations
particlefx = "BFG + GREENFOUNTAIN"

====Graphic Properties====
*'''translucency'''
:Default = 65536 (100%)
:This field allows fine, customizable control over a thing's translucency. This field accepts two types of values. First, it may be given an integer value in the range of 0 to 65536, with 0 being completely invisible, and 65536 being normal. Alternatively, beginning with EDF 1.3, you can provide a percentage value to this field indicating the amount of the foreground sprite that is blended with the background. A percentage value must be a base 10 integer between 0 and 100, with the final digit followed immediately by a '%' character (percent sign).

:Note this effect is mutually exclusive of BOOM-style translucency. If this value is not 65536 (or 100%), and the BOOM translucency flag is turned on for the same thing type, the flag will be turned off at run-time, and this field will take precedence.

*'''translation'''
:Default = 0
:Sets a translation for the thing's sprite. Translation tables are 256-byte lumps which can be used to remap any range of colors in a sprite. When this field defaults, no translation will be used. Otherwise, you may either provide a number to access one of the internal player translation tables, or you may provide the name of a translation lump, which must be found either inside the '''translations''' folder inside a [[PKE]], or between T_START and T_END markers inside a [[Doom Wiki:WAD|wad]]. Numeric values for player translations are as follows. All of the player translations remap the pure green range:
:*1: indigo
:*2: brown
:*3: red
:*4: tomato
:*5: dirt
:*6: blue
:*7: gold
:*8: sea
:*9: black
:*10: purple
:*11: orange
:*12: pink
:*13: cream
:*14: white

*'''tranmap'''
:Default: not used
:This is a [[translucency map]] lump name to use to render the thing. NOTE: it should NOT be between T_START and T_END. Useful if you want custom translucency effects, not easily available with simple parameterized means.

*'''skinsprite'''
:Default = "noskin"
:The skinsprite field defines a sprite that will be used to override the sprite value in any frame a thing of this type enters. This allows the creation of thingtypes which behave identically but look different without the creation of any new frames. Note that when things are crushed into gibs, the skinsprite is cleared at that time. If an Archvile resurrects such a thing, the proper skinsprite is then restored.
:NOTE: for any use of '''skinsprite''', you need to add the sprite to the '''spritenames''' list, e.g. <code>spritenames += { SPRT }</code> (for a sprite named <code>SPRT</code>)
*'''defaultsprite'''
:Default = the object's first spawn state's sprite
:Controls the remapping behavior of skins for objects that use more than one sprite. Any frame not using the defaultsprite is ignored for remapping by the skin. If not set, the defaultsprite is adapted from the object's first spawn state.
*'''alphavelocity'''
:Default = 0.0
:If nonzero, the thing's opacity (alpha value) will raise up to full solidity, or lower to full invisibility, depending on '''alphavelocity''''s sign and quantity per tic. If the '''CYCLEALPHA''' [[Thing type flags|flag]] is set, the thing will cycle between visibility and invisibility with this speed.
*'''xscale'''
:Default = 1.0
:Sets how much the horizontal component of the sprite is to be scaled.
*'''yscale'''
:Default = 1.0
:Sets how much the vertical component of the sprite is to be scaled.

*'''trail.type'''
:If specified, is the thing type of trail to spawn when moving as a '''RavenFast''' projectile.

*'''trail.zoffset'''
:Default = -8.0
:Vertical offset where to spawn the trail object.

*'''trail.spawnchance'''
:Default = 256
:Chance out of 256 to spawn a trail object.

*'''trail.sparsity'''
:Default = 0
: How sparsely to spawn the trail objects. Be careful that this uses the counter of 0 (commonly used in frame scripting [[codepointers]]). 1 or less means all the time, larger values reduce the amount of sparkles.

====Pick-up effect====
*'''pickupeffect'''
:You can define the details of an item with the '''SPECIAL''' [[Thing type flags|flag]] in this block. See the [[pickupeffect|standalone block definition]] for explanation of the available fields.
*'''clearpickupeffect'''
:If added, it will clear the previous '''pickupeffect''' definition from an inherited '''thingtype''' or when using a '''thingdelta'''. By default it will be copied.

====ACS Spawn Data Sub-Block====
*'''acs_spawndata'''
:Default = (nothing)
:This specifies the identification number for various parameterized specials, such as [[Thing_Spawn]] or [[Thing_SpawnNoFog]]. It also limits the number to a game namespace. For example, by default the Zombieman has
acs_spawndata { num 4; modes doom }
:Heretic objects will use '''modes heretic''' instead of '''modes doom'''. To make it work for any game mode, use '''modes all''' or simply omit it. You shouldn't need to use '''modes''' in any custom mod unless it's available for more than one game.
:'''num''' must be between 0 and 255 inclusive.
[[category:EDF]]

==References==
This document has content from:
*New Bifrost features, on Eternity website: http://eternity.mancubus.net/text/bifrost_docs.txt
*Old documentation

List of console commands and variables

2025-08-23T16:22:42Z

Printz: /* Console variables */

Console commands carry out a particular action when sent to the console.
:''Back to [[Console]]''
==Console commands==
Console commands are executed, they don't inherently store values to be checked.
===Flags===
Console commands have flags assigned to them, which alter their usability. They are:
*buffered: wait until all screen has rendered before running command.
*hidden: not showing when running cmdlist.
*level: only runnable during levels.
*netvar: under multiplayer, synchronizes with the other players.
*notnet: forbidden in multiplayer (unless during a demo).
*server: if under multiplayer, only triggerable by the "server" player.
===Categories===
The commands can be grouped by their purpose:
*Control: general game control.
*Core: main console stuff, such as "echo" or "delay".
*I/O: input/output setup.
*Information: purely informative commands. Can be executed any time as they don't affect the game.
*Logging: special console logging commands.
*Menu: commands that show various menus, as well as a few commands with actual effects, which depend on the current menu state, and can't be run standalone.
*Testing: gameplay testing and "cheating" commands.
===List of console commands===
{|class="wikitable sortable"
! Name
! Parameters
! Flags
! Category
! Description
|-
||'''addfile'''||''wadfilename''||buffered notnet||Control||Adds the specified wad file at run-time. Some features will not function completely as expected when WADs are loaded at run-time, so for maximum compatibility always use the command line to load files.
|-
||'''alias'''||''newcmdname'' ''command''||||Core||'''alias''' alone will list all currently defined aliases. Providing ''newcmdname'' alone will remove that alias if it exists. Providing ''newcmdname'' and a valid console ''command'' will create "newcmdname" as an alias to that command, allowing shortcuts.

In order to make an alias take parameters, use the special variable "%opt", as such:
alias "mycommand" "hu_overlay %opt"
|-
||'''animshot'''||''numframes''||||Control||Takes the given number of consecutive screenshots for the purpose of making a crude animation. Would be useful for animated GIFs or AVI movies. This command will make the game run very slow, however, and will eat up disk space quickly, so use it with care.
|-
||'''banish'''||||level notnet||Testing||If the player is autoaiming at an enemy, the enemy will be removed from the play simulation and its memory will be freed once no other objects reference it.
|-
||'''bind'''||''keyname'' ''actionname''||||I/O||Binds the specified action to the specified key. actionname is a string and should be enclosed in quotes if it contains whitespace. actionname may specify any valid action or console command. If "actionname" is not provided, the current binding status of the specified key will be displayed.
|-
||'''bindings'''||||||Information||Dumps a list of all active keybindings to the console.
|-
||'''buddha'''||||level notnet||Testing||Toggles "Buddha" mode, where you can take any amount of damage without dying.
|-
||'''c_popup'''||||||Core||Instantly removes the console from view.
|-
||'''closelog'''||||||Logging||Closes a console log opened by the '''openlog''' command. If no logging is currently occuring, this command does nothing. This command doesn't apply to files used by '''dumplog''', as they are closed immediately, so it doesn't need to be used with the '''dumplog''' command.
|-
||'''cmdlist'''||''filter''||||Core||Displays all user-visible console commands, one per line. As of Eternity Engine v3.31 Delta, this command accepts an optional ''filter'' parameter that, if provided, should consist of a single character between A and Z. The character will be used to filter the command list down to only commands beginning with that letter.
|-
||'''creator'''||||||Information||Displays the name of the creator as set in [[EMAPINFO]].
|-
||'''credits'''||||||Menu||Displays game engine / game credits.
|-
||'''cvarhelp'''||''variablename''||||Core||Outputs a list of possible values for the given variable.
|-
||'''delay'''||''amt''||||Core||Delays the running of the next console command by either 1, or if provided, by ''amt'' game tics.
|-
||'''defdmflags'''||''mode''||server||Control||Sets the deathmatch flags variable to its default settings. If no argument is provided, dmflags is set to the default for the current game type. Otherwise, the "mode" parameter indicates what game mode's defaults to set, with the following values:

*0 = Single-player mode
*1 = Cooperative mode
*2 = Deathmatch mode
*3 = Altdeath mode (deathmatch 2.0, items respawn)
*4 = Trideath mode (DM 3, barrels respawn, players drop backpacks)
|-
||'''dir'''||||||Information||Lists the contents of the current working directory to the console.
|-
||'''dumplog'''||''filename''||||Logging||Dumps the current state of the console message buffer to the specified file as ASCII text. The text will be appended to the file if it already exists, allowing multiple use of a single log file.
|-
||'''e_dumpitemeffect'''||''mnemonic''||||Information||Displays the properties of an item effect metatable.
|-
||'''e_dumpitems'''||||||Information||Lists all EDF thing type mnemonics and DeHackEd/DoomEd numbers for thing types which are collectable items. Useful in conjunction with the give command.
|-
||'''e_dumpmeta'''||''mnemonic''||||Information||Displays the properties stored in the metatable for the given thingtype.
|-
||'''e_dumpstate'''||''mnemonic''||||Information||Displays information on one EDF state definition.
|-
||'''e_dumpthings'''||||||Information||Lists all EDF thing type mnemonics along with the DeHackEd numbers and doomednums of the corresponding types.
|-
||'''e_linedef'''||''recordnum''||level||Information||Lists verbose information on an ExtraData linedef record with the given numeric record number. If no such linedef is defined or no ExtraData exists for the current map, an appropriate error message will be given.
|-
||'''e_listkeyitems'''||||||Information||Lists all key-type artifact definitions.
|-
||'''e_listlinedefs'''||||level||Information||Lists all linedef definitions from the current map's ExtraData. If no linedefs are defined or no ExtraData exists for the current map, an appropriate error message will be given.
|-
||'''e_listmapthings'''||||level||Information||Lists all mapthing definitions from the current map's [[ExtraData]]. If no mapthings are defined or no [[ExtraData]] exists for the current map, an appropriate error message will be given.
|-
||'''e_mapthing'''||''recordnum''||level||Information||Lists verbose information on an ExtraData mapthing record with the given numeric record number. If no such mapthing is defined or no ExtraData exists for the current map, an appropriate error message will be given.
|-
||'''e_playsound'''||''name''||||Testing||Plays an EDF sound.
|-
||'''e_thingtype'''||''thingtypename''||||Information||Lists verbose information on an EDF thingtype with the given mnemonic. If no such thingtype is defined, an error message will be given.
|-
||'''echo'''||''msg''||||Core||Echoes a string message to the console. As with all console strings, the string should be in quotes if it contains whitespace.
|-
||'''enable_lightning'''||||||Testing||Enables lightning sky effects in current level.
|-
||'''endgame'''||||notnet||Testing||Ends game and drops to console mode.
|-
||'''ev_mapsectorspecs'''||||level||Information||List out all the sector specials in use on the current map.
|-
||'''ev_mapspecials'''||||level||Information||Lists all linedef specials in current map.
|-
||'''exitlevel'''||||level netvar server||Testing||Exits the current level. Starting with EE v3.31 beta 1, this command will not allow an exit if the player is dead unless the comp_zombie variable is set to allow zombie exits.
|-
||'''flood'''||||||Testing||Writes 300 garbage characters to the console. Usefulness is of debate.
|-
||'''fly'''||||level notnet||Testing||Toggles flight mode, allowing you to fly like when having the [[Doom Wiki:Wings of Wrath|Wings of Wrath]].
|-
||'''frags'''||||||Information||Displays the current frag count for all players.
|-
||'''g_padprofile'''||''profilename''||||I/O||Runs a console script that can setup default bindings for a particular model/brand of gamepad. ''Profilename'' is the name of a lump, typically inside "gamepads/" in the Eternity's [[PKE]]. Example values (as currently in the base Eternity PKE) are:
*firestorm digital 3
*vanilla
*xbox360 keylook
*xbox360
|-
||'''give'''||''thingtypename'' ''num''||level notnet||Testing||Spawns 1, or "num" if provided, of the object with this EDF thing type name on the player and causes the player to collect it/them. If the requested thing type is not collectable, it will not be spawned. In addition, if a collectable item is not picked up by the player, it will be removed immediately.
|-
||'''GIVEARSENAL'''||||level notnet||Testing||Gives all weapons (as with IDFA).
|-
||'''GIVEKEYS'''||||level notnet||Testing||Gives all keys (as with IDK).
|-
||'''god'''||||level notnet||Testing||Toggles god mode (IDDQD) on or off.
|-
||'''help'''||||||Menu||Displays built-in and user-provided help screens. See the BOOM editing reference on how to provide up to 99 custom help screens.
|-
||'''i_error'''||...||||Testing||Exits Eternity with error. Prints any arguments provided as a single string when the game exits.
|-
||'''i_exitwithmessage'''||...||||Testing||Causes a non-error exit with message.
|-
||'''i_fatalerror'''||...||||Testing||Exits Eternity with error. Prints any arguments provided as a single string when the game exits.
|-
||'''i_joystick'''||''num''||||I/O||Selects the gamepad configured in ''num'', if it can be found.
|-
||'''infammo'''||||level notnet||Testing||Toggles infinite ammo (INFSHOTS) on or off.
|-
||'''kill'''||||level netvar||Testing||Causes the player to commit suiceide.
|-
||'''listactions'''||||||Information||Displays a list of all bindable actions, aside from console commands.
|-
||'''listkeys'''||||||Information||Displays a list of all bindable key names. Not all bindable key codes correspond to pressable keys, however. Most pressable keys have obvious names which correspond to those on the keyboard.
|-
||'''listskins'''||||||Information||Lists names of all available player skins.
|-
||'''listwads'''||||||Information||Lists all currently loaded WAD files.
|-
||'''map'''||''mapname''||netvar server||Control||Transfers game play to the given map. mapname may be the name of a WAD file to load, as well as the name of a map header itself.
Examples:
map E1M1
map w00t.wad
|-
||'''mapchecksum'''||||||Information||Displays the MD5 checksum of current level. Useful for [[EDF]] gameplay compatibility patches. Compatible with GZDoom's checksum calculation.
|-
||'''maxdisplaynum'''||||||Information||Displays the maximum index of the available displaynum.
|-
||'''mdk'''||||level notnet||Testing||Fires a tracer from the player that instantly kills any monster the player is targetting.
|-
||'''mdkbomb'''||||level notnet||Testing||As above, but fires 60 such tracers in a circle around the player.
|-
||'''mn_advkeys'''||||||Menu||Displays the advanced movement control customize menu.
|-
||'''mn_automap'''||||||Menu||Displays the automap options menu.
|-
||'''mn_automapkeys'''||||||Menu||Displays the automap keybindings menu.
|-
||'''mn_bindings||||||Menu||Displays the control customize menu.
|-
||'''mn_clearmenus'''||||||Menu||Deactivates any active menu and returns to the game
|-
||'''mn_compat'''||||||Menu||Displays the DOOM compatibility options menu.
|-
||'''mn_config'''||||||Menu||Displays the user configuration menu.
|-
||'''mn_consolekeys'''||||||Menu||Brings up the console keybindings menu.
|-
||'''mn_demos'''||||notnet||Menu||Displays the Demos menu
|-
||'''mn_dynamenu'''||''menuname''||||Menu||Brings up the EDF dynamic menu with the given mnemonic. If no such menu exists, an error message will appear in the console.
|-
||'''mn_endgame'''||||||Menu||Prompts the user to end the current game and return to the title screen.
|-
||'''mn_enemies'''||||||Menu||Displays enemy AI options menu.
|-
||'''mn_envkeys'''||||||Menu||Displays the environment keybindings menu.
|-
||'''mn_episode'''||''num''||notnet||Menu||Brings up the Doom difficulty selection menu. ''Num'' it the index of the episode after which to show the difficulty settings.
|-
||'''mn_gamepad'''||||||Menu||Brings up the gamepad menu.
|-
||'''mn_gamefuncs'''||||||Menu||Brings up the game function key bindings menu.
|-
||'''mn_gset'''||||||Menu||Brings up the game settings menu.
|-
||'''mn_hepis'''||''num''||notnet||Menu||Brings up the Heretic difficulty selection menu. ''Num'' it the index of the episode after which to show the difficulty settings.
|-
||'''mn_hud'''||||||Menu||Displays the heads-up display options menu.
|-
||'''mn_joymenu'''||||||Menu||Brings up the SDL joystick configuration menu. NOTE: This command does not exist in the DOS version of Eternity.
|-
||'''mn_load'''||''slotnum''||||Menu||Loads the save game from save slot slotnum.
|-
||'''mn_loadgame'''||||||Menu||Displays the load game menu.
|-
||'''mn_loadwad'''||||notnet||Menu||Displays the wad/file options menu.
|-
||'''mn_menukeys'''||||||Menu||Brings up the menue control keybindings menu.
|-
||'''mn_menus'''||||||Menu||Brings up the menu options menu.
|-
||'''mn_mouse'''||||||Menu||Displays the mouse options menu.
|-
||'''mn_movekeys'''||||||Menu||Displays the basic movement control customize menu.
|-
||'''mn_newgame'''||||||Menu||Displays the New Game menu or takes the player to the start map, depending on their configuration.
|-
||'''mn_old_options'''||||||Menu||Displays the vanilla Doom options menu.
|-
||'''mn_old_sound'''||||||Menu||Displays the vanilla Doom sounds menu.
|-
||'''mn_options'''||||||Menu||Displays the main options menu.
|-
||'''mn_padtest'''||||||Menu||If there's an active gamepad, brings up the testing widget.
|-
||'''mn_particle'''||||||Menu||Displays the particle effects options menu.
|-
||'''mn_player'''||||||Menu||Displays the player setup menu.
|-
||'''mn_prevmenu'''||||||Menu||Returns user to the last menu they viewed, or to the game if the present menu is the highest-most in that chain.
|-
||'''mn_quit'''||||||Menu||Displays a prompt asking the user if they want to quit.
|-
||'''mn_save'''||slot||||Menu||Saves the game. Use with caution!
|-
||'''mn_savegame'''||||||Menu||Displays the save game menu. Will not display if not in a level.
|-
||'''mn_search'''||||||Menu||Opens the menu search
|-
||'''mn_selectbank'''||||||Menu||Brings up the ADLMIDI bank selector.
|-
||'''mn_selectflat'''||||||Menu||Brings up the menu background customization menu.
|-
||'''mn_selectmusic'''||||||Menu||Brings up the music menu.
|-
||'''mn_selectwad'''||||||Menu||Brings up the wad selection dialog box. The selected wad cannot be loaded if the current gamemode is a shareware game. Flags: not in a netgame
|-
||'''mn_sound'''||||||Menu||Displays the sound options menu.
|-
||'''mn_status'''||||||Menu||Displays the status bar options menu.
|-
||'''mn_testfont'''||''fontname'' [''message'']||||Testing||Displays a widget to test a font.
|-
||'''mn_video'''||||||Menu||Displays the video options menu.
|-
||'''mn_weaponkeys'''||||||Menu||Displays the weapon control customize menu.
|-
||'''mn_weapons'''||||||Menu||Displays the weapons preferences menu
|-
||'''newgame'''||||notnet||Menu||Clears any active menus and starts a new game.
|-
||'''noclip'''||||level notnet||Testing||Toggles no clipping (IDCLIP) on or off.
|-
||'''nuke'''||||netvar level server||Testing||Kills all enemies on the level, and if there are no enemies, kills all friends on the level (equivalent to KILLEM).
|-
||'''openlog'''||''filename''||||Logging||Opens the specified file in append mode and begins writing any text printed to the console into the file. All console messages will be logged until either the '''closelog''' command is used, or the program closes. Note this log file is totally separate from any used with the "dumplog" command, which is simply for saving the current buffer. If a log file is already open, this command does nothing.
|-
||'''p_dumphubs'''||||||Information||Displays hub information (if hubs exist).
|-
||'''p_linespec'''||''name'' ''arg'' ''arg'' ''arg'' ''arg'' ''arg''||level notnet||Testing||Executes the named Eternity Engine parameterized line special with the given parameters. The line special is restricted to behaving as though it has been invoked without any linedef to reference, and thus certain effects such as sector special transfers will not occur even if specified by the special type or arguments.
|-
||'''p_testenvironment||''id1'' ''id2''||level||Testing||Alters player's sound zone to the one identified by ''id1'' and ''id2''.
|-
||'''pause'''||||server||Control||Pauses or unpauses the game.
|-
||'''playdemo'''||''demoname''||notnet||Control||Plays the given demo normally.
|-
||'''playerinfo'''||||||Information||Displays name information for all connected players.
|-
||'''puke'''||''script'' ''arg...''||notnet||Testing||Executes an [[ACS]] script. Neither activator thing nor trigger linedef are set.
|-
||'''r_changesky'''||''texturename'' [''index'']||||Testing||Changes sky to specified one in ''texturename''. If ''index'' is set, it uses the specified sky flat (if more than one).
|-
||'''quicksave'''||||||Control||Quicksaves a game. First time command is used, a slot must be chosen normally. Subsequent uses will overwrite the save in that slot.

NOTE: does nothing in network games or demos
|-
||'''quickload'''||||||Control||Quickloads a game from a previously chosen quicksave slot. NOTE: does nothing in network games or demos
|-
||'''quit'''||||||Control||Plays a random monster sound and exits the game normally, with no prompt.
|-
||'''quote'''||||||Core||Currently does nothing.
|-
||'''restartmap'''||||server netvar||Testing||Restarts current map.
|-
||'''resurrect'''||||level notnet||Testing||Raises dead player.
|-
||'''s_playmusic'''||''name''||||Testing||Plays the given lump as music, if that lump can be found in the music hash table. Only lumps listed in the internal music table, or new lumps with names beginning with "D_" in DOOM or "MUS_" in Heretic are available.
|-
||'''s_stopmusic'''||||||Testing||Stops the music.
|-
||'''say'''||''...''||netvar||Control||Sends all arguments as a single message to all players in a network game.
|-
||'''screenshot'''||||||Control||Takes a single screenshot. Bind this command to a key in order to take a shot without the console in the way.
|-
||'''skinviewer'''||||||Menu||Brings up the skin viewer menu widget.
|-
||'''snd_selectbank||||||Menu||Brings up the ADLMidi sound bank selector menu.
|-
||'''spacejump'''||||hidden notnet||Testing||Allows the player to jump any number of times in midair; useful for testing linked portals.
|-
||'''spectate_next'''||||||Control||Switches display to next player (spy mode). Only works during non-deathmatch gameplay, or during any multiplayer demo.
|-
||'''spectate_prev'''||||||Control||Switches display to previous player (spy mode). Only works during non-deathmatch gameplay, or during any multiplayer demo.
|-
||'''spectate_self'''||||||Control||Switches display to user-controlled player (back from spy mode). Only works during non-deathmatch gameplay, or during any multiplayer mode.
|-
||'''starttitle'''||||notnet||Testing||Returns the game to the title screen / demo / credits loop.
|-
||'''stopdemo'''||||notnet||Control||Stops any currently playing demo and drops to console.
|-
||'''summon'''||''thingtypename'' ''flagslist'' ''mode''||hidden level notnet||Testing||Allows spawning of things via their EDF thing type name. An EDF/BEX flag list can optionally be provided, with the flags separated by commas only. By default, this will cause the listed flags to be added to the thing along with its normal flags. By specifying the third parameter as "set" or "remove", it is possible to set the thing's flags value to only the listed flags, or to remove the listed flags if the thingtype has them set by default.

Example to spawn a friendly thing:
$ summon doomimp friend
|-
||'''thunder'''||||||Testing||Forces a thunder to occur.
|-
||'''timedemo'''||''demoname'' ''showmenu''||notnet||Control||Starts the given demo as a time demo, in which the framerate of the game can be measured. If showmenu is set to 1, a meter comparing the framerate against that of a "fast" machine will be displayed after the demo is complete. Otherwise, the framerate will be printed to the console as a number.
|-
||'''togglefullscreen'''||||buffered||I/O||Toggles between fullscreen and window, by toggling between 'w' and 'f' in the current [[geom string]].
|-
||'''unbind'''||''keyname'' ''bindingclass''||||I/O||Unbinds the specified key from any action, or from only the action in the specified class if the bindingclass parameter is specified. As of Eternity Engine v3.31 Delta, keys may have one binding from each separate binding class. Binding class numbers are displayed next to action names when using the "bind keyname" command.
|-
||'''unbindall'''||||||I/O||Releases *all* dynamic keybindings. Use with caution!
|-
||'''v_dumppatch'''||''lumpname'' ''filename'' ''fillcolor''||||Testing||Dumps a patch to a file as a PNG.
|-
||'''v_fontcolors'''||''fontname'' ''filename''||||Testing||Writes the colors of ''fontname'' to a file names ''filename''.
|-
||'''vilehit'''||||level notnet||Testing||If the player is autoaiming at an enemy, the player will perform an Arch-vile attack on that enemy.
|-
||'''viles'''||||hidden level notnet||Testing||A special command for DOOM II only. Try it and see what happens :)
|-
||'''w_masterlevels'''||[''skill'']||notnet||Menu||Shows the Master Levels menu, assuming master_levels_dir is properly configured.
|-
||'''w_playnorest'''||[''skill'']||||Control||Start playing No Rest for the Living (if available).
|-
||'''w_writelump'''||''lumpname''||||Testing||Writes a lump to a file, with the name of the lump followed by .lmp, stored in the user game path.
|-
||'''warp'''||''x'' ''y''||level notnet||Testing||Teleports player to given XY coordinates.
|-
||'''whistle'''||''thingtypename''||level notnet||Testing||If there is a live, friendly thing of the given EDF type, the first such thing found on the map will be teleported in front of the player. If the thing doesn't fit where the player is trying to teleport it, it will not be teleported. It will also not be teleported across blocking lines.
|-
||'''xl_dumpemapinfo'''||''mapname''||||Information||Displays information on a single [[EMAPINFO]] (Eternity) entry by map name.
|-
||'''xl_dumpmapinfo'''||''mapname''||||Information||Displays information on a single MAPINFO (Hexen/ZDoom) entry by map name.
|-
||'''z_dumpcore'''||||hidden||Information||Write the zone heap to a file. Useful for debugging.
|-
||'''z_print'''||||hidden||Information||Prints the zone heap. Useful for development debugging.
|}

==Console constants==
These can't be changed, and when executed, show their content as information.
{|class="wikitable sortable"
! Name
! Description
|-
||'''version'''||Eternity version number (only the major and minor components, not the subversion).
|-
||'''ver_date'''||Build date.
|-
||'''ver_time'''||Build time.
|-
||'''ver_name'''||Textual name of version.
|-
||'''opt'''||
|-
||'''rngseed'''||Show the random generator seed.
|}

==Console variables==
These items store inherent values (unlike the commands) which can be queried by simply executing the variable without a new value, and can also be changed, often with side effects to the game.
{|class="wikitable sortable"
! Name
! Type
! Limits
! Description
|-
||'''mapcolor_back'''||int||0 to 255||Colour of automap background
|-
||'''mapcolor_grid'''||int||0 to 255||Colour of grid
|-
||'''mapcolor_wall'''||int||0 to 255||Colour of normal walls
|-
||'''mapcolor_fchg'''||int||0 to 255||Colour of lines with floor height change
|-
||'''mapcolor_cchg'''||int||0 to 255||Colour of lines with ceiling height change
|-
||'''mapcolor_clsd'''||int||0 to 255||Colour of closed doors or areas
|-
||'''mapcolor_rkey'''||int||0 to 255||Colour of red key objects
|-
||'''mapcolor_bkey'''||int||0 to 255||Colour of blue key objects
|-
||'''mapcolor_ykey'''||int||0 to 255||Colour of yellow key objects
|-
||'''mapcolor_rdor'''||int||0 to 255||Colour of red doors
|-
||'''mapcolor_bdor'''||int||0 to 255||Colour of blue doors
|-
||'''mapcolor_ydor'''||int||0 to 255||Colour of yellow doors
|-
||'''mapcolor_tele'''||int||0 to 255||Colour of teleport lines
|-
||'''mapcolor_secr'''||int||0 to 255||Colour of secret sector boundaries
|-
||'''mapcolor_exit'''||int||0 to 255||Colour of exit lines
|-
||'''mapcolor_unsn'''||int||0 to 255||Colour of computer map unexplored lines
|-
||'''mapcolor_flat'''||int||0 to 255||Colour of no-height-change line seen when doing iddt
|-
||'''mapcolor_sprt'''||int||0 to 255||Colour of normal map objects when doing iddt/iddt
|-
||'''mapcolor_hair'''||int||0 to 255||Colour of map pointer
|-
||'''mapcolor_sngl'''||int||0 to 255||Colour of player arrow in single player
|-
||'''mapcolor_frnd'''||int||0 to 255||Colour of friends in iddt/iddt
|-
||'''mapcolor_prtl'''||int||0 to 255||Colour of lines from other portal layers
|-
||'''mapportal_overlay'''||bool||yes/no||
|-
||'''am_drawnodelines'''||toggle||on/off||Whether to draw node lines (and certain other internal lines not documented otherwise), for debugging
|-
||'''am_drawsegs'''||toggle||on/off||Whether to draw BSP segs, for debugging.
|-
||'''am_dynasegs_bysubsec'''||toggle||yes/no||
|-
||'''am_overlay'''||toggle||on/off||Whether automap is in overlay mode.
|-
||'''c_height'''||int||20 to 200||normal height of the console in pixels
|-
||'''c_speed'''||int||1 to 200||speed at which console descends/recedes
|-
||'''d_drawfps'''||toggle||on/off||
|-
||'''d_fastrefresh'''||toggle||on/off||
|-
||'''d_interpolate'''||toggle||on/off||
|-
||'''gl_colordepth'''||int||16 to 32||
|-
||'''gl_filter_type'''||int||0 to 1 or GL_LINEAR, GL_NEAREST||
|-
||'''gl_use_extensions'''||toggle||yes/no||
|-
||'''gl_arb_pixelbuffer'''||toggle||yes/no||
|-
||'''draw_particles'''||bool||on/off||Whether to show particle effects.
|-
||'''bloodsplattype'''||int||0 to 2 or sprites, particles, both||effect for blood splats
|-
||'''bulletpufftype'''||int||0 to 2 or sprites, particles, both||effect for bullet puffs
|-
||'''rocket_trails'''||bool||on/off||whether rockets have a smoke trail
|-
||'''grenade_trails'''||bool||on/off||whether MBF grenades have a smoke trail
|-
||'''bfg_cloud'''||bool||on/off||whether BFG projectiles have a particle cloud
|-
||'''alwaysmlook'''||bool||on/off||Whether mouse movements are always interpreted as mouse-look.
|-
||'''invertmouse'''||bool||on/off||Whether vertical mouse movements are reversed.
|-
||'''invert_padlock'''||bool||on/off||
|-
||'''sens_horiz'''||float||0 to 1024||Relative horizontal sensitivity of the mouse.
|-
||'''sens_vert'''||float||0 to 1024||Relative vertical sensitivity of the mouse.
|-
||'''sens_combined'''||int||0 to 16||Also changes '''sens_horiz''' and '''sens_vert''' with this value times 4.
|-
||'''sens_vanilla'''||toggle||yes/no||
|-
||'''weapon_hotkey_cycling'''||bool||on/off||Whether to allow a weapon key to select one from multiple weapons, as is the case with the fist/chainsaw and the two shotguns in original DOOM.
|-
||'''weapon_hotkey_holding'''||bool||on/off||Whether holding the weapon key keeps changing the current weapon, when multiple weapons are selectable from the same key.
|-
||'''turbo'''||int||10 to 400||Turbo scale factor for walking/running. Only affects current player, even in multiplayer.
|-
||'''cooldemo'''||int||0 to 2 or off, random, follow||If '''follow''' and if the level has intermission cameras, the view will move between them randomly during the demo. If '''random''', it will alternate between the "follow" mode and the chase-cam. If '''off''', demos are normal even in levels with intermission cameras.
|-
||'''shot_type'''||int||0 to 3 or bmp, pcx, tga, png||file type written when screenshots are taken
|-
||'''shot_gamma'''||bool||yes/no||whether to create gamma correct screenshots
|-
||'''textmode_startup'''||bool||on/off||If '''on''', game starts in text mode like the original DOOM. If '''off''', game starts in console mode with graphics.
|-
||'''demo_insurance'''||int||0 to 2 or off, on, "when recording"||Determines whether or not extra steps should be taken to ensure that demos will remain in sync. This should not be needed for vanilla Doom demos.
|-
||'''smooth_turning'''||bool||on/off||Whether mouse turning is smoothed by the game.
|-
||'''mouse_accel_type'''||int||0 to 3 or off, linear, choco, custom||
|-
||'''mouse_accel_threshold'''||int||0 to 1024||
|-
||'''mouse_accel_value'''||float||0 to 100||
|-
||'''mouse_vert'''||bool||on/off||Was previously '''mouse_novert'''.
|-
||'''mouse_dblc1'''||int||-1 to 2||
|-
||'''mouse_dblc2'''||int||-1 to 2||
|-
||'''map_coords'''||bool||on/off||Whether automap coordinates follow the pointer in non-follow mode, or show the player coordinates.
|-
||'''map_secret_after'''||bool||yes/no||
|-
||'''numhelpers'''||int||0 to 3||Number of helper creatures that spawn with the player.
|-
||'''autorun'''||bool||on/off||Makes the player always run, without having to hold the shift key.
|-
||'''runiswalk'''||bool||on/off||Makes it so the shift key makes the player walk if '''autorun''' is '''on'''.
|-
||'''iwad_doom_shareware'''||string||||
|-
||'''iwad_doom'''||string||||
|-
||'''iwad_ultimate_doom'''||string||||
|-
||'''iwad_doom2'''||string||||
|-
||'''iwad_bfgdoom2'''||string||||
|-
||'''iwad_tnt'''||string||||
|-
||'''iwad_plutonia'''||string||||
|-
||'''iwad_hacx'''||string||||
|-
||'''iwad_heretic_shareware'''||string||||
|-
||'''iwad_heretic'''||string||||
|-
||'''iwad_heretic_sosr'''||string||||
|-
||'''iwad_freedoom'''||string||||
|-
||'''iwad_freedoomu'''||string||||
|-
||'''iwad_freedm'''||string||||
|-
||'''pwad_id24res'''||string||||Support finding NR4TL from Doom + Doom II for GOG/Steam
|-
||'''master_levels_dir||string||||Path to the Master Levels for DOOM II WADs. Must be path to the location which contains the actual WAD files. Used when starting the Master Level menu.
|-
||'''w_norestpath'''||string||||
|-
||'''use_doom_config'''||bool||yes/no||
|-
||'''i_joysticksens'''||int||0 to 32767||**Removed in EE 4.04.00**
|-
||'''i_joyturnsens'''||float||0.0 to 100.0||
|-
||'''i_joy_deadzone_left'''||int||0 to 32767||
|-
||'''i_joy_deadzone_right'''||int||0 to 32767||
|-
||'''i_joy_deadzone_trigger'''||int||0 to 32767||
|-
||'''i_forcefeedback'''||toggle||on/off||
|-
||'''i_gamespeed'''||int||0 to 500||Changes the speed of the entire game. The value is a percentage. 100 means the normal speed. Caution: setting 0 effectively freezes the game (stops time), but fortunately the console is available even then, so you can restore it to a nonzero value. This variable is useful for testing rendering interpolation.
|-
||'''v_retrace'''||bool||yes/no||Vertical synchronization. Turn it on if the display looks like tearing in the middle when changing frames. Turn it off if you experience other problems due to it.
|-
||'''i_usemouse'''||bool||yes/no||
|-
||'''i_grabmouse'''||bool||yes/no||whether the window grabs mouse input
|-
||'''i_videomode'''||string||buffered||This is a [[geom string]]. Use it to change the video mode.
|-
||'''i_resolution'''||string||buffered||Resolution of the renderer's target (WWWWxHHHH or native). Usually it's set to '''native''', which means to just use the same resolution as in '''i_videomode''', but sometimes you may want a different resolution, such as for displaying in low-detail.
|-
||'''i_videodriverid'''||int||-1 to 1 or default, "SDL Software", "SDL GL2D"||
|-
||'''i_letterbox'''||toggle||yes/no buffered||Whether to enable letterboxing when '''i_videomode''' is set to a square tower-like aspect ratio. This flag only applies for that; it does not apply for fullscreen letter/pillarboxing of 4:3 or wider aspect ratios.
|-
||'''show_scores'''||bool||on/off||Whether to show frags when you die.
|-
||'''hu_overlayid'''||int||-1 to 1 or default, "Modern HUD", "Boom HUD"||
|-
||'''hu_overlaystyle'''||int||0 to 4 or off, "boom style", flat, distributed, graphical||
|-
||'''hu_hidesecrets'''||bool||yes/no||whether to display secrets on the HUD.
|-
||'''hu_hidestats'''||bool||yes/no||whether to display kills/items/secrets on the HUD.
|-
||'''hu_obituaries'''||bool||on/off||whether to show obituary when player dies.
|-
||'''hu_obitcolor'''||int||0 to 9||Color of obituary message
|-
||'''hu_crosshair'''||int||0 to 2 or none, cross, angle||Shape/presence of aiming crosshairs.
|-
||'''hu_crosshair_hilite'''||toggle||on/off||Whether crosshair will highlight when player is aiming at a monster or friend
|-
||'''hu_crosshair_scale'''||toggle||on/off||Whether the crosshair gets scaled. It gets saved into the '''crosshair_scale''' [[OPTIONS]] field.
|-
||'''hu_messages'''||bool||on/off||Whether to show HUD messages.
|-
||'''hu_messagealignment'''||int||0 to 2 or default, left, centered||
|-
||'''hu_messagecolor'''||int||0 to 9||Colour of HUD messages.
|-
||'''hu_messagelines'''||int||0 to 14||Number of lines of the HUD message widget.
|-
||'''hu_messagescroll'''||bool||yes/no||Whether the widget can be scrolled to see previous messages.
|-
||'''hu_messagetime'''||int||0 to 100000||Length of time messages appear.
|-
||'''hu_showtime'''||toggle||yes/no||Whether to display level time in the automap.
|-
||'''hu_showcoords'''||toggle||yes/no||Whether to display player/pointer coordinates in the automap.
|-
||'''hu_alwaysshowcoords'''||toggle||yes/no||
|-
||'''hu_timecolor'''||int||0 to 9||Colour of the time widget
|-
||'''hu_levelnamecolor'''||int||0 to 9||Colour of the level name widget
|-
||'''hu_coordscolor'''||int||0 to 9||Colour of the coordinate widget.
|-
||'''hu_restrictoverlaywidth'''||toggle||yes/no buffered||Whether to restrict the modern HUD to a 16:9 subscreen (if at 16:9 or wider aspect)
|-
||'''mn_toggleisback'''||toggle||yes/no||whether the '''menu_toggle''' keybinding action goes back one menu instead of exiting.
|-
||'''mn_background'''||string||length 8||
|-
||'''wad_directory'''||string||length 1024||user's wad directory which will be listed in the wad loading dialog
|-
||'''mn_wadname'''||string||handlerset||
|-
||'''mn_start_mapname'''||string||length 9 handlerset||Exact map header name of a map at which a new game started from the menus should begin at. If invoked from the menus, this command will immediately invoke the gamemode-dependent skill selection menu when its value is set.
|-
||'''mn_demoname'''||string||length 12||
|-
||'''startlevel'''||string||length 9 handlerset||name of first level to start new games
|-
||'''mn_favaspectratio'''||int||0 to 7 or Legacy, 5:4, 4:3, 3:2, 16:10, 5:3, WSVGA, 16:9||
|-
||'''mn_favscreentype'''||int||0 to 1 or windowed, fullscreen||
|-
||'''mn_searchstr'''||string||length 32||string to search for in menus via the '''mn_search''' command
|-
||'''mn_classic_menus'''||bool||yes/no||
|-
||'''chasecam'''||bool||on/off||Whether to have a third-person camera behind you.
|-
||'''chasecam_height'''||int||-31 to 100||Preferred height of the chasecam above player's viewheight.
|-
||'''chasecam_dist'''||int||10 to 1024||Preferred distance from chasecam to player.
|-
||'''chasecam_speed'''||int||1 to 100||Percentage of distance to target chasecam moves per gametic.
|-
||'''walkcam'''||bool||on/off notnet||Whether to control a walkcam, which lets you explore the entire level as a spectator.
|-
||'''spechits_emulation'''||int||0 to 2 or off, chocodoom, prboomplus||
|-
||'''donut_emulation'''||bool||on/off||
|-
||'''p_markunknowns'''||bool||yes/no||'''yes''': location of unknown thingtypes will be marked with EDF '''Unknown''' objects. '''no''': only messages are displayed when unknown things are used in a map.
|-
||'''wipewait'''||int||0 to 2 or never, always, demos||Whether or not the screen wipe routine blocks the main game loop
|-
||'''wipetype'''||int||0 to 2 or none, melt, fade||
|-
||'''p_lastenemyroar'''||bool||on/off||
|-
||'''secret_notification'''||bool||on/off||Whether to sound the secret found notification
|-
||'''r_numcontexts||int||0 to CPU thread count||Sets the number of render contexts. If 0 it just means the maximum.
|-
||'''r_fov'''||int||20 to 179||
|-
||'''r_showrefused'''||bool||on/off||
|-
||'''gamma'''||int||0 to 4||Gamma correction level
|-
||'''lefthanded'''||bool||right/left||whether player is left handed (flips the player weapon sprites)
|-
||'''r_blockmap'''||bool||on/off||whether to rebuild blockmaps at runtime
|-
||'''r_homflash'''||bool||on/off||whether to flash the HOM indicator or keep it red.
|-
||'''r_precache'''||bool||on/off||whether to precache graphics
|-
||'''r_showgun'''||bool||yes/no||whether to draw weapon sprites
|-
||'''r_showhom'''||bool||yes/no||whether to show the flashing HOM indicator
|-
||'''r_stretchsky'''||bool||on/off||{{deprecated}} Do not use. Skies no longer need stretching, as Eternity will just fade them to a flat colour when looking up.
|-
||'''r_swirl'''||bool||on/off||Whether to enable the swirling effect for all animated flats. Meant mainly for testing the effect; otherwise it's preferable to use [[EDF animations]].
|-
||'''r_trans'''||bool||on/off||whether general translucency is enabled
|-
||'''r_tranpct'''||int||0 to 100||general global translucency percentage
|-
||'''screensize'''||int||0 to 8 buffered||View frame size.
|-
||'''r_ptcltrans'''||int||0 to 2 or none, smooth, general||translucency type for particle effects — smoth is ZDoom-style smooth fading, and general is static, BOOM-style translucency as used in Eternity v3.29 Gamma and earlier.
|-
||'''r_columnengine'''||int||0 to 1 or normal, quad||
|-
||'''r_spanengine'''||int||0 or highprecision||
|-
||'''r_tlstyle'''||int||0 to 2 or none, boom, new||
|-
||'''r_sprprojstyle'''||int||0 to 2 or default, fast, thorough||
|-
||'''r_boomcolormaps'''||toggle||on/off||If '''on''', causes all sectors with colormaps to apply the Boom-like logic of changing player's full colormap instead of using it locally. This is mainly for compatibility. See also '''sector-colormap''' in [[EMAPINFO]] for level-based options on how to customize this behaviour.
|-
||'''r_drawplayersprites'''||toggle||on/off||
|-
||'''r_centerfire'''||toggle||on/off||Whether to centre the weapon sprites when firing, like in GZDoom. Can also be saved in [[OPTIONS]].
|-
||'''displaynum'''||int||0 to number of displays||
|-
||'''snd_card'''||int||-1 to 1 or "SDL mixer", none, "PC Speaker"||type of sound driver to be used by SDL
|-
||'''mus_card'''||int||-1 to 0 or "SDL mixer", none||MIDI driver used by SDL
|-
||'''detect_voices'''||int||0 to 1 or yes, no||Unused.
|-
||'''snd_spcpreamp'''||int||1 to 6||amplification factor for SPC music
|-
||'''snd_spcbassboost'''||int||0 to 31||logarithmic bass boost scale for SPC music
|-
||'''snd_mididevice'''||int||-1 to 0 or Default, ADLMIDI||
|-
||'''snd_numchips'''||int||1 to 8||
|-
||'''snd_bank'''||int||0 to bank count||
|-
||'''snd_oplemulator'''||int||0 to 4 or "Nuked 1.8", "Nuked 1.7.4", Dosbox, Opal, Java||
|-
||'''s_lowfreq'''||float||minimum 0||
|-
||'''s_highfreq'''||float||minimum 0||
|-
||'''s_eqpreamp'''||float||0 to 1||
|-
||'''s_lowgain'''||float||0 to 3||
|-
||'''s_midgain'''||float||0 to 3||
|-
||'''s_highgain'''||float||0 to 3||
|-
||'''i_ledsoff'''||bool||yes/no||Whether to keep keyboard LEDs off regardless of lock states.
|-
||'''i_waitatexit'''||bool||yes/no||whether game will wait for input after exiting ('''yes'''), or shut down immediately ('''no''').
|-
||'''i_showendoom'''||bool||yes/no||whether to show ENDOOM on exit.
|-
||'''i_endoomdelay'''||int||35 to 3500||how long is ENDOOM shown
|-
||'''com'''||int||1 to 4||COM port to use for serial connections
|-
||'''ammo_red'''||int||0 to 100||ammo amount at which status bar numbers turn red
|-
||'''ammo_yellow'''||int||0 to 100||ammo amount at which status bar numbers turn yellow
|-
||'''health_red'''||int||0 to 200||health amount at which status bar numbers turn red
|-
||'''health_yellow'''||int||0 to 200||health amount at which status bar numbers turn yellow
|-
||'''health_green'''||int||0 to 200||health amount at which status bar numbers turn green
|-
||'''armor_red'''||int||0 to 200||armor amount at which status bar numbers turn red
|-
||'''armor_yellow'''||int||0 to 200||armor amount at which status bar numbers turn yellow
|-
||'''armor_green'''||int||0 to 200||armor amount at which status bar numbers turn green
|-
||'''armor_byclass'''||toggle||yes/no||
|-
||'''st_graypct'''||bool||yes/no||whether to keep % sign grey or to make it change colour with the numbers (if that's enabled).
|-
||'''st_rednum'''||bool||yes/no||whether status bar numbers are always red, or coloured like in Boom.
|-
||'''st_singlekey'''||bool||yes/no||Whether to show just the skull keys when both are picked, like in vanilla Doom.
|-
||'''st_fsalpha'''||int||0 to 100||
|-
||'''s_enviro_volume'''||int||0 to 16||
|-
||'''s_precache'''||bool||on/off||whether to precache sounds at the beginning of the game
|-
||'''s_pitched'''||bool||on/off||whether to have variable pitched sounds like in old Doom and new Doom re-releases.
|-
||'''snd_channels'''||int||1 to 32||number of software sound channels to maintain.
|-
||'''sfx_volume'''||int||0 to 15||base volume for digital sound effects
|-
||'''music_volume'''||int||0 to 15||base volume for MIDI synthesis
|-
||'''s_flippan'''||bool||on/off||whether to reverse stereo channels
|-
||'''s_hidefmusic'''||bool||on/off||
|-
||'''s_randmusic'''||toggle||on/off||
|-
||'''v_ticker'''||int||0 to 3 or off, chart, classic, text||FPS ticker display
|-
||'''bobbing'''||bool||on/off netvar||'''on''': players see themselves bob about like chickens. '''off''': players see themselves scoot around like robots on wheels.
|-
||'''name'''||string||length 20 netvar||Name of player.
|-
||'''dogjumping'''||bool||on/off netvar||
|-
||'''dmflags'''||int||minimum 0 netvar||deathmatch flags bitmask -- add the values below together to set individual flags; values are as follows:
* 1 (0x1): items respawn
* 2 (0x2): weapons stay
* 4 (0x4): barrels respawn
* 8 (0x8): players drop backpacks
* 16 (0x10): super powerups respawn
* 32 (0x20): instagib, any damage gibs players
* 64 (0x40): keep items when player respawns
|-
||'''colour'''||int||netvar 0 to 14 or green, indigo, brown, red, tomato, dirt, blue, gold, sea, black, purple, orange, pink, cream, white||Player's uniform color.
|-
||'''gametype'''||int||netvar 0 to 2 or single, coop, deathmatch||determines rules used for gameplay; cannot set single if more than one player is present
|-
||'''skill'''||int||netvar 0 to 4 or "im too young to die", "hey not too rough", "hurt me plenty", "ultra violence", "nightmare"||game skill level
|-
||'''allowmlook'''||bool||on/off netvar||Whether to allow looking up and down.
|-
||'''bfgtype'''||int||netvar 0 to 4 or bfg9000, "press release", bfg11k, bouncing, "plasma burst"||Choose between one of the various port-implemented BFG variants.
|-
||'''autoaim'''||bool||on/off netvar||Autoaim enabled.
|-
||'''recoil'''||bool||on/off netvar||Boom-style recoil enabled.
|-
||'''pushers'''||bool||on/off netvar||Whether objects are affected by wind and current.
|-
||'''varfriction'''||bool||on/off netvar||Whether players (and possibly monsters) experience variable friction.
|-
||'''nukage'''||bool||on/off netvar||Whether damaging sectors hurt players as normal.
|-
||'''p_pitchedflight'''||toggle||on/off netvar||Whether flying in a pitched direction follows that direction (unlike vanilla Heretic).
|-
||'''timelimit'''||int||0 to 100 netvar||Time limit for deathmatch.
|-
||'''fraglimit'''||int||0 to 100 netvar||Frag limit for deathmatch.
|-
||'''fast'''||toggle||on/off netvar||Fast monsters.
|-
||'''nomonsters'''||toggle||on/off netvar||No monsters spawned.
|-
||'''respawn'''||toggle||on/off netvar||Respawning enabled.
|-
||'''mon_remember'''||bool||on/off netvar||Monsters remember target.
|-
||'''mon_infight'''||bool||on/off netvar||Monster infighting.
|-
||'''mon_backing'''||bool||on/off netvar||Monsters backing out from melee attackers.
|-
||'''mon_avoid'''||bool||on/off netvar||Monsters avoiding hazards such as crushing ceilings.
|-
||'''mon_friction'''||bool||on/off netvar||Monsters affected by friction.
|-
||'''mon_climb'''||bool||on/off netvar||Monsters can walk steep stairs.
|-
||'''mon_helpfriends'''||bool||on/off netvar||
|-
||'''mon_distfriend'''||int||0 to 1024 netvar||Distance friends stay away.
|-
||'''skin'''||string||length 256 netvar||Player skin setting.
|-
||'''comp_*'''||bool||on/off netvar||These are the various compatibility options. See the equivalent '''comp_*''' fields from the [[OPTIONS]] lump for a full list of variables.
|}

[[category:console]]

SetLineActivation

2025-08-23T16:21:49Z

Printz:

{{ACSFunction|
description=Modifies a line's activation type, if it has a special set: who can activate it, from which side, whether it is repeatable.
|usage=''void'' '''SetLineActivation'''(''int lineid'', ''int activation''[, ''int repeat''])
|parameters=
*''lineid'': ID (tag) of line to modify
*''activation'': activation type. Can be:
**'''SPAC_None''' or 0: disable the activation
**a combination (sum or OR-operation) of the following:
***'''SPAC_Cross''' (1): on player crossing
***'''SPAC_Use''' (2): on player using from first side
***'''SPAC_MCross''' (4): on monster crossing
***'''SPAC_Impact''' (8): on player or monster shooting bullets (hitscans) on line
***'''SPAC_Push''' (16): on player bumping into line
***'''SPAC_PCross''' (32): on projectile crossing line
***'''SPAC_UseThrough''' (64): when player uses it from front side + allow 'passthru' effect
***'''SPAC_AnyCross''' (128): when any of player, monster, projectile or polyobject crosses it
***'''SPAC_MUse''' (256): when monster uses it from front side
***'''SPAC_MPush''' (512): when monster bumps into line
***'''SPAC_UseBack''' (1024): allow using from back side
*''repeat'': if greater than 0, then it allows the activation to be repeated. Otherwise, if 0, it removed the "repeatable" attribute.
|id=-76}}

SetLineActivation

2025-08-23T16:21:11Z

Printz: Created page with "{{ACSFunction| description=Modifies a line's activation type, if it has a special set: who can activate it, from which side, whether it is repeatable. |usage=''void'' '''SetLineActivation'''(''int lineid'', ''int activation''[, ''int repeat'']) |parameters= *''lineid'': ID (tag) of line to modify *''activation'': activation type. Can be: **'''SPAC_None''' or 0: disable the activation **a combination (sum or OR-operation) of the following: ***'''SPAC_Cross''' (1): on play..."

ACS built-in functions

2025-08-23T16:13:33Z

Printz: /* Linedefs and sidedefs */

These are predefined ACS functions with no [[parameterized linedef specials|parameterized linedef special]] equivalents, accessible only through ACS scripts.

NOTE: most of these functions are meant to be compatible with those from ZDoom. For any ones not yet documented on this wiki, you can check the ZDoom wiki. A few of them may be incompletely implemented in Eternity. Don't hesitate to update the wiki in case of any mistakes.
==Special TID info==
For functions affecting things, some TIDs (thing tags) carry special meaning. TID 0 means the activator, and TIDs -1 ... -4 mean each of the four players in the game -- this is an Eternity extension
==Data type info==
You may see specifiers such as ''void'', ''str'', ''int'' and others in ACS function signatures. They act as a guide on what kinds of values are expected, but in ACS there really are only two types: '''str''' and '''int''' (and '''str''' internally is merely a string ID number). Most importantly:
*''void'' means that a function should be used as a procedure (command) without returning anything,
*''fixed'' means you can use the decimal point notation: 1.0 is equivalent to 65536, 1.5 to 98304 etc. In ACS, such values are still of '''int''' type, but whether you use the decimal point or not is quite relevant. A value such as 128.0 is ''not'' the same as 128: it's actually equal to 8388608 (no decimal point).
==Function list==
===Sound and music===
*[[ActivatorSound]]
*[[AmbientSound]]
*[[LocalAmbientSound]]
*[[PlayActorSound]]
*[[PlaySound]]
*[[SectorSound]]
*[[SetMusic]]
*[[LocalSetMusic]]
*[[SoundSequence]]
*[[SoundSequenceOnActor]]
*[[StopSound]]
*[[ThingSound]]

===Sectors===
{|class="wikitable sortable
! Name
! Description
|-
||[[ChangeCeiling]]||Changes the ceiling texture.
|-
||[[ChangeFloor]]||Changes the floor texture.
|-
||[[GetSectorCeilingZ]]||Gets the ceiling height.
|-
||[[GetSectorFloorZ]]||Gets the floor height.
|-
||[[GetSectorLightLevel]]||Gets the light level.
|-
||[[SectorDamage]]||Damages things in sector.
|-
||[[SetSectorDamage]]||Modifies the damaging floor status.
|-
||[[TagWait]]||Waits for sectors to stop movement.
|}

===Things===
*[[ActivatorTID]]
*[[ChangeActorAngle]]
*[[ChangeActorPitch]]
*[[CheckActorCeilingTexture]]
*[[CheckActorClass]]
*[[CheckActorFloorTexture]]
*[[CheckActorProperty]]
*bool [[CheckFlag]](int tid, str flag)
:Returns true if the first thing with the given tid has the given flag enabled.
*[[CheckProximity]]
*bool CheckSight(int source, int dest, int flags)
:Returns true if there's a line of sight between at least one thing tagged as source and one thing tagged as dest. Currently flags is reserved and must be 0.
*int [[ClassifyActor]](int tid)
:Checks the kind of thing tagged tid. It returns a set of flags, possibly combined:
:*ACTOR_PLAYER (2): it's player-controlled
:*ACTOR_VOODOODOLL (8): it's a duplicate player start, not controlled by the player but still linked to it. Used in Boom maps for advanced mapping tricks
:*ACTOR_MONSTER (16): it's a monster (has COUNTKILL or KILLABLE thing type flag set)
:*ACTOR_MISSILE (128): it's a projectile in flight (has MISSILE thing type flag set)
:*ACTOR_GENERIC (256): neither a monster, nor a projectile
:*ACTOR_ALIVE (32): has positive health
:*ACTOR_DEAD (64): has health <= 0
:*ACTOR_NONE (0): no thing found with this TID
:*ACTOR_WORLD (1): TID is 0 but activator isn't a thing
*[[GetActorAngle]]
*[[GetActorCeilingZ]]
*[[GetActorFloorZ]]
*[[GetActorLightLevel]]
*[[GetActorPitch]]
*[[GetActorProperty]]
*[[GetActorVelX]]
*[[GetActorVelY]]
*[[GetActorVelZ]]
*[[GetActorX]]
*[[GetActorY]]
*[[GetActorZ]]
*[[IsTIDUsed]]
*[[SetActivator]]
*[[SetActivatorToTarget]]
*void SetActorAngle (int tid, fixed angle)
*[[SetActorVelocity]]
*void SetActorPitch (int tid, int pitch)
*[[SetActorPosition]]
*void SetThingSpecial (int tid, int special [, int arg0 [, int arg1 [, int arg2 [, int arg3 [, int arg4]]]]])
*int SetActorState(int tid, str statename[, bool exact]);
*[[SetActorProperty]]
*int Spawn (str classname, fixed x, fixed y, fixed z [, int tid [, int angle]])
*int SpawnForced (str classname, fixed x, fixed y, fixed z [, int tid [, int angle]])
*[[SpawnProjectile]]
*[[SpawnSpot]]
*int SpawnSpotFacing (str classname, int spottid [, int tid])
*[[SpawnSpotFacingForced]]
*[[SpawnSpotForced]]
*int ThingCount (int type, int tid)
*int ThingCountName (str classname, int tid)
*int ThingCountSector (int type, int tid, int tag)
*int ThingCountNameSector (str classname, int tid, int tag)
*int Thing_Damage2 (int tid, int amount, str type);
*void Thing_Projectile2 (int tid, int type, int angle, int speed, int vspeed, int gravity, int newtid)
*int UniqueTID ([int tid[, int limit]])

===Player===
*[[CheckInventory]]
*[[CheckWeapon]]
*[[GetWeapon]]
*[[GetSigilPieces]]
*[[PlayerArmorPoints]]
*[[PlayerCount]]
*[[PlayerFrags]]
*[[PlayerHealth]]
*[[PlayerNumber]]
*[[SetWeapon]]
*[[TakeInventory]]

===Linedefs and sidedefs===
{|class="wikitable sortable"
! zspecial.acs index
! Name
! Return type
! Parameters
! Description
|-
||internal|| [[ClearLineSpecial]] || nothing || nothing || Clears the trigger linedef's special.
|-
|| || [[GetLineRowOffset]] || || ||
|-
|| || [[GetLineX]] || || ||
|-
|| || [[GetLineY]] || || ||
|-
|| || [[LineSide]] || || ||
|-
|| || [[ReplaceTextures]] || nothing || str old_texture_name, str new_texture_name[, int flags] ||
|-
|| || [[SetLineBlocking]] || || ||
|-
||internal|| [[SetLineMonsterBlocking]] || || || Makes a linedef block or not block monsters.
|-
|| || [[SetLineActivation]] || nothing || int lineid, int activation[, int repeat] ||
|-
|| || [[SetLineSpecial]] || || ||
|-
|| || [[SetLineTexture]] || nothing || int line_id, int line_side, int sidedef_texture, str texture_name ||
|}

===Sky===
*[[SetSkyScrollSpeed]]

===Scripts===
*bool ACS_NamedExecuteAlways(str script, int map, int arg1, int arg2, int arg3)
:*Executes a named script, starting a new instance if one already exists. Returns true if successfully started.
*bool ACS_NamedExecute(str script, int map, int arg1, int arg2, int arg3)
:*Executes a named script. Returns true if successfully started.
*int ACS_NamedExecuteWithResult (string script, int s_arg1, int s_arg2, int s_arg3, int s_arg4)
*bool ACS_NamedSuspend (string script, int map)
*bool ACS_NamedTerminate (string script, int map)

===Console===
*int [[GetCVar]] (str cvar)
*string [[GetCVarString]] (str cvar)
*int GetPlayerInput (int player, int input)

===Polyobjects===
*[[GetPolyobjX]]
*[[GetPolyobjY]]
*[[PolyWait]]

===Quake===
*[[Radius_Quake2]]

===Math===
*[[Cos]]
*fixed [[FixedSqrt]] (fixed number)
*int [[Random]] (int min, int max)
*int [[Sqrt]] (int number)
*[[Sin]]
*[[VectorAngle]]
*int [[VectorLength]] (int x, int y)

===Strings===
*str StrLeft (str string, int length)
*str StrMid (str string, int start, int length)
*str StrRight (str string, int length)

===Level state===
*[[GameSkill]]
*[[GameType]]
*[[GetLevelInfo]]
*[[SetAirControl]]
*[[SetAirFriction]]
*[[SetGravity]]
*[[SinglePlayer]]
*[[Timer]]

==See also==
*[[Parameterized linedef specials]]

[[Category:ACS]]
[[Category:Editing reference]]

ThrustThing

2025-08-23T16:11:56Z

Printz:

72:'''ThrustThing'''(''angle'', ''speed'', ''nolimit'', ''tid'')

Pushes a thing or more in a horizontal direction.

==Arguments==
*''angle'': [[byte angle]] of direction to push things by.
*''speed'': starting speed by which to push things.
*''nolimit'': if 1, it will allow thrusting at speeds greater than the usual limit in DOOM of plasma projectiles. Otherwise, if 0, the velocity will be capped.
*''tid'': [[TID]] optional tag of things to push. As usual, 0 means activator.

==Remarks==
In Hexen, from where this special was inherited, it can only be triggered from the front side. In Eternity however it can be triggered from any side, unless you set a [[UDMF]] or [[ExtraData]] flag to limit activation from front side.

See also [[ThrustThingZ]] for vertical thrusting.