The jaw hung off the side of the skull because a creature rig carries bones a
human rig has no answer for. Unmatched bones fell back to bones[0] - the root -
so the mandible was skinned to the hips and followed them. The remap now walks
the creature'''s own hierarchy upward until something matches, which lands a jaw on
the head. It no longer opens, which no player will notice, and it is attached,
which every player did. Teeth and any other facial part the model carries are
fixed by the same walk.
The head flame never appeared. It was built by hand out of the smoke material
with a hand-rolled fire gradient, which at best would have read as a wisp rather
than a burning skull, and at worst never resolved a source at all and returned in
silence. It now clones real fire particles off a vanilla prefab - the torch
first, ground torches and the fire pit behind it - and says in the log which one
it took, or warns if none of them resolved. The torch light comes with it, at
half range and reduced intensity, since a light tuned to fill a corridor from
waist height blows out a face at point-blank range.
Fader now stands 15% taller. That scale goes on the player root, which is how
this race has always sized itself, so the collider, the camera pivot and every
equipment attachment scale with the mesh rather than leaving the model to drift
away from them.
The poison immunity fix before this one was necessary but not sufficient: it kept
the damage modifiers current, on an effect that was not there.
SE_SkeletonStats carries every damage modifier the race has - pierce and slash
resistance, the weakness to blunt, and the poison immunity - and it was applied
in exactly one place, the moment the player clicked Skeleton in the race menu.
Status effects are not saved with a character and do not survive death, so from
the next respawn or the next login onward a Skeleton simply had none of them.
That is why a blob still poisoned a tier 5 Skeleton. It is now re-applied
whenever it is missing.
The Moder regeneration bonus was broken the same way round: SkeletonRace wrote
m_healthRegenMultiplier onto the registered template, but SEMan.AddStatusEffect
clones what it is given and adds the clone, so the write reached nobody. The
effect now sets it on itself, alongside the modifiers it already rebuilds per
tier.
Also lights the skull. Cosmetic only, worn with the fire-tier model and nothing
else. It is parented to the player and moved onto the head bone each frame
rather than parented to the bone: the rig is authored at roughly 100x and a
particle system inheriting that would put a bonfire where a candle belongs.
Swaps the model the race takes at Moder. Hildir'''s skeleton is built on the same
rig as the plain one, so the 0.85/1.20/0.85 squeeze goes with it - that existed
only to make the charred twitcher'''s broader, shorter proportions read as a
player, and the bone-by-name remapping the swap relies on now has an exact rig to
match against rather than an approximate one.
The compendium no longer claims the bones blacken, since they no longer do; the
fire aura it describes is unchanged.
An unresolved model id used to fail silently and invisibly - the human body is
switched off before the replacement is built, so a bad name leaves a player with
no mesh at all. It now warns once per name.
Four separate faults were behind one player report.
The tier table had drifted a long way from the published progression. Poison
immunity arrived at Bonemass instead of Eikthyr, auto-stun at The Queen instead
of The Elder, and lifesteal jumped 20/30/40 where the description promises a
climb in fives from 5% to 35%. Rewritten to match the description tier for tier,
which is the copy players actually read.
Poison immunity never worked even at the tier that granted it. SE_SkeletonStats
built its damage modifiers in Setup, which runs once when the effect is applied -
at spawn, before any boss has fallen - and nothing ever asked again, so the
modifiers stayed frozen at tier 1 for the whole session. Everything else the race
does re-reads the rules per hit, which is why only the modifiers looked broken.
They are now rebuilt when the tier actually changes.
Max health was whatever three scaled sausages happened to add up to. A Skeleton
cannot eat, so the race fakes three permanent foods to carry the tier bonus -
sound enough for regeneration, which Valheim drives off the food list, but the
number the game reads is Food.m_health, recomputed every second from the burn
curve, and anything that leaves those foods partly burnt or one short quietly
costs health. A Bonemass Skeleton had 95 where the table promises 165. The foods
stay for regeneration; the total is now overwritten at Player.GetTotalFoodValue,
which has exactly one caller and decides the number outright.
Skeleton Secrets was a one-line placeholder returning the same sentence at every
tier - never written rather than broken. It now unfolds tier by tier, and opens
by naming the standing the race believes it is on, so the next player who kills a
boss and sees nothing change can tell a tier that failed to advance from an
unlock that failed to fire.
The charred model moves from Fader to Moder, where the description asks for a
fire skeleton, and summons stay skeletons at both tiers rather than turning
charred at Fader. Both are one-line reverts if the old look is preferred.
Trenta: a greydwarf shaman trophy is hung on the player head bone and sunk into
the skull until only the horns and branches clear it - the Furling wears a goblin
head the same way, aimed at the opposite result. A trophy is a plain static mesh,
so unlike the Dvergar hood there is no rig to collapse: the player own head does
all the hiding, which makes the three offsets in TrentaConfig the entire look.
They are a first pass and want eyeballing in game.
Draugh: the smoke and the cloud of flies only ever existed on the client of the
player wearing them. DraughRace is a single MonoBehaviour that looks at
Player.m_localPlayer and nothing else, so in multiplayer every other player saw
an ordinary, unrotted Viking. The build moved to DraughVisuals, which takes a
Player, and RacesVisualController now grows the same aura on every remote Draugh
it can see. Nothing is networked and nothing needs to be - each client reads the
race off the ZDO and makes its own particles.
Both hang off VisEquipment.UpdateVisuals or the visual controller, the two hooks
that already run for remote players, so neither had to invent a sync path.
Wolf, Ulv, Fenring and Cultist all hid the player by scaling the Visual child
to a thousandth of its size. That has quietly stopped working: the scale reset
that keeps a non-Trol player at normal height runs from a postfix on the same
update and puts the scale straight back to 1, so the man reappeared standing
inside his own wolf a frame after transforming. Fenrir is not one of the races
listed as sizing itself, so nothing exempted it from that reset.
Use PlayerVisualHider, the same fix Skadi and the Aswid already carry: renderers
go off with forceRenderingOff and are re-swept periodically, so nothing that
touches the transform can undo it, and the Animator is never disabled - which is
what made reverting look like respawning back when this was solved for the
dragon forms.
Both the local form and the copy other players see are switched over; the remote
path in ZdoVisualSync used the same scale trick and had the same bug.
Three things stood between a clean machine and a working build.
net48 reference assemblies now come from the Microsoft.NETFramework.ReferenceAssemblies
package, so the plain SDK is enough and no Visual Studio install is needed to
supply the targeting pack. Build-time only; nothing reaches the shipped DLL.
Jotunn publicizes the game assemblies and then references them, but it reads the
flag that enables it out of DoPrebuild.props, which its own Paths.props imports
through $(SolutionDir) - undefined on a `dotnet build` of this project, the same
trap that already caught the packaging target. The flag never arrived, the
publicizer never ran, and ten references failed to resolve on every build. It now
runs exactly when its output is missing: once on a fresh machine, never again,
and -p:ExecutePrebuild=true still forces it after a game update.
Jotunn 2.29.2 also references UnityEngine.ProfilerModule, which this build of
Valheim does not ship and nothing here uses. Dropped.
Build is clean: 0 errors, and the only warnings left are the pre-existing unused
locals and fields.
VALHEIM_INSTALL and BEPINEX_PATH were read from machine-level environment
variables that a fresh clone does not have. With them empty every derived path
started at the drive root, so the first Copy of a build failed on a new machine.
They now default to the standard Steam install and the environment variables
still override.
The DLL has exactly one destination, BepInEx\plugins, and it goes there on Debug
builds too - that is the loop you actually iterate in. If the folder is missing
the build warns instead of failing. The Thunderstore and Nexus zips stay in
dist\ and stay Release-only.
Copying assemblies into the Unity stub project is now opt-in
(-p:CopyAssembliesToUnity=true). It rewrote a folder of game assemblies on every
build for the sake of asset authoring that most builds are not doing.
dist\ is ignored. Only a stale icon.png was ever tracked in there - the packaging
step reads the real one from JotunnModStub\Package - so it is untracked, not
deleted.
The hover window that holds a form level after you stop powering goes from 2
seconds to 5, so gliding is a choice rather than something that happens to you
the moment you let go.
Shift while holding W spends 15 stamina a second for 22 m/s instead of 12. It is
the only part of flight that costs anything - base flight stays free, because the
drake arrives at The Elder, long before a player has the pool to pay for simply
staying airborne - and running dry drops you back to the free boost rather than
out of the sky.
S beats backwards along the aim, pitch included: look down and press it and you
rise away from what you are watching. Reverse thrust alone would have spun the
dragon round to fly nose-first away from the camera, putting its tail where its
breath comes out, so the form claims AlwaysRotateCamera for exactly those frames
and keeps facing what it is retreating from.
Water is no longer a trap. Character.UpdateMotion asks IsSwimming before it ever
looks at m_flying, so a dragon that touched the sea was handed to UpdateSwimming
every frame: the flight patch never ran and there was no way back up short of
finding land. The Aswid's bat escapes this only because debug-fly is checked at
the very top of UpdateMotion, before water is considered at all - which is
exactly why it can take off from the water and Moder could not. Those frames now
go back to UpdateFlying, and while in swim depth the form climbs regardless of
where the camera points, so the surface is something you break out of rather than
something you sit in. Nothing that merely asks IsSwimming - the Wet status, the
animator, stamina - is touched.
All five speeds now run through m_flySlowSpeed instead of the m_run/m_flyFastSpeed
pair, which only ever picked between two of them.
Trenta, the Dvergur rename, and three fixes since 1.3.10.
The manifest description still listed seven races - it was never updated when the
Dvergur shipped either - so it now names all nine, alphabetically. Both copies of
the manifest are updated; the packaged one is what Thunderstore reads.
Race Progressions in the README are sorted alphabetically rather than by the order
the races happened to be written, which had stopped being an order at all.
The changelog keeps saying "Dvergur" for 1.3.10, because that is the name the race
shipped under. Only the sections describing what is currently true were renamed.
A vegan, tree-born race unlocking new perks per boss defeated: skin/hair
tint, blocked non-vegan food, awakened seed foods after Eikthyr, a mob
hostility list, Photosynthesis, elemental resistances, Purple Rain after
the Elder, swim/poison/wet immunity after Bonemass, Last Stand and Thorns
after Moder, a Homecoming Portal after Yagluth, Hornet's Nest after the
Queen, and Muspell (a half-size Elder transformation with Stomp/Spike
attacks) after Fader.
Also fixes RaceScale never listing Trenta as self-sizing, which let a
shared Player.Update postfix fight Muspell's own scale changes every
frame.
The aura dealt its damage through Character.ApplyDamage, which only edits
the local copy of a character. On anything we do not own - in multiplayer
that is most mobs - the owner overwrote the health change on the next sync,
so the aura neither hurt anything nor showed anything. It also bypassed our
own Character.Damage patches, which is why it never healed and never
triggered devour-on-kill despite being the *vampiric* aura. It now calls
Character.Damage, which routes RPC_Damage to whoever owns the target, and
sets m_dir so the target reacts to the hit.
The aura no longer has to be channelled by holding block in bat or mist
form. It ticks on its own in every form, with no key to hold and no icon or
message of its own; the form only decides how hard it bites - half damage
as a human, full as a bat, double as mist.
Also guarded the sunrise mist auto-revert with isTransformingSequence.
Without it the revert re-triggered on every frame of its own one-second
animation, stacking coroutines that fought over the same visuals and status
effect.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Rename covers the folder, all seven filenames and every identifier, status
effect name and display string. Valheim's own Dverger/dvergr prefab references
are untouched - the names never collided.
The race id is what sits in m_customData and the ZDO, so renaming it alone would
have handed every existing character the selection menu again. DvergarRace
migrates the old id on spawn, before anything else reads it.
Runic Spark is modelled on Skadi's Ice Affinity and deliberately shares its
shape: live from the base tier and growing a flat step per progression state, so
+2 at Base through +16 after Fader. Lightning rather than frost, and like
Skadi's it rides every blow rather than melee only. AddFlat gained the elemental
channels while it was there - lightning would otherwise have landed in generic
damage.
The Trol remote-sync trace fired on a two-second timer for as long as a remote
player existed, which in the main menu is forever: Player.m_localPlayer is null
there, so the character preview counts as remote and it never stopped. Keyed on
the state it reports instead, so it still catches a remote player being sized
wrongly without narrating an idle menu.
Death runs Skills.OnDeath, which is only
LowerAllSkills(m_DeathLowerFactor * Game.m_skillReductionRate)
and the world modifier works by driving that rate to zero. LowerAllSkills then
takes nothing off m_level, as intended - but it also wipes m_accumulator on
every skill and prints "$msg_skills_lowered" unconditionally, whatever the
factor. So a death on a no-skill-loss world still quietly threw away all the
progress banked toward the next level and still announced a loss.
On a skill sitting just short of the next level that is indistinguishable from
losing one, which is how this surfaced on Blood Magic - the skill the Aswid
gains fastest, and so the one most often near a boundary.
The guard is on the factor rather than on any race, so it holds for every skill
and every race, and a world with a partial death penalty is left alone. It logs
the factor and the world rate on each death, since a death that lowers nothing
and a death that lowers something are otherwise identical from in-game.
Mastery forced Player.HaveEitr true and skipped Player.UseEitr, and neither is
what refuses the attack. Attack.Start gates on Character.TryUseEitr, whose first
test is GetMaxEitr() == 0 - an Aswid carrying no eitr food has a maximum of
zero, so the cast was rejected there and HaveEitr was never consulted at all.
That is also why it looked intermittent: it appeared to work for anyone who
happened to be eating eitr food and failed for exactly the player it was written
for, one leaning on blood magic without eitr.
TryUseEitr only gates - the spend is a separate UseEitr call - so returning true
there costs nothing, and the existing UseEitr prefix still blocks the drain. The
health price is untouched; it is meant to be the whole price.
The local-Aswid-holding-blood-magic test was written out three times and now
lives in one helper, so the weapon lookup cannot drift between them.
The 1.3.10 entry had the Aswid aura and Guardian Power fixes but nothing at all
about the race that is the release. Adds a short description to the changelog
and to the features list, with the tier-by-tier detail in Race Progressions
alongside the other seven.
Leaves out the AswidDebug log removal, which is already filed under 1.3.9, and
the spectral claw, which is in the tree but disabled.
A Windows .lnk stores an absolute path to the machine that created it, so the
file resolves for nobody else who clones the repo. It arrived alongside the
dist icon and has no business being versioned.
The local shortcut is left on disk; only the tracking is dropped. *.lnk joins
.gitignore so the next one does not follow it back in.
Vampiric Aura was centered 2m in front of the player instead of on
them, and its Blood Magic scaling only ever added up to +1 damage at
level 100; rebalanced to a 1 base + up to 5 scaled split.
Aswid Bat Form, Skadi Cold Spell, Skadi Drake/Moder Form and Fenrir
Wolf Form all borrow the native "gpower" animator trigger for its
arms-raised casting pose. That clip carries a baked-in Animation Event
that calls Player.ActivateGuardianPower(), which fired regardless of
who triggered the animation - borrowing it silently cast the player's
real Guardian Power (and burned its cooldown) whenever one was
available. Added a brief, time-based suppression window in RaceInput
around each borrowed trigger so only that one call is swallowed.
Also includes AswidSpectralClaw.cs, a boss-scaled bare-fist damage
item for Aswid, currently disabled pending equip-state fixes.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The dump settled both.
Skin: UpdateColors writes m_bodyModel.materials[0] _SkinColor, which is what
the postfix already targeted, so the patch was never wrong - the colour was.
_SkinColor multiplies the human skin texture rather than replacing it, and
(0.72, 0.74, 0.82) is close enough to white to change nothing anyone can see.
Every race that reads clearly commits to a channel, so the Dvergur now does too.
Hood: the dvergr mesh reports zero triangles because it ships with Read/Write
disabled, so its vertices and indices are unreachable at runtime and no submesh
carving could ever have produced geometry. The rig does carry a hat1/hat2/hat3
chain that nothing but the hood is skinned to, so the hood is isolated without
touching the mesh at all: instantiate the whole body, detach the hat chain from
the skull, and collapse the armature root to zero scale, which pulls every
vertex weighted to it into a single point and leaves only the hood standing.
Alignment is computed rather than measured - the object is shifted by the gap
between the hat bone and the player head bone - so there are no hand-tuned
offsets, only optional nudges. Animator and LODGroup are stripped alongside the
MonoBehaviours since neither is one and both would keep driving or hiding the
rig, and the renderers are set to update when offscreen because the collapsed
bones leave the skinned bounds meaningless.
The log settled it: the Dverger prefab holds a single renderer, dvergr, with
the hood, body and clothes baked into one mesh. There was never a separate
object to lift out, so the whole-object search could only ever fail.
Resolution now falls through three steps - a separate renderer object, a
submesh picked out by its material name, and an index pinned by hand in
DvergurConfig - and the submesh path rebuilds the chosen triangles as a
standalone skinned renderer. Vertices, bone weights and bindposes are all
carried over untouched and only the triangle list is narrowed, so the skinning
still lines up and the player rig places the hood without any offsets.
The candidate list also covers the mage variants, which wear a different hood
and may keep it as its own object.
dumpdverger now reports submesh count, per-submesh material and triangle count,
which is the part that actually identifies the hood.
The tint was applied the way the race-selection menu appears to do it, with
VisEquipment.SetSkinColor followed by UpdateColors, and had no visible effect.
That pair is not what colours a player: UpdateColors rebuilds the body material
from Valheim own state each refresh, so a tint only survives if it is written
after it runs. Every race here that visibly changes colour already has a
postfix on UpdateColors setting _SkinColor on the material, and the SetSkinColor
calls in the menu are decorative on their own. The Dvergur now follows the Trol.
Reading the race from the ZDO with a m_customData fallback and no local-player
check covers the main-menu preview and the first spawn frame, where
Player.m_localPlayer is still null. Nothing needs saving or restoring either,
since the tint stops being applied the moment the race changes.
Beard and hair go pale to match; the hood hides most of the hair but the beard
shows.
Height goes from 0.70 to 0.78. The spec asked for at least -30% but that read as
too small beside a human on screen.
Health: the malus was taken off Character.GetMaxHealth, which only made the
getter lie. Character.SetMaxHealth is the one thing that clamps current health
to the new maximum and it never saw a lower number, so the bar shrank while the
value stayed where it was. Player.SetMaxHealth also flashes the bar whenever the
new maximum is above GetMaxHealth(), so against a getter that always read low
every food tick looked like an increase and re-triggered the flash. Taking the
malus off Player.GetTotalFoodValue instead puts it upstream of both, and leaves
Valheim to do its own clamping on an honest number.
Scale: applied from the plugin MonoBehaviour, it was overwritten on the same
frame by Trol's Player.Update postfix, which forced every non-Trol player back
to scale 1. Sizing now happens in a postfix on that same method, the way the
Trol does it, and RaceScale records which races size themselves so they stop
undoing each other. This also fixes the Furling, which was losing the same race.
Hood: the Dverger Circlet is a metal band, not the hood, and instantiating a
skinned mesh leaves its bones pointing at the source prefab so it renders
nowhere. The headgear is now lifted off the Dvergr NPC and rebound to the
player's own bones by name, as the Skeleton does for whole bodies.
Skin is tinted to a dvergr grey, saved and restored through the same
OriginalSkinColor keys the other tinted races use.
Adds a dumpdverger console command: prefab contents live in the asset bundles
and cannot be read outside a running game, so this is how the hood mesh and the
per-star LevelEffects colours get identified.
An eighth race built on the existing per-race pattern: a MonoBehaviour driver
registered from Awake, a progression table keyed on the boss state, an SE_Stats
carrier, and Harmony patches for the individual perks.
The helmet slot stays free. Whatever the player equips keeps every one of its
stats and only its mesh is swapped for the dvergr hood, which is the Skeleton's
helmet handling turned into a replacement rather than a plain hide.
Every percentage the spec left open lives in DvergurConfig as a named value and
is marked TODO there, so tuning the race never means touching the logic. The
knobs are static readonly rather than const so that switching a perk off with a
zero does not fold its guard into dead code.
The [AswidDebug] logging shipped in 1.3.8 wrote a line per aura tick per enemy
in radius, four times a second while channelling, plus a line for every devour
attempt and every inedible kill. It filled BepInEx's log for anyone playing an
Aswid. Genuine failure warnings are kept and retagged [Aswid]; the F8
consume-nearest-mob test patch goes with it.
PlayerVisualHider.Diagnostics is off now that transformed bodies are confirmed
hidden. It is a static rather than a const so flipping it back does not leave
the guarded calls unreachable.
The 1.3.9 changelog also records the logging removal, and that remote Skadi
flight now works for observers - the second of the two known issues left open
in 1.3.8, confirmed in multiplayer.
Bumps manifest.json, the packaged manifest and PluginVersion, adds the 1.3.9
changelog entry and swaps in the updated package icon.
Ships the transform animation fix along with the multiplayer and Aswid work
merged after 1.3.8: remote dragon forms now animate for other players, remote
Trol sizing is corrected (the 1.3.8 known issue), Aswid food buffs survive
death, and Surtlings, Bears and the Greydwarf family have real nutrition.
Hiding the human body with SetActive(false) on the player's "Visual" also
disabled the Animator that lives on it, and Unity rebinds an Animator when it
is re-enabled: the controller restarts from its entry state, which for the
player is the get-up clip played when joining a world. Every Skadi dragon form,
Bat Form and Mist Form therefore ended with the player standing back up off the
ground.
PlayerVisualHider hides the body by suppressing its renderers instead, leaving
the GameObject active so the Animator and ZSyncAnimation keep running for the
whole transformation. Hiding uses forceRenderingOff on top of Renderer.enabled,
which nothing else in the game writes on a character, so the body cannot be
un-hidden behind our back.
Applied to the local and remote paths of both races, and to the ZDO sync's
revert so a remote player who dies mid-form cannot stay invisible.
Bumps manifest.json, the packaging copy under Package/, and PluginVersion -
the last of which had been stuck at 1.3.2 since well before 1.3.6, so BepInEx
and every log line reported the wrong version.
Changelog covers everything since 1.3.6: the Draugh race, the Race Menu Ward
and personal progression, the Aswid aura/diet/keybind work, and the Skadi
combat cost rework and tier rebalance. The known multiplayer issue with remote
Trol sizing and remote Skadi flight is written down rather than left implicit.
Also documents the Draugh and the ward in the README itself, which still
claimed six races, and drops three Furling progression lines that had been
duplicated verbatim.
Packaging fixes, both in the target added last commit:
- SolutionDir is only defined when msbuild is handed a .sln, so it expanded to
"*Undefined*" and broke `dotnet build` of the project on its own. The repo
root is derived from ProjectDir instead.
- Zip names now carry the version, read back out of manifest.json so a release
is still numbered in exactly one place:
dist/RacesOfValheim_Thunderstore_1.3.8.zip and _Nexus_1.3.8.zip.
Race Menu Ward: a buildable ward (2 wood, hammer/Misc, no crafting station)
that manages your race outside the debug console - reset the race, switch
between the server's boss progression and your own, and advance that personal
progression by offering a boss's secondary drop to it. One is placed near the
sacrificial stones on first load of a world, by the host only.
BossProgressionManager grows a personal mode alongside the world one. The tier
is stored on the character rather than the world, so a personal tier travels
with the player between servers instead of being tied to whichever world
unlocked it. resetrace and the ward now share RacesOfValheim.ResetRace so both
paths clean up identical state.
Also in progress, and NOT yet working: remote Trol sizing and remote Skadi
flight. Both are computed from the observer instead of the observed -
- Remote Trols are scaled from the observing player's own progression, and
never show True Form, because SE_TrolTrueForm only exists on the transformed
player's client. Each Trol now publishes its state and True Form flag onto
its own ZDO for others to read.
- Remote Skadi dragons sink to the terrain regardless of the altitude being
replicated: Character.m_flying is only ever set on the flying player's
client, so observers run grounded motion under gravity. Flight is mirrored
through the ZDO and the remote copy's rigidbody gravity is disabled while it
lasts.
Neither has fixed the symptom yet, so both paths keep a throttled diagnostic
log reporting what each observer actually computes. Committed to get the
instrumentation onto the branch, not because it works.
Packaging no longer hardcodes another machine's desktop path: Thunderstore and
Nexus zips go to dist/ on Release builds only, and the DLL is copied into
Valheim only when VALHEIM_INSTALL actually points at a plugins folder.
It was a placeholder reading "The secrets of winter will be revealed
soon...". It now unfolds tier by tier like the Aswid and Furling ones,
covering the passives, the form keybinds, the flight controls and which
attacks are free. The frost bonus and spell damage figures are computed
from the same formulas the code uses, so the text cannot drift when
those constants are tuned.
Dragon melee never dealt damage at all: the damage block sat behind
!isMelee, so bite, claw and spin played an animation, charged eitr and
did nothing. Melee now sweeps for targets the way Fenrir's claws do, and
costs nothing - it is the baseline attack that has to work at every tier.
Everything Skadi casts now runs on stamina rather than eitr. Eitr food
only exists from the Mistlands on, while the Cold Spell unlocks at
Eikthyr and the drake at the Elder, so the old costs were either
unpayable or, in the drake's case, silently ignored because UseEitr
never checked affordability. Ranged volleys are charged per projectile
so the sixty shard breath no longer costs the same as a three shard
spit, capped so the widest one stays castable.
The Cold Spell also stopped borrowing the Staff of Frost's damage, which
handed out Mistlands numbers from Eikthyr and multiplied them by every
shard. It now scales with progression, and the improved cast spreads one
budget across its shards: wider, not stronger.
The kick that played over every cast was Valheim's own SecondaryAttack,
bound to the same Middle Mouse button - suppressed for a Skadi holding
the spell. Moder now keeps its ranged attack on Middle Mouse in the air
as on the ground, with no left hand attack aloft, and Fader's airborne
branch is gone since its form cannot fly.
Ability cooldowns finally show on the HUD, each with its own icon and a
live countdown.
Eikthyr was carrying three unlocks while later tiers carried little, so
the two passives move up: the Freezing-to-Cold conversion now lands with
Bonemass alongside the drake's attack, and eitr regeneration first
appears at Yagluth with the improved Cold Spell.
The +20% at Eikthyr is dropped rather than relocated, since Yagluth
already granted an undocumented +50% - now written down in the README.
Both manifests still described five races; Trol has been playable since
1.3.1. Draugh is deliberately left out until it ships. The packaging
manifest was also stuck at 1.3.3.1, two releases behind the root one
the build actually publishes.