ScriptParseTree Asset - Revision history

BullyWiiPlaza: /* Using Animtree Section */

2015-11-16T20:20:59Z

Using Animtree Section

← Older revision		Revision as of 20:20, 16 November 2015
Line 48:		Line 48:
	The include section is probably the easiest section to reverse. Each include exists as a single integer which holds the offset of the include's string in the buffer.		The include section is probably the easiest section to reverse. Each include exists as a single integer which holds the offset of the include's string in the buffer.
	=== Using Animtree Section ===		=== Using Animtree Section ===
	Although this section doesn't follow the include section, it is what needs to be dumped second. When a GSC wants to directly access ~~and~~ animtree, then the following code is added (for animtree "mp_vehicles")		Although this section doesn't follow the include section, it is what needs to be dumped second. When a GSC wants to directly access an animtree, then the following code is added (for animtree "mp_vehicles")
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	#using_animtree( "mp_vehicles" );		#using_animtree( "mp_vehicles" );
Line 74:		Line 74:
	</syntaxhighlight>		</syntaxhighlight>
	XRefs are explained in better detail in the code section. Each animtree thats included will have an GSC_ANIMTREE_ITEM struct, and every time an animation is used it will be defined in the references.		XRefs are explained in better detail in the code section. Each animtree thats included will have an GSC_ANIMTREE_ITEM struct, and every time an animation is used it will be defined in the references.

	=== StringTable Reference Section ===		=== StringTable Reference Section ===
	The stringtable reference section not only defines any function arguments that are defined with function declarations, but any local variable a function might create. Although they are defined the same, the difference between the two is highlighted in the code section. This section maps instances in code of a string (whether it be an actual string, or a literal name) to the string itself in the stringtable. Each reference will be defined as follows		The stringtable reference section not only defines any function arguments that are defined with function declarations, but any local variable a function might create. Although they are defined the same, the difference between the two is highlighted in the code section. This section maps instances in code of a string (whether it be an actual string, or a literal name) to the string itself in the stringtable. Each reference will be defined as follows

Red-EyeX32: /* OP_GetHash */

2014-12-27T20:44:13Z

OP_GetHash

← Older revision		Revision as of 20:44, 27 December 2014
Line 517:		Line 517:
	unsigned int hash = 5381;		unsigned int hash = 5381;

	while (*~~str~~ != 0)		while (*dvar != 0)
	hash = (33 * hash) + tolower(*~~str~~++);		hash = (33 * hash) + tolower(*dvar++);

	return hash;		return hash;

CraigChrist8239 at 00:23, 21 December 2014

2014-12-21T00:23:53Z

Show changes

Kokole: /* Executable Data */

2014-12-20T19:12:44Z

Executable Data

Show changes

Kokole at 19:11, 20 December 2014

2014-12-20T19:11:48Z

← Older revision		Revision as of 19:11, 20 December 2014
Line 8:		Line 8:
	const char *name;		const char *name;
	int len;		int len;
	~~const~~ char *buffer;		char *buffer;
	};		};
	</syntaxhighlight>		</syntaxhighlight>

Kokole at 19:10, 20 December 2014

2014-12-20T19:10:29Z

← Older revision		Revision as of 19:10, 20 December 2014
Line 15:		Line 15:
	#define GSCMagic = 0x804753430D0A0006		#define GSCMagic = 0x804753430D0A0006

	~~struct GSCHeader~~
	{
	~~__int64 magic;~~
	~~int unknown1;~~
	~~unsigned int includeSectionOffset;~~
	~~unsigned int usingAnimtreeSectionOffset;~~
	~~unsigned int executionDataSectionOffset;~~
	~~unsigned int argumentSectionOffset;~~
	~~unsigned int functionDeclSectionOffset;~~
	~~unsigned int callFunctionSectionOffset;~~
	~~//Sections that do not exist point to the next section.~~
	~~//The next two, for the last time, are most likely NOT the gsc's total size, repeated twice.~~
	~~//There is most likely a section that I am missing, that has probably never been used.~~
	~~//- CraigChrist8239~~
	~~char unknown2[0xC];~~
	~~unsigned short nameOffset;~~
	~~unsigned short totalArgumentCount;~~
	~~unsigned short functionDeclCount;~~
	~~unsigned short callFunctionCount;~~
	~~int unknown3;~~
	~~byte includeSectionCount;~~
	~~byte usingAnimtreeCount;~~
	};

	~~BO2 PDB VERSION:~~
	struct GSC_IMPORT_ITEM		struct GSC_IMPORT_ITEM
	{		{
Line 49:		Line 24:
	};		};

	~~/* 4301 */~~
	struct GSC_ANIMNODE_ITEM		struct GSC_ANIMNODE_ITEM
	{		{
Line 56:		Line 30:
	};		};

	~~/* 4302 */~~
	struct GSC_STRINGTABLE_ITEM		struct GSC_STRINGTABLE_ITEM
	{		{
Line 64:		Line 37:
	};		};

	~~/* 4303 */~~
	struct GSC_ANIMTREE_ITEM		struct GSC_ANIMTREE_ITEM
	{		{
Line 73:		Line 45:
	};		};

	~~/* 4304 */~~
	struct GSC_PROFILE_ITEM		struct GSC_PROFILE_ITEM
	{		{
Line 80:		Line 51:
	};		};

	~~/* 4305 */~~
	struct GSC_EXPORT_ITEM		struct GSC_EXPORT_ITEM
	{		{
Line 90:		Line 60:
	};		};

	~~/* 4306 */~~
	struct GSC_FIXUP_ITEM		struct GSC_FIXUP_ITEM
	{		{

Kokole at 11:55, 20 December 2014

2014-12-20T11:55:46Z

@@ Line 40: / Line 40: @@
 BO2 PDB VERSION:
 struct GSC_OBJ
+{

Kokole at 11:54, 20 December 2014

2014-12-20T11:54:16Z

@@ Line 37: / Line 37: @@
    byte includeSectionCount;
    byte usingAnimtreeCount;
 };
 </syntaxhighlight>

CraigChrist8239 at 05:39, 7 August 2014

2014-08-07T05:39:21Z

← Older revision		Revision as of 05:39, 7 August 2014
Line 222:		Line 222:
	OP_getdvarint = 0x69,		OP_getdvarint = 0x69,
	OP_getdvarfloat = 0x6A,		OP_getdvarfloat = 0x6A,
			OP_getdvarvec3d = 0x6B,
	OP_getdvarred = 0x6C,		OP_getdvarred = 0x6C,
	OP_getdvargreen = 0x6D,		OP_getdvargreen = 0x6D,

CraigChrist8239 at 02:27, 7 August 2014

2014-08-07T02:27:16Z

← Older revision		Revision as of 02:27, 7 August 2014
Line 222:		Line 222:
	OP_getdvarint = 0x69,		OP_getdvarint = 0x69,
	OP_getdvarfloat = 0x6A,		OP_getdvarfloat = 0x6A,
			OP_getdvarred = 0x6C,
			OP_getdvargreen = 0x6D,
			OP_getdvarblue = 0x6E,
	OP_GetFirstArrayKey = 0x70,		OP_GetFirstArrayKey = 0x70,
	OP_GetNextArrayKey = 0x71,		OP_GetNextArrayKey = 0x71,
Line 536:		Line 539:
	==== OP_getdvarfloat ====		==== OP_getdvarfloat ====
	This is a simple 1 byte opcode that is added to the stack once its read. It is used for the "getDvarFloat()" function. The next entity on the stack is the dvar to get, typically an OP_GetHash for the dvar's hash.		This is a simple 1 byte opcode that is added to the stack once its read. It is used for the "getDvarFloat()" function. The next entity on the stack is the dvar to get, typically an OP_GetHash for the dvar's hash.

			==== OP_getdvarred ====
			This is a simple 1 byte opcode that is added to the stack once its read. It is used for the "getDvarRed()" function to grab the red component of a color dvar. The next entity on the stack is the dvar to get, typically an OP_GetHash for the dvar's hash.

			==== OP_getdvargreen ====
			This is a simple 1 byte opcode that is added to the stack once its read. It is used for the "getDvarGreen()" function to grab the green component of a color dvar. The next entity on the stack is the dvar to get, typically an OP_GetHash for the dvar's hash.

			==== OP_getdvarblue ====
			This is a simple 1 byte opcode that is added to the stack once its read. It is used for the "getDvarBlue()" function to grab the blue component of a color dvar. The next entity on the stack is the dvar to get, typically an OP_GetHash for the dvar's hash.

	==== OP_GetFirstArrayKey ====		==== OP_GetFirstArrayKey ====