Docs

Configuration

Back to docs

Configuration

sphere.exe stores per-character configuration in %APPDATA%\gods-eye\client-config.json. The desktop GUI is the canonical editor; the JSON file is documented here for operators who want to inspect or script profile changes.

The file is a JSON array. Each entry is validated as a ClientProfile. Unknown nested sections such as mining.*, defense.*, or drones.* are not read by the client.

Profile fields

  • pid - EVE process id for the bound client, or null before detection.
  • character_name - detected character name, or null if unavailable.
  • role - currently miner.
  • home_system_id and target_system_id - numeric EVE system ids.
  • home_station_name, target_system_name, and target_station_name - optional display names used by the GUI and docking flow.
  • belt_id - optional target belt id.
  • selected_ore_types - array of ore names. Empty means any ore.
  • ore_hold_threshold_pct - unload threshold as a percentage from 0 to 100; the default is 95.0.
  • sanderling_path - optional path override for the reader integration.
  • dry_run - true means the client will not send real input.

Example

[
  {
    "pid": 1234,
    "character_name": "Example Pilot",
    "role": "miner",
    "home_system_id": 30000142,
    "home_station_name": "Jita IV - Moon 4 - Caldari Navy Assembly Plant",
    "target_system_id": 30000142,
    "target_system_name": "Jita",
    "target_station_name": "Jita IV - Moon 4 - Caldari Navy Assembly Plant",
    "belt_id": null,
    "selected_ore_types": ["Veldspar", "Scordite"],
    "ore_hold_threshold_pct": 95.0,
    "sanderling_path": null,
    "dry_run": true
  }
]

If an entry fails validation, the client skips that entry and keeps loading the rest of the file.