GreenHouse wrote: ↑Sat Jul 04, 2020 3:54 am
Slade wrote: ↑Sat Jul 04, 2020 2:55 am
The Always 5x Speed has changed code and is no longer compatible with the table as posted.
Updated code that should work if dropped in and replaced.
I need to click 3-4 times for it to work, that's because the routine isn't triggered until you get the value pushed to [RSI+8C] above 0. This takes a few clicks.
Use this one in that case:
Code: Select all
<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
<CheatEntries>
<CheatEntry>
<ID>269</ID>
<Description>"Always at x5 Speed (Click Once If It Doesn't Change)"</Description>
<LastState/>
<VariableType>Auto Assembler Script</VariableType>
<AssemblerScript>[ENABLE]
//NitroPanel:Update+48e
aobscanregion(get_Nitro,NitroPanel:Update+300,NitroPanel:Update+520,F3 0F 11 AE 88 00 00 00 F3 0F 10 86 88 00 00 00)
alloc(newmem,$1000)
label(code)
label(return)
newmem:
code:
mov [rsi+00000088],(float)100
jmp return
get_Nitro:
jmp newmem
nop 3
return:
registersymbol(get_Nitro)
[DISABLE]
get_Nitro:
db F3 0F 11 AE 88 00 00 00
unregistersymbol(get_Nitro)
dealloc(newmem)
</AssemblerScript>
</CheatEntry>
</CheatEntries>
</CheatTable>
Did you test this ? If not, it appears you're pushing a value to the wrong location.
Hence why I posted the code I did. Try watching that address to see what happens now.
Your code no longer exists, like I said, it's changed.
[Link]
Your code is not going to work. Your scan range is outside of the actual location you're searching for.
You start scanning at +520, but the routine you're trying to influence starts at +48e.
[Link]
Just to point out the obvious. If we watch the instruction you're referencing, and then click like crazy (using an auto clicker - I'm lazy), this is what happens.
[Link]
Nothing.
Just paste the code I provided into your cheat table. It works fine.
edit
Ok, interesting. That last picture is wrong. Not sure why, but it took me going to full boost and letting it drop to nothing for the routine to work.
Either way, your new code still isn't going to work correctly, as your constrained search misses the actual location you're trying to find.
So apologies for the last pic.
[Link]