Animation-CobConstants - Revision history

Hokomoko: /* Custom Variables */

2016-05-31T11:40:23Z

Custom Variables

← Older revision		Revision as of 12:40, 31 May 2016
Line 21:		Line 21:
	=== Custom Variables ===		=== Custom Variables ===
	{{removed\|101.0}}		{{removed\|101.0}}

	Higher GET/SET numbers are reserved for custom variables. These are very useful for Lua integration. Setting these variables is much (perhaps 100x) faster than calling functions across Lua and COB; the disadvantages are the limited number of variables and the fact that the other side is not immediately notified of a change in the variable.		Higher GET/SET numbers are reserved for custom variables. These are very useful for Lua integration. Setting these variables is much (perhaps 100x) faster than calling functions across Lua and COB; the disadvantages are the limited number of variables and the fact that the other side is not immediately notified of a change in the variable.

2016-05-31T11:40:15Z

Custom Variables

← Older revision		Revision as of 12:40, 31 May 2016
Line 20:		Line 20:

	=== Custom Variables ===		=== Custom Variables ===
			{{removed\|101.0}}
	Higher GET/SET numbers are reserved for custom variables. These are very useful for Lua integration. Setting these variables is much (perhaps 100x) faster than calling functions across Lua and COB; the disadvantages are the limited number of variables and the fact that the other side is not immediately notified of a change in the variable.		Higher GET/SET numbers are reserved for custom variables. These are very useful for Lua integration. Setting these variables is much (perhaps 100x) faster than calling functions across Lua and COB; the disadvantages are the limited number of variables and the fact that the other side is not immediately notified of a change in the variable.

2014-04-09T18:26:40Z

← Older revision		Revision as of 19:26, 9 April 2014
Line 37:		Line 37:
	*2048: Fire weapon. Fires a weapon from the piece (no aiming involved). Again, the first weapon is 0, the second weapon is 1, etc.		*2048: Fire weapon. Fires a weapon from the piece (no aiming involved). Again, the first weapon is 0, the second weapon is 1, etc.
	*4096: Explode weapon. Detonates a weapon at the piece. Again, the first weapon is 0, the second weapon is 1, etc.		*4096: Explode weapon. Detonates a weapon at the piece. Again, the first weapon is 0, the second weapon is 1, etc.

			If the piece has no geometry, then the sfx is emitted in the +z direction from the origin of the piece.

			If the piece has 1 vertex, the emit dir is the vector from the origin to the the position of the first vertex the emit position is the origin of the piece.

			If there is more than one vertex in the piece, then the emit vector is the vector pointing from v[0] to v[1], and the emit position is v[0].

	==explode==		==explode==

2013-08-04T18:50:25Z

2013-03-21T10:48:27Z

1cat

← Older revision		Revision as of 11:48, 21 March 2013
Line 55:		Line 55:
	*NOHEATCLOUD: No explosion before the piece flies off.		*NOHEATCLOUD: No explosion before the piece flies off.
	*BITMAP[1...5]: Not used in Spring, may overlap with Spring specific bits.		*BITMAP[1...5]: Not used in Spring, may overlap with Spring specific bits.
	~~[[Category:Unit_development]]~~
	[[Category:Animation]]		[[Category:Animation]]

2011-07-04T22:21:22Z

Source: use sourcelink

← Older revision		Revision as of 23:21, 4 July 2011
Line 1:		Line 1:
	==Source==		==Source==

	This has a list of all COB SET/GET constants: ~~https://github.com/spring/spring/blob/master/~~rts/Sim/Units/Scripts/CobDefines.h		This has a list of all COB SET/GET constants: {{sourcelink\|file=rts/Sim/Units/Scripts/CobDefines.h}}

	You'll want to include a file with these constants in your script.		You'll want to include a file with these constants in your script.

2011-05-03T09:01:49Z

Source

← Older revision		Revision as of 10:01, 3 May 2011
Line 1:		Line 1:
	==Source==		==Source==

	This has a list of all COB SET/GET constants: ~~http~~://github.com/spring/spring/blob/master/rts/Sim/Units/~~COB~~/~~CobInstance~~.~~cpp~~		This has a list of all COB SET/GET constants: https://github.com/spring/spring/blob/master/rts/Sim/Units/Scripts/CobDefines.h

	You'll want to include a file with these constants in your script.		You'll want to include a file with these constants in your script.

2010-03-13T17:37:06Z

fix category

← Older revision		Revision as of 18:37, 13 March 2010
Line 55:		Line 55:
	*NOHEATCLOUD: No explosion before the piece flies off.		*NOHEATCLOUD: No explosion before the piece flies off.
	*BITMAP[1...5]: Not used in Spring, may overlap with Spring specific bits.		*BITMAP[1...5]: Not used in Spring, may overlap with Spring specific bits.
			[[Category:Unit_development]]
			[[Category:Animation]]

2009-08-23T21:05:22Z

← Older revision	Revision as of 22:05, 23 August 2009
(No difference)

2009-08-23T20:57:48Z

← Older revision	Revision as of 21:57, 23 August 2009
(No difference)

← Older revision		Revision as of 19:50, 4 August 2013
Line 16:		Line 16:
	*ACTIVATION: Whether the unit is on (true) or off (false).		*ACTIVATION: Whether the unit is on (true) or off (false).
	*ARMORED: When true, any damage dealt to the unit will be multiplied by its damageModifier.		*ARMORED: When true, any damage dealt to the unit will be multiplied by its damageModifier.
	*PRINT: You can use GET PRINT to send up to 4 arguments to chat. Useful for debugging.		*PRINT: You can use GET PRINT to send up to 4 arguments to chat. Useful for debugging. Example: '''get PRINT(1, 5,9,10);''' statement will print the following into infolog: '''Value 1: 1, 2: 5, 3: 9, 4: 10'''
	*VETERAN_LEVEL: The unit's experience times 100. Note that you can SET this via script, although the unit won't gain any extra health from doing so.		*VETERAN_LEVEL: The unit's experience times 100. Note that you can SET this via script, although the unit won't gain any extra health from doing so.