THISACTOR - Revision history

Hunter byte at 21:06, 21 April 2008

2008-04-21T21:06:18Z

← Older revision		Revision as of 14:06, 21 April 2008
Line 13:		Line 13:
	When used in an actor event, such as the ones listed above, THISACTOR works as it does in actor code.		When used in an actor event, such as the ones listed above, THISACTOR works as it does in actor code.

	~~[[Category:Constantly updated gamevars]]~~
	[[Category:Pre-defined gamevars]]		[[Category:Pre-defined gamevars]]

Jblade at 09:18, 21 April 2008

2008-04-21T09:18:45Z

← Older revision		Revision as of 02:18, 21 April 2008
Line 14:		Line 14:

	[[Category:Constantly updated gamevars]]		[[Category:Constantly updated gamevars]]
			[[Category:Pre-defined gamevars]]

DeeperThought at 04:47, 18 May 2006

2006-05-18T04:47:00Z

← Older revision		Revision as of 21:47, 17 May 2006
Line 1:		Line 1:
	THISACTOR is a [[gamevar]] that refers to the current [[actor]].		THISACTOR is a [[gamevar]] that refers to the current [[actor]].

	HOWEVER it is [[special case]]d in get/set[[Player Member Functions\|player]]/[[Sector Member Functions\|sector]] to refer to the current player and sector (it is also special cased in [[getactor\|get]]/[[setactor]] though this special casing shouldn't make any difference to behaviour).		HOWEVER it is [[special case]]d in get/set[[Player Member Functions\|player]]/[[Sector Member Functions\|sector]] to refer to the current player and sector (it is also special cased in [[getactor\|get]]/[[setactor]] though this special casing shouldn't make any difference to behaviour). Specifically:

			When used with get/setactor inside of actor code, THISACTOR refers to the actor you're manipulating.

			When used with get/setplayer inside of actor code, THISACTOR refers to the nearest player.

			When used with get/setsector inside of actor code, THISACTOR refers to the current actor's sector.

			When used in a player event (as opposed to the special actor events like [[EVENT_GAME]], [[EVENT_EGS]], [[EVENT_SPAWN]], et cetera), THISACTOR typically refers to the APLAYER sprite (or rather, it refers to whatever sprite has the sprite number contained in the value for the "i" member of the player struct).

			When used in an actor event, such as the ones listed above, THISACTOR works as it does in actor code.

			[[Category:Constantly updated gamevars]]

Plugwash at 09:26, 10 January 2005

2005-01-10T09:26:09Z

← Older revision		Revision as of 02:26, 10 January 2005
Line 1:		Line 1:
	THISACTOR is a [[gamevar]] that refers to the current [[actor]].		THISACTOR is a [[gamevar]] that refers to the current [[actor]].

	HOWEVER it is [[special case]]d in get/~~setplayer~~/sector to refer to the current player and sector (it is also special cased in get/setactor though this special casing shouldn't make any difference to behaviour).		HOWEVER it is [[special case]]d in get/set[[Player Member Functions\|player]]/[[Sector Member Functions\|sector]] to refer to the current player and sector (it is also special cased in [[getactor\|get]]/[[setactor]] though this special casing shouldn't make any difference to behaviour).

Plugwash at 09:23, 10 January 2005

2005-01-10T09:23:19Z

← Older revision		Revision as of 02:23, 10 January 2005
Line 1:		Line 1:
	THISACTOR is a gamevar that refers to the current actor		THISACTOR is a [[gamevar]] that refers to the current [[actor]].

	HOWEVER it is [[special case]]d in get/setplayer/sector to refer to the current player and sector (it is also special cased in get/setactor though this special casing shouldn't make any difference to behaviour).		HOWEVER it is [[special case]]d in get/setplayer/sector to refer to the current player and sector (it is also special cased in get/setactor though this special casing shouldn't make any difference to behaviour).

Plugwash at 08:59, 10 January 2005

2005-01-10T08:59:50Z

New page

THISACTOR is a gamevar that refers to the current actor

HOWEVER it is [[special case]]d in get/setplayer/sector to refer to the current player and sector (it is also special cased in get/setactor though this special casing shouldn't make any difference to behaviour).