I have question:
How about resourcetool? Is there any way to bypass this detect?
How about resourcetool? Is there any way to bypass this detect?
i don't think you can bypass it via memory because the old clients are disconnecting aswel so my guess is that it is serversidedQuote:
For sure, yes. It can be bypassed from the memory. But it don't think it will be public for now.
People seem to be use old clients for that and old clients may not work if the devs change stuff and make the packets incompatible for that client in future.
KRS4 has the same security checks like 2 months ago and it can be bypassed from either memory or the way you've just mentioned. But the system works kinda differently in KR, it dcs you on somewhere else. I dunno how they did implement it into EU client. :rolleyes:Quote:
Stupid or srsly just unknown? Yes it is serversided but for fck says it can be bypassed easily in the "Memory". Its just a hash that the client send to the server. Just send the original hash with modded res and everything is fine.
copy & paste with half of the code from KR? :awesome:Quote:
KRS4 has the same security checks like 2 months ago and it can be bypassed from either memory or the way you've just mentioned. But the system works kinda differently in KR, it dcs you on somewhere else. I dunno how they did implement it into EU client. :rolleyes:
There are no half code for it. You can wait someone to find 'n release a bypass for it or replace & use the old client below. Also i'm not sure if the function is same as EU's one since i only use it for KR.Quote:
copy & paste with half of the code from KR? :awesome:
well the half code thing was meant as a joke but i'll try it thanksQuote:
There are no half code for it. You can wait someone to find 'n release a bypass for it or replace & use the old client below. Also i'm not sure if the function is same as EU's one since i only use it for KR.
[Only registered and activated users can see links. Click Here To Register...]