ScriptFile Asset - Revision history

Aerosoul94: /* XBOX & PS3 */

2015-02-03T15:16:07Z

XBOX & PS3

← Older revision		Revision as of 15:16, 3 February 2015
Line 346:		Line 346:
	=== Ghosts ===		=== Ghosts ===
	The opcodes for Ghosts do the exact same thing as the Modern Warfare 3 opcodes, only their values seem to be scrambled in some way.		The opcodes for Ghosts do the exact same thing as the Modern Warfare 3 opcodes, only their values seem to be scrambled in some way.
	==== XBOX & PS3 ====		==== XBOX & PS3 & Wii U ====
	<source lang="cpp">		<source lang="cpp">
	#define OP_CastFieldObject 0x1D		#define OP_CastFieldObject 0x1D
Line 502:		Line 502:
	#define OP_bit_ex_or 0xB5		#define OP_bit_ex_or 0xB5
	</source>		</source>

	==== PC ====		==== PC ====
	<source lang="cpp">		<source lang="cpp">

Therifboy at 13:57, 28 January 2015

2015-01-28T13:57:28Z

Show changes

Therifboy: /* OP_AddArray */

2015-01-27T19:40:06Z

OP_AddArray

← Older revision		Revision as of 19:40, 27 January 2015
Line 687:		Line 687:
	</syntaxhighlight>		</syntaxhighlight>
	=== OP_AddArray ===		=== OP_AddArray ===
	This opcode ~~adds the value on top~~ of ~~the stack~~ to ~~the~~ array ~~on the second place on the stack~~. ~~It is used to initialize arrays with known values~~, ~~most likely with curly brackets e.g~~.:		This opcode is used to append an object of any type to an array. When initializing a new array, it starts off from an empty one.
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	array = { 0, 1 };		array = [ 0, 1 ];
	</syntaxhighlight>		</syntaxhighlight>
	The asm:		The asm:
Line 700:		Line 700:
	OP_SetNewLocalVariableFieldCached0 0		OP_SetNewLocalVariableFieldCached0 0
	</syntaxhighlight>		</syntaxhighlight>
	~~The second thing this~~ opcode can ~~do is append two arrays to each other. Note that it~~ is not supposed to be used like this.		This opcode can also build on another array, but is not supposed to be used like this.
	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">
	array2 = array + { 2.0, "3" };		array2 = array + [ 2.0, "3" ];
	</syntaxhighlight>		</syntaxhighlight>
	The asm:		The asm:
Line 713:		Line 713:
	OP_SetNewLocalVariableFieldCached0 1		OP_SetNewLocalVariableFieldCached0 1
	</syntaxhighlight>		</syntaxhighlight>

	=== OP_SetNewLocalVariableFieldCached0 ===		=== OP_SetNewLocalVariableFieldCached0 ===
	This creates a new local variable and then sets the ent on the stack as its value. The variable index is stored as a byte after the opcode.		This creates a new local variable and then sets the ent on the stack as its value. The variable index is stored as a byte after the opcode.

Aerosoul94: /* Operation Codes */

2015-01-18T09:46:52Z

Operation Codes

Show changes

Red-EyeX32: /* OP_CallBuiltin */

2014-12-30T16:18:50Z

OP_CallBuiltin

← Older revision		Revision as of 16:18, 30 December 2014
Line 659:		Line 659:
	</source>		</source>
	=== OP_CallBuiltin ===		=== OP_CallBuiltin ===
	These opcodes are used to make calls to native functions built into the game's executable. ~~Unline~~ methods, these functions do not pass any objects. For opcodes OP_CallBuiltin0 through OP_CallBuiltin5, the number it ends with is the number of parameters to be passed to the function. For OP_CallBuiltin, the number of parameters is loaded after the opcode as an 8 bit integer. The function id is then loaded as a 16 bit integer. That value is then used as an index in the function table below.		These opcodes are used to make calls to native functions built into the game's executable. Unlike methods, these functions do not pass any objects. For opcodes OP_CallBuiltin0 through OP_CallBuiltin5, the number it ends with is the number of parameters to be passed to the function. For OP_CallBuiltin, the number of parameters is loaded after the opcode as an 8 bit integer. The function id is then loaded as a 16 bit integer. That value is then used as an index in the function table below.
	{\| class="wikitable" class="article-table mw-collapsible mw-collapsed wikitable"		{\| class="wikitable" class="article-table mw-collapsible mw-collapsed wikitable"
	\|-		\|-
Line 1,859:		Line 1,859:
	\|0x124		\|0x124
	\|}		\|}

	=== OP_CallBuiltinMethod ===		=== OP_CallBuiltinMethod ===
	These opcodes are used to make calls to native methods built into the game's executable. Unlike functions, the methods must pass an object. For OP_CallBuiltinMethod0 - OP_CallBuiltinMethod5, the number it ends with is the number of parameters to be passed to the function. For OP_CallBuiltinMethod, the number of parameters is loaded after the opcode as an 8 bit integer. The method id is then loaded as a 16 bit integer. That value is then used as an index in the method table below.		These opcodes are used to make calls to native methods built into the game's executable. Unlike functions, the methods must pass an object. For OP_CallBuiltinMethod0 - OP_CallBuiltinMethod5, the number it ends with is the number of parameters to be passed to the function. For OP_CallBuiltinMethod, the number of parameters is loaded after the opcode as an 8 bit integer. The method id is then loaded as a 16 bit integer. That value is then used as an index in the method table below.

Aerosoul94: /* Code Section */

2014-12-30T13:06:45Z

Code Section

← Older revision		Revision as of 13:06, 30 December 2014
Line 24:		Line 24:
	At the beginning of each function, the linker loads a 32 bit value, which is the length of the function in the program section. Then it loads a 16 bit value which is the function id. If the id is equal to zero, then it will load a string after it, which is the name of the function. After this, the opcodes may begin to use the data section. The opcodes that use the data section are OP_GetAnimTree, OP_GetString, OP_GetIString, OP_GetAnimation, OP_GetFarFunction, OP_EvalLevelFieldVariable, OP_EvalAnimFieldVariable, OP_EvalSelfFieldVariable, OP_EvalFieldVariable, OP_EvalLevelFieldVariableRef, OP_EvalAnimFieldVariableRef, OP_EvalSelfFieldVariableRef, OP_EvalFieldVariableRef, OP_ClearFieldVariable, OP_SetLevelFieldVariableField, OP_SetSelfFieldVariableField, all the far call opcodes, and OP_endswitch.		At the beginning of each function, the linker loads a 32 bit value, which is the length of the function in the program section. Then it loads a 16 bit value which is the function id. If the id is equal to zero, then it will load a string after it, which is the name of the function. After this, the opcodes may begin to use the data section. The opcodes that use the data section are OP_GetAnimTree, OP_GetString, OP_GetIString, OP_GetAnimation, OP_GetFarFunction, OP_EvalLevelFieldVariable, OP_EvalAnimFieldVariable, OP_EvalSelfFieldVariable, OP_EvalFieldVariable, OP_EvalLevelFieldVariableRef, OP_EvalAnimFieldVariableRef, OP_EvalSelfFieldVariableRef, OP_EvalFieldVariableRef, OP_ClearFieldVariable, OP_SetLevelFieldVariableField, OP_SetSelfFieldVariableField, all the far call opcodes, and OP_endswitch.

	=== Code ~~Section~~ ===		=== Byte Code ===
	The ~~code section~~ is the actual compiled game script code.		The byte is the actual compiled game script code.

	== Operation Codes ==		== Operation Codes ==
	=== Modern Warfare 3 ===		=== Modern Warfare 3 ===

Therifboy at 12:24, 30 December 2014

2014-12-30T12:24:06Z

@@ Line 3,806: / Line 3,806: @@
 === OP_Script Pointer Calls ===
 These opcodes load a pointer from the stack and simply jump to them. For threaded calls (OP_ScriptThreadCallPointer - OP_ScriptMethodChildThreadCallPointer), the parameter count is loaded afterwards as an 8 bit integer.
 == Field IDs ==
 In Ghosts and AW, fields have been sorted alphabetically and were then enumerated. This way, fields starting with the letter a such as "alignx" have got the lowest field ids.

Aerosoul94 at 08:51, 30 December 2014

2014-12-30T08:51:10Z

Show changes

Aerosoul94: /* Operation Codes */

2014-12-29T16:57:11Z

Operation Codes

← Older revision		Revision as of 16:57, 29 December 2014
Line 138:		Line 138:
	#define OP_ScriptMethodCallPointer 0x6A		#define OP_ScriptMethodCallPointer 0x6A
	#define OP_ScriptThreadCallPointer 0x6B		#define OP_ScriptThreadCallPointer 0x6B
	#define OP_ScriptMethodChildThreadCallPointer 0x6C		#define OP_ScriptMethodChildThreadCallPointer 0x6C
	#define OP_ScriptMethodThreadCallPointer 0x6D		#define OP_ScriptMethodThreadCallPointer 0x6D
	#define OP_ScriptMethodChildThreadCallPointer 0x6E		#define OP_ScriptMethodChildThreadCallPointer 0x6E
	#define OP_CallBuiltinPointer 0x6F		#define OP_CallBuiltinPointer 0x6F
	#define OP_CallBuiltinMethodPointer 0x70		#define OP_CallBuiltinMethodPointer 0x70
	#define OP_DecTop 0x71		#define OP_DecTop 0x71
	#define OP_CastFieldObject 0x72		#define OP_CastFieldObject 0x72
Line 175:		Line 175:
	#define OP_size 0x8F		#define OP_size 0x8F
	#define OP_waittillmatch 0x90		#define OP_waittillmatch 0x90
	#define OP_waittillmatch2 0x91		#define OP_waittillmatch2 0x91 // nop
	#define OP_waittill 0x92		#define OP_waittill 0x92
	#define OP_notify 0x93		#define OP_notify 0x93
Line 266:		Line 266:
	#define OP_less_equal 0x4D		#define OP_less_equal 0x4D
	#define OP_jumpback 0x4E		#define OP_jumpback 0x4E
	#define ~~OP_NOP~~ 0x4F		#define OP_waittillmatch2 0x4F // nop
	#define OP_waittill 0x50		#define OP_waittill 0x50
	#define OP_notify 0x51		#define OP_notify 0x51
Line 307:		Line 307:
	#define OP_checkclearparams 0x76		#define OP_checkclearparams 0x76
	#define OP_EvalLocalVariableRefCached0 0x77		#define OP_EvalLocalVariableRefCached0 0x77
	#define OP_EvalNewLocalVariableRefCached0 0x78		#define OP_EvalNewLocalVariableRefCached0 0x78 // nop
	#define OP_EvalLocalVariableRefCached 0x79		#define OP_EvalLocalVariableRefCached 0x79
	#define OP_SetLevelFieldVariableField 0x7A		#define OP_SetLevelFieldVariableField 0x7A
	#define OP_SetVariableField 0x7B		#define OP_SetVariableField 0x7B
	#define OP_ClearVariableField 0x7C		#define OP_ClearVariableField 0x7C // nop
	#define OP_SetAnimFieldVariableField 0x7D		#define OP_SetAnimFieldVariableField 0x7D
	#define OP_SetSelfFieldVariableField 0x7E		#define OP_SetSelfFieldVariableField 0x7E

Aerosoul94: /* Data Section */

2014-12-29T16:40:54Z

Data Section

← Older revision		Revision as of 16:40, 29 December 2014
Line 15:		Line 15:
	};		};
	</source>		</source>
	=== ~~Data Section~~ ===		=== Buffer ===
	The ~~data section~~ is a zlib compressed section in which the compressed size is equal to ~~deflatedSize~~ and it's uncompressed size is equal to ~~inflatedSize~~.		The buffer is a zlib compressed section in which the compressed size is equal to compressedLen and it's uncompressed size is equal to len.

	This section of data is not needed during runtime. Before being executed, the linker runs through the ~~code~~ once and links the ~~data~~ and ~~code~~ section together so that all programs can be ran as one. It contains strings and function call info.		This section of data is not needed during runtime. Before being executed, the linker runs through the bytecode once and links the buffer and bytecode section together so that all programs can be ran as one. It contains strings and function call info.

	In order to be linked correctly, the ~~code~~ and ~~data~~ section must be read synchronously (e.g. when reading the OP_GetString opcode, the ~~data~~ pointer must be pointing to the string ready to be loaded). The linker does this by incrementing the ~~data~~ pointer each time it reads an opcode that uses it.		In order to be linked correctly, the buffer and bytecode section must be read synchronously (e.g. when reading the OP_GetString opcode, the buffer pointer must be pointing to the string ready to be loaded). The linker does this by incrementing the buffer pointer each time it reads an opcode that uses it.

	At the beginning of each function, the linker loads a 32 bit value, which is the length of the function in the program section. Then it loads a 16 bit value which is the function id. If the id is equal to zero, then it will load a string after it, which is the name of the function. After this, the opcodes may begin to use the data section. The opcodes that use the data section are OP_GetAnimTree, OP_GetString, OP_GetIString, OP_GetAnimation, OP_GetFarFunction, OP_EvalLevelFieldVariable, OP_EvalAnimFieldVariable, OP_EvalSelfFieldVariable, OP_EvalFieldVariable, OP_EvalLevelFieldVariableRef, OP_EvalAnimFieldVariableRef, OP_EvalSelfFieldVariableRef, OP_EvalFieldVariableRef, OP_ClearFieldVariable, OP_SetLevelFieldVariableField, OP_SetSelfFieldVariableField, all the far call opcodes, and OP_endswitch.		At the beginning of each function, the linker loads a 32 bit value, which is the length of the function in the program section. Then it loads a 16 bit value which is the function id. If the id is equal to zero, then it will load a string after it, which is the name of the function. After this, the opcodes may begin to use the data section. The opcodes that use the data section are OP_GetAnimTree, OP_GetString, OP_GetIString, OP_GetAnimation, OP_GetFarFunction, OP_EvalLevelFieldVariable, OP_EvalAnimFieldVariable, OP_EvalSelfFieldVariable, OP_EvalFieldVariable, OP_EvalLevelFieldVariableRef, OP_EvalAnimFieldVariableRef, OP_EvalSelfFieldVariableRef, OP_EvalFieldVariableRef, OP_ClearFieldVariable, OP_SetLevelFieldVariableField, OP_SetSelfFieldVariableField, all the far call opcodes, and OP_endswitch.