Entity properties - Revision history

TheY4Kman: s/encapsulates/encapsulate

2008-05-14T20:22:24Z

s/encapsulates/encapsulate

2007-11-16T00:15:12Z

2007-10-22T07:52:45Z

2007-09-24T14:12:48Z

2007-04-27T01:52:51Z

2007-03-27T02:37:05Z

2007-03-26T16:23:16Z

2007-03-26T01:27:07Z

‎Network Properties

2007-03-26T01:22:55Z

2007-03-26T01:10:21Z

@@ Line 64: / Line 64: @@
 ==Send Tables==
-Send tables, also called ''data tables'', encapsulates a set of related send properties.  Send tables can be nested; if there is a send property that includes a send table, the tables will effectively be merged.
+Send tables, also called ''data tables'', encapsulate a set of related send properties.  Send tables can be nested; if there is a send property that includes a send table, the tables will effectively be merged.
 '''Important Headers''': <tt>public/dt_send.h</tt>

← Older revision		Revision as of 00:15, 16 November 2007
Line 288:		Line 288:

	[[Category:SourceMod Development]]		[[Category:SourceMod Development]]
		+	[[Category:SourceMod Scripting]]

@@ Line 275: / Line 275: @@
 	*(int *)((char *)pEntity + offset) = health;
 }</cpp>
 =External Links=
 *[http://www.bailopan.net/table_dump.txt Sample CS:S Network Property Dump]
 [[Category:SourceMod Development]]

@@ Line 2: / Line 2: @@
 =Introduction=
-Entity properties are named, retrievable properties that represent a certain data structure specific to an entity instance.  They are usually tied to variables of CBaseEntity and its derivatives.  Each named property is tied to, among other pieces of information, an offset from the <tt>this</tt> pointer of the entity.  This means that server-side developers can easily decompose entity information, because the variable names and offsets are enumerable.
+'''In layman's terms:'''
 The information here is intended for server-side plugin developers who are learning, programming, or reverse engineering a mod that does not nicely expose API for modifying entities.  Mod developers should use the [http://developer.valvesoftware.com/ Valve Wiki].

@@ Line 221: / Line 221: @@
 		for (int i=0; i<pMap->dataNumFields; i++)
+		{
 			if (strcmp(name, pMap->dataDesc[i].fieldName) == 0)
+			{

← Older revision		Revision as of 02:37, 27 March 2007
Line 271:		Line 271:
	=External Links=		=External Links=
	*[http://www.bailopan.net/table_dump.txt Sample CS:S Network Property Dump]		*[http://www.bailopan.net/table_dump.txt Sample CS:S Network Property Dump]
		+
		+	[[Category:SourceMod Development]]

← Older revision		Revision as of 16:23, 26 March 2007
Line 112:		Line 112:

	However, CBaseEntity is ultimately mod specific. Even if it's rare that its position in the virtual table will change, care should be taken to ensure cross-mod compatibility. It is incorrect to assume that calling this function will result in the same behaviour on every mod.		However, CBaseEntity is ultimately mod specific. Even if it's rare that its position in the virtual table will change, care should be taken to ensure cross-mod compatibility. It is incorrect to assume that calling this function will result in the same behaviour on every mod.
		+
		+	An example of a data map being declared can be found in <tt>dlls/player.cpp</tt>:
		+	<cpp>BEGIN_SIMPLE_DATADESC( CPlayerState )
		+	// DEFINE_FIELD( netname, FIELD_STRING ), // Don't stomp player name with what's in save/restore
		+	DEFINE_FIELD( v_angle, FIELD_VECTOR ),</cpp>

@@ Line 14: / Line 14: @@
 Network properties deal with properties that must be transmitted over the network.  There are four pieces to this:
 *Network variables, which handle marking offsets in memory as changed.
-*Send properties, which describe how offset properties should be networked.
+*Send properties, which describe how the memory/data at the offset should be networked.
-*Send tables, also called data tables, which contains a list of send properties.
+*Send tables, also called data tables, which contain lists of send properties.
 *Server classes, which contain all of the send tables an entity needs for networking.
@@ Line 93: / Line 93: @@
 Because server classes can be enumerated without the instantiation of a given object/entity, send property lookup can be resolved at load time.  Even if it needs to be done at run-time, it can be easily optimized given this linear structure.
 =Data Maps=

← Older revision		Revision as of 01:22, 26 March 2007
Line 263:		Line 263:
	(int )((char *)pEntity + offset) = health;		(int )((char *)pEntity + offset) = health;
	}</cpp>		}</cpp>
		+
		+
		+	=External Links=
		+	*[http://www.bailopan.net/table_dump.txt Sample CS:S Network Property Dump]

@@ Line 98: / Line 98: @@
 Data maps are properties which are enumerated for save/restore mechanisms.  They are less complicated than send properties, but more mod-specific.
-''Important Headers'': <tt>public/datamap.h</tt>
+'''Important Headers''': <tt>public/datamap.h</tt>
 Data maps are encapsulated in a structure called <tt>datamap_t</tt>.  This structure contains the following information: