little tools, fewer interruptions.

POKEBRIDGE · LINUX X86-64 · CLIENT 34932

Your desktop still yours.

A local memory-and-packet bridge for the official PokeMMO client, with a desktop GUI, live party state and diagnostics. This repair build supports client 34932 with updated native layouts and packet mappings. It reads actual Disable restrictions, handles zero-ID turn events without inventing damage, and prevents an obsolete decoder from overwriting a newer client session. This build also recognizes the separate Pokémon summary and closes only its verified close button before resuming movement.

Development build, not a complete unattended Kanto playthrough. Bill’s S.S. Ticket exchange, Misty’s badge and the captain’s HM01 Cut receipt are live-verified. Teaching and using Cut, Mart restocking, PC transfers, later story choices and every gym puzzle are not implemented end to end. Catching and horde targeting still need complete live confirmation. Missing handlers remain visible; supported training can continue without pretending a story gate was cleared.

Install and start

  1. Use Linux x86-64 with a graphical desktop. This package targets the build machine’s current glibc; older distribution compatibility is unverified. Windows, macOS and Android packages are not included.
  2. Download and extract the entire archive. Keep PokeBridge, _internal, runtime, src, scripts, and linux together. Do not run from inside an archive viewer.
  3. Open the extracted folder and run ./PokeBridge. If your file manager stripped executable permissions, run chmod +x PokeBridge first. Python and Node are bundled; no separate installation is required.
  4. Choose Import ROM folder and supply your own legally obtained compatible ROMs. At least Black or White is required; FireRed is needed for the Kanto routing data used by this build. No ROMs or accounts are supplied.
  5. Choose Open / reconnect client, then log into the official client and your character there. An existing client must be relaunched through PokeBridge to load the local hook and relay.
  6. Choose an available automation mode and click Start automation. Use Stop automation to stop. Automation does not start just because you open the launcher.

What has been checked

Background operation and dialogue

The game can remain behind another application. Gameplay uses the client’s native memory/action paths and encrypted packet relay, not screenshots or desktop-wide keys. Dialogue confirmations stay inside the exact client. The computer must remain awake, the client open and the character connected. Minimized, locked-desktop and suspended operation are not certified.

Ordinary speech continues automatically while automation is running. Healing and the chosen Mt. Moon fossil use dedicated handlers. The fossil exchange still needs complete live confirmation. Yes/no and multi-option menus are not blindly confirmed: trades, releases, purchases and unknown story choices need specific support. Evolution is not canceled by generic confirmation spam.

Training, catching and recovery

The trainee leads before a wild encounter, then switches to a stronger finisher when needed. A trainee at or above the opponent’s level can fight directly with a damaging move and more than 35% HP; observed knockout risk, critical health or exhausted moves can still trigger a handoff. A prepared healthy gym squad can attempt the next badge before every unrelated trainee reaches the target; whole-party progress stays visible separately. Catch weakening compares the living party’s available moves and PP, aims for red HP, and can switch to a lower-damage member without a fixed species or move preference. Damage estimates can still result in a knockout; an ordinary catch knockout or empty ball stock does not end the training loop. Hidden opponent IVs are not claimed available.

Routine switch, movement and healing failures keep the campaign active while it refreshes verified native state and retries with bounded delays. Temporary NPC obstructions trigger replanning. Automatic move learning rechecks the exact native offer and UI phase before a retry; the selected Keep current moves or Pause policy is respected. No recovery guesses a missing actor, grants an unobserved badge, or overrides the Stop button.

Missing-species collection and gym-counter catches are no longer suppressed by a full six-member party. Ownership history still covers verified own-party observations, not every boxed Pokémon, so boxed-only species can be attempted again. Hunting, recovery and return-to-grass routes all use fresh native NPC positions. The summary handler never opens a summary to inspect ownership and does not send a general Cancel or dismiss evolution prompts.

Client updates and recovery

Native profiles are bound to an exact client binary. This archive targets revision 34932. An unknown update is not automatically treated as compatible; inspect Diagnostics and obtain a validated build. Known profiles and saved baselines support the next repair assessment. A local optional 40-minute watchdog can recover narrowly defined connection/movement stops, but it does not log in, rewrite code or bypass unknown dialogue. A disconnected client cannot continue sending gameplay actions.

Privacy and limits

The public archive excludes ROMs, account credentials, captures, private session data and legacy VPS deployment settings. Your local client configuration and runtime data stay on your computer. No VPS dashboard or upload from your local bot is needed for this build.

Shiny identity is observed where supported and catching has priority when balls and a supported battle state are available. Complete catching and shiny-horde behavior remain unverified end to end in this release. Use automation only where you have permission and understand the server’s rules.

Technical notes and current limitations · Build manifest · Back to the Apps page