FearLess Cheat Engine

I get an instruction without offset (mov ebx, cbx etc.) so I can't trace further if it's something like mov ebx, [eax] then the offset is 0 eg. mov ebx, [eax+0] if it's more like mov ebx, eax then look up in the code to see where eax got it's value. Generally I prefer using assembly scripts over po...

http://fearlessrevolution.com/viewtopic.php?f=8&t=17 ? same rules as CEF, which are presumably there to keep any big game companies from getting particularly annoyed and going after the site. Also, many people don't appreciate others ruining their online game experience (even more so when you're pay...

None of these seem to work now

Make sure you're clicking the + next to the call and looking at the last instructions there, I imagine just having the call selected shows the registers at the time of the call (though I'm not certain). It's also possible that it simply reached the max instruction count before reaching the instructi...

yeah, completely different instructions/bytes. My guess is that "Terraria.UI.ItemSlot::MouseHover" is an overloaded function, meaning the same name is used for multiple functions that are distinguished by only by the types of the parameters... I don't really work with mono much so the best I can do ...

call qword ptr[xxxxxxx] is just calling a function using a 64 bit address. Most likely you had "step over" checked so CE didn't actually trace through all the instructions in that function, just ran it and then checked the stop condition, since it was true it stopped. So it was something in that fu...

TheByteSize wrote: ↑

Fri Sep 29, 2017 9:39 am

Is it possible to trace until a register become certain number?

Sure, just set the stop condition

Generally, backtrace. Meaning look at the code that's running using break+trace (or ultimap if you've got an Intel CPU that can use it) and see where that function is getting it's value from. Alternatively find a table/trainer that's doing what you want and see how it works (then try to figure out h...

You've got the basic idea there. To read a pointer path in assembly you have to do each offset separately (well I believe CE supports the combined format but it only calculates the address when you enable the script so if it changes that's useless because it'd still be using the old address after it...

without the createTimer object, sure you can use createThread and sleep to reimplement your own timer, but without the general idea of repeatedly checking it... no. At least not without hooking the assembly actual code that changes it and doing the check/assignment there but that's not necessarily l...

Fruitpunch wrote: ↑

Sat Sep 23, 2017 3:56 pm

Still it doesn't make sense why upon injection health goes to 0 or Nan when using add [ecx+118], (float)50 in the code.

Is there any way to get around this?

Hm, I just woke up but you're using fadd (or addss for x64 sse) not just the normal add, which works on integer values not floats, right?

Why I never! How dare you insinuate that such an upstanding community of people would have anything to do with such a thing as, as, that!

It's possible that once your health reaches 0 the game sets some other values that declare you as dead and checks those, moving 0 into your health if it considers you dead. Just a guess however.

sigh, not sure how that email got marked as spam but whatever, fixed now.

Yeah, you'll want to hook something that runs often like an access used to display health on the screen.