EVENT PREGAME - Revision history

Doom64hunter: Previous author just copy pasted the EVENT_GAME text and forgot to edit it, wtf?

2022-02-05T08:08:15Z

Previous author just copy pasted the EVENT_GAME text and forgot to edit it, wtf?

← Older revision		Revision as of 01:08, 5 February 2022
Line 1:		Line 1:
	~~EVENT_GAME~~ is a [[EDuke32_event_list\|Game Event]].		{{EventTable\|1=EVENT_PREGAME\|2=closest player to sprite\|3=current sprite\|4=0 values}}
			EVENT_PREGAME 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]] is the current spriteNum, 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_PREWORLD]], but before any of the engine code pertaining to sprites and actors, such as <code>MoveActors()</code>, <code>MovePlayers()</code>,<code>MoveFallers()</code> etc. has executed. It also occurs before all CON code defined using [[actor]] or [[useractor]].

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

Fox at 20:32, 20 July 2014

2014-07-20T20:32:33Z

← Older revision		Revision as of 13:32, 20 July 2014
Line 1:		Line 1:
	~~EVENT_PREGAME~~ 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:~~		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.

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

	One potential use specifically for EVENT_PREGAME is to examine struct values which are clobbered by commands such as [[ifhitweapon]]/[[ifwasweapon]]~~. Otherwise, [[EVENT_GAME]] is generally sufficient~~.		One potential use specifically for EVENT_PREGAME is to examine struct values which are clobbered by commands such as [[ifhitweapon]]/[[ifwasweapon]].

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

Hendricks266 at 00:46, 15 April 2013

2013-04-15T00:46:44Z

← Older revision		Revision as of 17:46, 14 April 2013
Line 1:		Line 1:
	~~''' ''this page~~ is a ~~stub'' '''~~		EVENT_PREGAME 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.

			All sprites are processed in the following fashion:

	~~All sprites are processed in the following fashion:~~		#EVENT_PREGAME
			#hardcoded stuff
			#[[EVENT_GAME]]

	1. EVENT_PREGAME~~<br>~~		One potential use specifically for EVENT_PREGAME is to examine struct values which are clobbered by commands such as [[ifhitweapon]]/[[ifwasweapon]]. Otherwise, [[EVENT_GAME]] is generally sufficient.
	2. ~~hardcoded stuff<br>~~
	3. ~~EVENT_GAME<br>~~

	~~One potential use is to examine values which are clobbered by commands such as~~ [[~~ifhitweapon~~]]~~/[[ifwasweapon]].~~		[[Category:Events]]

Mblackwell at 21:56, 14 April 2013

2013-04-14T21:56:37Z

← Older revision		Revision as of 14:56, 14 April 2013
Line 1:		Line 1:
	''this page is a stub''		''' ''this page is a stub'' '''

Mblackwell at 21:54, 14 April 2013

2013-04-14T21:54:32Z

← Older revision		Revision as of 14:54, 14 April 2013
Line 1:		Line 1:
	''this page is a stub''		''this page is a stub''

	~~---~~

Mblackwell at 21:54, 14 April 2013

2013-04-14T21:54:15Z

← Older revision		Revision as of 14:54, 14 April 2013
Line 1:		Line 1:
	''this page is a stub''		''this page is a stub''

	----		---

Mblackwell at 21:54, 14 April 2013

2013-04-14T21:54:05Z

← Older revision		Revision as of 14:54, 14 April 2013
Line 10:		Line 10:
	3. EVENT_GAME<br>		3. EVENT_GAME<br>

	One potential use is to examine values which are clobbered by commands such as ifhitweapon/ifwasweapon.		One potential use is to examine values which are clobbered by commands such as [[ifhitweapon]]/[[ifwasweapon]].

Mblackwell: Created page with "''this page is a stub'' ---- All sprites are processed in the following fashion: 1. EVENT_PREGAME
2. hardcoded stuff
3. EVENT_GAME
One potential use is to exa..."

2013-04-14T21:53:52Z

Created page with "''this page is a stub'' ---- All sprites are processed in the following fashion: 1. EVENT_PREGAME 2. hardcoded stuff 3. EVENT_GAME One potential use is to exa..."

New page

''this page is a stub''

----

All sprites are processed in the following fashion:

1. EVENT_PREGAME 
2. hardcoded stuff 
3. EVENT_GAME 

One potential use is to examine values which are clobbered by commands such as ifhitweapon/ifwasweapon.

EVENT PREGAME - Revision history

Doom64hunter: Previous author just copy pasted the EVENT_GAME text and forgot to edit it, wtf?

Fox at 20:32, 20 July 2014

Hendricks266 at 00:46, 15 April 2013

Mblackwell at 21:56, 14 April 2013

Mblackwell at 21:54, 14 April 2013

Mblackwell at 21:54, 14 April 2013

Mblackwell at 21:54, 14 April 2013

Mblackwell: Created page with "''this page is a stub'' ---- All sprites are processed in the following fashion: 1. EVENT_PREGAME 2. hardcoded stuff 3. EVENT_GAME One potential use is to exa..."

Mblackwell: Created page with "''this page is a stub'' ---- All sprites are processed in the following fashion: 1. EVENT_PREGAME
2. hardcoded stuff
3. EVENT_GAME
One potential use is to exa..."