CEG-Format - Revision history

Flozi: tag for delete, replaced by CEG:Defs

2014-10-05T16:44:06Z

tag for delete, replaced by CEG:Defs

← Older revision		Revision as of 17:44, 5 October 2014
Line 1:		Line 1:
			{{delete}}
	'''Source:''' {{sourcelink\|file=rts/Sim/Projectiles}}		'''Source:''' {{sourcelink\|file=rts/Sim/Projectiles}}

Line 97:		Line 98:

	All distances are in elmos; all time is in frames.		All distances are in elmos; all time is in frames.

	~~[[Category:CEG]]~~

Beherith: /* useDefaultExplosions */

2013-11-23T00:04:43Z

useDefaultExplosions

← Older revision		Revision as of 01:04, 23 November 2013
Line 39:		Line 39:
	If this is set, the CEG will use the default explosion (based on damage and area of effect) in addition to any spawners you define.		If this is set, the CEG will use the default explosion (based on damage and area of effect) in addition to any spawners you define.
	The default explosions are sometimes very heavy in performance, especially for large damage values.		The default explosions are sometimes very heavy in performance, especially for large damage values.

	The basedamage is min((damage/20), areaofeffect1.5)(damage>500?1:2)		The basedamage is min((damage/20), areaofeffect1.5)(damage>500?1:2)

	This means :		This means :

	basedamage*0.6 smoke projectiles		basedamage*0.6 smoke projectiles

	min(20, basedamage*0.8) dist projectiles		min(20, basedamage*0.8) dist projectiles

	random(6)+3+basedamage/25 debris projectiles		random(6)+3+basedamage/25 debris projectiles

	sqrt(basedamage)+8 explospike projectiles		sqrt(basedamage)+8 explospike projectiles

	1 standardgroundflash		1 standardgroundflash

	1 spherepartprojectile		1 spherepartprojectile

Beherith: /* useDefaultExplosions */

2013-11-23T00:04:22Z

useDefaultExplosions

← Older revision		Revision as of 01:04, 23 November 2013
Line 38:		Line 38:
	=== useDefaultExplosions ===		=== useDefaultExplosions ===
	If this is set, the CEG will use the default explosion (based on damage and area of effect) in addition to any spawners you define.		If this is set, the CEG will use the default explosion (based on damage and area of effect) in addition to any spawners you define.
			The default explosions are sometimes very heavy in performance, especially for large damage values.
			The basedamage is min((damage/20), areaofeffect1.5)(damage>500?1:2)
			This means :
			basedamage*0.6 smoke projectiles
			min(20, basedamage*0.8) dist projectiles
			random(6)+3+basedamage/25 debris projectiles
			sqrt(basedamage)+8 explospike projectiles
			1 standardgroundflash
			1 spherepartprojectile

	=== Spawners ===		=== Spawners ===

Kingraptor: /* Conditions */ Underwater tag works.

2013-08-13T17:47:09Z

Conditions: Underwater tag works.

← Older revision		Revision as of 18:47, 13 August 2013
Line 49:		Line 49:

	==== Conditions ====		==== Conditions ====
	These determine under what conditions the spawner will run. The available conditions are "air" (at least 20 elmos above ground/sea level), "water", "ground", "unit" (hits a unit), and "nounit" (doesn't hit a unit)~~. There is an "underwater" condition, but it doesn't actually work at time of writing~~. If you set the condition to true (e.g., "water = 1;"), the spawner will run if the explosion takes place under that condition. If you set more than one condition, the spawner will run if ''any'' of them are true. If you want a spawner to run only if two or more conditions are ''all'' true, you have to do a little trick with the CExpGenSpawner class.		These determine under what conditions the spawner will run. The available conditions are "air" (at least 20 elmos above ground/sea level), "water", "underwater", "ground", "unit" (hits a unit), and "nounit" (doesn't hit a unit). If you set the condition to true (e.g., "water = 1;"), the spawner will run if the explosion takes place under that condition. If you set more than one condition, the spawner will run if ''any'' of them are true. If you want a spawner to run only if two or more conditions are ''all'' true, you have to do a little trick with the CExpGenSpawner class.

	==== Count ====		==== Count ====

Jk: /* Data Types */

2012-02-22T16:22:17Z

Data Types

← Older revision		Revision as of 17:22, 22 February 2012
Line 71:		Line 71:
	*float: Most properties are floats. e.g. `0.123`		*float: Most properties are floats. e.g. `0.123`
	*int: Used for counts and ttls. e.g. `1234`		*int: Used for counts and ttls. e.g. `1234`
	*bool: Use for conditions, and some properties. e.g. "true", "1", "false"		*bool: Use for conditions, and some properties. e.g. `true`, `1`, `false`
	*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG. e.g. "0.1 , 1.2 , 3.4", "dir"		*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG. e.g. "0.1 , 1.2 , 3.4", "dir"
	*string: Used for colormaps and texture names. In .lua you delimit a string by quotes; in .tdf you do not. Color maps consist of 2 or more groups of 4 numbers, each group representing a RGBA color. Textures are the names you define in gamedata/resources.tdf or gamedata/resources.lua. e.g. "1.0 0.0 0.0 1 0 0 1.0 1" (are gradient from red to blue)		*string: Used for colormaps and texture names. In .lua you delimit a string by quotes; in .tdf you do not. Color maps consist of 2 or more groups of 4 numbers, each group representing a RGBA color. Textures are the names you define in gamedata/resources.tdf or gamedata/resources.lua. e.g. "1.0 0.0 0.0 1 0 0 1.0 1" (are gradient from red to blue)

Jk: /* Data Types */

2012-02-22T16:21:51Z

Data Types

← Older revision		Revision as of 17:21, 22 February 2012
Line 69:		Line 69:
	CEGs use the following data types:		CEGs use the following data types:

	*float: Most properties are floats. e.g. "0.123"		*float: Most properties are floats. e.g. `0.123`
	*int: Used for counts and ttls. e.g. "1234"		*int: Used for counts and ttls. e.g. `1234`
	*bool: Use for conditions, and some properties. e.g. "true", "1", "false"		*bool: Use for conditions, and some properties. e.g. "true", "1", "false"
	*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG. e.g. "0.1 , 1.2 , 3.4", "dir"		*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG. e.g. "0.1 , 1.2 , 3.4", "dir"

Jk: /* Data Types */

2012-02-22T16:21:12Z

Data Types

← Older revision		Revision as of 17:21, 22 February 2012
Line 69:		Line 69:
	CEGs use the following data types:		CEGs use the following data types:

	*float: Most properties are floats.		*float: Most properties are floats. e.g. "0.123"
	*int: Used for counts and ttls.		*int: Used for counts and ttls. e.g. "1234"
	*bool: Use for conditions, and some properties.		*bool: Use for conditions, and some properties. e.g. "true", "1", "false"
	*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG.		*float3: Used for vectors and colors. The components are floats, separated by commas. You can also use the keyword <code>dir</code>, which represents the direction fed to the CEG. e.g. "0.1 , 1.2 , 3.4", "dir"
	*string: Used for colormaps and texture names. In .lua you delimit a string by quotes; in .tdf you do not. Color maps consist of 2 or more groups of 4 numbers, each group representing a RGBA color. Textures are the names you define in gamedata/resources.tdf or gamedata/resources.lua.		*string: Used for colormaps and texture names. In .lua you delimit a string by quotes; in .tdf you do not. Color maps consist of 2 or more groups of 4 numbers, each group representing a RGBA color. Textures are the names you define in gamedata/resources.tdf or gamedata/resources.lua. e.g. "1.0 0.0 0.0 1 0 0 1.0 1" (are gradient from red to blue)

	You can use [[CEG-Operators]] to define floats that are not fixed.		You can use [[CEG-Operators]] to define floats that are not fixed.

Flozi: update to git using sourcelink template

2011-07-07T23:38:44Z

update to git using sourcelink template

← Older revision		Revision as of 00:38, 8 July 2011
Line 1:		Line 1:
	'''Source:''' ~~https://spring.clan-sy.com/svn/spring/trunk/~~rts/Sim/Projectiles		'''Source:''' {{sourcelink\|file=rts/Sim/Projectiles}}

	== Overall Format ==		== Overall Format ==

Sdbryan at 04:29, 6 February 2011

2011-02-06T04:29:43Z

@@ Line 1: / Line 1: @@
 '''Source:''' https://spring.clan-sy.com/svn/spring/trunk/rts/Sim/Projectiles
 == Overall Format ==
@@ Line 82: / Line 80: @@
 All distances are in elmos; all time is in frames.
 [[Category:CEG]]

Sdbryan: /* .LUA */

2011-02-05T18:28:42Z

.LUA

← Older revision		Revision as of 19:28, 5 February 2011
Line 84:		Line 84:

	= .LUA =		= .LUA =
			This uses the LUPS (Lua Particle System).

			== Overall Format ==

			A CEG file contains one or more CEGs. Each CEG follows this format:

			<code><pre>
			local ceg_name = {
			useDefaultExplosions = 0,
			[spawner_name_0] = {
			class=CClassName,
			[properties] = {
			property0 = value0,
			property1 = value1,
			--and so on...
			},
			condition0 = 1,
			condition1 = 0,
			count = 1,
			},

			[spawner_name_1] = {
			--each spawner follows that format
			}

			[groundflash] = {
			--groundflash is a special name; it always generates a groundflash
			flashsize=16,
			flashalpha=1,
			circlegrowth=1,
			circlealpha=0,
			ttl=8,
			color=1,1,1,
			},
			}
			</pre></code>

	[[Category:CEG]]		[[Category:CEG]]