deploy_home

326 Commits 1 Branch 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
Bastian de BylandClaude Opus 5	ba9c4f2bfe	fix(zomboid): re-sync the world settings from the live server The vendored Sophie preset and the running debbzoid world had drifted, and the repo only held the preset. That is not a restore point: force-pushing it would have reverted the admins' in-game tuning rather than recovering it, which is exactly how a Sophie world quietly became an Apocalypse one once already -- 139 values reverted, loot from 0.35 back to 0.9, CharacterFreePoints 0 to 60. files/zomboid/sophie/SandboxVars.lua is now a snapshot of the live world taken 2026-08-31, not the preset as shipped. The modlist is untouched and still upstream, which is why zomboid_preset_version now names the two halves and their separate dates. server.ini.j2 carries the eight keys that had drifted: PlayerSafehouse false -> true SafehouseAllowNonResidential false -> true (the diner/gas-station case) SafehouseAllowRespawn false -> true SafehouseAllowLoot true -> false SafehouseAllowFire true -> false TrashDeleteAll false -> true MapRemotePlayerVisibility 1 -> 4 ResetID 6953472 -> 826046 ResetID is in that list on purpose, and matters most. It is the world's soft-reset token: a file value that differs from the one the live world was created with tells every connected client to roll a new character. Carrying the live value makes a deliberate force-push a no-op instead of a server-wide wipe prompt. Spawn config gets its own switch, zomboid_spawn_force. spawnregions.lua and spawnpoints.lua are the only config a running world re-reads -- at every server start, where SandboxVars is read once, when the world is created -- so a spawn edit is deployable on the live world without a wipe. Sharing zomboid_config_force between them would have meant force-pushing the whole preset to land a one-line spawn edit, rewriting the INI (hence the ResetID hazard above) and the world's SandboxVars along with it. config-template/ now tracks the repo unconditionally. Nothing on the host writes that directory and the server cannot see it, so it has no hand edits to protect; if it does not track the repo it is not a restore point, just an older world's settings. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016QdWYhwUtwM2NQGukiRh12	2026-09-05 09:11:31 -04:00
Bastian de BylandClaude Opus 5	a0421226a2	fix: correct four stale mod IDs in the Sophie preset On 42.20.3 the server loaded 279 of the preset's 283 mods and reported the other four as "required mod ... not found". None of it was a download problem: all 256 workshop items fetched, and every one of these four is in the preset's own WorkshopItems= list. Only the ID each is referenced by has drifted. Checked against the id= field of the mod.info files on disk rather than folder names, which are unrelated to mod IDs -- an early look at folder names was misleading here. FWOBenchPress&Treadmill -> FWOBenchPressTreadmill (stray ampersand) Ladders42131 -> Ladders4220 (per-build variants; 42131 is the 42.16 one) ServingPlatesB42 -> ServingPlates42 NewMusic_OrchestraMix -> NewMusic_CMM (renamed upstream to "Classical Music Mix") Kept as a rename map applied at template time rather than edited into the vendored list, so the list stays a faithful copy of upstream and re-vendoring a newer preset keeps the corrections. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-26 02:23:31 -04:00
Bastian de BylandClaude Opus 5	d34c6cd36d	rebuild the Zomboid server on the Sophie 42 preset as "debbzoid" The deployment had drifted badly. It was pinned to the Steam `-beta unstable` branch, which stopped being right the moment B42 became the default at 42.20, and it wrote every mod ID with the `\` prefix that B42 required only during that unstable period and now rejects. Three server profiles were carried around (vanilla, modded, b42revamp) whose mod lists were hand-curated blobs from a Steam collection that has since moved on. Moves to the Sophie 42 community preset, vendored from GerDeathstar/sophie-pz ("Sophie 42 Files.zip", 2026-07-31 == the b42 release tag): 283 mod IDs, 256 workshop items, map_distanciado over Muldraugh, plus its SandboxVars, spawnregions and spawnpoints. Sophie's gameplay settings are kept exactly as shipped -- PVP with its damage modifiers, the safety system, MaxPlayers=32, PauseEmpty, no sleep, safehouses off. Only the keys this deployment actually owns are templated over the top. The modlist is stored as YAML lists rather than the INI's semicolon blobs, so the next Sophie update produces a diff you can read. Exclusions live in zomboid_mods_excluded with a reason each, seeded with IconsInventory -- already absent upstream, listed so a re-vendor cannot quietly bring it back. Config is now seeded before first boot instead of patched after it. The old approach could not write the INI until the server had generated one, so every setting went through lineinfile guarded on a stat; seeding the whole file from the preset removes the chicken-and-egg and puts the config in git. force is off by design: these files are a starting point, not managed state, so the server can be stopped, hand-edited and regenerated without Ansible clobbering the edits. Push them again deliberately with -e zomboid_config_force=true. The B41 Discord keys were dead. B42 replaced DiscordChannel/DiscordChannelID with DiscordChatChannel, which takes a channel name rather than a snowflake, so the DiscordChannelID=... this role had been appending was a key the server ignores and the chat bridge has not been working. Renaming the server to debbzoid is what starts the new world: PZ derives the INI, save directory and player DB from the name, so gregboid stays on disk untouched as a rollback. Re-enabled, because the reason it was off is now fixed. It was disabled for saturating the SSD -- ~10 MB/s of log writes into the shared journal, which starved Gitea CI badly enough to stretch a firmware build to 17 minutes. The container now logs to its own rotating k8s-file instead of the journal every other service shares, and logrotate caps the server's own server-console.txt and Logs/ at 100M keeping 3. copytruncate is mandatory there: PZ holds those fds for its whole life, so a rename would leave it writing into an unlinked inode. Memory is unchanged; idle draw is nowhere near MAX_RAM. Also stops the entrypoint recursively chowning the install tree on every boot. With 256 workshop mods that is a large inode walk and pure churn once the first run has set ownership. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-25 23:41:00 -04:00

Author

SHA1

Message

Date

Bastian de BylandClaude Opus 5

ba9c4f2bfe

fix(zomboid): re-sync the world settings from the live server

The vendored Sophie preset and the running debbzoid world had drifted, and the
repo only held the preset. That is not a restore point: force-pushing it would
have reverted the admins' in-game tuning rather than recovering it, which is
exactly how a Sophie world quietly became an Apocalypse one once already -- 139
values reverted, loot from 0.35 back to 0.9, CharacterFreePoints 0 to 60.

files/zomboid/sophie/SandboxVars.lua is now a snapshot of the live world taken
2026-08-31, not the preset as shipped. The modlist is untouched and still
upstream, which is why zomboid_preset_version now names the two halves and their
separate dates. server.ini.j2 carries the eight keys that had drifted:

  PlayerSafehouse              false -> true
  SafehouseAllowNonResidential false -> true   (the diner/gas-station case)
  SafehouseAllowRespawn        false -> true
  SafehouseAllowLoot           true  -> false
  SafehouseAllowFire           true  -> false
  TrashDeleteAll               false -> true
  MapRemotePlayerVisibility    1     -> 4
  ResetID                      6953472 -> 826046

ResetID is in that list on purpose, and matters most. It is the world's
soft-reset token: a file value that differs from the one the live world was
created with tells every connected client to roll a new character. Carrying the
live value makes a deliberate force-push a no-op instead of a server-wide wipe
prompt.

Spawn config gets its own switch, zomboid_spawn_force. spawnregions.lua and
spawnpoints.lua are the only config a running world re-reads -- at every server
start, where SandboxVars is read once, when the world is created -- so a spawn
edit is deployable on the live world without a wipe. Sharing zomboid_config_force
between them would have meant force-pushing the whole preset to land a one-line
spawn edit, rewriting the INI (hence the ResetID hazard above) and the world's
SandboxVars along with it.

config-template/ now tracks the repo unconditionally. Nothing on the host writes
that directory and the server cannot see it, so it has no hand edits to protect;
if it does not track the repo it is not a restore point, just an older world's
settings.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016QdWYhwUtwM2NQGukiRh12

2026-09-05 09:11:31 -04:00

Bastian de BylandClaude Opus 5

a0421226a2

fix: correct four stale mod IDs in the Sophie preset

On 42.20.3 the server loaded 279 of the preset's 283 mods and reported the
other four as "required mod ... not found". None of it was a download problem:
all 256 workshop items fetched, and every one of these four is in the preset's
own WorkshopItems= list. Only the ID each is referenced by has drifted.

Checked against the id= field of the mod.info files on disk rather than folder
names, which are unrelated to mod IDs -- an early look at folder names was
misleading here.

  FWOBenchPress&Treadmill  ->  FWOBenchPressTreadmill  (stray ampersand)
  Ladders42131             ->  Ladders4220             (per-build variants;
                                                        42131 is the 42.16 one)
  ServingPlatesB42         ->  ServingPlates42
  NewMusic_OrchestraMix    ->  NewMusic_CMM            (renamed upstream to
                                                        "Classical Music Mix")

Kept as a rename map applied at template time rather than edited into the
vendored list, so the list stays a faithful copy of upstream and re-vendoring
a newer preset keeps the corrections.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-26 02:23:31 -04:00

Bastian de BylandClaude Opus 5

d34c6cd36d

rebuild the Zomboid server on the Sophie 42 preset as "debbzoid"

The deployment had drifted badly. It was pinned to the Steam `-beta unstable`
branch, which stopped being right the moment B42 became the default at 42.20,
and it wrote every mod ID with the `\` prefix that B42 required only during
that unstable period and now rejects. Three server profiles were carried
around (vanilla, modded, b42revamp) whose mod lists were hand-curated blobs
from a Steam collection that has since moved on.

Moves to the Sophie 42 community preset, vendored from GerDeathstar/sophie-pz
("Sophie 42 Files.zip", 2026-07-31 == the b42 release tag): 283 mod IDs, 256
workshop items, map_distanciado over Muldraugh, plus its SandboxVars,
spawnregions and spawnpoints. Sophie's gameplay settings are kept exactly as
shipped -- PVP with its damage modifiers, the safety system, MaxPlayers=32,
PauseEmpty, no sleep, safehouses off. Only the keys this deployment actually
owns are templated over the top.

The modlist is stored as YAML lists rather than the INI's semicolon blobs, so
the next Sophie update produces a diff you can read. Exclusions live in
zomboid_mods_excluded with a reason each, seeded with IconsInventory -- already
absent upstream, listed so a re-vendor cannot quietly bring it back.

Config is now seeded before first boot instead of patched after it. The old
approach could not write the INI until the server had generated one, so every
setting went through lineinfile guarded on a stat; seeding the whole file from
the preset removes the chicken-and-egg and puts the config in git. force is
off by design: these files are a starting point, not managed state, so the
server can be stopped, hand-edited and regenerated without Ansible clobbering
the edits. Push them again deliberately with -e zomboid_config_force=true.

The B41 Discord keys were dead. B42 replaced DiscordChannel/DiscordChannelID
with DiscordChatChannel, which takes a channel name rather than a snowflake,
so the DiscordChannelID=... this role had been appending was a key the server
ignores and the chat bridge has not been working.

Renaming the server to debbzoid is what starts the new world: PZ derives the
INI, save directory and player DB from the name, so gregboid stays on disk
untouched as a rollback.

Re-enabled, because the reason it was off is now fixed. It was disabled for
saturating the SSD -- ~10 MB/s of log writes into the shared journal, which
starved Gitea CI badly enough to stretch a firmware build to 17 minutes. The
container now logs to its own rotating k8s-file instead of the journal every
other service shares, and logrotate caps the server's own server-console.txt
and Logs/ at 100M keeping 3. copytruncate is mandatory there: PZ holds those
fds for its whole life, so a rename would leave it writing into an unlinked
inode. Memory is unchanged; idle draw is nowhere near MAX_RAM.

Also stops the entrypoint recursively chowning the install tree on every boot.
With 256 workshop mods that is a large inode walk and pure churn once the
first run has set ownership.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-25 23:41:00 -04:00