Troubleshooting

sphere.exe cannot find the EVE client

• Confirm the EVE Online client is running and you have logged in to a character. The bot needs a character in space or in station — not the launcher screen.
• Run sphere.exe as Administrator. The memory reader needs the same privilege level as the EVE process.

License key rejected

• Copy the key from /account rather than typing it. The key uses an unambiguous alphabet but it is case-sensitive.
• Renewed licenses rotate the key. If you renewed today, fetch the new key from the dashboard and update the client.
• If you hit the device cap, revoke an unused device at /account/devices and try again.

Bot stops at unload

• Make sure your dock target is reachable from the belt. Citadels with access controls require your character to have appropriate roles.
• Check the diagnostics panel for parser_warning: hangar_window_missing. The bot will wait for the hangar window to open before unloading.

Cold-start delays

• The first read after launch takes 5–15 seconds while the memory map is built. Subsequent reads are sub-second.
• If reads time out repeatedly, restart the EVE client first, then sphere.exe.

Detection concerns

We won't make ban-risk guarantees. The architecture choices — read-only memory, no patching, humanized input, no kernel hooks — are documented on /how-it-works.