Repository navigation
Releases
v0.7.0
The web app in French, and a SUPPORT YAASM card on OPS for anyone who wants
to tip the project. A browser set to French shows the app in French after
the update; OPS › DISPLAY › LANGUAGE switches that browser back to English.
-
A way to support YAASM. OPS › YAASM has a SUPPORT YAASM card that
links to a tip page, once or monthly. Nothing is unlocked by it, and OPS ›
SCREENS hides it. -
The web app in French. It follows the browser's language, and OPS ›
DISPLAY › LANGUAGE picks one for this browser alone, so two people on one
fleet can each read their own. Every page is translated, along with
lengths of time, sizes, dates and cron schedules, and search finds things
by their English or French name whichever is shown. The CLI, the MCP
tools and the daemon's messages stay in English.
v0.7.0-rc.1
A pre-release of v0.7.0: the web app in French. It holds everything
listed under Unreleased at the time:
- The web app in French. It follows the browser's language, and OPS ›
DISPLAY › LANGUAGE picks one for this browser alone, so two people on one
fleet can each read their own. Every page is translated, along with
lengths of time, sizes, dates and cron schedules, and search finds things
by their English or French name whichever is shown. The CLI, the MCP
tools and the daemon's messages stay in English.
v0.6.1
One YAASM driving several machines: servers on other PCs are listed, started,
backed up and moderated from one place, a cluster can span machines, and any
machine can take over as controller. Also: importing servers another tool set
up, yaasm uninstall, and Windows network shares for clusters run as a
service. Nothing changes on update: a machine only becomes a node once it is
given a node port and paired.
-
YAASM signs in to network shares itself (Windows). Run as a service,
YAASM reaches a share as the computer, which a share on another PC turns
down, so a cluster folder linked to one (mklink /D) stopped working the
moment YAASM became a service. OPS › PATHS has a NETWORK SHARES card that
lists the shares YAASM's folders lead to: give each the user and password
of an account on the computer sharing it (oryaasm settings shares set),
and YAASM signs in at every start, for itself and the game servers it
starts. The password is kept encrypted and never shown again.yaasm doctorsays when a saved share can't be opened. -
A cluster folder YAASM can't open says why. A start used to fail with
mkdir …\clusters: Cannot create a file when that file already exists
when the cluster folder was a link to a network share YAASM's Windows
service can't reach. It now names the link and the share, and says what
to do.yaasm doctorchecks each cluster's folder, and no longer passes a
folder it can't open as one still to be created. The README says what a
share on another PC means for a Windows machine running the service. -
The top bar picks a machine. Once there is a node, the top bar's
first crumb is a MACHINE picker, ALL MACHINES by default, beside the
cluster one: FLEET, its heading and its START, RESTART and STOP ALL then
cover that machine's servers. The server picker groups servers by machine
as well as by cluster, so two machines' unclustered servers no longer
read as one group. -
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
OPS › SCREENS lists what can be hidden by page. FLEET, SERVER,
CONSOLE, AUTOMATION and OPS each have their own group, instead of one long
SECTIONS list mixing every page's parts. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
OPS folds. Each section's heading folds it away, and this browser
remembers which; a link or search result to a section opens it again.
The list under OPS jumps to each section, and the audit log, the longest,
is now last. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. When they don't, the OVERVIEW of each
of its servers andyaasm doctoron the controller warn too: players
moving between those machines lose their characters and items. The
servers still start. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
The new-server form suggests
island, notisland-pve. A new server
isn't PvE unless its settings make it so, and the suggestion read as
though it were.yaasm server create's examples changed the same way. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
yaasm service restart. Restarts YAASM's service the same way on
Windows and Linux, leaving the game servers running. It first asks YAASM
what it's in the middle of, and refuses while a backup, a download or a
server starting or stopping would be cut short (--forcegoes ahead).yaasm doctornow says how to restart YAASM where it asks you
to, and, when SteamCMD is missing under the service, to run
yaasm service installagain: the service's PATH is set at install, so
a restart alone never found a newly installed SteamCMD. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
yaasm uninstall. Removes what the installer put on the machine: the
service, the binary and its folder, its place on PATH, the firewall rules
yaasm firewallmade and, on Linux, the downloaded GE-Proton. It lists
everything first and asks. YAASM's data stays;--purgedeletes it too,
with theyaasmaccount on Linux, for a machine done with YAASM or a
fresh install from scratch. Game servers have to be stopped first. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
clear of the notch. -
An event's start date sticks. A repeating event set to begin on a later
date used to start at the schedule's next match instead, and the editor
showed that date after saving, with no way to put the chosen one back. The
start picked in the dates view is now kept, and no run begins bef...
v0.6.1-rc.5
The fifth pre-release of v0.6.1. Fixed since rc.4:
-
yaasm uninstallon Windows stops a game build download too. It
found the download the service had started but couldn't end it, said
nothing, and--purgethen failed on the files it held open. -
A forgotten network share says it's still open. FORGET deletes the
password and the connection, but Windows keeps the sign-in until the share
has gone unused for a few minutes, game servers included, and nothing can
end it sooner. OPS › PATHS showed CONNECTED meanwhile, as if FORGET had
done nothing. It now shows STILL OPEN and why, and so doesyaasm settings shares.
Everything since v0.6.0, as in rc.4:
-
YAASM signs in to network shares itself (Windows). Run as a service,
YAASM reaches a share as the computer, which a share on another PC turns
down, so a cluster folder linked to one (mklink /D) stopped working the
moment YAASM became a service. OPS › PATHS has a NETWORK SHARES card that
lists the shares YAASM's folders lead to: give each the user and password
of an account on the computer sharing it (oryaasm settings shares set),
and YAASM signs in at every start, for itself and the game servers it
starts. The password is kept encrypted and never shown again.yaasm doctorsays when a saved share can't be opened. -
A cluster folder YAASM can't open says why. A start used to fail with
mkdir …\clusters: Cannot create a file when that file already exists
when the cluster folder was a link to a network share YAASM's Windows
service can't reach. It now names the link and the share, and says what
to do.yaasm doctorchecks each cluster's folder, and no longer passes a
folder it can't open as one still to be created. The README says what a
share on another PC means for a Windows machine running the service. -
The top bar picks a machine. Once there is a node, the top bar's
first crumb is a MACHINE picker, ALL MACHINES by default, beside the
cluster one: FLEET, its heading and its START, RESTART and STOP ALL then
cover that machine's servers. The server picker groups servers by machine
as well as by cluster, so two machines' unclustered servers no longer
read as one group. -
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
OPS › SCREENS lists what can be hidden by page. FLEET, SERVER,
CONSOLE, AUTOMATION and OPS each have their own group, instead of one long
SECTIONS list mixing every page's parts. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
OPS folds. Each section's heading folds it away, and this browser
remembers which; a link or search result to a section opens it again.
The list under OPS jumps to each section, and the audit log, the longest,
is now last. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. When they don't, the OVERVIEW of each
of its servers andyaasm doctoron the controller warn too: players
moving between those machines lose their characters and items. The
servers still start. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
The new-server form suggests
island, notisland-pve. A new server
isn't PvE unless its settings make it so, and the suggestion read as
though it were.yaasm server create's examples changed the same way. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
yaasm service restart. Restarts YAASM's service the same way on
Windows and Linux, leaving the game servers running. It first asks YAASM
what it's in the middle of, and refuses while a backup, a download or a
server starting or stopping would be cut short (--forcegoes ahead).yaasm doctornow says how to restart YAASM where it asks you
to, and, when SteamCMD is missing under the service, to run
yaasm service installagain: the service's PATH is set at install, so
a restart alone never found a newly installed SteamCMD. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
yaasm uninstall. Removes what the installer put on the machine: the
service, the binary and its folder, its place on PATH, the firewall rules
yaasm firewallmade and, on Linux, the downloaded GE-Proton. It lists
everything first and asks. YAASM's data stays;--purgedeletes it too,
with theyaasmaccount on Linux, for a machine done with YAASM or a
fresh install from scratch. Game servers have to be stopped first. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
clear of the notch. -
**An event's start da...
v0.6.1-rc.4
The fourth pre-release of v0.6.1. Fixed since rc.3:
-
yaasm uninstallon Linux finishes the job. A game build download
YAASM had started kept running after it, and kept--purgefrom removing
theyaasmaccount. It's now stopped first.--purgeno longer refuses
/var/lib/yaasmas your home folder, and no longer reports the binary,
deleted along with it, as a failure. -
OPS › DAEMON folds once. The daemon panel kept a fold of its own
inside the section's.
Known in this pre-release: after FORGET on a network share, OPS › PATHS can
still say CONNECTED while the game servers can no longer reach it. Saving the
share again brings it back. Being looked into.
Everything since v0.6.0, as in rc.3:
-
YAASM signs in to network shares itself (Windows). Run as a service,
YAASM reaches a share as the computer, which a share on another PC turns
down, so a cluster folder linked to one (mklink /D) stopped working the
moment YAASM became a service. OPS › PATHS has a NETWORK SHARES card that
lists the shares YAASM's folders lead to: give each the user and password
of an account on the computer sharing it (oryaasm settings shares set),
and YAASM signs in at every start, for itself and the game servers it
starts. The password is kept encrypted and never shown again.yaasm doctorsays when a saved share can't be opened. -
A cluster folder YAASM can't open says why. A start used to fail with
mkdir …\clusters: Cannot create a file when that file already exists
when the cluster folder was a link to a network share YAASM's Windows
service can't reach. It now names the link and the share, and says what
to do.yaasm doctorchecks each cluster's folder, and no longer passes a
folder it can't open as one still to be created. The README says what a
share on another PC means for a Windows machine running the service. -
The top bar picks a machine. Once there is a node, the top bar's
first crumb is a MACHINE picker, ALL MACHINES by default, beside the
cluster one: FLEET, its heading and its START, RESTART and STOP ALL then
cover that machine's servers. The server picker groups servers by machine
as well as by cluster, so two machines' unclustered servers no longer
read as one group. -
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
OPS › SCREENS lists what can be hidden by page. FLEET, SERVER,
CONSOLE, AUTOMATION and OPS each have their own group, instead of one long
SECTIONS list mixing every page's parts. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
OPS folds. Each section's heading folds it away, and this browser
remembers which; a link or search result to a section opens it again.
The list under OPS jumps to each section, and the audit log, the longest,
is now last. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. When they don't, the OVERVIEW of each
of its servers andyaasm doctoron the controller warn too: players
moving between those machines lose their characters and items. The
servers still start. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
The new-server form suggests
island, notisland-pve. A new server
isn't PvE unless its settings make it so, and the suggestion read as
though it were.yaasm server create's examples changed the same way. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
yaasm service restart. Restarts YAASM's service the same way on
Windows and Linux, leaving the game servers running. It first asks YAASM
what it's in the middle of, and refuses while a backup, a download or a
server starting or stopping would be cut short (--forcegoes ahead).yaasm doctornow says how to restart YAASM where it asks you
to, and, when SteamCMD is missing under the service, to run
yaasm service installagain: the service's PATH is set at install, so
a restart alone never found a newly installed SteamCMD. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
yaasm uninstall. Removes what the installer put on the machine: the
service, the binary and its folder, its place on PATH, the firewall rules
yaasm firewallmade and, on Linux, the downloaded GE-Proton. It lists
everything first and asks. YAASM's data stays;--purgedeletes it too,
with theyaasmaccount on Linux, for a machine done with YAASM or a
fresh install from scratch. Game servers have to be stopped first. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
cle...
v0.6.1-rc.3
The third pre-release of v0.6.1. New since rc.2, from a tester's Windows
machine sharing a cluster with another PC:
-
YAASM signs in to network shares itself (Windows). Run as a service,
YAASM reaches a share as the computer, which a share on another PC turns
down, so a cluster folder linked to one (mklink /D) stopped working the
moment YAASM became a service. OPS › PATHS has a NETWORK SHARES card that
lists the shares YAASM's folders lead to: give each the user and password
of an account on the computer sharing it (oryaasm settings shares set),
and YAASM signs in at every start, for itself and the game servers it
starts. The password is kept encrypted and never shown again.yaasm doctorsays when a saved share can't be opened. -
A cluster folder YAASM can't open says why. A start used to fail with
mkdir …\clusters: Cannot create a file when that file already exists
when the cluster folder was a link to a network share YAASM's Windows
service can't reach. It now names the link and the share, and says what
to do.yaasm doctorchecks each cluster's folder, and no longer passes a
folder it can't open as one still to be created. The README says what a
share on another PC means for a Windows machine running the service.
Everything else since v0.6.0, as in rc.2:
-
The top bar picks a machine. Once there is a node, the top bar's
first crumb is a MACHINE picker, ALL MACHINES by default, beside the
cluster one: FLEET, its heading and its START, RESTART and STOP ALL then
cover that machine's servers. The server picker groups servers by machine
as well as by cluster, so two machines' unclustered servers no longer
read as one group. -
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
OPS › SCREENS lists what can be hidden by page. FLEET, SERVER,
CONSOLE, AUTOMATION and OPS each have their own group, instead of one long
SECTIONS list mixing every page's parts. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
OPS folds. Each section's heading folds it away, and this browser
remembers which; a link or search result to a section opens it again.
The list under OPS jumps to each section, and the audit log, the longest,
is now last. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. When they don't, the OVERVIEW of each
of its servers andyaasm doctoron the controller warn too: players
moving between those machines lose their characters and items. The
servers still start. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
The new-server form suggests
island, notisland-pve. A new server
isn't PvE unless its settings make it so, and the suggestion read as
though it were.yaasm server create's examples changed the same way. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
yaasm service restart. Restarts YAASM's service the same way on
Windows and Linux, leaving the game servers running. It first asks YAASM
what it's in the middle of, and refuses while a backup, a download or a
server starting or stopping would be cut short (--forcegoes ahead).yaasm doctornow says how to restart YAASM where it asks you
to, and, when SteamCMD is missing under the service, to run
yaasm service installagain: the service's PATH is set at install, so
a restart alone never found a newly installed SteamCMD. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
yaasm uninstall. Removes what the installer put on the machine: the
service, the binary and its folder, its place on PATH, the firewall rules
yaasm firewallmade and, on Linux, the downloaded GE-Proton. It lists
everything first and asks. YAASM's data stays;--purgedeletes it too,
with theyaasmaccount on Linux, for a machine done with YAASM or a
fresh install from scratch. Game servers have to be stopped first. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
clear of the notch. -
An event's start date sticks. A repeating event set to begin on a later
date used to start at the schedule's next match instead, and the editor
showed that date after saving, with no way to put the chosen one back. The
start picked in the dates view is now kept, and no run begins before it
(frominyaasm schedule eventsJSON). Moving the start no longer moves
the end, unless the start lands on or after it. -
EDIT beside a server's name, at the top of its page, changes the name
players see in the server browser. It's ...
v0.6.1-rc.2
The second pre-release of v0.6.1, with what rc.1's test run asked for. New
or changed since rc.1:
-
A node's server stops flashing its firewall warning. On a server held
by a Windows node, the WINDOWS FIREWALL warning appeared and disappeared
every five seconds; it now stays while the firewall blocks the server. -
The top bar picks a machine. Once there is a node, the top bar's
first crumb is a MACHINE picker, ALL MACHINES by default, beside the
cluster one: FLEET, its heading and its START, RESTART and STOP ALL then
cover that machine's servers. The server picker groups servers by machine
as well as by cluster, so two machines' unclustered servers no longer
read as one group. -
OPS › SCREENS lists what can be hidden by page. FLEET, SERVER,
CONSOLE, AUTOMATION and OPS each have their own group, instead of one long
SECTIONS list mixing every page's parts. -
OPS folds. Each section's heading folds it away, and this browser
remembers which; a link or search result to a section opens it again.
The list under OPS jumps to each section, and the audit log, the longest,
is now last. -
The new-server form suggests
island, notisland-pve. A new server
isn't PvE unless its settings make it so, and the suggestion read as
though it were.yaasm server create's examples changed the same way. -
yaasm service restart. Restarts YAASM's service the same way on
Windows and Linux, leaving the game servers running. It first asks YAASM
what it's in the middle of, and refuses while a backup, a download or a
server starting or stopping would be cut short (--forcegoes ahead).yaasm doctornow says how to restart YAASM where it asks you
to, and, when SteamCMD is missing under the service, to run
yaasm service installagain: the service's PATH is set at install, so
a restart alone never found a newly installed SteamCMD. -
yaasm uninstall. Removes what the installer put on the machine: the
service, the binary and its folder, its place on PATH, the firewall rules
yaasm firewallmade and, on Linux, the downloaded GE-Proton. It lists
everything first and asks. YAASM's data stays;--purgedeletes it too,
with theyaasmaccount on Linux, for a machine done with YAASM or a
fresh install from scratch. Game servers have to be stopped first. -
Building from source on Windows no longer gives a blank page. A build
made after the sources changed produced a web app that never started.
Releases and builds on Linux weren't affected. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. When they don't, the OVERVIEW of each
of its servers andyaasm doctoron the controller warn too: players
moving between those machines lose their characters and items. The
servers still start. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share.
Everything else since v0.6.0, as in rc.1:
-
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
clear of the notch. -
An event's start date sticks. A repeating event set to begin on a later
date used to start at the schedule's next match instead, and the editor
showed that date after saving, with no way to put the chosen one back. The
start picked in the dates view is now kept, and no run begins before it
(frominyaasm schedule eventsJSON). Moving the start no longer moves
the end, unless the start lands on or after it. -
EDIT beside a server's name, at the top of its page, changes the name
players see in the server browser. It's written into the game's config, as
the INI tab would; a running server shows the new name from its next start,
and the page says so. -
A server's id can be changed, from MOVE SERVER on a stopped server's
SETTINGS,yaasm server move, ormove_serverfor assistants. The id
is its folder under servers/ and what YAASM knows it by; the new-server
form now calls it ID rather than NAME, beside the session name players
see. Its folder moves, and its backups, schedules, plugins, the bans YAASM
applied there, its players' history and the events that list it follow.
On Windows, runyaasm firewallagain afterwards. -
Nodes, the first step towards one YAASM driving several machines. A
machine can pair with another YAASM, its controll...
v0.6.1-rc.1
A pre-release of v0.6.1, and the first release built and published from the
self-hosted Forgejo CI rather than GitHub Actions. It holds everything
listed under Unreleased at the time:
-
One column on every page. A server's OVERVIEW and SETTINGS, AUTOMATION
and its event and dynamic-config editors no longer split into two columns
on a wide screen; they read top to bottom like the other pages. -
Import servers another tool set up. A server from another server
manager, or one copied over by hand, no longer has to be renamed and given
a hand-writtenasm-config.json.yaasm server import "<folder>"lists the
servers in a folder (or YAASM's own servers folder, with no folder) and
imports one, or all with--all; IMPORT on the new-server page and the
assistant'sfind_importsandimport_serverdo the same. YAASM makes a
new server on its own build, copies the old one's saves, config and logs
in, and keeps its map, ports, session name and admin password. An id is
made from the folder's name, since an id can't hold spaces. The old folder
is left as it was, for you to delete once the new server runs. Mods are
usually not written in the old server's files: give them when importing
if the world uses any.yaasm doctor, which the installers run, now says
when YAASM's servers folder holds servers it doesn't manage yet. -
A Windows node's port is checked against the firewall.
yaasm doctorwarns when Windows Firewall blocks the node port a controller
reaches the machine on, andyaasm firewalllets it in, with the same
rule as YAASM's web port. Before, a node whose web app stayed on this
machine could be unreachable from its controller with nothing saying why. -
A node can take over as controller. The controller keeps a copy of
its accounts, tokens, player history, bans, events and node list on every
node. If it's gone for good,yaasm node promote(or PROMOTE on a node's
OPS › NODES) makes that node the controller from the copy, and the other
nodes answer it at once. An old controller that comes back can no longer
command them, and says it was replaced. -
Clusters across machines. FLEET says, for each cluster with servers on
more than one machine, whether they all see one cluster folder (ONE
FOLDER) or not (FOLDER NOT SHARED, naming the machine that differs);
yaasm cluster listsays the same. The README's new Several machines
section covers pairing and how to put a cluster's folder on a share. -
Events reach every machine. An event made on the controller can name
servers and clusters on any node; each node changes its own servers at
the event's start and puts them back at its end, and AUTOMATION shows the
run with every machine's servers. START NOW and END NOW act on every
machine. A node's own events join the controller's at pairing; one that
would clash with an event already there joins switched off, saying why. -
One backup schedule, one set of update settings and one dynamic-config
library for every machine. The controller's are sent to each node when
saved, when a node is paired, and when a node comes back after being
down; a node's own pages then refuse changes to them, pointing at the
controller. A node's dynamic configs join the controller's library at
pairing, under a name of their own when one is taken, and its servers
keep exactly the settings they had. A node that couldn't take something
says so on OPS › NODES. -
Each machine's own settings, from the controller. OPS gains a
MACHINE picker once there is a node: paths, YAASM's own update, plugins
and the daemon panel below it then show and change that node's. A node
server's pages use its own machine's builds, plugins and firewall check.
On the command line,doctor,self-update,settings paths,
version,buildandplugintake--node. A node on an older version can still be
updated from the controller. -
Players and bans cover every machine. The controller's PLAYERS shows
who is on its nodes' servers too, keeps one history for the whole fleet,
and a ban, note or whitelist entry made there reaches every server on
every node. When a node is paired, its own history and bans are merged
into the controller's; from then on the node leaves them to its
controller, and its PLAYERS refuses changes to bans and notes, pointing
there. Unpairing gives it back what it had. -
Servers on nodes. Once a machine is paired as a node, its servers
show on the controller's FLEET beside its own, each marked with its
machine, and everything on a server's page works on them as on the
controller's: start, stop, the live chart, the console, settings, INI,
backups. + NEW SERVER asks which machine once there is a node, as do
yaasm server create --nodeandcreate_server. A server's id now has to
be unique across every machine, and a node bringing an id the fleet
already has is turned away at pairing with the list to move. A node that
stops answering keeps its servers on FLEET, marked unreachable. Players,
bans and the OPS panels are still each machine's own; they follow in
later releases. A controller and its nodes must all be updated to this
release together. -
Deleting a server works on Windows while another server on the same
build is running. It used to fail withAccess is deniedon one of the
game's DLLs, after deleting part of the server's folder; delete it again
to finish. Removing old builds and old plugin releases could fail the
same way and leave their files behind. -
The web app fits an iPad in landscape and a phone turned sideways.
Between about 900 and 1100 pixels wide, pages ran off the right edge of
the screen: the fleet's tiles and START/RESTART/STOP ALL, a server's
SETTINGS switches, the event editor's dates. In that range the search
field is now an icon, as on a phone, and the event editor is one column.
On an iPhone in landscape, text no longer grows and the sidebar keeps
clear of the notch. -
An event's start date sticks. A repeating event set to begin on a later
date used to start at the schedule's next match instead, and the editor
showed that date after saving, with no way to put the chosen one back. The
start picked in the dates view is now kept, and no run begins before it
(frominyaasm schedule eventsJSON). Moving the start no longer moves
the end, unless the start lands on or after it. -
EDIT beside a server's name, at the top of its page, changes the name
players see in the server browser. It's written into the game's config, as
the INI tab would; a running server shows the new name from its next start,
and the page says so. -
A server's id can be changed, from MOVE SERVER on a stopped server's
SETTINGS,yaasm server move, ormove_serverfor assistants. The id
is its folder under servers/ and what YAASM knows it by; the new-server
form now calls it ID rather than NAME, beside the session name players
see. Its folder moves, and its backups, schedules, plugins, the bans YAASM
applied there, its players' history and the events that list it follow.
On Windows, runyaasm firewallagain afterwards. -
Nodes, the first step towards one YAASM driving several machines. A
machine can pair with another YAASM, its controller: set
YAASM_NODE_LISTEN_ADDRon it, press PAIR on its OPS › NODES (or run
yaasm node pair), and type the code it shows on the controller's
OPS › NODES › ADD (oryaasm node add). The controller lists each node
with whether it's up and its version. The link is always encrypted, and
the code proves each machine to the other. Servers on nodes come in a
later release.
Fleet
- CPU and RAM on every fleet card. Each running server shows what it uses
(CPU 1.5% RAM 7.8 GB), and the header shows the machine's memory. The
line stays grey while things are normal and turns amber or red when a server
is using most of the machine's CPU or the machine is running out of memory,
so a healthy fleet has nothing to read. It can be hidden from OPS › SCREENS. - A server's RAM chart leads with the amount. The top of the chart now
reads7.8 GB / 64, as on the fleet card; the share of the machine moved to
the legend, next to CPU's.
v0.6.0
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. Alsoyaasm player ban|unban|bans,
andban_player,unban_playerandlist_bansfor 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. Alsoyaasm player whitelist,
yaasm server edit --whitelist on, andlist_whitelist,
whitelist_playerandunwhitelist_playerfor assistants. - A server with
-exclusivejoinin 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, inyaasm player noteandadd_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 --statussays 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=valuelines, 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-pluginsor
withoutPluginsfor 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
andyaasm doctornow say so, andyaasm firewalladds 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-allinyaasm server edit.-ServerPlatform=ALLis what
the game does without being told, so the switch changed nothing. A server
that had it on starts exactly as before.
v0.5.0
Installing YAASM is now one command, on Ubuntu and on Windows, and on Linux
YAASM runs as an account of its own. Existing installs carry on as they are.
yaasm setupsets YAASM up on a machine in one go. It asks where
YAASM keeps its files, showing the space free on each disk, and whether
the web app is for this machine only or the whole local network. Then it
installs the service, checks the result withyaasm doctor, and prints the
address to open, where the web app asks for the first account. Every
question has a flag, and--yestakes the suggested answers. Run it again
to repair an install: it never moves your data.- Linux: one command installs YAASM:
install.sh, attached to this
release, piped into bash
(curl -fsSL …/releases/latest/download/install.sh | bash).
It replacesinstall-linux.sh, which releases no longer carry. New
installs run YAASM and its game servers as ayaasmsystem account
(--current-userkeeps them on yours), and you're added to its group so
theyaasmcommand still signs in.--yesinstalls without a terminal,
for agents and provisioning scripts. An existing install keeps its
account, binary and folders. - Windows: one command installs YAASM:
install.ps1, attached to this
release, in PowerShell (irm …/releases/latest/download/install.ps1 | iex).
It putsyaasm.exein%LOCALAPPDATA%\Programs\yaasmand on your PATH,
downloads SteamCMD from Valve if needed (checking Valve's signature), and
runsyaasm setup, which asks for Administrator rights once, to install
the service. - Linux: the service shares its local token with its group in
/run/yaasm, which is how theyaasmcommand signs in to a service
running as another account. Reinstall the service (sudo yaasm service install) to get it on an existing install; nothing changes until then. - The README explains reaching YAASM from other devices: changing the
address setup chose, the local network, Tailscale step by step, and a
reverse proxy on a domain of your own, with Caddy and nginx examples.