OllyDBG & CO

always dc client after patch 5076 and i upgrade Co YETI tool i still face same problem dc , i need help

Quote:

Originally Posted by ace_heart always dc client after patch 5076 and i upgrade Co YETI tool i still face same problem dc , i need help

Not if u use my loader or multi :)

i try many exe , i try exe by _fobos_ and UCo exe and same result dc
i think a problem from TQ to give result invalid jump / invalid walk
Dr Yeti learn me how can update his tool and i do all goods and for 2 days i try to find good
memory addresses to keep speed without dc but all same
note: original exe for TQ is dc and give invalid jump / invalid walk

Quote:

Originally Posted by ace_heart i try many exe , i try exe by _fobos_ and UCo exe and same result dc i think a problem from TQ to give result invalid jump / invalid walk Dr Yeti learn me how can update his tool and i do all goods and for 2 days i try to find good memory addresses to keep speed without dc but all same note: original exe for TQ is dc and give invalid jump / invalid walk

Fine, ill update my multi so it wont d/c on walk,
Seriously it works perfectly for jumping.
unless you run around, Ill fix the running too.

edit: alright, added so it wont d/c on running aswell,
i kind of liked the idea that people could only use speed to jump lol

Quote:

Originally Posted by clipper _fobos_, unfortunately i can't use your multi because i play the spanish version. Give us a clue where this problem. There are more calls to gettime? There are some later validation that can be modified on the client? we must relocate the code where they do not bother? we have to find the push of error (strres.ini) to patch too? Tell us the direction that we move :rolleyes:

BP them all and start eliminating ^_^

GW Gate/Wall Jump:
search for/all referenced text strings "MsgAction.cpp"
double click the very last one(below "Mine")
nine lines below you should see(the address could be different)
all we need to do is double click and change the "MOV EBX,DWORD PTR DS:[EBX+3C]"
into "JMP 004D6A54" making sure fill with NOP's is checked it should end up something like:
save as normal and bobs your uncle.
Im not sure if this is the right way to go about it but it works fine for me.
Im also not sure but you may have to of edited the high wall jump
explained here [Only registered and activated users can see links. Click Here To Register...]
oh and also a big thank you to *M* for releasing some source.

I personally never wanted to release the GW walljump, this way I could "control" the cheating on pvp places a little bit. (Even that I explained how to do various things I dislike people who cheat on PvP)

But yah.. Nice guide. :P (If it works, haven't tested.)

well i figured seeing as *M* released some source that kinda just led me right to it
I didnt think it would hurt to much and i dont like the idea of only proxy users having it easy.
anyhow i can remove it if you wish, its not like its the modded exe.

Currently I zero out 3deffect.ini and 3deffectobj.ini for TG clients, removing all effects to reduce lag. That worked fine until 5076, then it seems TQ started making use of the debug folder and I now have error logs reaching 2+ GB per day containing error reports about missing effects, etc. My question is, how to disable the error log creation via NOPing some code or whatever. I tried NOPing out the code where it opens/appends data to the file, tried changing the method it uses to open the file (from a+ to r). It stil manages to create and append to teh file.

Any clues anyone?

Quote:

Originally Posted by tanelipe I personally never wanted to release the GW walljump, this way I could "control" the cheating on pvp places a little bit. (Even that I explained how to do various things I dislike people who cheat on PvP) But yah.. Nice guide. :P (If it works, haven't tested.)

I agree :p

They can add the settings for to use COSpeed?

Please I need it:)

Translated with google, I speak Spanish.

Quote:

Originally Posted by daveq Currently I zero out 3deffect.ini and 3deffectobj.ini for TG clients, removing all effects to reduce lag. That worked fine until 5076, then it seems TQ started making use of the debug folder and I now have error logs reaching 2+ GB per day containing error reports about missing effects, etc. My question is, how to disable the error log creation via NOPing some code or whatever. I tried NOPing out the code where it opens/appends data to the file, tried changing the method it uses to open the file (from a+ to r). It stil manages to create and append to teh file. Any clues anyone?

JMP it, don't NOP it

Quote:

Originally Posted by Ian* JMP it, don't NOP it

Good idea ..+thanks, however I found an easier way...simply comment out a few lines in one of the ini files :)