From 06c1bdeda0bf0be53b4d25c5f2ea071964dfdbb3 Mon Sep 17 00:00:00 2001 From: Sini Date: Mon, 3 Sep 2012 20:22:46 +0000 Subject: [PATCH] Update MediaWiki page 'Class Check' --- Class-Check.mediawiki | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/Class-Check.mediawiki b/Class-Check.mediawiki index 694975f..678efeb 100644 --- a/Class-Check.mediawiki +++ b/Class-Check.mediawiki @@ -1,5 +1,33 @@ The class check originated with the new Runescape engine update which took place around the 4xx revisions. It gives the Jagex servers the ability to check the modifiers, update, or fetch the value for a field. It also gives functionality to invoke a method with parameters and get it's return value, or check it's modifiers. Each of these functionalities are described with a request type. A class check request is built up with many of these request types. +== Request Types == + +{| border=2px +! Opcode +! Name +! Description +|- +! 0 +! Fetch Numeric Field +! Fetches the value of a numeric field. +|- +! 1 +! Update Numeric Field +! Updates the value of a numeric field. +|- +! 2 +! Get Field Modifiers +! Gets the modifiers of a field. +|- +! 3 +! Invoke Method +! Invokes a method and sends back its return object. +|- +! 4 +! Get Method Modifiers +! Gets the modifiers of a method. +|} + == Return Codes == All the return codes are in descending priority by numerical order. For opcode 0, there are cases where a numeric value is sent to the server on fetch requests. This value is always a dword. For a method invoke request, there isn't a value that is sent to the server. It is just assumed that there wasn't a return object from the invoked method.