OpenKore / OpenKore/openkore

idRO Classic, Poseidon cant work after Gameguard update

Open
#4,075 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Perl
Stars
1.5k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Describe the solution you'd like
Image

Openkore version : openkore-master from github

Server: idRO Classic

Feature Request: Poseidon server shows "no msg" window and dc , openkore dc after that.**

I have a little bit experience at Visual Basic when i was in high school.
Last Saturday i want to build a warp bot for GVG so i started try to set parameter in openkore.
I googled and found some informations at Openkore Official Forums (how to set a poseidon server for idRO classic server , poseidon.txt ,config.txt,
client.xml in data.grf ), openkore finally works.

But, after Gameguard update from last maintenance(8/21), the poseidon server doesnt work anymore.
I googled and find #3964 have a same problem in May, and looks like they solve it.
But the solution is in Openkore Official Forums and it's already dead now. dead solution

After that i try to change the ip and port of poseidon in data.grf ,and it doesnt works.
This seems to be relate to packets , and it's obviously beyond my knowledge

Can someone teach me or help me? So i can do it by myself when i meet the same situation again.

@alisonrag master of openkore please help me..

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #3964 and the referenced poseidon.txt, config.txt, and client.xml settings, then reproduce the Poseidon "no msg" window and disconnect after the GameGuard update. Done means identifying the changed packet or connection behavior and restoring compatibility for idRO Classic; the issue does not identify a source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
networking, reverse-engineering
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.