Client error 28_3

i meant people like coder vb and stuff who aparrently stopped all client errors. @derh.acker
Please tell us if its in the cshell module

if you can stop client error 28_3 then you can stop all of them what is great you can make all of old good options

I don't understand why someone would want to keep something so vital to themselves. If we stop it, crossfire won't be able to make new ones. It may never be patched. Please help out a little @derh.acker
Idk if its even possible

No, most client errors are serversided.
This client error checks the value so every hack can get detected.
I'll keep it secret where it is.


Anti Hack tool also works without changing XTrap Files or editing memory.

So we need to find the function that chek's the value and kill it send it STFU right ? but i think we will never find it

another good idea make cshell fld your own value while keeping the original untouched

hm.. what you mean whit "fld" and it's even possible or it's only a new idea ?

FLD
/msg2short

That's what I tried first, but you'll have to search for references to every Offset.

you could make a jump to your own fld.
It would lead to somekind of hook.
but does it rly work?
aren't they checking for damages when hit?

The new client errors are clientsided.
The client errors which were added before this patch are serversided.

You don't need to hook it, you can also just modify it.
Allocate new memory, write some floats into it and change the FLD so it accesses the new memory.

but the jump hook would work right?

i'll try it.

I wish i was competent in asm T_T.
FLD completely confuses me.