CON mutator - Revision history

Hendricks266 at 01:23, 4 April 2015

2015-04-04T01:23:04Z

← Older revision		Revision as of 18:23, 3 April 2015
Line 11:		Line 11:
	===Supplementing Actor Code and Event Code===		===Supplementing Actor Code and Event Code===

	Unlike actors, [[event]]s work in an additive fashion. All instances of ~~EVENT~~ blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] ~~allows~~ coders to modify actor code without completely replacing it as [[actor]] blocks do.		Unlike actors, [[event]]s work in an additive fashion. All instances of event blocks are compiled and used by the game. This allows for true "mutators".

			[[EVENT_PREGAME]] and [[EVENT_GAME]] allow coders to modify actor code without completely replacing it as [[actor]] blocks do.

	==Guidelines==		==Guidelines==
Line 21:		Line 23:
	===Log File Identification===		===Log File Identification===

	In your mutator, add an ~~instance of~~ [[EVENT_INIT]] with an [[echo]] command identifying your mutator, and possibly a version number.		In your mutator, add an <code>appendevent [[EVENT_INIT]]</code> block with an [[echo]] command identifying your mutator, and possibly a version number.

	[[Category:Scripting documentation]]		[[Category:Scripting documentation]]

Hendricks266 at 02:12, 25 May 2012

2012-05-25T02:12:05Z

← Older revision		Revision as of 19:12, 24 May 2012
Line 16:		Line 16:

	===Namespacing Variables===		===Namespacing Variables===

	For your mutator to be properly interoperable, any variables that are expected to retain values from one tic to the next should be given a name with a prefix unique to your mutator. A variable like "temp" which is used and discarded immediately will only generate a warning if it is duplicated and may serve as an optimization to keep the total number of variables low.		For your mutator to be properly interoperable, any variables that are expected to retain values from one tic to the next should be given a name with a prefix unique to your mutator. A variable like "temp" which is used and discarded immediately will only generate a warning if it is duplicated and may serve as an optimization to keep the total number of variables low.

			===Log File Identification===

			In your mutator, add an instance of [[EVENT_INIT]] with an [[echo]] command identifying your mutator, and possibly a version number.

			[[Category:Scripting documentation]]

Hendricks266: Hendricks 266 moved page CON Mutator to CON mutator

2012-05-23T23:32:53Z

Hendricks 266 moved page CON Mutator to CON mutator

← Older revision	Revision as of 16:32, 23 May 2012
(No difference)

Hendricks266: Hendricks 266 moved page CON Mutators to CON Mutator

2012-05-23T23:24:46Z

Hendricks 266 moved page CON Mutators to CON Mutator

← Older revision		Revision as of 16:24, 23 May 2012
(No difference)

Hendricks266 at 23:21, 23 May 2012

2012-05-23T23:21:07Z

← Older revision		Revision as of 16:21, 23 May 2012
Line 3:		Line 3:
	CON '''mutators''' are a specific kind of CON module that meets certain guidelines in order to be interoperable and compatible with base CON files and other mutators. Mutators can be used to alter game functionality in certain ways or provide "libraries" of sorts containing additional code assets for mappers, to name a few example uses.		CON '''mutators''' are a specific kind of CON module that meets certain guidelines in order to be interoperable and compatible with base CON files and other mutators. Mutators can be used to alter game functionality in certain ways or provide "libraries" of sorts containing additional code assets for mappers, to name a few example uses.

	==Replacing Actor Code==		==Mechanics==

			===Replacing Actor Code===

	Each time an [[actor]] or [[useractor]] block is created, its contents completely overwrite any others for the same tilenum above its position in CON compilation order. This is useful if you want to completely change an existing actor, and may be necessary for some changes albeit having to duplicate the code.		Each time an [[actor]] or [[useractor]] block is created, its contents completely overwrite any others for the same tilenum above its position in CON compilation order. This is useful if you want to completely change an existing actor, and may be necessary for some changes albeit having to duplicate the code.

	==Supplementing Actor Code and Event Code==		===Supplementing Actor Code and Event Code===

	Unlike actors, [[event]]s work in an additive fashion. All instances of EVENT blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] allows coders to modify actor code without completely replacing it as [[actor]] blocks do.		Unlike actors, [[event]]s work in an additive fashion. All instances of EVENT blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] allows coders to modify actor code without completely replacing it as [[actor]] blocks do.

	==Namespacing Variables==		==Guidelines==
	For your mutator to be properly interoperable, any variables that are expected to retain a values from one tic to the next should be given a name with a prefix unique to your mutator. A variable like "temp" which is used and discarded immediately will only generate a warning if it is duplicated and may serve as an optimization to keep the total number of variables low.
			===Namespacing Variables===
			For your mutator to be properly interoperable, any variables that are expected to retain values from one tic to the next should be given a name with a prefix unique to your mutator. A variable like "temp" which is used and discarded immediately will only generate a warning if it is duplicated and may serve as an optimization to keep the total number of variables low.

Hendricks266 at 23:13, 23 May 2012

2012-05-23T23:13:37Z

← Older revision		Revision as of 16:13, 23 May 2012
Line 10:		Line 10:

	Unlike actors, [[event]]s work in an additive fashion. All instances of EVENT blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] allows coders to modify actor code without completely replacing it as [[actor]] blocks do.		Unlike actors, [[event]]s work in an additive fashion. All instances of EVENT blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] allows coders to modify actor code without completely replacing it as [[actor]] blocks do.

			==Namespacing Variables==
			For your mutator to be properly interoperable, any variables that are expected to retain a values from one tic to the next should be given a name with a prefix unique to your mutator. A variable like "temp" which is used and discarded immediately will only generate a warning if it is duplicated and may serve as an optimization to keep the total number of variables low.

Hendricks266: Created page with "Introduced in EDuke32 are the concept of CON '''modules''', which can be used with the -mx command line parameter. These are standalone CON files that make adjustments and add..."

2012-05-22T18:27:36Z

Created page with "Introduced in EDuke32 are the concept of CON '''modules''', which can be used with the -mx command line parameter. These are standalone CON files that make adjustments and add..."

New page

Introduced in EDuke32 are the concept of CON '''modules''', which can be used with the -mx command line parameter. These are standalone CON files that make adjustments and additions to the code and can work in tandem with other modules.

CON '''mutators''' are a specific kind of CON module that meets certain guidelines in order to be interoperable and compatible with base CON files and other mutators. Mutators can be used to alter game functionality in certain ways or provide "libraries" of sorts containing additional code assets for mappers, to name a few example uses.

==Replacing Actor Code==

Each time an [[actor]] or [[useractor]] block is created, its contents completely overwrite any others for the same tilenum above its position in CON compilation order. This is useful if you want to completely change an existing actor, and may be necessary for some changes albeit having to duplicate the code.

==Supplementing Actor Code and Event Code==

Unlike actors, [[event]]s work in an additive fashion. All instances of EVENT blocks are compiled and used by the game. This allows for true "mutators". [[EVENT_GAME]] allows coders to modify actor code without completely replacing it as [[actor]] blocks do.