Operateactivators - Revision history

Doom64hunter: Formatting and wording

2021-01-09T13:09:30Z

Formatting and wording

← Older revision		Revision as of 06:09, 9 January 2021
Line 1:		Line 1:
	'''operateactivators''' <lotag> <player id><~~br>~~		<span {{code}}>'''operateactivators''' <lotag> <player id></span>
	~~'''activate''' <lotag~~>

	~~Placed inside an actor code~~, '''~~operateactivators~~''' ~~allows an actor to trigger ACTIVATOR and~~ ACTIVATORLOCKED ~~sprites. The actor does not need to be near the activator at hand, as long as it identifies~~ the lotag ~~specified in the map~~. ~~The parameter "lotag" can be either a gamevar or a regular number. The player id specified determines which player receives the "LOCKED"~~ and ~~"UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current~~ [[~~MULTIMODE~~]] ~~will cause the messages not to be sent to any player~~.		When executed, will trigger the sprites ''ACTIVATOR'' (tilenum 2) and ''ACTIVATORLOCKED'' (tilenum 4) identified by the lotag. This works both from within [[actor]] and [[event]] code.

	'''activate''' ~~is a~~ command originally found in pre-v1.0 prototypes of Duke Nukem 3D. In EDuke32, it functions the same as '''operateactivators''' but with a <player id> of 0.		====Arguments====

			* <span {{code}}><lotag></span>: Either a [[gamevar]] or a constant. Identifies the activator to be triggered in the current map.

			* <span {{code}}><player id></span>: Defines which player to send the "LOCKED" and "UNLOCKED" messages to, if triggered (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.

			== activate ==

			<span {{code}}>'''activate''' <lotag></span>

			A deprecated command originally found in pre-v1.0 prototypes of Duke Nukem 3D.

			In EDuke32, it functions the same as '''operateactivators''' but with a fixed <player id> value of 0.

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Sector manipulation]]		[[Category:Sector manipulation]]

Hendricks266 at 10:34, 3 June 2013

2013-06-03T10:34:28Z

← Older revision		Revision as of 03:34, 3 June 2013
Line 1:		Line 1:
	'''operateactivators '''<lotag> <player id>		'''operateactivators''' <lotag> <player id><br>
			'''activate''' <lotag>

	Placed inside an actor code, it allows an actor to trigger ~~activators~~ and ~~activatorlocked~~ sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The parameter "lotag" can be either a gamevar or a regular number. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.		Placed inside an actor code, '''operateactivators''' allows an actor to trigger ACTIVATOR and ACTIVATORLOCKED sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The parameter "lotag" can be either a gamevar or a regular number. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.

			'''activate''' is a command originally found in pre-v1.0 prototypes of Duke Nukem 3D. In EDuke32, it functions the same as '''operateactivators''' but with a <player id> of 0.

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Sector manipulation]]		[[Category:Sector manipulation]]

EmericaSkater at 17:19, 21 October 2011

2011-10-21T17:19:15Z

← Older revision		Revision as of 10:19, 21 October 2011
Line 1:		Line 1:
	'''operateactivators '''<lotag> <player id>		'''operateactivators '''<lotag> <player id>

	Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.		Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The parameter "lotag" can be either a gamevar or a regular number. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Sector manipulation]]		[[Category:Sector manipulation]]

One at 20:13, 4 May 2009

2009-05-04T20:13:11Z

← Older revision		Revision as of 13:13, 4 May 2009
Line 1:		Line 1:
	operateactivators <lotag> <player id>		'''operateactivators '''<lotag> <player id>

	Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.		Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.

TX: Corrections

2008-06-14T09:42:44Z

Corrections

← Older revision		Revision as of 02:42, 14 June 2008
Line 1:		Line 1:
	operateactivators <lotag> <~~sprite~~ id>		operateactivators <lotag> <player id>

	Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map and ~~uses~~ the ~~correct sprite id~~.		Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map. The player id specified determines which player receives the "LOCKED" and "UNLOCKED" messages (quotes 4 and 8, respectively). A value greater than the current [[MULTIMODE]] will cause the messages not to be sent to any player.

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
	[[Category:Sector manipulation]]		[[Category:Sector manipulation]]

Hunter byte at 20:22, 21 April 2008

2008-04-21T20:22:12Z

← Older revision		Revision as of 13:22, 21 April 2008
Line 4:		Line 4:

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]
			[[Category:Sector manipulation]]

Jblade at 09:37, 21 April 2008

2008-04-21T09:37:38Z

← Older revision		Revision as of 02:37, 21 April 2008
Line 2:		Line 2:

	Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map and uses the correct sprite id.		Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map and uses the correct sprite id.

			[[Category:EDuke32 specific commands]]

Hendricks266 at 21:24, 26 June 2007

2007-06-26T21:24:09Z

← Older revision		Revision as of 14:24, 26 June 2007
Line 1:		Line 1:
	operateactivators <lotag> <sprite id>		operateactivators <lotag> <sprite id>

	Placed inside an actor code, it allows an actor to trigger activators and ~~activorlocked~~ sprites. The actor does not need to be near the activator at hand, as long as it ~~points to~~ the lotag specified in the map and uses the correct sprite id.		Placed inside an actor code, it allows an actor to trigger activators and activatorlocked sprites. The actor does not need to be near the activator at hand, as long as it identifies the lotag specified in the map and uses the correct sprite id.

86.27.191.111 at 16:21, 26 June 2007

2007-06-26T16:21:05Z

← Older revision		Revision as of 09:21, 26 June 2007
Line 1:		Line 1:
	operateactivators <lotag> <sprite id>		operateactivators <lotag> <sprite id>

	Placed inside an actor code, it allows an actor to trigger activators. The actor does not need to be near the activator at hand, as long as it points to the lotag specified in the map and uses the correct sprite id.		Placed inside an actor code, it allows an actor to trigger activators and activorlocked sprites. The actor does not need to be near the activator at hand, as long as it points to the lotag specified in the map and uses the correct sprite id.

86.27.191.111: New page: operateactivators Placed inside an actor code, it allows an actor to trigger activators. The actor does not need to be near the activator at hand, as long as it points...

2007-06-26T16:20:18Z

New page: operateactivators <lotag> <sprite id> Placed inside an actor code, it allows an actor to trigger activators. The actor does not need to be near the activator at hand, as long as it points...

New page

operateactivators <lotag> <sprite id>

Placed inside an actor code, it allows an actor to trigger activators. The actor does not need to be near the activator at hand, as long as it points to the lotag specified in the map and uses the correct sprite id.