• No code changed. Only the version number moves.
• FireFront 1.0.0 carries everything this mod reaches for. It was checked two ways:
  • Decompiling the 1.0.0 that Hexium serves. A mod manager's own download of it is byte-identical to the uploaded package. It has FireFront.Fire.FireManager with its static Instance, CollectActiveFirePositions(List<Vector3>), CurrentFireIgniterPlayerId and IgniteGroundNear(Vector3, float), one overload each, under the unchanged plugin GUID.
  • Booting a dedicated server on this build with FireFront 1.0.0. The bridge resolved on its first pass and raised no warning in the minute the server ran.
• The BepInExPack line moves from 5.4.2333 to 5.4.2350. That changes the file, not what installs. For that one dependency Hexium lists the current pack whatever the zip says: 5.4.2350 for the live 0.27.3, whose zip says 5.4.2333, and the same for this studio's other mods. It does not do that for FireFront.
• An older FireFront still works if you install by hand. The README says which FireFront each feature needs. The manifest line only decides what a mod manager fetches.
• The README now matches 0.27.3 on bosses. It said every creature that kills you gains a star; a boss is marked but never does.

The wild answers a spawn war again. On contested ground, wildlife (deer, boar and hares by default) refills quickly while the war lasts, as it did before Valheim 1.0. Nothing needs doing to upgrade.

The wild's answer, working again

Since Valheim 1.0 (Ragnarok's Wrath 0.27.0), the wild side of a spawn war did nothing. The mod raised wildlife spawns through the game's own attraction mechanism, the one the Bog Witch's meads use, and Valheim 1.0 stopped reading the two values that mechanism relied on. The war still starred hostile spawns harder and still resolved, but no extra animals came.

• In a contested zone, every animal on the wildlife list spawns at ContestWildSpawnChance (default 100%) instead of the game's own lower chance. It never lowers the game's chance, and 0 turns it off.
• The game's own limit on how many can stand there is untouched, so a war refills hunted-out ground quickly and never crowds it past what the game would allow. The first spawn check after you arrive, which makes up for time away, rolls at the game's own chance, because at 100% that catch-up could overshoot the limit. Raids and other event spawns are never affected.
• It is read on the game of the player standing there, like the rest of a war's local effects, so every player needs the setting in their own config.
• ContestWildMaxSpawned is retired. It never added an animal even when the game read it, and nothing reads it now. The first start removes its line and says so in the log. Your ContestWildSpawnChance stays exactly as you set it.

Packaging

• Tested on Valheim 1.0.16. The BepInExPack dependency is now 5.4.2351; FireFront stays at 1.0.2.

The config is two readable files now, with every value kept. Storm lightning checks for rain where it would strike. And a code review of 0.27.5 fixed a world's state leaking into the next one you load, storms ending raids, and titles swapping back and forth. Nothing needs doing to upgrade: the first start moves your settings and says so in the log.

Two config files, every value kept

The single com.raveniron.ragnarokswrath.cfg had grown to 148 settings in 18 sections, numbered in the order they were added. It is now two files:

• com.raveniron.ragnarokswrath.cfg holds 42 settings: every gameplay system's on/off switch and the few settings most servers change, such as storm timing and look, storm lightning, how often outbreaks start, the nemesis, announcements and the visual effects.
• com.raveniron.ragnarokswrath.advanced.cfg holds the other 104: rates, thresholds, intervals and lists.
• Both files use the same 15 sections, 01 - General to 15 - Visuals, one per system, so a setting sits under the same heading as its switch.
• Every description is rewritten in plain terms: what the setting does, in what unit, and, for the ones each player's own game reads, that it does.
• docs/CONFIG.md is a guide to all of them, section by section, and marks the gameplay settings each player's own game reads: sickness and chill, the exposure tiers, tired soil and the crop list, every land consequence with its thresholds and the wildlife list, grudges and spawn wars, the nemesis, and relic stones. Give every player the server's values for those. The visual effects are each player's own choice.
• Two settings are removed, because neither ever did anything. StormFireRiskMultiplier and StormWindMultiplier only ever fed a log line.
• The wind settings moved into 03 - Weather in the advanced file. The mod reads the wind, but since the two retired settings went, nothing uses it.

Upgrading. The first start of 0.28.0 moves every setting to its new place with its value. It keeps the old file beside the new ones as com.raveniron.ragnarokswrath.cfg.v1.bak (.v0.bak if it was last written by 0.27.0 or earlier, before config files recorded a layout version), and logs one line naming what moved and what was removed. wrath status shows the layout version the files are at. Going back to an older version? Restore that backup first. An older version cannot read the new layout and would start from its defaults.

An interrupted move is safe. If a file is locked or the disk fills, the mod leaves your files as they were and moves them on the next start:

• A save that fails part-way puts the file back exactly as it was, because BepInEx empties a config file before writing it.
• The main file is written only after the advanced one has saved, so no setting is ever lost between the two.
• If a setting turns up in both its old and its new place with different values (left behind by an interrupted earlier start and edited since), the new place's value is kept, unless it is only the shipped default. The log names both values either way.
• If the mod cannot read the file at all, it writes nothing to either file and says, in the log and in wrath status, that settings may be at their defaults until the next start.

Verified on a dedicated server (Valheim 1.0.15).

• A server config in the 0.27.x layout, with custom values, moved on the first start with all 146 of its values unchanged: 145 settings moved to new places, and one (AnnounceTitles) was already in its place, since its section kept its name. A second start changed nothing.
• A player's own config, last written by 0.27.5, moved the same way when they launched the game on 0.28.0.
• An interrupted move, rebuilt by hand under real BepInEx: a value edited in the new place was kept with a warning, and a default left there gave way to the old value.

Storm lightning checks for rain where it would strike

On a dedicated server, storm lightning struck in the rain. That was the default setup, with StormsForceWeather off. The game only works out the weather for a machine that has a camera, so a dedicated server's own weather reading never changes from the value it started with, and the rain check read that. The README promised "never in rain".

• Each bolt now asks FireFront whether it is raining where the bolt would land. FireFront works out the weather for any position the same way the game does for a player standing there. If it rains there, or FireFront cannot say, the bolt does not fall.
• This needs FireFront 0.21.0 or later when no storm sky is forced. With an older FireFront the log warns at startup, and no bolt falls unless StormsForceWeather is on.
• With StormsForceWeather on, nothing changes. The storm's own sky decides, as it has since 0.27.2.
• Verified on a dedicated server (Valheim 1.0.15, FireFront 1.0.2). With the server's weather forced to rain, all three bolts a storm rolled were withheld, each logged as "FireFront reads rain there". Forced clear, the next bolt struck about 30 m from the player and started a ground fire.

From a code review of 0.27.5

One save file gains an optional column: the titles file marks a player who has earned Winterborn this winter with a W, so the award stays once per winter across a restart. Older builds ignore the column and drop the mark on their next save.

• Each world keeps its own state. Going back to the main menu and then starting or hosting another world kept the first world's zone drift, titles, grudges, sickness and relic stones in memory. They carried on in the second world at the same map positions, and the next autosave wrote them over the second world's own files. Now a world's state is saved and cleared when you leave it, and the next world loads its own. A dedicated server runs one world per start and was never affected.
• Joining a server after playing a local world reads the server's state. The same leftover data made a player who went on to join a server see their local world's plague, frost, grudges and relic auras instead of the server's. The same fix covers it.
• A storm no longer ends another event. Valheim runs one event at a time, and starting a storm ended whatever was running: a raid on a base, or Valkyrie's Cargo's merchant visit. A storm that comes due during another event now waits, and starts once that event is over. If the storm event is missing from the game's list, the storm no longer starts at all (the log says why), where before it ended the running event and announced a storm that never came. One side effect: a vanilla raid pauses while no player is near it, so a raid everyone walked away from can hold storms back until someone returns to it or the game replaces it with another event.
• Titles no longer swap back and forth. Stormrider, Plaguewalker and Winterborn were awarded again on every title check while their condition held. Two that held together (plague in winter, a storm over plague) swapped every check, each swap announced to everyone. Every title is now earned once, when its condition starts. Winterborn's clock now starts again at zero each winter, so it is earned once per winter, after that winter's full stretch online; before, a server up through two winters awarded it the moment the second began. Titles earned at the same moment give one announcement.
• Arson blame stays with the arsonist's own fire. FireFront used to report a single igniter for the whole map, so while one player's fire burned, every other fire anywhere was booked as their harm.
  • With a FireFront that reports who lit each fire (1.0.2 or later), each fire's harm goes to the player who lit it, or the fire it spread from. Natural fires and lightning blame nobody, and a storm no longer holds its lightning back while someone's fire burns.
  • With FireFront 1.0.1 or older, harm is booked only in the zones next to where that player's fire has spread. A fire elsewhere on the map is no longer blamed on them. A fire started right next to theirs, while theirs still burns, can still be.
• Autosaves stay quick on old worlds. Saving the zone file compared every visited zone against every stored one, a pause on the server that grew with the world's age. It is now a direct lookup.
• Nearby messages are rate-limited per player. One shared limit meant a message to one player could silently swallow another player's one-time message elsewhere on the map, such as a relic's story or the line a player gets on first reaching barren or festering ground.
• Relic and zone messages are checked. The server drops relic and zone messages from a client that claims to be someone else. Clients accept relic and zone updates only from the server. A report that a relic stone broke counts only from a player near it, a report that one was raised only from the player the server asked to raise it, and the breaker is blamed only when they are near the stone.
• A mod manager now installs FireFront 1.0.2 with it (was 1.0.0). It is the first FireFront that reports who lit each fire. Installing by hand, an older FireFront now names itself at boot, with what it still does and what needs the update.