Polyobject - Revision history

Printz: /* Polyobjects with 2-sided lines */

2026-06-14T14:12:31Z

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]]

Printz at 14:04, 14 June 2026

2026-06-14T14:04:49Z

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

Printz: /* Creating PolyObjects */

2026-04-23T17:24:40Z

Creating PolyObjects

← Older revision		Revision as of 13:24, 23 April 2026
Line 11:		Line 11:
	==Creating PolyObjects==		==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.		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'''===		==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===

Printz at 17:23, 23 April 2026

2026-04-23T17:23:18Z

← Older revision		Revision as of 13:23, 23 April 2026
Line 6:		Line 6:

	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.		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}}		{{Backto\|Linedef types}}

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

2026-04-21T20:59:47Z

Method 2: The Polyobj_ExplicitLine Special

← Older revision		Revision as of 16:59, 21 April 2026
Line 39:		Line 39:
	==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===		==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===

	:The <code>349:Polyobj_ExplicitLine('''~~linedef_tag~~''', '''~~linedef_tag~~''', '''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.		: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:		:Diagrammatic Example:
Line 51:		Line 51:
	:* '''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.		:* '''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('''~~linedef_tag~~''', '''~~linedef_tag~~''', '''mirror_id''')</code> are as follows:		: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		:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
	:* ''~~linedef_tag~~'' : 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.		:* ''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.		:* ''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.

Printz: added link

2016-07-22T07:10:55Z

added link

← Older revision		Revision as of 03:10, 22 July 2016
Line 207:		Line 207:
	} (...)		} (...)
	</pre>		</pre>

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

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

Printz: /* Creating PolyObjects */ added numbers

2016-02-16T19:00:31Z

Creating PolyObjects: added numbers

← Older revision		Revision as of 15:00, 16 February 2016
Line 17:		Line 17:
	==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===		==='''Method 1: The <code>Polyobj_StartLine</code> Special'''===

	:The <code>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).		: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:		:Diagrammatic Example:
Line 39:		Line 39:
	==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===		==='''Method 2: The <code>Polyobj_ExplicitLine</code> Special'''===

	:The <code>Polyobj_ExplicitLine('''linedef_tag''', '''linedef_tag''', '''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.		:The <code>349:Polyobj_ExplicitLine('''linedef_tag''', '''linedef_tag''', '''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:		:Diagrammatic Example:

88.141.46.205: Removed outdated or otherwise false allusions to limitations in ZDoom's polyobjects.

2013-02-20T21:56:42Z

Removed outdated or otherwise false allusions to limitations in ZDoom's polyobjects.

← Older revision		Revision as of 17:56, 20 February 2013
Line 1:		Line 1:
	PolyObjects are special sets of one-sided linedefs which, unlike any other lines, can be moved on the map during gameplay. Unlike the Hexen ~~and ZDoom~~ 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 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.		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.
Line 5:		Line 5:
	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.		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~~, unlike ZDoom~~, 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.		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.		'''NOTE:''' Polyobjects must be convex, to be rendered properly.

Ellmo at 19:35, 12 February 2013

2013-02-12T19:35:56Z

← Older revision		Revision as of 15:35, 12 February 2013
Line 6:		Line 6:

	Finally, unlike ZDoom, 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.		Finally, unlike ZDoom, 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}}		{{Backto\|Linedef types}}

Ellmo: /* Creating PolyObjects */

2013-02-10T18:40:03Z

Creating PolyObjects

← Older revision		Revision as of 14:40, 10 February 2013
Line 28:		Line 28:
	: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.		: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</code> are as follows:		: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		:* ''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.		:* ''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.
Line 48:		Line 48:
	:* '''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.		:* '''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('''linedef_tag''', '''linedef_tag''', '''mirror_id''') are as follows:		:The complete arguments to <code>Polyobj_ExplicitLine('''linedef_tag''', '''linedef_tag''', '''mirror_id''')</code> are as follows:
	:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject		:* ''polyobj_id'' : the unique ID number (greater than zero) of the PolyObject
	:* ''linedef_tag'' : 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.		:* ''linedef_tag'' : 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.