Eternity Wiki - Recent changes [en]

List of maps and mods made for Eternity

Printz — Mon, 06 Jul 2026 04:32:53 GMT

← Older revision		Revision as of 00:32, 6 July 2026
Line 22:		Line 22:
	\|\|[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/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/idgames/levels/doom2/Ports/d-f/eovr An ~~eternity~~ of /vr/]\|\| \|\|		\|\|[https://www.doomworld.com/idgames/levels/doom2/Ports/d-f/eovr An Eternity of /vr/]\|\|various \|\|See also [https://www.doomworld.com/forum/topic/159090-my-first-eternity-map-a-familiar-place/ “A familiar place”]
	\|-		\|-
	\|\|[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/120175-heartland-an-episode-for-the-eternity-engine-rc2-out-lots-of-bugfixes/ Heartland] \|\| [[Doom Wiki:skillsaw\|skillsaw]] \|\|

List of maps and mods made for Eternity

86.120.13.199 — Mon, 06 Jul 2026 04:29:55 GMT

Maps

← Older revision		Revision as of 00:29, 6 July 2026
Line 21:		Line 21:
	\|-		\|-
	\|\|[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/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/idgames/levels/doom2/Ports/d-f/eovr An eternity of /vr/]\|\| \|\|
	\|-		\|-
	\|\|[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/120175-heartland-an-episode-for-the-eternity-engine-rc2-out-lots-of-bugfixes/ Heartland] \|\| [[Doom Wiki:skillsaw\|skillsaw]] \|\|

Polyobject

Printz — Sun, 14 Jun 2026 14:12:31 GMT

Polyobjects with 2-sided lines

← Older revision		Revision as of 10:12, 14 June 2026
Line 218:		Line 218:
	# Textures will retain their initial Y offset when the line moves across different sector elevations. Previously in Hexen they would always make sure the Y offset agrees to the current sectors where they're located.		# Textures will retain their initial Y offset when the line moves across different sector elevations. Previously in Hexen they would always make sure the Y offset agrees to the current sectors where they're located.
	# No more collision detection influenced by the source control sector. Previously in Hexen you would need to match the height of the control sector with the one of the game sector. Normally this wasn't an issue, because of the subsector restriction, which no longer exists in Eternity.		# No more collision detection influenced by the source control sector. Previously in Hexen you would need to match the height of the control sector with the one of the game sector. Normally this wasn't an issue, because of the subsector restriction, which no longer exists in Eternity.
			# 2-sided lines with actions will also trigger if actor stands still and is crossed by the polyobject.
	# 3DMidTex lines now work properly and as expected. You can use them as horizontal moving platforms.		# 3DMidTex lines now work properly and as expected. You can use them as horizontal moving platforms.
	# Impassable 2-sided lines also behave as transporters to things above if moving below sector portals.		# Impassable 2-sided lines also behave as transporters to things above if moving below sector portals.

	[[category:Editing reference]]		[[category:Editing reference]]

ExtraData

Printz — Sun, 14 Jun 2026 14:11:42 GMT

extflags

← Older revision		Revision as of 10:11, 14 June 2026
(One intermediate revision by the same user not shown)
Line 212:		Line 212:
	CLIPMIDTEX Linedef middle texture will not "bleed" on floor and ceiling.		CLIPMIDTEX Linedef middle texture will not "bleed" on floor and ceiling.
	WRAPMIDTEX Linedef middle texture of two-sided is repeated vertically instead of being drawn only once.		WRAPMIDTEX Linedef middle texture of two-sided is repeated vertically instead of being drawn only once.
			3DMTPASSPROJ Linedef will always let projectiles pass even if marked as 3DMidTex
	LOWERPORTAL Linedef copies floor portal from its backside to its lower visible edge		LOWERPORTAL Linedef copies floor portal from its backside to its lower visible edge
	UPPERPORTAL Linedef copies ceiling portal from its backside to its upper visible edge		UPPERPORTAL Linedef copies ceiling portal from its backside to its upper visible edge

Thing types

Printz — Sun, 14 Jun 2026 14:08:14 GMT

New to Eternity

← Older revision		Revision as of 10:08, 14 June 2026
Line 84:		Line 84:
	:Slightly edited Lost Soul from the press release beta version of Doom.		:Slightly edited Lost Soul from the press release beta version of Doom.

	*'''EEMusicChanger (~~14101~~ - ~~14164~~)'''		*'''EEMusicChanger (14100 - 14165)'''
	:Music changer from Risen3D and PrBoom+. You place it in the map. The player who steps inside the sector with this thing will have their music changed. ~~See~~ [[Doom Wiki:MUSINFO\|MUSINFO]] in the Doom Wiki for info on how to use it. The MUSINFO lump is supported in Eternity.		:Music changer from Risen3D and PrBoom+. You place it in the map. The player who steps inside the sector with this thing will have their music changed. For 14101-14164, see [[Doom Wiki:MUSINFO\|MUSINFO]] in the Doom Wiki for info on how to use it. The MUSINFO lump is supported in Eternity. Type 14100 will reset the music to the current level music, while 14165 is the parameterized type, which will use the first argument.
	:Another way to change music at runtime is to use [[ACS]] scripting with the [[LocalSetMusic]] function.		:Another way to change music at runtime is to use [[ACS]] scripting with the [[LocalSetMusic]] function.
	===Sector actions===		===Sector actions===

Polyobject

Printz — Sun, 14 Jun 2026 14:04:49 GMT

@@ Line 210: / Line 210: @@
 ==Polyobjects with portals==
 :See [[Linked_portals#Polyobject_portals | Polyobject portals]]
 [[category:Editing reference]]

ExtraData

Printz — Sun, 14 Jun 2026 13:56:07 GMT

extflags

← Older revision		Revision as of 09:56, 14 June 2026
Line 211:		Line 211:
	ZONEBOUNDARY Linedef will work as a reverb effect boundary. Not needed for one-sided lines.		ZONEBOUNDARY Linedef will work as a reverb effect boundary. Not needed for one-sided lines.
	CLIPMIDTEX Linedef middle texture will not "bleed" on floor and ceiling.		CLIPMIDTEX Linedef middle texture will not "bleed" on floor and ceiling.
			WRAPMIDTEX Linedef middle texture of two-sided is repeated vertically instead of being drawn only once.
	LOWERPORTAL Linedef copies floor portal from its backside to its lower visible edge		LOWERPORTAL Linedef copies floor portal from its backside to its lower visible edge
	UPPERPORTAL Linedef copies ceiling portal from its backside to its upper visible edge		UPPERPORTAL Linedef copies ceiling portal from its backside to its upper visible edge

3DMidTex tutorial

Printz — Sun, 14 Jun 2026 13:54:55 GMT

← Older revision		Revision as of 09:54, 14 June 2026
Line 45:		Line 45:

	Now that you've mastered the art of the 3D bridge, you should give [[3DMidTex advanced topics]] a try.		Now that you've mastered the art of the 3D bridge, you should give [[3DMidTex advanced topics]] a try.

			=== Wrap-midtex ===
			If the UDMF '''wrapmidtex''' or ExtraData '''WRAPMIDTEX''' flag is set, the texture will visually continue by the entire height of the area, and as such, the 3DMidTex blocking will also cover the entire area.

	==See also==		==See also==

3DMidTex advanced topics

Printz — Sun, 14 Jun 2026 13:52:57 GMT

← Older revision		Revision as of 09:52, 14 June 2026
Line 28:		Line 28:

	Now simply run the map and press on the 3DMidTex door. The door should now raise up, wait for 3 seconds, and close. If the player is caught under the door, it will now close (just like if the player was caught under a sector ceiling closing) because the link is two way. This also means that crushing ceilings will cause 3DMidTex lines to do damage to things when they are caught.		Now simply run the map and press on the 3DMidTex door. The door should now raise up, wait for 3 seconds, and close. If the player is caught under the door, it will now close (just like if the player was caught under a sector ceiling closing) because the link is two way. This also means that crushing ceilings will cause 3DMidTex lines to do damage to things when they are caught.

			==Making a polyobject 3DMidTex moving platform==
			A polyobject may be made of two-sided lines, not just one-sided walls. Such two-sided lines can be marked as 3DMidTex. Objects currently standing on top of such 3DMidTex lines will be transported when the polyobject moves. Pushing and crushing will only happen if the touched objects stand in the way of the 3dmidtex lines of the polyobject. It is also possible to move the lines vertically using the sector linking mechanism.

	==See also==		==See also==

UDMF

Printz — Sun, 14 Jun 2026 13:50:11 GMT

Linedefs

← Older revision		Revision as of 09:50, 14 June 2026
(One intermediate revision by the same user not shown)
Line 41:		Line 41:
	zoneboundary = <boolean>;		zoneboundary = <boolean>;
	clipmidtex = <boolean>;		clipmidtex = <boolean>;
			wrapmidtex = <boolean>;
	midtex3dimpassible = <boolean>;		midtex3dimpassible = <boolean>;
	lowerportal = <boolean>;		lowerportal = <boolean>;
Line 69:		Line 70:
	:Linedef acts like a boundary for [[EDF_sound_reference#Sound_environments\|reverb]] effects.		:Linedef acts like a boundary for [[EDF_sound_reference#Sound_environments\|reverb]] effects.
	*'''clipmidtex'''		*'''clipmidtex'''
	:Middle texture is clipped against the floor or ceiling as if a light change took place.		:Middle texture of two-sided line is clipped against the floor or ceiling as if a light change took place.
			*'''wrapmidtex'''
			:Middle texture of two-sided is repeated vertically instead of being drawn only once. This will make '''midtex3d''' lines also physically occupy the whole vertical space.
	*'''midtex3dimpassible'''		*'''midtex3dimpassible'''
	:Treat the 3dmidtex line as a classic impassable middle texture, with regards to projectiles (i.e. they will pass through, just like hitscans).		:Treat the 3dmidtex line as a classic impassable middle texture, with regards to projectiles (i.e. they will pass through, just like hitscans).
Line 94:		Line 97:
	offsetx_bottom = <floating-point>;		offsetx_bottom = <floating-point>;
	offsety_bottom = <floating-point>;		offsety_bottom = <floating-point>;

			scalex_top = <floating-point>;
			scaley_top = <floating-point>;
			scalex_mid = <floating-point>;
			scaley_mid = <floating-point>;
			scalex_bottom = <floating-point>;
			scaley_bottom = <floating-point>;

	light = <integer>;		light = <integer>;
Line 114:		Line 124:
	*'''offsetx_top''', '''offsety_top''', '''offsetx_mid''', '''offsety_mid''', '''offsetx_bottom''', '''offsety_bottom'''		*'''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.		:Horizontal and vertical offsets for the individual top, middle, and bottom portions of this sidedef.
			*'''scalex_top''', '''scaley_top''', '''scalex_mid''', '''scaley_mid''', '''scalex_bottom''', '''scaley_bottom'''
			:Horizontal and vertical scaling of parts of the sidedef.
	*'''light''', '''light_top''', '''light_mid''', '''light_bottom''', '''lightabsolute''', '''lightabsolute_top''', '''lightabsolute_mid''', '''lightabsolute_bottom'''		*'''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.		: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.

OPTIONS

Printz — Sun, 14 Jun 2026 13:44:51 GMT

OPTIONS full listing

← Older revision		Revision as of 09:44, 14 June 2026
Line 188:		Line 188:
	[0-1(1)] Disable jumping for DOOM/Heretic *		[0-1(1)] Disable jumping for DOOM/Heretic *
	comp_aircontrol 1		comp_aircontrol 1

			[0-1(0)] MObjs are lit by transfered light *
			comp_thingsectorlight 0

	[("No")] chat string associated with 0 key *		[("No")] chat string associated with 0 key *

List of cheat codes

Printz — Sun, 14 Jun 2026 13:42:33 GMT

Eternity Cheats

← Older revision		Revision as of 09:42, 14 June 2026
Line 127:		Line 127:

	This is a master cheat which will make you all-powerful. It will turn on god mode, infinite ammo, total invisibility, and silencer effects if they are not on (it will not deactivate them if you type it again). It also gives full ammo, weapons, and armor.		This is a master cheat which will make you all-powerful. It will turn on god mode, infinite ammo, total invisibility, and silencer effects if they are not on (it will not deactivate them if you type it again). It also gives full ammo, weapons, and armor.

			===IDDKT, IDDIT, IDDST===
			These cheat codes work when automap is active, and move the cursor to the next remaining monster, item or secret which counts for the final score.

	==See also==		==See also==
	* [[List of console commands]]		* [[List of console commands]]

BFGSpray

Printz — Sun, 14 Jun 2026 13:38:41 GMT

← Older revision		Revision as of 09:38, 14 June 2026
Line 1:		Line 1:
	{{codepointer\|description=BFGSpray is a codepointer which causes a BFG explosion effect.\|usage='''BFGSpray'''(''sprayType'', ''numRays'', ''damageCount'', ''fov'', ''maxDist'')		{{codepointer\|description=BFGSpray is a codepointer which causes a BFG explosion effect.\|usage='''BFGSpray'''(''sprayType'', ''numRays'', ''damageCount'', ''fov'', ''maxDist'', ''damageMOD'')
	\|parameters=		\|parameters=
	*''sprayType'': name of thing type to spawn on hit targets. Default is the thingtype with dehackednum 43, which in Doom is BFGFlash.		*''sprayType'': name of thing type to spawn on hit targets. Default is the thingtype with dehackednum 43, which in Doom is BFGFlash.
Line 6:		Line 6:
	*''fov'': angle in degrees of the spread. Default: 90.		*''fov'': angle in degrees of the spread. Default: 90.
	*''maxDist'': range of each ray. Default: 1024.		*''maxDist'': range of each ray. Default: 1024.
			*''damageMOD'': means-of-death (damage type). Default: BFG_Splash.
	\|notes=		\|notes=
	The effect differs depending on the player's selected type of BFG:		The effect differs depending on the player's selected type of BFG:

VileAttack

Printz — Sun, 14 Jun 2026 13:37:30 GMT

← Older revision		Revision as of 09:37, 14 June 2026
Line 4:		Line 4:

	Thunk: Yes.		Thunk: Yes.

			==Optional parameters==
			Even though VileAttack is a classic Doom codepointer, it accepts the following optional arguments:
			# name of sound to play (default "barexp")
			# direct damage (default 20)
			# blast damage (default 70)
			# blast radius (default 70)
			# thrust factor (default 1.0)
			# damage type of direct hit (default: actor's MOD)
			# damage type of blast hit (default: actor's MOD)
			==See also==
			*[[VileTarget]]

VileTarget

Printz — Sun, 14 Jun 2026 13:34:42 GMT

← Older revision		Revision as of 09:34, 14 June 2026
(One intermediate revision by the same user not shown)
Line 2:		Line 2:

	Purpose: Causes the object to [[FaceTarget\|face]] its target, and spawns a VileFire object at the target's location. The [[Fire]] codepointer will be called on the VileFire object after it is spawned.		Purpose: Causes the object to [[FaceTarget\|face]] its target, and spawns a VileFire object at the target's location. The [[Fire]] codepointer will be called on the VileFire object after it is spawned.

			==Optional parameter==
			VileTarget accepts an optional parameter: thing type to spawn. If omitted, it will be the VileFire (dehackednum 5) type.
			==See also==
			*[[VileAttack]]

DEMOLOOP

Printz — Sun, 14 Jun 2026 13:07:47 GMT

Explanation of fields

@@ Line 35: / Line 35: @@
 *"metadata": required id24 information. Eternity does not consume them, but they should be provided.
 *"data": must contain a single "entries" array of one or more elements (the example above shows two entries). Each element is described below:
-:*"type": can be 0 or 1. 0 means art screen, 1 means demo (game replay).
+:*"type": can be 0 or 1. 0 means art screen, 1 means demo (game replay). Caution: demos will only replay reliably in Eternity if the they are recorded in MBF-compatible or below (Boom or vanilla Doom) ports. Do not rely on Eternity-recorded demos to stay in sync with any Eternity update.
-:*"primarylump": if "type" is 0 (art screen), this is the name of the graphics lump to display as the art screen. Eternity tolerates a missing "primarylump", in which case it will show the Eternity credits screen, but this is nonstandard and not portable. If "type" is 1 (demo), this is the name of the demo lump, and it's required.
+:*"primarylump": if "type" is 0 (art screen), this is the name of the graphics lump to display as the art screen. If "type" is 1 (demo), this is the name of the demo lump, and it's required.
 :*"outrowipe": can be 0 or 1. 0 means no screen wipe effect (e.g. melt) will occur after the end of the current stage. 1 means to apply the wipe effect.
 :*"secondarylump": only applies if "type" is 0 (art screen). This is optional and will be the lump name of the music to play during the display of the art screen. Eternity allows omitting the game-specific prefix such as "D_" on Doom; for example both "runnin" and "D_RUNNIN" are valid for Doom 2. The name is case insensitive. Completely omitting "secondarylump" will just keep playing the music from the previous stage. Demos don't use this option because the levels they replay have their own music.
 :*"duration": only applies when "type" is 0 (art screen). This is time in seconds that the art screen will display before going to the next stage. It can be expressed in decimal quantities. It should be set for every entry of "type" 0.

EDF game properties reference

Printz — Sun, 14 Jun 2026 13:03:16 GMT

Demo control

← Older revision		Revision as of 09:03, 14 June 2026
Line 132:		Line 132:
	All other missions have 0 flags.		All other missions have 0 flags.
	===Demo control===		===Demo control===
			NOTE: for finer control of the title and demo sequence, you can instead use a [[DEMOLOOP]] lump.
	*'''demo.titletics'''		*'''demo.titletics'''
	:Time to show the title screen. Defaults: 170 (Doom I), 385 (Doom II), 210 (Heretic).		:Time to show the title screen. Defaults: 170 (Doom I), 385 (Doom II), 210 (Heretic).
Line 138:		Line 139:
	*'''demo.pagetics'''		*'''demo.pagetics'''
	:Time to show the page between demos. Defaults: 385 (Doom), 200 (Heretic).		:Time to show the page between demos. Defaults: 385 (Doom), 200 (Heretic).

	===Menu customization===		===Menu customization===
	*'''menu.background'''		*'''menu.background'''

DEMOLOOP

Printz — Sun, 14 Jun 2026 13:01:49 GMT

@@ Line 1: / Line 1: @@
-Eternity supports the DEMOLOOP lump, which is part of the id24 specifications.
+Eternity supports the DEMOLOOP lump, which is part of the id24 specifications. This lump lets you define the startup sequence, when the game typically shows you various screens and game demos (replays) in sequence, repeating in a loop. Previously you would need to replace various lumps (like TITLEPIC and credits for the art screens, or the DEMOx lumps, possibly emptying them to remove demos) or set EDF [[gameproperties]], but the DEMOLOOP lump gives you complete control over this sequence.
 DEMOLOOP must contain a JSON text data. The content of DEMOLOOP must be of the form:
@@ Line 13: / Line 13: @@
       "data": {
-          "entries: [
+          "entries": [
+              {
                   "type":          0,
                   "primarylump":   "IMAGE1",
                   "secondarylump": "MUSIC1",
-                  "duration":      5,
+                  "duration":      5.5,
                   "outrowipe":     1
               },
@@ Line 29: / Line 29: @@
+      }
+  }

DEMOLOOP

Printz — Sun, 14 Jun 2026 10:13:18 GMT

Created page with "Eternity supports the DEMOLOOP lump, which is part of the id24 specifications. DEMOLOOP must contain a JSON text data. The content of DEMOLOOP must be of the form: { "type": "demoloop", "version": "1.0.0", "metadata": { "author": "...", "timestamp": "...", "application": "... }, "data": { "entries: [ { "type": 0, "primarylump": "IMAGE1",..."

New page

Eternity supports the DEMOLOOP lump, which is part of the id24 specifications.

DEMOLOOP must contain a JSON text data. The content of DEMOLOOP must be of the form:

{
"type": "demoloop",
"version": "1.0.0",
"metadata": {
"author": "...",
"timestamp": "...",
"application": "...
},

"data": {
"entries: [
{
"type": 0,
"primarylump": "IMAGE1",
"secondarylump": "MUSIC1",
"duration": 5,
"outrowipe": 1
},
{
"type": 1,
"primarylump: "DEMO5",
"outrowipe": 0
}
]
}
}

Predefined lumps

Printz — Sun, 14 Jun 2026 09:58:00 GMT

← Older revision		Revision as of 05:58, 14 June 2026
Line 245:		Line 245:
	==Sprite colour translation tables==		==Sprite colour translation tables==
	[[Thingtype]] [[EDF]] definitions allow a sprite's colour range to be translated, similar to how the green range is changed with the TRANSLATION1 and TRANSLATION2 [[thing type flags]], but in this case, by using custom external tables. These lumps are 256 bytes large and must be included between T_START and T_END. Normally, they will consist of consecutive 8-bit numbers from 0 to 255 if there is no translation, but the indices which need to be changed will have the numbers of the target colours.		[[Thingtype]] [[EDF]] definitions allow a sprite's colour range to be translated, similar to how the green range is changed with the TRANSLATION1 and TRANSLATION2 [[thing type flags]], but in this case, by using custom external tables. These lumps are 256 bytes large and must be included between T_START and T_END. Normally, they will consist of consecutive 8-bit numbers from 0 to 255 if there is no translation, but the indices which need to be changed will have the numbers of the target colours.

			==Demo loop control==
			See [[DEMOLOOP]].

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

Eternity Engine

Printz — Sun, 14 Jun 2026 09:56:56 GMT

Making mods for Eternity

← Older revision		Revision as of 05:56, 14 June 2026
Line 47:		Line 47:
	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]]		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.		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]], [[Doom Wiki:Hexen\|Hexen]] and recently the id24 standard such as [[ANIMDEFS]] or [[DEMOLOOP]], 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.		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.

Main Page

Printz — Sun, 14 Jun 2026 09:55:50 GMT

← Older revision		Revision as of 05:55, 14 June 2026
Line 42:		Line 42:
	*[[ANIMDEFS]]		*[[ANIMDEFS]]
	*[[Dehacked]]		*[[Dehacked]]
			*[[DEMOLOOP]]
	*[[S_SKIN]]		*[[S_SKIN]]
	===Base game data===		===Base game data===

EMAPINFO

Printz — Sun, 14 Jun 2026 09:52:41 GMT

Level identification

← Older revision		Revision as of 05:52, 14 June 2026
Line 22:		Line 22:
	! Example		! Example
	\|-		\|-
	\|\|creator\|\|The level author's name, ~~which~~ can ~~be viewed~~ in the console using the "creator" console command. If this value is not provided, the default value is "unknown".\|\|		\|\|creator\|\|The level author's name. As of Eternity 4.06.00, the creator name will show up in the intermission under the level name. This is adapted from the [[UMAPINFO]] specifications for "author". You can view the current creator in the console using the "creator" console command. If this value is not provided, the default value is "unknown", which will not show up in the intermission.\|\|
	creator = Edwin Chadwick 'chadders'		creator = Edwin Chadwick 'chadders'
	\|-		\|-

UMAPINFO

Printz — Sun, 14 Jun 2026 09:51:18 GMT

UMAPINFO - EMAPINFO equivalence table

← Older revision		Revision as of 05:51, 14 June 2026
Line 5:		Line 5:
	!UMAPINFO property		!UMAPINFO property
	!EMAPINFO equivalent		!EMAPINFO equivalent
			\|-
			\|\|'''author'''\|\|'''creator'''
	\|-		\|-
	\|\|'''levelname''', '''label'''\|\|Both of these influence '''levelname''' and '''inter-levelname'''		\|\|'''levelname''', '''label'''\|\|Both of these influence '''levelname''' and '''inter-levelname'''
Line 58:		Line 60:
	\|\|'''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'''.		\|\|'''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==		==See also==
	*[[EMAPINFO]]		*[[EMAPINFO]]

Eternity Engine

Printz — Sat, 13 Jun 2026 21:16:35 GMT

Releases

← Older revision		Revision as of 17:16, 13 June 2026
Line 143:		Line 143:
	===Version 4.05===		===Version 4.05===
	* [https://www.doomworld.com/forum/topic/154848-eternity-engine-40504-citadel/ 4.05.04] "Citadel" - August 23, 2025		* [https://www.doomworld.com/forum/topic/154848-eternity-engine-40504-citadel/ 4.05.04] "Citadel" - August 23, 2025

			===Version 4.06===
			* [https://www.doomworld.com/forum/topic/158835-eternity-engine-40600-nidhogg/ 4.06.00] "Nidhogg" — June 13, 2026

	==Cross-platform development==		==Cross-platform development==

Template:Latest

Printz — Sat, 13 Jun 2026 21:03:16 GMT

← Older revision		Revision as of 17:03, 13 June 2026
Line 1:		Line 1:
	[https://www.doomworld.com/forum/topic/~~154848~~-eternity-engine-~~40504~~-~~citadel~~/ 4.05.04]		[https://www.doomworld.com/forum/topic/158835-eternity-engine-40600-nidhogg/ 4.06.00]

← Older revision		Revision as of 05:56, 14 June 2026
Line 47:		Line 47:
	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]]		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.		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]], [[Doom Wiki:Hexen\|Hexen]] and recently the id24 standard such as [[ANIMDEFS]] or [[DEMOLOOP]], 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.		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.