Fieldname - Revision history

ReyalP: warning on field descriptions.

2007-05-24T22:18:59Z

warning on field descriptions.

← Older revision		Revision as of 22:18, 24 May 2007
Line 251:		Line 251:

	== Field details ==		== Field details ==
			'''WARNING'''
			The following are incomplete, and likely contain errors. Also be aware that the meaning of many fields depends on which entity the field belongs to. "damage" on one entity may have a completely different meaning on another. When in doubt, consult the ET source. ETPro may differ slightly, but the majority of entity fields are the same. The full meaning of a given field can ONLY be obtained from the source.

	=== classname ===		=== classname ===
	Entity class name.		Entity class name.

Major Zeman: field detailed descriptions

2007-05-20T09:23:28Z

field detailed descriptions

@@ Line 246: / Line 246: @@
 ===meansOfDeath===
 :a '''meansOfDeath_t''' is a number indicating the [[etdamage|Method of Death]] Click  [[etdamage|here]] for a list with possible value's
 [[Category:ETPro]]
 [[Category:Lua]]
 [[Category:ETPro:Mods]]

Major Zeman: I believe sess.spectatorClient returns entity rather than int

2007-05-20T07:29:59Z

I believe sess.spectatorClient returns entity rather than int

← Older revision		Revision as of 07:29, 20 May 2007
Line 123:		Line 123:
	sess.spectatorTime;integer;RW;		sess.spectatorTime;integer;RW;
	sess.spectatorState;spectatorState_t;RW;		sess.spectatorState;spectatorState_t;RW;
	sess.spectatorClient;~~integer~~;RW;		sess.spectatorClient;entity;RW;
	sess.latchSpectatorClient;integer;RW;		sess.latchSpectatorClient;integer;RW;
	sess.playerType;integer;RW;		sess.playerType;integer;RW;

Major Zeman: added to Lua category

2007-05-18T22:10:28Z

added to Lua category

← Older revision		Revision as of 22:10, 18 May 2007
Line 248:		Line 248:

	[[Category:ETPro]]		[[Category:ETPro]]
			[[Category:Lua]]
	[[Category:ETPro:Mods]]		[[Category:ETPro:Mods]]

ReyalP: make boolean description more accurate

2007-03-06T03:55:44Z

make boolean description more accurate

← Older revision		Revision as of 03:55, 6 March 2007
Line 183:		Line 183:

	===qboolean===		===qboolean===
	:a '''qboolean''' is ~~a number representing~~ a boolean value.		:a '''qboolean''' is a boolean value.
	:0 is false		:0 is represented by the lua value false
	:1 is true		:1 is represented by the lua value true

	----		----

ReyalP: Im2spelling4u

2007-02-25T02:20:30Z

Im2spelling4u

← Older revision		Revision as of 02:20, 25 February 2007
Line 245:		Line 245:

	===meansOfDeath===		===meansOfDeath===
	:a '''meansOfDeath_t''' is a number indicating the [[etdamage\|Method of Death]] Click [[etdamage\|here]] for a list ~~whit posable~~ value's		:a '''meansOfDeath_t''' is a number indicating the [[etdamage\|Method of Death]] Click [[etdamage\|here]] for a list with possible value's

	[[Category:ETPro]]		[[Category:ETPro]]
	[[Category:ETPro:Mods]]		[[Category:ETPro:Mods]]

Lagger: link fix

2006-04-28T08:17:55Z

link fix

← Older revision		Revision as of 08:17, 28 April 2006
Line 1:		Line 1:
	__NOEDITSECTION__		__NOEDITSECTION__
	==Entity Fieldnames==		==Entity Fieldnames==
	List of fields supported by [[~~ETPro:~~Lua Mod API#entities\|et.gentity_get() and et.gentity_set()]] functions<br>		List of fields supported by [[Lua Mod API#entities\|et.gentity_get() and et.gentity_set()]] functions<br>
	<pitatable columns=3 headlines="field;type;access" widths="180;120;60" headerfontcolor="#FFFFFF">		<pitatable columns=3 headlines="field;type;access" widths="180;120;60" headerfontcolor="#FFFFFF">
	activator;entity;RO;		activator;entity;RO;

WeblionX: You forgot an "a"!

2006-04-04T19:26:03Z

You forgot an "a"!

← Older revision		Revision as of 19:26, 4 April 2006
Line 183:		Line 183:

	===qboolean===		===qboolean===
	:a '''qboolean''' is number representing a boolean value.		:a '''qboolean''' is a number representing a boolean value.
	:0 is false		:0 is false
	:1 is true		:1 is true

ReyalP: describe array fields + FFisms

2006-04-03T01:12:55Z

describe array fields + FFisms

← Older revision		Revision as of 01:12, 3 April 2006
Line 176:		Line 176:
	</pitatable>		</pitatable>
	:''note'': all the sess.* fields will return nil unless the entity is associated with client slot < sv_maxclients.		:''note'': all the sess.* fields will return nil unless the entity is associated with client slot < sv_maxclients.
	:''note'': all array variables need ~~tobe called~~ or ~~get whit~~ an additional parameter		:''note'': all array variables need to be get or set with an additional parameter.

	----		----
Line 183:		Line 183:

	===qboolean===		===qboolean===
	:a '''qboolean''' is a ~~bool made of a number, it has 2 valeus 1 or 0~~		:a '''qboolean''' is number representing a boolean value.
	:0 is ~~considered as~~ false		:0 is false
	:1 is ~~considered as~~ true		:1 is true

	----		----
Line 196:		Line 196:
	origin = et.gentity_get(entNum,"r.currentOrigin") --a vec3 value		origin = et.gentity_get(entNum,"r.currentOrigin") --a vec3 value
	x,y,z = origin[1],origin[2],origin[3]</pre>		x,y,z = origin[1],origin[2],origin[3]</pre>

			----

			===array===
			:The fields listed as having type '''array''' represent an entity value which is an array. Individual elements of the array are accessed by passing the desired index in the ''arrayindex'' argument to the et.gentity_get and et.gentity_set functions. Valid array indexes are integers from 0 up to some field specific maximum. The ''arrayindex'' argument is '''required''' when accessing array type fields, so only one element of an array can be accessed in a given call to the gentity_* functions.<br>

	----		----

=FF=im2good4u: fixors

2006-03-08T17:51:34Z

fixors

← Older revision		Revision as of 17:51, 8 March 2006
Line 186:		Line 186:
	:0 is considered as false		:0 is considered as false
	:1 is considered as true		:1 is considered as true

			----

	===vec3===		===vec3===
Line 234:		Line 236:
	:1023 is '''ENTITYNUM_NONE''' which is used instead of null in C under some circumstances to indicate no entity. This is needed where an entity number will be passed over the network.		:1023 is '''ENTITYNUM_NONE''' which is used instead of null in C under some circumstances to indicate no entity. This is needed where an entity number will be passed over the network.
	:''Note'': Some other fields not listed as type 'entity' may take an entity number value. '''mg42BaseEnt''' and '''s.number''' are examples.<br>		:''Note'': Some other fields not listed as type 'entity' may take an entity number value. '''mg42BaseEnt''' and '''s.number''' are examples.<br>

			----

	===meansOfDeath===		===meansOfDeath===