A native Linux companion application in development, written in Rust for DC Universe Online running under Wine or Proton. It displays game information in a normal managed window on another monitor, reads game memory, and cross-checks supported character fields through dcuobot-api. Its Map tab previews experimental live position on locally imported open-world and indoor maps.
Status: experimental live map preview. The managed application displays API character references, experimental memory resources/position, and automatic maps from the local game installation. All 313 installed main overviews pass import and cache validation; this is not live calibration of every instance. The user confirmed matching map/marker movement in Gotham and the MHDT0107 indoor area. Current-character identity, quantitative indoor accuracy, multi-launch profiles and full release acceptance remain incomplete. See live map evidence.
The Broker tab compares your observed listings with other sellers' asking prices. Keep the companion's Broker tab selected, open My Wares in game, then browse or search for competing items. Observations remain visible for 15 minutes, with ages and partial coverage shown. Prices come from the read-only client cache; no public Broker API was found. Stack sizes and item variants still need in-game confirmation. See Broker usage and limitations.
The Character tab includes a solo On Duty feat checklist. Look up an exact character name/world to load API completion data, then use Refresh feats when needed. With the supported game connected, the tab automatically uses live completion for the current in-game character and refreshes about every eight seconds while visible. It reads the client's feat definitions without needing the in-game Feats menu open. Definitions and confirmed completions are cached for the connected character session, including across tab switches. Completed feats never revert to incomplete; refreshes check unfinished progress and new completions. Restarting or reconnecting rebuilds this memory cache. API character details remain a separate reference. The checklist retains previously read rows during scan gaps and merges new findings. The cached API character faction filters both API and memory views consistently; it does not verify live identity. The All/Hero/Villain filter is saved across launches and can be changed on Character. A new character lookup selects that reference faction; connecting a process preserves the reference. Missions are ordered by Normal-entry CR (level-30 missions first); each documented feat shows its reward points. Completed feats are hidden unless Show completed is checked. Search matches mission names, feat names and requirements. Character details and experimental Log remain available.
Catalog coverage is partial: 40 missions, 171 documented feat entries and 24 bundled completion-ID mappings. Live client definitions can resolve additional entries by an exact trimmed title and reward. Duplicate titles require a unique exact mission-requirement match. Unsupported or ambiguous matches remain unknown. Account-only unlocks do not count as completed by the current character. Unknown completion remains visible. Nekron's Lair and Summit of Sorrow currently lack documented feat lists. Census retrieval time does not establish in-game freshness, and the selected API character is not automatically verified against the controlled player. Sources and coverage are available under each mission's Details. No personal snapshots are bundled.
Use Linux/X11 and Rust 1.95 or newer (validated with 1.96.0):
cargo run --locked --bin dcuo-companion
cargo run --locked --no-default-features --bin dcuo-probe -- self-test
cargo run --locked --no-default-features --bin dcuo-probe -- listIn the window, refresh/select the game process and Connect to inspect its build and read access. Enter an exact character name/world and choose Look up reference for API data. Scan next bounded step searches the selected process for matching name bytes, separately labeled as unverified string evidence. Diagnostics shows the actual process/build, application version and backend. Pause, Disconnect, Settings, About and Quit are available. Current area automatically imports the matching installed map in the background, even while another tab is open, and switches when fresh area evidence changes. The game installation is detected on connection; Settings allows a CookedPC path override and disabling automatic imports. Browse preserves manual selection. Missing maps or ambiguous area evidence hide the marker; Retry current map retries a failed import. Multi-floor selection is not yet proven. See local import details. DWM owns placement, tags, borders, and focus; use its controls to choose a monitor.
Optional reconnect recovers only one fresh session with the same executable build; manual Disconnect cancels recovery. API references retain their original receipt time through a five-minute local cache and honor service cooldowns. Closing the application cancels incomplete map imports. Preferences can be reset without deleting imported maps. See local install and rollback and offline validation and remaining live checks.
See development instructions for explicit-PID inspection, bounded name-search experiments, X11 checks, and build requirements.
A complete application with Character, Map, and Diagnostics tabs, shared session controls/status, Settings, Help/About, and desktop integration. The Character tab shows the active character, proven memory fields, and per-field API verification. The Map tab adds a live position marker, area/floor display, zoom/pan, and follow/recenter. First-release coverage includes both open-world and indoor/ instance maps, with supported areas listed explicitly. Unknown maps, stale positions, and unproven fields remain visibly unavailable.
The initial target is DWM-Titus on X11. The main window must be managed
(override_redirect=false), with DWM handling placement, tags, borders, and focus.
Phase 0 must verify operation on a separate monitor while the game is active,
including fullscreen gameplay, focus switching, and display reconnection.
First-release packaging precedes optional personal combat analytics, encounter history, timers, and other quality-of-life features. These depend on establishing reliable sources.
- Specification: scope, architecture, data contracts, and constraints.
- Roadmap: implementation phases and acceptance criteria.
- Tasks: current status and actionable checklist.
- Contributing: development and validation expectations.
- Agent conventions: durable repository instructions.
Game memory provides live observations. The API provides character and reference data that can corroborate selected fields. API matches do not certify an entire memory layout. Current health, cooldowns, combat events, and live position/zone/ floor are not exposed by the inspected API contract. Live maps need independently proven memory observations and correctly matched, calibrated map assets.
Optional combat-log support will be evaluated for event-based analytics. Each feature must identify its source and distinguish measurements from estimates.
- DCUO-Assistant: feature inspiration.
- dcuobot-api: character and reference API.
- Linux process memory reads.
- egui: initial Rust UI candidate.
No reference-project code is included. Dependency and source licenses must be checked before incorporating external code or assets.
On the Map tab, enable Ground spawns to show recognized spawn objects exposed by the running client. The switch is saved and defaults to off. Discovery runs in bounded background steps; the status shows progress. Colored diamonds identify recognized spawn visuals, while the yellow circle remains your character. Unloaded spawns and collected/uncollected status are unavailable.
Orange diamonds mark recognized exobyte spawns whenever the Ground spawns layer is enabled and the client exposes a valid live object.
Spawn locations stay cached during partial scans and temporary read gaps. A location disappears after two consecutive complete scans miss it; seeing it again resets that count. These are last-seen locations, not a guarantee that a spawn is available. The cache clears on a confirmed area/character/session change and is not saved to disk. Turning the layer off hides cached locations without erasing them in the same context.
