ExtraData - Revision history

Printz: /* extflags */

2026-06-14T14:11:42Z

extflags

← Older revision		Revision as of 10:11, 14 June 2026
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.
	~~3DMDPASSPROJ~~ Linedef will always let projectiles pass even if marked as 3DMidTex		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

Printz: /* extflags */

2026-06-14T14:11:34Z

extflags

← Older revision		Revision as of 10:11, 14 June 2026
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.
			3DMDPASSPROJ 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

Printz: /* extflags */

2026-06-14T13:56:07Z

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

Printz: /* Linedef Syntax and Fields */

2025-07-28T05:29:07Z

Linedef Syntax and Fields

← Older revision		Revision as of 01:29, 28 July 2025
Line 168:		Line 168:
	id <number>		id <number>
	alpha <number>		alpha <number>

			portalid <number>
	}		}
	===Explanation of fields: ===		===Explanation of fields: ===
Line 248:		Line 250:

	The alpha field takes a value from 0.0 to 1.0 to set the opacity at which this linedef's midtexture is drawn. When combined with the ADDITIVE extflag, this can be used for additive-blended translucency as well.		The alpha field takes a value from 0.0 to 1.0 to set the opacity at which this linedef's midtexture is drawn. When combined with the ADDITIVE extflag, this can be used for additive-blended translucency as well.

			====portalid====
			:''Default: none''

			Portal ID to apply on front side middle part, as defined from [[Portal_Define]].

	=Sectors=		=Sectors=

Printz: /* Sector Syntax and Fields */

2022-05-27T06:19:04Z

Sector Syntax and Fields

← Older revision		Revision as of 02:19, 27 May 2022
Line 301:		Line 301:
	overlayalpha.floor <percentage or value from 0 to 255>		overlayalpha.floor <percentage or value from 0 to 255>
	overlayalpha.ceiling <percentage or value from 0 to 255>		overlayalpha.ceiling <percentage or value from 0 to 255>
			portalid.floor <number>
			portalid.ceiling <number>
	}		}
	===Explanation of fields: ===		===Explanation of fields: ===
Line 470:		Line 472:

	These two fields (overlayalpha.floor and overlayalpha.ceiling) specify the opacity of the corresponding portal overlay, if any exists. You can specify either a percentage value from 0% to 100%, or a plain integer number from 0 to 255. 100%/255 are completely solid, while 0% is invisible.		These two fields (overlayalpha.floor and overlayalpha.ceiling) specify the opacity of the corresponding portal overlay, if any exists. You can specify either a percentage value from 0% to 100%, or a plain integer number from 0 to 255. 100%/255 are completely solid, while 0% is invisible.

			====portalid.floor/portalid.ceiling====
			:''Default'': 0

			These two fields control the placement of portals defined by [[Portal_Define]] on the floor or ceiling of this sector. Values can be positive (in which case the direct portal will be used) or negative (in which case the opposite direction portal will be used, ''if'' applicable).

Printz: /* options */

2021-11-06T16:01:20Z

options

← Older revision		Revision as of 12:01, 6 November 2021
Line 91:		Line 91:
	FRIEND Thing uses MBF friendly logic		FRIEND Thing uses MBF friendly logic
	DORMANT Thing is dormant at map startup (script feature)		DORMANT Thing is dormant at map startup (script feature)
			STANDING Currently only used for [[Thing_types#Sector_actions\|sector actions]].
	------------------------------------------------------------------------------		------------------------------------------------------------------------------

Printz: /* type */

2020-04-01T18:47:05Z

type

← Older revision		Revision as of 14:47, 1 April 2020
Line 64:		Line 64:

	This field can also accept EDF thingtype mnemonics. EDF thingtype mnemonics must be prefixed with ''thing:'' -- this allows the parser to know it is dealing with a string instead of a number. EDF thingtypes must have a unique doomednum to be specified in an ExtraData mapthing record. If the specified EDF thingtype doesn't exist or has a doomednum of -1, an Unknown object will be spawned instead.		This field can also accept EDF thingtype mnemonics. EDF thingtype mnemonics must be prefixed with ''thing:'' -- this allows the parser to know it is dealing with a string instead of a number. EDF thingtypes must have a unique doomednum to be specified in an ExtraData mapthing record. If the specified EDF thingtype doesn't exist or has a doomednum of -1, an Unknown object will be spawned instead.

			See [[Thing types]] for a list of potentially useful types, new to Eternity, to use here.

	Example:		Example:
Line 69:		Line 71:

	mapthing { type DoomImp } // This record specifies an Imp by its EDF mnemonic		mapthing { type DoomImp } // This record specifies an Imp by its EDF mnemonic

	====options====		====options====
	Default: No flags are set by default.		Default: No flags are set by default.

Printz: /* extflags */

2020-03-22T07:35:55Z

extflags

← Older revision		Revision as of 03:35, 22 March 2020
Line 210:		Line 210:
	---------------------------------------------------------------------------------------		---------------------------------------------------------------------------------------

	Notes: IMPACT is currently only implemented for bullet weapons~~. The ability to use IMPACT with MISSILE will be added in the near future. The PUSH style of activation is not implemented at all yet, so this flag currently does nothing~~.		Notes: IMPACT is currently only implemented for bullet weapons.

	LOWERPORTAL and UPPERPORTAL are used to enable portals on the front side's upper and/or lower edges of a linedef, if the sector in front of the linedef is tall enough compared to the back sector to expose them. It is the only way to enable such portals, which will copy the sector portal(s) from the backside, if any.		LOWERPORTAL and UPPERPORTAL are used to enable portals on the front side's upper and/or lower edges of a linedef, if the sector in front of the linedef is tall enough compared to the back sector to expose them. It is the only way to enable such portals, which will copy the sector portal(s) from the backside, if any.

Altazimuth: Make note that ExtraData is now deprecated, in favour of UDMF.

2018-12-17T13:00:30Z

Make note that ExtraData is now deprecated, in favour of UDMF.

← Older revision		Revision as of 09:00, 17 December 2018
Line 1:		Line 1:
			With support of [[Universal Doom Map Format]] in releases of Eternity, ExtraData is now considered {{Deprecated}}. In the future new features introduced into UDMF will not be supported by ExtraData. ExtraData maps will still work, but new projects should use UDMF due to its greatly streamlined mapping experience, especially if using editors such as [https://www.doomworld.com/forum/topic/96943 Doom Builder X] or [https://forum.zdoom.org/viewtopic.php?t=54957 GZDoomBuilder-Bugfix] are used (the former including specific improvements for Eternity's UDMF, such as for [[linked portals]]).

	ExtraData is a new data specification language for the [[Eternity Engine]] that allows arbitrary extension of mapthings, lines, and sectors with any number of new fields, with data provided in more or less any format. The use of a textual input language forever removes any future problems caused by binary format limitations. The ExtraData parser is based on the libConfuse configuration file parser library by Martin Hedenfalk, which is also used by GFS and EDF.		ExtraData is a new data specification language for the [[Eternity Engine]] that allows arbitrary extension of mapthings, lines, and sectors with any number of new fields, with data provided in more or less any format. The use of a textual input language forever removes any future problems caused by binary format limitations. The ExtraData parser is based on the libConfuse configuration file parser library by Martin Hedenfalk, which is also used by GFS and EDF.

	Each section in this document deals with one of the ExtraData constructs, as well as how to embed ExtraData in a WAD and how to associate it with a given map.		Each section in this document deals with one of the ExtraData constructs, as well as how to embed ExtraData in a WAD and how to associate it with a given map.

	~~ExtraData will continue to be supported in future versions of Eternity, even though it will soon be superceded by support for the [[Universal Doom Map Format]]~~.
	{{Backto\|Eternity Engine}}		{{Backto\|Eternity Engine}}
	{{editref}}		{{editref}}

Printz: /* portalflags.floor/portalflags.ceiling */

2017-08-03T06:36:42Z

portalflags.floor/portalflags.ceiling

← Older revision		Revision as of 02:36, 3 August 2017
Line 452:		Line 452:
	Flag name Meaning		Flag name Meaning
	---------------------------------------------------------------------------------------		---------------------------------------------------------------------------------------
	DISABLED Portal is completely disabled		DISABLED Portal is completely disabled
	NORENDER Portal will not be rendered, but may still be interactive		NORENDER Portal will not be rendered, but may still be interactive
	NOPASS Objects cannot pass through the portal even if it is a linked portal		NOPASS Objects cannot pass through the portal even if it is a linked portal
	BLOCKSOUND Sound will not traverse through a linked portal		BLOCKSOUND Sound will not traverse through a linked portal
	OVERLAY The portal will render the sector's flat as a blended overlay		OVERLAY The portal will render the sector's flat as a blended overlay
	ADDITIVE If OVERLAY is also specified, the overlay will use additive blending		ADDITIVE If OVERLAY is also specified, the overlay will use additive blending
	USEGLOBALTEX Reserved for future per-portal texture specification		USEGLOBALTEX Reserved for future per-portal texture specification
			ATTACHEDPORTAL If a linked portal is on the respective floor or ceiling, move it along
			with the surface. Useful for vertically moving platforms.
	---------------------------------------------------------------------------------------		---------------------------------------------------------------------------------------