Skip to content

1.1.4

Latest
Compare
Choose a tag to compare
@BigBang1112 BigBang1112 released this 08 Jul 20:13
bf3c179

GitHub release (by tag)

  • Added BannedMaps to Config.yml in the Rules section
    • Specify TMX type and a list of track IDs to not show when randomizing
    • This info is included in the session file, and is therefore not valid for regular RMC records
    • See below how to specify the track IDs correctly
  • Fixed Min/Max AT hundredths to be limited to 99 instead of 59 (thx fabi for the report)
  • Finished the secured sessions transition completely
  • Updated dependencies

How to specify banned track IDs: (spacing has to be followed like shown here!)

    AuthorTimeMax: 3:00.00 # here just for context
  BannedMaps: # remove the {} that's there by default
    TMNF:
    - 1234
    - 5678
    TMUF:
    - 91011
    - 121314
    - 151617
    Nations:
    - ... etc

Possible TMX type keys: TMNF, TMUF, Nations, Sunrise, Original

Installation

Common questions (see all)

Other details

Linux build is not guaranteed to work, in fact, you have to fix some things first.

WIN-X64 SHA256: 28748975732232770ebca796126e45916523923706a0b6db4c47292a144c84f0
WIN-X86 SHA256: 7c92853ed2b23cde42d49715dbac3b4f9ed30e990731b221aac3cef1742adaef
LINUX-X64 SHA256: a5e0f0b4467cbae7a0547bd07189e89753ebb1fe499c78549cbd9483cb4e24d9

You can also validate via the checksum outputted in the workflow run.