Skip to content

Releases

CATS More Features v3.2.2

Choose a tag to compare

@kxdxzr kxdxzr released this 08 Nov 00:53

CATS More Features v3.2.2

This fork remains under active testing and may contain bugs. Scheduled start has been tested in game, but
complete routes, refuelling modes, cooldown recovery, power saving and completion actions need further in-game
testing. Run supervised tests before relying on unattended operation.

Download

Download the Windows x64 ZIP below, extract it to a writable folder, and run CATS-new.exe. Requires 64-bit
Windows and .NET Framework 4.7.2 or later; Python is bundled. See START_HERE.txt and README.md in the ZIP.

Highlights

  • Scheduled start with calendar, time selectors and shortcuts.
  • Route completion actions: keep open, close the game and CATS, or request computer shutdown.
  • Test refuel... executes one refuelling input sequence without starting a route or completion action.
    It sends real game inputs and can move cargo even when automatic refuelling is disabled. Manually verify the result.
  • Scheduling controls stay aligned with the route editor when the window is resized.
  • Journal-based pending-jump/cooldown recovery and saved route position.
  • Updated personal carrier transfer sequence; squadron sequence is unchanged.

Safety and limitations

  • Stop cancels CATS automation, not a jump already submitted in-game. A previous onefile packaging regression
    could leave a child process running; the fix has automated coverage but needs more in-game validation.
  • The game-close action may terminate the game after 15 seconds. Shutdown has a 30-second Windows countdown;
    use shutdown /a to cancel it.
  • Fuel transfer and different carrier modes remain unverified in full. A completed test sequence does not
    confirm that fuel moved. Stop, cooldown recovery and completion actions may have bugs.
  • The packaged defaults keep the game open, do not schedule shutdown, and have an empty route and webhook.
  • Frontier API login requires your own registered client ID; journal-based traversal does not.

Automated checks cover journal handling, stop/restart process management, UI layout and mock completion/refuelling
logic. They do not send game inputs or perform real game exits or shutdowns.

Report issues at https://github.com/kxdxzr/CATS_more_features/issues. Thanks to the original CATS authors.

CATS More Features v3.2.2-beta.1

Pre-release

Choose a tag to compare

@kxdxzr kxdxzr released this 14 Oct 23:48

CATS More Features v3.2.2-beta.1

Experimental beta / pre-release. This build is still under active testing and may contain many bugs.
It is not a stable release.
Scheduled start has been tested in game, but full routes, different refuelling
modes, power saving, cooldown transitions, and real completion actions still need broader in-game verification.

Download and run

  • Download CATS-More-Features-v3.2.2-beta.1-windows-x64.zip from the release assets below.
  • Extract the complete ZIP to a writable folder and launch CATS-new.exe.
  • Read START_HERE.txt, configure your journal directory and route, and check the refuelling options.
  • Requires 64-bit Windows and .NET Framework 4.7.2 or newer. No separate Python installation is needed.
  • The ZIP contains the GUI, bundled Python backend, required DLLs, input sequences, clean default settings,
    documentation, build information and checksums. The initial route is empty and completion defaults to keeping everything open.

Changes from upstream

  • Scheduled start with calendar/time selectors and Now, +10 min and +1 hour shortcuts.
  • Completion choices: keep open, close the game and CATS, or shut down the computer with a 30-second countdown.
  • Recovery of pending jumps and cooldown state from recent journal files before navigation.
  • Resume-position synchronization, journal rotation/partial-record handling, and bounded navigation retries.
  • Personal carrier cargo-transfer sequence adjustment and tritium-slot validation improvements.
  • Build support without a private OAuth source file; a registered Frontier client ID is still required for API login.
  • English README, build/deployment guide, automated checks and a clean portable beta package.

Important behaviour and known limitations

  • Stop stops automation, not a carrier jump already submitted in the game.
  • This fork's switch to a onefile backend introduced a Stop regression that could leave the Python child process
    running. This beta includes a fix for that regression; it is not an upstream defect or a new feature, and
    stopping/restarting still needs broader in-game testing.
  • Cooldown is conservatively five minutes after a recovered arrival event; missing arrival history can cause an initial five-minute wait.
  • Close game and CATS first requests normal game exit and can terminate the game after 15 seconds if needed.
  • Shut down computer uses shutdown /s /t 30; cancel the Windows countdown with shutdown /a.
  • Automated tests do not guarantee reliable unattended operation. Game updates, menu state, display settings,
    key bindings and refuelling mode can still cause failures or regressions.
  • This build does not contain a Frontier API client ID. Configure your own ID if you use the admin interface's API login.

Verification

  • Eight unit tests cover journal recovery, event matching, cancellation, held-key release and mocked completion actions.
  • Windows integration checks exercise synthetic parent/child process Stop and immediate restart, GUI selectors/settings,
    and cancellation of the real onefile backend during scheduled-start and cooldown waits.
  • The packaged default configuration is checked for an empty initial route, empty webhook and disabled automatic completion actions.
  • Real game exit and real Windows shutdown are not triggered by these automated checks.

Please report reproducible problems at https://github.com/kxdxzr/CATS_more_features/issues with steps,
relevant configuration and log excerpts. Thanks to the original CATS project and its authors.