Tutorial:Mono:Basic - Revision history

TheyCallMeTim13: /* Finding the Namespace */

2018-05-06T01:16:27Z

‎Finding the Namespace

TheyCallMeTim13 at 22:46, 5 May 2018

2018-05-05T22:46:33Z

TheyCallMeTim13: /* Finding the Namespace with script */

2018-05-05T21:17:18Z

‎Finding the Namespace with script

TheyCallMeTim13: /* Finding the Namespace */

2018-05-05T21:16:46Z

‎Finding the Namespace

TheyCallMeTim13 at 21:14, 5 May 2018

2018-05-05T21:14:15Z

TheyCallMeTim13 at 21:10, 5 May 2018

2018-05-05T21:10:26Z

TheyCallMeTim13 at 21:09, 5 May 2018

2018-05-05T21:09:19Z

TheyCallMeTim13: /* Working with Mono in scripts */

2018-05-05T21:07:17Z

‎Working with Mono in scripts

TheyCallMeTim13 at 20:59, 5 May 2018

2018-05-05T20:59:13Z

TheyCallMeTim13 at 13:08, 5 May 2018

2018-05-05T13:08:10Z

@@ Line 180: / Line 180: @@
 <br>
 === Finding the Namespace ===
-To find the ''Namespace'', we can use the find tool of the [[Mono:MonoDissect|Mono Dissect Form]], by searching for the class name and seeing what Namespace it's under.<br>
+We can use [[Mono:Lua:mono_getJitInfo|mono_getJitInfo]] with [[Mono:Lua:mono_method_getClass|mono_method_getClass]] in the Lua Engine to get the ''Namespace''.
 <pre>
 local mID = mono_getJitInfo(getAddress('PlayerStatsManager:TakeDamage')).method

@@ Line 2: / Line 2: @@
 [[Category:Tutorial]]
 [[Category:Mono]]
 {{DISPLAYTITLE:Mono Features}}
 So what are the Cheat Engine ''mono features''?

@@ Line 192: / Line 192: @@
 </pre>
 But this returns an empty Namespace, and it turns out ''[[Mono:Lua:mono_findMethod|mono_findMethod]]'' will tend to work with an empty Namespace.
-: Note: '''Most stuff in a Mono games will be in the ''Assembly-CSharp'' Namespace.'''
+: Note: '''Most stuff in Mono games will be in the ''Assembly-CSharp'' Namespace.'''
 <!-- == Find stuff with [[Mono:MonoDissect|Mono Dissect Form]] == -->
 {{MonoSeeAlso}}

@@ Line 179: / Line 179: @@
 <br>
 === Finding the Namespace ===
-To do that we need the ''Namespace'', ''Class'', and ''Method'' names, we have the ''Class'' and ''Method'' in the above code. We can use the find tool of the [[Mono:MonoDissect|Mono Dissect Form]] to find the Namespace by searching for the class name.<br>
+To find the ''Namespace'', we can use the find tool of the [[Mono:MonoDissect|Mono Dissect Form]], by searching for the class name and seeing what Namespace it's under.<br>
 [[File:Mono.Tutorial.MonoDissector.01.png||Mono Dissector form|border]]<br>
 [[File:Mono.Tutorial.MonoDissector.02.png||Mono Dissector form|border]]

@@ Line 13: / Line 13: @@
 I'll be using [https://wikipedia.org/wiki/Cuphead Cuphead].
+<br>
+<br>
 == Attaching to the process ==
 So if you attach to a Mono game then Cheat Engine initializes the Mono features and there will be a new ''Mono'' menu item in the Cheat Engine main form.
@@ Line 70: / Line 70: @@
 </pre>
+<br>
 == Working with Mono in scripts ==
 So let's say we already found health with traditional value scanning.
@@ Line 106: / Line 106: @@
 we can use '''[[Mono:Lua:mono_findMethod|mono_findMethod]]''' with '''[[Mono:Lua:mono_compile_method|mono_compile_method]]''' in the scripts.
+<br>
 === JIT the method ===
 You can JIT a method in the [[Mono:MonoDissect|Mono Dissect Form]] by right clicking on a ''selected method''.<br>
@@ Line 114: / Line 114: @@
 [[File:Mono.Tutorial.MonoDissector.03.JITed.png||JITed method|border]]
 ==== Scripted JITting ====
 Or we can setup a script to JIT the method.
@@ Line 145: / Line 146: @@
 With this we can just enable the script after the Mono features have been enabled.
+<br>
 === Make method only return ===
 We could also try to just make the method return with out doing any thing.<br>
@@ Line 176: / Line 177: @@
 </pre>
+<br>
 === Finding the Namespace ===
 To do that we need the ''Namespace'', ''Class'', and ''Method'' names, we have the ''Class'' and ''Method'' in the above code. We can use the find tool of the [[Mono:MonoDissect|Mono Dissect Form]] to find the Namespace by searching for the class name.<br>
@@ Line 182: / Line 183: @@
 [[File:Mono.Tutorial.MonoDissector.02.png||Mono Dissector form|border]]
 ==== Finding the Namespace with script ====
 Or we can use [[Mono:Lua:mono_getJitInfo|mono_getJitInfo]] with [[Mono:Lua:mono_method_getClass|mono_method_getClass]] in the Lua Engine to get the ''Namespace''.

@@ Line 104: / Line 104: @@
 for the above code we have to take damage.
 So how do we JIT the code,
-we can use '''[[Mono:Lua:mono_findMethod|mono_findMethod]]''' with '''[[Mono:Lua:mono_compile_method|mono_compile_method]]'''.
+we can use '''[[Mono:Lua:mono_findMethod|mono_findMethod]]''' with '''[[Mono:Lua:mono_compile_method|mono_compile_method]]''' in the scripts.

@@ Line 74: / Line 74: @@
 So let's say we already found health with traditional value scanning.
 If you have the Mono features enabled and setup an injection script then you will
-see an addresses like this "''PlayerStatsManager:TakeDamage+ABC''" instead of just a game plus offset address.<br>
+see addresses like this "''PlayerStatsManager:TakeDamage+ABC''" instead of just a game plus offset address.<br>
 [[File:Mono.Tutorial.Method.01.png||Take Damage Code|border]]

@@ Line 24: / Line 24: @@
 it needs to be called after attaching to the process (after the Mono features are initialized).
 <pre>--[============================================================[
-	Process			: Cuphead.exe
+    Process         : Cuphead.exe
-	Game Version	: 5.6.2.10718
+    Game Version    : 5.6.2.10718
-	CE Version		: 6.7
+    CE Version      : 6.7
 ]============================================================]--
 PROCESS_NAME = 'Cuphead.exe'
@@ Line 36: / Line 36: @@
 local autoAttachTimer = nil
 local function autoAttachTimer_tick(timer)
-	if autoAttachTimerTickMax > 0 and autoAttachTimerTicks >= autoAttachTimerTickMax then
+    if autoAttachTimerTickMax > 0 and autoAttachTimerTicks >= autoAttachTimerTickMax then
-		timer.destroy()
+        timer.destroy()
-	end
+    end
-	if getProcessIDFromProcessName(PROCESS_NAME) ~= nil then
+    if getProcessIDFromProcessName(PROCESS_NAME) ~= nil then
-		timer.destroy()
+        timer.destroy()
-		--openProcess(PROCESS_NAME)
+        --openProcess(PROCESS_NAME)
-		mono_OpenProcess(getProcessIDFromProcessName(PROCESS_NAME))
+        mono_OpenProcess(getProcessIDFromProcessName(PROCESS_NAME))
-		local InjectedMono = LaunchMonoDataCollector()
+        local InjectedMono = LaunchMonoDataCollector()
-		if InjectedMono and InjectedMono ~= 0 then
+        if InjectedMono and InjectedMono ~= 0 then
-			print(string.format('Mono Features Enabled: %X', InjectedMono))
+            print(string.format('Mono Features Enabled: %X', InjectedMono))
-		end
+        end
-	end
+    end
-	autoAttachTimerTicks = autoAttachTimerTicks + 1
+    autoAttachTimerTicks = autoAttachTimerTicks + 1
 end
 autoAttachTimer = createTimer(MainForm)
 autoAttachTimer.Interval = autoAttachTimerInterval
 autoAttachTimer.OnTimer = autoAttachTimer_tick
 </pre>
@@ Line 90: / Line 105: @@
 So how do we JIT the code,
 we can use '''[[Mono:Lua:mono_findMethod|mono_findMethod]]''' with '''[[Mono:Lua:mono_compile_method|mono_compile_method]]'''.
 === Finding the Namespace ===
@@ Line 96: / Line 112: @@
 [[File:Mono.Tutorial.MonoDissector.02.png||Mono Dissector form|border]]
 Or we can use [[Mono:Lua:mono_getJitInfo|mono_getJitInfo]] with [[Mono:Lua:mono_method_getClass|mono_method_getClass]] in the Lua Engine to get the ''Namespace''.
 <pre>
@@ Line 103: / Line 120: @@
 </pre>
 But this returns an empty Namespace, and it turns out ''[[Mono:Lua:mono_findMethod|mono_findMethod]]'' will tend to work with an empty Namespace.
 === JIT the method ===
-Then we can setup a script like this
+You can JIT a method in the [[Mono:MonoDissect|Mono Dissect Form]] by right clicking on a ''selected method''.<br>
 <pre>{$STRICT}
 define(bytes,89 47 60)
@@ Line 114: / Line 139: @@
 {$lua}
 if syntaxcheck then return end
-local mId = mono_findMethod('Assembly-CSharp', 'PlayerStatsManager', 'TakeDamage')
+if LaunchMonoDataCollector() ~= 0 then
---local mId = mono_findMethod('', 'PlayerStatsManager', 'TakeDamage') ---- This also works
+    local mId = mono_findMethod('Assembly-CSharp', 'PlayerStatsManager', 'TakeDamage')
-mono_compile_method(mId)
+    --local mId = mono_findMethod('', 'PlayerStatsManager', 'TakeDamage') ---- This also works
 {$asm}
@@ Line 124: / Line 151: @@
    nop
    nop
 ////
@@ Line 133: / Line 159: @@
    // mov [edi+60],eax
 </pre>
-Now with this we can just enable the script after the Mono features have been enabled.
+With this we can just enable the script after the Mono features have been enabled.
@@ Line 147: / Line 173: @@
 {$lua}
 if syntaxcheck then return end
-local mId = mono_findMethod('Assembly-CSharp', 'PlayerStatsManager', 'TakeDamage')
+if LaunchMonoDataCollector() ~= 0 then
---local mId = mono_findMethod('', 'PlayerStatsManager', 'TakeDamage') ---- This also works
+    local mId = mono_findMethod('Assembly-CSharp', 'PlayerStatsManager', 'TakeDamage')
-mono_compile_method(mId)
+    --local mId = mono_findMethod('', 'PlayerStatsManager', 'TakeDamage') ---- This also works
 {$asm}
@@ Line 155: / Line 183: @@
 PlayerStatsManager:TakeDamage:
    ret
 ////
@@ Line 166: / Line 193: @@
 {{MonoSeeAlso}}