Can't bot anymore after client update

[koukou2]

Well I could bot few days ago, but after a recent update I can't anymore.
-> recvpackets.txt is fine , I used PEEK, version and master_version seem good for me. Maybe my serverType isn't good but I'm using the latest one available on openKore and it worked few days ago.






Following guide it seems I should use a more recent serverType but how to upgrade openKore for this one :



1 December 2013's update, last one available on openKore : kRO_RagexeRE_2013_08_07a.

Does it mean they just add a protection? Should I use poseidon?

Thanks for helping.

[koukou2]

Up, can someone explain me compatibility between kRO_RagexeRE_2013 and recent private server.
And how to use XCore (GUI) (configuration) comparing to openKore ?

[slashGG]

^
They modified their client.. Try to extract again their RECVPACKETS and find the SERVER Info again... If it has no Gameguard probably you can still bot. Hope so

[koukou2]

Nop, still same error, Can charBlockSize provoke this error?

[kevin_kebz021]

Well I could bot few days ago, but after a recent update I can't anymore.
-> recvpackets.txt is fine , I used PEEK, version and master_version seem good for me. Maybe my serverType isn't good but I'm using the latest one available on openKore and it worked few days ago.






Following guide it seems I should use a more recent serverType but how to upgrade openKore for this one :



1 December 2013's update, last one available on openKore : kRO_RagexeRE_2013_08_07a.

Does it mean they just add a protection? Should I use poseidon?

Thanks for helping.

Sir, can i ask you? after you use the !PE Viewer, and then you save the file where can i see the saved file in !PE Viewer? Sorry for questioning you because i'm a newbie

[4epT]

see this:
http://forums.openkore.com/viewtopic.ph ... 43#p269743

[koukou2]

@kevin_kebz021 : I just followed the guide.

@4epT : Thank you for your answer. My serv config is good except clienthash. How do you obtain it?
From your guide it should be 040298a8402f00f418532af7eb2790e8b31b, shouldn't it ?

Ok so we have to hash ids client side.