Originally posted by TheRealVate
well just be careful because the antiban DID get hotfixed so its not stable like normal, a lot of people complaining about all eboot's right now and we pretty much all have the same offsets due to us all updating the same offsets since they've been released, I am trying to find a fix and as soon as I do you all will be the first to know
You might want to double check to see if the bytes are the same as the last few builds. A minor change in code can influence the use of whichever registers are used during that build. That's all pretty much determined by the compiler.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.