-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
idRO Classic: Poseidon is no longer usable since the latest patch (GameGuard update) #3964
Comments
any solution for this update game guard sir |
Hi @helpwillbetter , thanks for the response! So please, instead of begging for a solution, help us to find any clue or information to solve this. FYI, we don't have an active supporter for idRO Classic(see the Status of botting on Official Servers table), so now it's up to us to solve this, and please be patient. |
Try this solution Here |
hello @tricell17 still same i cant use poseidon did your openkore works now sir ? after following thats solution ? |
@tricell17 bro can help us to solve this openkore? thanks bro |
already solve |
all hail tricell |
------------------ Openkore Issues Template ------------------
Openkore version git: feature/idro-support
Server: idRO Classic
Bug Report / Feature Request: Poseidon is no longer usable since the latest update (GameGuard update). Opening Poseidon caused "no msg" error message and ended up not responding, then Openkore lost the connection to Poseidon.
Summary: Looks like the GameGuard detects the IP and PORT changes of
data.grf
, then immideately throw "no msg" error message.** Based on some discussion on going, mapping the PORT from the original data.grf (ragexe.exe) could be potentially solve this issue, since we don't need to change data.grf to use Poseidon. But we have limitation technical capability to solve this issue.
Would you mind to help us?
Thank you!
The text was updated successfully, but these errors were encountered: