Leaderboard

New version 9.6.0.1.5 released!

If you want the gold hack then search the amount of gold you have (memory region Anonymous & dword). Keep refining until you have 1 value. Then if you Goto that address the line below it is 0. Make that 99 and freeze it.

New version 9.6.0.2.2 released!

New version 9.6.0.4.9 released!

Without a doubt, your support for those who like and play RR3 is important. Thanks again.

You are welcome, also Yes! you could learn C++ and Java so you could learn modding with lgl (template isn't for newbies) Learn java. then C++ then you should sign up on the polar mods forums after you are done with both. just learn the basics then you could learn the hooking, hex patching API Library they have Have a nice Day!

New version 9.6.0.4.5 released!

New version 9.6.0.3.6 released!

New version 9.6.0.3.5 released!

I'm not sure if this is any help to you. If you watch my recording you'll see the coin amount is huge and even when it goes back to zero I can continue buying. https://sbupload.com/36e1ec13b1ea3bae

I have an updated Room Id file the old ones are the same 0 - 162 is the old stuff, 163 - 217 are Altars. OH BOI, THAT'S A LOT OF ALTARS!!! 218 - 220 are abyssal shard, crystal and portal Dungeon Maker Updated Room Ids.txt

Gathering information about GG errors (#5ojwyhci)

Let me explain this real quick. How they load offset, and calculate address ? Explanation: * PC = (Current Instruction Address + 0x8) 00000000 LDR R0, [PC, 0x1C]; Its calculated like this, R0 = (PC:00000008 + 0x1C = 00000024). Read val at 00000024 which is 0x14, then put into R0. 00000004 ADD R0, PC, R0 ; Again, R0 = (PC:0000000C + 0x14 (Offset) = 00000020) 00000008 MOV R1, #0x1234; Move 0x1234 into R1 0000000C STR R1, [R0]; Store R1:0x1234 value into R0:00000020 address. 00000010 BX LR; Jump into LR (LR is register that store address of this function caller.) 00000014 ALIGN 0x10 00000020 MyValue DCD 0x0 00000024 Offset DCD 0x14 You can find lot of information here, The ARM instruction set

This is how the ARM architecture works. Most addresses are not absolute, but relative, relative to the PC. This is done to save space in instructions. The instruction size is 4 bytes. The size of the 32-bit pointer is also 4 bytes. An absolute address almost always requires 4 bytes, since the code can be located in different places. A relative address can be encoded with 2 or 3 bytes. This will give the opportunity to refer to the memory near the code, where this code would not be located. And since .bss is not far from .code (.text), this is enough.

0000 LDR R3, =(dword_36BD38 - 0x19D86C) -- Load offset to R3 0004 ADD R3, PC, R3 ; dword_36BD38 -- R3 = PC + Offset (R3) 0008 CMP R0, #0 -- Check if R0 value equal to 0 000C STR R0, [R3] -- Store R0 value into R3 (R3 = dword_36BD38) 0010 MOVLT R2, #0x7FFFFFFF -- If R0 value less than 0, then put (0x7FFFFFFF) 2147483647 into R2. 0014 STRLT R2, [R3] -- If R0 value less than 0, then store R2 value which is 2147483647, into R3 (R3 = dword_36BD38) Conclusion is, if R0 value less than 0.. then put 2147483647 into bss:dword_36BD38. Anyway, if you not understand about the logic. F5 hotkey may come handy.