Skip to content

v0.6.0

Choose a tag to compare

@anthomaxcool anthomaxcool released this 09 Nov 19:13

Moderation across the whole fleet, roles for the people who help run it, and
dynamic configs that change rates on running servers with nobody kicked.
Updating changes nothing anyone can do today: existing accounts keep every
permission they had.

Players

  • Bans are fleet-wide and can be timed. Ban a player from their page,
    with a reason and a length (a day, a week, a month, for good, or until a
    date), and YAASM applies it on every server, including servers started or
    created later, then lifts it by itself when it ends. A player can also be
    banned by id before they've ever joined. Also yaasm player ban|unban|bans,
    and ban_player, unban_player and list_bans for assistants.
  • A whitelist, one for every server. Add players on PLAYERS › ALL PLAYERS ›
    WHITELIST, by id even before they've ever joined, or from their page; turn
    it on per server with WHO CAN JOIN in its SETTINGS. YAASM applies the list
    on each server itself, like bans. Also yaasm player whitelist,
    yaasm server edit --whitelist on, and list_whitelist,
    whitelist_player and unwhitelist_player for assistants.
  • A server with -exclusivejoin in its extra options is moved onto the new
    whitelist switch when YAASM starts, and the flag is no longer accepted
    there. Its own list in the game stays as it is: YAASM only ever takes off
    players it put on. Add them to YAASM's whitelist to have them on every
    server.
  • Notes on players, signed with the account that wrote them, on the
    player's page, in yaasm player note and add_player_note.
  • PLAYERS › HISTORY is now ALL PLAYERS, with a BANNED filter and each
    player's note count. It shows the map an offline player was last on beside
    how long ago, with a grey dot where an online player has a lit one. The
    roster's BAN used to ban on that one server; it now opens the player's page
    to ban them everywhere.
  • PLAYERS › ONLINE shows how long each player has been on this session,
    where it used to show their place in the game's list.
  • A player's page lists their last 10 sessions, with a choice of 25, 50, 100
    or all of them that is remembered on every device.

Accounts

  • Roles. The first account owns the install and can hand ownership to
    another; every other account has a role that says what it may change:
    Admin, Operator, Moderator, Viewer, or roles you make on OPS › ROLES.
    Everyone can still see the fleet. Existing accounts: the oldest becomes the
    owner and the rest Admin, which can do everything but hand ownership on.
    API tokens, the command line and assistants act with their account's role;
    yaasm login --status says what it allows. The app leaves out what your
    role can't do, and says so where a whole section would be: a Viewer sees
    the fleet, its settings and backups, with nothing to press.

Dynamic configs and events

  • Dynamic configs, for rates and the other settings the game fetches
    while it runs. Keep a library of them under AUTOMATION, give one to each
    server on its SETTINGS tab (USE THIS ADDRESS sets the server up, once), and
    switch servers between them with no restart: YAASM serves the file itself
    and tells the game to fetch it at once. Write the file as plain
    Key=value lines, with no [ServerSettings] header.
  • Events can switch servers to a dynamic config for a while. An event
    that only does that reaches running servers at once, with nobody kicked,
    and gives each server back what it had at the end. A setting the file
    leaves out keeps the value it last had, so the config handed back should
    name everything the event's one changes.
  • An event's schedule can be written as dates: when it starts, when it ends,
    and whether it repeats every day, week, month or year, or never. The cron
    view is still there, one click away, and both edit the same schedule.

Plugins

  • A server with plugins can start or restart without them, this once, from
    its MORE menu, search, yaasm start|restart --no-plugins or
    withoutPlugins for assistants. Its plugins stay on for the next start.
    For after a game update that the plugin framework hasn't caught up with.
  • IF THEY FAIL, START WITHOUT THEM on a server's PLUGINS tab (or
    yaasm server edit --plugins-fallback on): a start with plugins that
    crashes or hangs before it answers comes back without them, rather than
    staying down until someone looks. The server's page says while it runs
    without its plugins.

Windows

  • Windows Firewall blocks a game server that YAASM's service starts,
    without a prompt, so nobody can join from another machine. A server's page
    and yaasm doctor now say so, and yaasm firewall adds the rules (it asks
    for Administrator rights). Run it again after creating a server.
  • A fresh Windows install no longer shows the first game build download as
    failed: the installer lets SteamCMD update itself first, and YAASM tries a
    failed SteamCMD run once more before giving up.

Removed

  • The CROSSPLAY (ALL PLATFORMS) switch is gone from a server's SETTINGS, with
    --option platform-all in yaasm server edit. -ServerPlatform=ALL is what
    the game does without being told, so the switch changed nothing. A server
    that had it on starts exactly as before.