feat(lab): add isolated Tibia Global login analysis project - #284
feat(lab): add isolated Tibia Global login analysis project#284blakinio wants to merge 25 commits into
Conversation
|
Closing as superseded for the current OTCLIENT-TIBIA-RE programme. The canonical live path is the official CipSoft Linux client on PR #48; this OTClient-as-game-client lab remains preserved as historical HTTP-login evidence and must not consume the dedicated runner during the official-client phase. |
|
Coordination correction from the owner, 2026-08-13: this PR is Track B only ( |
|
Track B checkpoint (native Linux only): exact head |
2b184f8 to
281a9d4
Compare
|
Track B cross-track oracle checkpoint (2026-08-14) Repository evidence review is now persisted at Key correction: Track A exact-SHA evidence ( Decision: before another official-service E2E solely for the full-version hypothesis, obtain/consume a non-secret exact-SHA structural contract from the official |
69f9f0f to
154277e
Compare
154277e to
fd39cef
Compare
Track B — OTClient to Tibia Global compatibility
This PR is the active implementation lane for Track B
otclient-global-login/OTCLIENT-GLOBAL-LOGINonly.It is not the
OTCLIENT-TIBIA-REofficial-client reverse-engineering lane and must not take ownership of Track A tasks, PRs, runtime bridge/worldmap work, containers, state directories or mutable paths.Objective
Prove whether this
blakinio/otclientfork can authenticate to and enter official Tibia Global using the repository-ownedsynology-otclient-01runner.Scope
tools/tibia-global-login-lab/**;.github/workflows/tibia-global-login-lab.ymlon[otclient, synology];Repository and research boundary
All material work, decisions, checkpoints, failure classification and next actions for this track stay in
blakinio/otclient. Do not search, read, cite, reference or depend on Oteryn repositories/runners/containers for normal continuation. Missing facts areUNKNOWNand must be recovered inside this Track B lane.Track A
official-client-re/OTCLIENT-TIBIA-REremains independent and owns analysis of the official Linux Tibia client runtime, protocol, structural game state, native actions, worldmap/OTBM evidence and stable bridge.The two tracks may share
synology-otclient-01only with isolated task-owned container names, volumes, state, displays and loopback ports; no cross-track cleanup or process control is allowed.Durable state
Current acceptance, live evidence and exact
next_actionare tracked in:docs/agents/tasks/active/OTC-20260813-tibia-global-login-lab.mdwhile this PR remains active. Resolve it from branch
feat/OTC-20260813-tibia-global-login-laband revalidate the live PR head before continuation.2026-08-14 cross-track oracle correction
Read
tools/tibia-global-login-lab/evidence/official-1532-game-login-oracle.mdbefore continuing game-wire experiments. It records the historical exact-SHA Track A oracle and corrects the earlier inference that successful HTTPS use of a full package build string proves the same full string is required on the game socket.Do not spend another official-service E2E solely on a full-version hypothesis; consume only promoted, non-secret exact-version/wire evidence and compare it with
ProtocolGame::sendLoginPacket().No proprietary Tibia binaries/assets, account credentials, cookies or session keys are committed or uploaded. No OCR/Tesseract is part of the semantic proof path.
2026-08-23 current invocation checkpoint
The branch was rebuilt as one current-main child while preserving all unrelated main changes. The workflow now refreshes current assets through WARP, re-verifies the exact-head OTClient binary across container recreation, uses current HTTP package identity
15.32.bf29ac, and does not assume a full build string on the game wire.The lab workflow path filter no longer includes the task-record path, so a later task-only checkpoint cannot silently schedule a second secret-bearing E2E.
Per the repository anti-stall budget, the exact-head workflow was checked twice while unchanged and remained pending. Do not perform an identical third polling loop in this invocation. The next fresh continuation action is to inspect run
32655026407; if complete, consume its redacted markers/logs. If it repeats structured opcode0x14, do not retry the same E2E and require a promoted current-build final queue/wire contract before any protocol mutation.