EVENT GAME - Revision history

Doom64hunter at 08:08, 5 February 2022

2022-02-05T08:08:32Z

← Older revision		Revision as of 01:08, 5 February 2022
Line 2:		Line 2:
	EVENT_GAME is a [[EDuke32_event_list\|Game Event]].		EVENT_GAME is a [[EDuke32_event_list\|Game Event]].

	This [[event]] is triggered once per tic per sprite in the game, if and only if said sprite does not have [[spriteflags\|SFLAG_NOEVENTS]] set. The gamevar [[THISACTOR]] ~~refers to~~ the spriteNum ~~of the actor executing the code~~, while the current player is the closest player to said sprite.		This [[event]] is triggered once per tic per sprite in the game, if and only if said sprite does not have [[spriteflags\|SFLAG_NOEVENTS]] set. The gamevar [[THISACTOR]] is the current spriteNum, while the current player is the closest player to said sprite.

	This event occurs after [[EVENT_PREGAME]], and after [[EVENT_WORLD]]. Furthermore, it occurs after all engine code pertaining to sprites and actors, such as <code>MoveActors()</code>, <code>MovePlayers()</code>,<code>MoveFallers()</code> etc. has executed. The event also occurs after all CON code defined using [[actor]] or [[useractor]], while [[EVENT_PREGAME]] is processed before.		This event occurs after [[EVENT_PREGAME]], and after [[EVENT_WORLD]]. Furthermore, it occurs after all engine code pertaining to sprites and actors, such as <code>MoveActors()</code>, <code>MovePlayers()</code>,<code>MoveFallers()</code> etc. has executed. The event also occurs after all CON code defined using [[actor]] or [[useractor]], while [[EVENT_PREGAME]] is processed before.

Doom64hunter at 07:54, 5 February 2022

2022-02-05T07:54:10Z

← Older revision		Revision as of 00:54, 5 February 2022
Line 1:		Line 1:
			{{EventTable\|1=EVENT_GAME\|2=closest player to sprite\|3=current sprite\|4=0 values}}
	EVENT_GAME is a [[EDuke32_event_list\|Game Event]].		EVENT_GAME is a [[EDuke32_event_list\|Game Event]].

	This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code~~. Thus~~, ~~it takes~~ the ~~value of each actor in~~ the ~~game~~.		This [[event]] is triggered once per tic per sprite in the game, if and only if said sprite does not have [[spriteflags\|SFLAG_NOEVENTS]] set. The gamevar [[THISACTOR]] refers to the spriteNum of the actor executing the code, while the current player is the closest player to said sprite.

	~~Typically this~~ event ~~is processed~~ after ~~hard-coded effects~~ and ~~the actor~~ code (~~with~~ [[actor]] or [[useractor]]), while [[EVENT_PREGAME]] is processed before. ~~Thus~~ EVENT_GAME can be used to override these effects~~. Generally EVENT_GAME is sufficient for coding needs but EVENT_PREGAME has some specific uses~~.		This event occurs after [[EVENT_PREGAME]], and after [[EVENT_WORLD]]. Furthermore, it occurs after all engine code pertaining to sprites and actors, such as <code>MoveActors()</code>, <code>MovePlayers()</code>,<code>MoveFallers()</code> etc. has executed. The event also occurs after all CON code defined using [[actor]] or [[useractor]], while [[EVENT_PREGAME]] is processed before.
			Therefore, EVENT_GAME can be used to override these effects.

	Unlike [[actor]] or [[useractor]], EVENT_GAME and EVENT_PREGAME are triggered the same tic the sprite is loaded/spawned, but are processed after [[EVENT_LOADACTOR]] or [[EVENT_EGS]].		Unlike [[actor]] or [[useractor]], EVENT_GAME and EVENT_PREGAME are triggered the same tic the sprite is loaded/spawned, but are processed after [[EVENT_LOADACTOR]] or [[EVENT_EGS]].

	[[Category:Events]]		[[Category:Events]]

Fox at 20:31, 20 July 2014

2014-07-20T20:31:32Z

← Older revision		Revision as of 13:31, 20 July 2014
Line 3:		Line 3:
	This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

	Typically this event is processed after hard-coded effects and the actor code (with [[actor]] or [[useractor]]), while [[EVENT_PREGAME]] is processed before.		Typically this event is processed after hard-coded effects and the actor code (with [[actor]] or [[useractor]]), while [[EVENT_PREGAME]] is processed before. Thus EVENT_GAME can be used to override these effects. Generally EVENT_GAME is sufficient for coding needs but EVENT_PREGAME has some specific uses.

	Unlike [[actor]] or [[useractor]], EVENT_GAME and EVENT_PREGAME are triggered the same tic the sprite is loaded/spawned, but are processed after [[EVENT_LOADACTOR]] or [[EVENT_EGS]].		Unlike [[actor]] or [[useractor]], EVENT_GAME and EVENT_PREGAME are triggered the same tic the sprite is loaded/spawned, but are processed after [[EVENT_LOADACTOR]] or [[EVENT_EGS]].

	[[Category:Events]]		[[Category:Events]]

Fox at 20:28, 20 July 2014

2014-07-20T20:28:14Z

← Older revision		Revision as of 13:28, 20 July 2014
Line 3:		Line 3:
	This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

	~~All sprites are~~ processed in the ~~following fashion:~~		Typically this event is processed after hard-coded effects and the actor code (with [[actor]] or [[useractor]]), while [[EVENT_PREGAME]] is processed before.

	~~#[[EVENT_PREGAME]]~~		Unlike [[actor]] or [[useractor]], EVENT_GAME and EVENT_PREGAME are triggered the same tic the sprite is loaded/spawned, but are processed after [[EVENT_LOADACTOR]] or [[EVENT_EGS]].
	~~#hardcoded stuff~~
	~~#EVENT_GAME~~

	~~EVENT_GAME is generally sufficient for coding needs but EVENT_PREGAME has some specific uses.~~

	Unlike [[actor]] or [[useractor]], EVENT_GAME is triggered the same tic the sprite is loaded/spawned.

	[[Category:Events]]		[[Category:Events]]

Fox at 01:08, 22 March 2014

2014-03-22T01:08:46Z

← Older revision		Revision as of 18:08, 21 March 2014
Line 1:		Line 1:
	EVENT_GAME is a [[EDuke32_event_list\|Game Event]].		EVENT_GAME is a [[EDuke32_event_list\|Game Event]].

	This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

	All sprites are processed in the following fashion:		All sprites are processed in the following fashion:
Line 10:		Line 10:

	EVENT_GAME is generally sufficient for coding needs but EVENT_PREGAME has some specific uses.		EVENT_GAME is generally sufficient for coding needs but EVENT_PREGAME has some specific uses.

			Unlike [[actor]] or [[useractor]], EVENT_GAME is triggered the same tic the sprite is loaded/spawned.

	[[Category:Events]]		[[Category:Events]]

Hendricks266 at 00:46, 15 April 2013

2013-04-15T00:46:47Z

← Older revision		Revision as of 17:46, 14 April 2013
Line 2:		Line 2:

	This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

			All sprites are processed in the following fashion:

			#[[EVENT_PREGAME]]
			#hardcoded stuff
			#EVENT_GAME

			EVENT_GAME is generally sufficient for coding needs but EVENT_PREGAME has some specific uses.

	[[Category:Events]]		[[Category:Events]]

One at 18:24, 3 May 2009

2009-05-03T18:24:11Z

← Older revision		Revision as of 11:24, 3 May 2009
Line 1:		Line 1:
	EVENT_GAME is an [[event]] ~~that~~ is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		EVENT_GAME is a [[EDuke32_event_list\|Game Event]].

			This [[event]] is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

	[[Category:Events]]		[[Category:Events]]

Usurper: Reverted edits by 201.21.218.199 (Talk); changed back to last version by TX

2006-12-29T02:50:14Z

Reverted edits by 201.21.218.199 (Talk); changed back to last version by TX

← Older revision		Revision as of 19:50, 28 December 2006
Line 1:		Line 1:
	EVENT_GAME is an [[event]] that is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		EVENT_GAME is an [[event]] that is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

	~~Very usefull, you can instead of modding original CON files, use <i>ifactor MYACTOR</i> to edit actors or <i>ifactor APLAYER</i> for add codes as if was added on APLAYER code without editing GAME.CON.~~

	~~Most important, can edit hard-coded actor without breaking it using the <i>[[actor]] MYENEMY</i> code.~~
	~~onevent EVENT_GAME~~
	~~ifactor RECON~~
	~~ifai 0~~
	~~strength 50~~
	~~ifactor RPG~~
	~~ifspawnedby BOSS2~~
	~~spawn SMALLSMOKE~~
	~~endevent~~
	~~This will change RECON strength and adding a trail to the RPG that Cycloid Emperor shoots.~~

	[[Category:Events]]		[[Category:Events]]

201.21.218.199 at 22:19, 25 December 2006

2006-12-25T22:19:23Z

← Older revision		Revision as of 15:19, 25 December 2006
Line 5:		Line 5:
	Most important, can edit hard-coded actor without breaking it using the <i>[[actor]] MYENEMY</i> code.		Most important, can edit hard-coded actor without breaking it using the <i>[[actor]] MYENEMY</i> code.
	onevent EVENT_GAME		onevent EVENT_GAME
	ifactor RECON		ifactor RECON
	ifai 0		ifai 0
	strength 50		strength 50
	ifactor RPG		ifactor RPG
	ifspawnedby BOSS2		ifspawnedby BOSS2
	spawn SMALLSMOKE		spawn SMALLSMOKE
	endevent		endevent
	This will change RECON strength and adding a trail to the RPG that Cycloid Emperor shoots.		This will change RECON strength and adding a trail to the RPG that Cycloid Emperor shoots.

	[[Category:Events]]		[[Category:Events]]

201.21.218.199 at 22:18, 25 December 2006

2006-12-25T22:18:48Z

← Older revision		Revision as of 15:18, 25 December 2006
Line 1:		Line 1:
	EVENT_GAME is an [[event]] that is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.		EVENT_GAME is an [[event]] that is triggered once per tic per sprite in the game. The gamevar [[THISACTOR]] refers to the ID of the actor executing the code. Thus, it takes the value of each actor in the game.

			Very usefull, you can instead of modding original CON files, use <i>ifactor MYACTOR</i> to edit actors or <i>ifactor APLAYER</i> for add codes as if was added on APLAYER code without editing GAME.CON.

			Most important, can edit hard-coded actor without breaking it using the <i>[[actor]] MYENEMY</i> code.
			onevent EVENT_GAME
			ifactor RECON
			ifai 0
			strength 50
			ifactor RPG
			ifspawnedby BOSS2
			spawn SMALLSMOKE
			endevent
			This will change RECON strength and adding a trail to the RPG that Cycloid Emperor shoots.

	[[Category:Events]]		[[Category:Events]]