Fixed

• A host no longer takes your keybinds. Registering a mod syncs its whole config file, which is right for anything a mismatch could desync and wrong for the one class of setting the readme had already warned against in as many words. Three mods here bind a key - Tether, Vaettir's stow and Devkit - so for as long as this stood, joining a server moved your keys to whatever the host had chosen, greyed the entry out, and put the value back if you tried to change it. Keybinds are now held back by type. A mod that genuinely needs one to match can still say so with Suite.Sync.

  discuss

Added

• Suite.Local, the other half of that. Keybinds are the only thing Core can recognise on its own, and they are not the only thing a player would resent losing - a UI scale, a colour, a hover-text toggle. Anything a mismatch cannot desync belongs to the player, and only the mod knows which of its settings those are.

  discuss

• shared\Prefabs.cs: one runtime prefab registry for the suite, as shared source rather than as part of this DLL. Five mods have their own copy, and the copies are not the point: the wrong version of this destroys saved objects in silence. ZNetScene and ObjectDB are rebuilt on every world load, including a trip to the menu and back, so a mod answering "registered yet?" from a static bool says yes to a scene that has never heard of the prefab, registration early-returns, and every ZDO of it is discarded as junk with nothing written to any log. Stow lost a built piece that way on 2026-08-16. Everything here asks the live scene instead. Prefabs.Keep takes a name and a builder and holds the thing registered for whatever world is loaded - both of ZNetScene's lookups, ObjectDB when it is an item, a tool's build menu when it is a piece.

  It is linked into each mod's csproj and excluded from this project, so Core gains no new responsibility and the mods gain no new dependency. That is the whole reason it is a file and not a class in here: Core is soft everywhere, and a mod that could not register its prefab would load, patch nothing into the world and look broken - so owning this would have made Core mandatory for five mods to do anything at all. A runtime fallback was considered and rejected for costing two code paths, the second of which only ever runs where nobody tests, which is how the bug above survived in the first place.

  Linked so far by Taum; the five mods carrying their own copy are a change each.

  discuss

Refused a connection: Balder (76561198662440314) has played on 1 other world(s)

Why it was missing

Judge is a prefix on ZNet.RPC_PeerInfo, so it runs before vanilla has parsed the package the player's name arrives in. All it holds at that moment is the socket. The name therefore had to come from Dyrr's own report, which the client sends first - so the report format moves to 3 and the name is the first field after the version, deliberately: everything below it can throw on a read and leave the report unreadable, and a report that failed halfway is exactly the one worth naming.

A format mismatch was already handled and still is, with the same clear line rather than a garbled read.

The bug

ZoneSystem.RPC_GlobalKeys clears every global key and re-adds them one at a time, and it runs on every client every time anybody sets any key, because SetGlobalKey ends in SendGlobalKeys(Everybody). For the length of that loop the dictionary this mod reads its roster and its credits out of is incomplete.

Vanilla never notices - the refill is synchronous, no frame boundary falls inside it. A Harmony postfix on GlobalKeyAdd does notice, and Yoke has one, hooked there deliberately so it catches the bulk list a server sends on connect. So every key in that list made Yoke ask this mod whether the group had cleared a boss, once per key, while the answer was built from whatever fraction had arrived.

With a partial roster the counted members can be exactly the ones who hold the key - the two who had just killed the Elder, whose credits were already in - and LatchIfGroupCleared then finds a group that has cleared it. The !anyCounted guard only ever caught a completely empty roster; a partial one walked straight through it. The open key is permanent by design, RPC_SetGlobalKey has no permission check, and so one client's half-loaded view became everyone's, for good.

The two-second roster cache is what let one frame of that outlive itself.

Fixed

• The latch refuses to run while the world's keys are settling. A prefix and postfix on RPC_GlobalKeys hold a flag across the rebuild; while it is up, nothing latches. This is the irreversible half of the mod, so it is the half that must decline to answer early rather than answer wrongly.

  discuss

• The roster is never cached from a half-filled key list, and is invalidated on every key that arrives rather than only on a publish. A cache can no longer outlive the world state it was built from.

  discuss

The seed calls the forest to it

• A planted sapling now draws greydwarfs to itself, and calls harder the closer it is to opening. Without this it was entirely passive, and the quest it actually set was "go and find a place greydwarfs already walk through, then stand in it" - a scouting problem rather than a defending one, and the wrong half of what the piece is for. Now the place you chose is the thing that matters, and what it summons is what feeds it: a seed planted in an empty meadow is slow rather than impossible, and one planted beside a real camp is still faster, because the camp counts too.

  discuss

• It ramps, and it is a raid rather than wildlife. The interval falls from 20 seconds at an unfed seed to 6 at one about to open, so the loudest part of the fight is the end of it. A constant rate is a wave you learn to stand in; a rising one can be heard without looking at anything. 90 and 30 were the first numbers and they were far too polite - one greydwarf every minute and a half is something you deal with between other jobs.

  discuss

• Ridden on vanilla's own SpawnArea, which is the component a greydwarf nest is made of. That buys the near and total caps, the floor-finding, the spawn effect, and - the part that matters most - its own guards: owner only, inside the active area, with a player in range. Nothing happens while you are asleep, which was the sapling's first principle and is the one thing a spawner could most easily have broken.

  discuss

• They arrive from a distance and run in rather than appearing around the seed. Found in play: they were materialising on top of it. Widening the radius does not fix that, because vanilla's FindSpawnPoint draws its distance from Random.Range(0, radius) - uniform across a disc, so most points land near the middle however wide it is. A prefix replaces that search with one that draws from a band, 35 to 60 metres by default, making the same two ZoneSystem checks in the same order so nothing lands inside a rock. Every other SpawnArea in the game runs vanilla's own method untouched.

  discuss

• Getting them to actually come is a second thing. SetPatrolSpawnPoint is off, so they do not treat the trees they appeared in as home, and a sweep every two seconds calls SetHuntPlayer on everything from the roster within reach - which is what a vanilla raid does and means "stop wandering, go and find someone". They hunt the player rather than the sapling: there is no vanilla "attack this object" to ride, the player is standing at the sapling anyway, and it puts the raid on the person holding the ground instead of on the thing with 500 health.

  discuss

• It says so. "The forest is enraged." goes to everyone within BeckonRange, centre screen, once per sapling per load - fired from the first wave actually landing rather than from planting, so a sapling that can find nowhere to spawn never announces a siege that is not coming. Everyone nearby rather than whoever planted it, because it is a warning about a place and on that frame there is nothing on screen to account for the noise. The text is a config line and blank turns it off.

  discuss

• The first wave leaves immediately. Vanilla counts its spawn timer up from zero on a two-second repeat and fires when it exceeds the interval, so an unfed seed produced nothing at all for 22 seconds and then the wave still had to walk in - half a minute of silence after planting, which reads as the mod not working. The timer now starts full, so the first wave goes out on the next tick. It does the same on every later load, and since the timer only advances with a player in range, walking back to a half-fed sapling restarts the siege as you arrive rather than after another silent interval.

  discuss

• The band came in from 35-60m to 25-40m with it, so the first wave is on you in roughly fifteen seconds rather than forty. Still far enough to be out of sight in forest.

  discuss

• They arrive in waves, from one side. Vanilla's spawner produces exactly one creature per interval, which is a queue rather than a raid - a greydwarf, a wait, another greydwarf, and nothing that has to be handled as a group. A wave is 2 at an unfed seed rising to 5 at one about to open, and the whole wave comes out of the trees within 40 degrees of one bearing so it can be turned to face. The extra members go through the game's own SpawnOne, so MaxNear and MaxTotal police themselves and a wave that would breach them simply comes up short.

  discuss

• A sapling now costs 50 greydwarf deaths, not 30. Thirty was chosen when the sapling was passive and thirty was roughly one raid happening to arrive. It does not wait for a raid any more, it makes one, so the number is the length of a fight you started rather than the odds of one finding you. Ten of them around you at a time, twenty-four alive in the area.

  discuss

• The trigger range is 48m rather than vanilla's 256m. A nest filling a forest you are nowhere near is one thing; a sapling quietly getting itself killed by what it summoned while you are two zones away is another.

  discuss

• Six standing around it at once, sixteen alive in the area. Deliberately more than the sapling survives being ignored for - it has 500 health and about ten brute hits in it - which is the trade the whole feature makes: the forest comes to you instead of you going out to find it, and the price is having to hold the ground.

  discuss

• All of it is off with one setting, and every number above is config.

  discuss

Black Forest only

• A seed refuses to go in anywhere but the Black Forest, and refuses the last five metres before the edge of it too. It is a greydwarf ritual - what it calls and what feeds it both live there - and one that works in the meadows makes the biome a backdrop rather than the reason.

  discuss

• The margin is checked on a ring of eight points as well as under the cursor, so the whole circle has to be inside. Planting one step past the treeline and then summoning the forest would put half the fight in the meadow, and a boundary is where a raid is least interesting.

  discuss

• Both the biome list and the margin are config, and the refusal says which of the two reasons it was.

  discuss

It will not go in anybody's base

• A sapling cannot be planted inside a base, and one already standing goes quiet if a base grows around it. This is the price of the seed calling: passive, one planted in someone else's home was rude; summoning waves of greydwarfs at it is a weapon, and a dozen around a stranger's longhouse is the obvious grief on a public server.

  discuss

• A ward already refused it and always did - the sapling is an ordinary piece, so PrivateArea turns it down like anything else. The gap was unwarded bases, which is most of them.

  discuss

• Filled with the game's own EffectArea.PlayerBase, which is what a workbench or fire radiates and the same test vanilla uses to keep creatures from spawning in your house. So the counter-play to a sapling planted next to you is to put a workbench down rather than to fight it, and "is this someone's home" stays the game's question rather than a guess of ours.

  discuss

• Any base, including your own. Working out whose it is means reading Piece.m_creator off whatever is nearby, which is more code for a worse answer - it would still stop you at a friend's base in co-op - and a wilderness ritual has no business in your own hall either.

  discuss

• The refusal says which reason. Vanilla would show "invalid placement", which is true and useless to somebody standing in their own garden.

  discuss

• Client-side, honestly. A modded client could ignore it; what makes it stick on a server is Core's version gate.

  discuss

Everyone defending it can see the count

• Fixed: only whoever landed the killing blow saw the counter. Character.OnDeath runs on the client that owns the creature and nowhere else, and the message went to Player.m_localPlayer - so with two players clearing greydwarfs around one sapling, each of them saw roughly half the kills register and neither could tell whether the other's were counting at all. They always were; only the message was missing. It now goes to every player within the sapling's own feed range, which needs no networking of ours because Player.Message already RPCs to a player this client does not own.

  discuss

A marker on the map

• A planted sapling puts a pin on your map, and takes it off again when it opens or is destroyed. This is the one piece in the mod you are meant to walk away from, and a seed in bare ground is not findable from fifty metres away - losing one to "I know it was around here" costs the same ancient seed as losing it to a brute.

  discuss

• Client-side and per player, saved in your own profile like a pin you placed by hand. Nothing about it is networked and a server needs to know nothing about it.

  discuss

• The pin comes off by reconciling against the world - a pin whose zone is loaded with no sapling under it is stale - rather than from the sapling's own OnDestroy. Found in play: the pins never went away. OnDestroy fires on a destroyed sapling and an unloaded one alike, and the test meant to tell them apart asked ZDOMan whether the ZDO was gone, which it never is on that frame - DestroyZDO only queues the uid on m_destroySendList and the ZDO leaves m_objectsByID some frames later. Both endings read as "merely unloaded". Asking whether a sapling is standing there needs no guess, covers every ending including one another player removed, and clears the pins the first version stranded.

  discuss

The spirit's parting has an effect again

• The parting effect shipped blank in 1.0 because the name it wanted was a guess about the game and the honest answer was "not confirmed". It is now a list walked in order - vfx_ghost_death, then two fallbacks - and the first name that resolves is used, so the wrong ones cost nothing and are skipped in silence. Looked up through PropIndex as well as ZNetScene, because plenty of effect prefabs carry no ZNetView and are invisible to ZNetScene however loaded they are.

  discuss

Not in this yet

• The sapling's staged growth and the sowing of a rank of seeds are still on v1.1-sowing, cut from 1.0 for their art. They are 1.2 now: the roadmap in the 1.0 entry below was renumbered when this release took the 1.1 slot, and that branch keeps its old name. Nothing here touches it, and merging is a separate job - it predates the 1.0 tidy-up and does not fast-forward.

  discuss

Fixed

• The key hook marks rather than acts. The flag is drained in Update, which is the first moment the whole list is certainly in. As a side effect a connect's worth of keys is now one walk of the item database instead of one walk per key.

  discuss