The body swap read the race off the ZDO and gave up when there was none, which
is exactly the situation on the menu preview - FejdStartup instantiates a Player
and calls PlayerProfile.LoadPlayerData on it, so the preview knows its own custom
data and therefore its race, but it has no business owning a network view. It now
falls back to m_customData the way every other race in the mod already does, so a
Skeleton character looks like one before you press Start.
The tier falls back the same way. In the menu there is no world loaded to have
killed anything, so the preview is the base skeleton whatever the character has
done elsewhere.
feat(dvergar): age into a starred dverger's colours
One star at Bonemass, two at Fader.
Nothing is picked by eye. A starred creature in Valheim is not a second model: it
is the same one recoloured by LevelEffects, whose LevelSetup list holds a
hue/saturation/value offset per star. Those offsets are read off the Dverger
prefab at runtime and applied to the race's own slate blue-grey, so the tiers land
on the tints the game itself uses and keep following them if the prefab changes.
The tier comes from the ZDO key DvergarRace already publishes, so a remote Dvergar
is coloured at their own standing rather than the observer's - which matters as
soon as anyone runs personal progression.
Crossing a tier pushes a colour refresh through immediately, since the tint is
only written from the UpdateColors postfix and Valheim runs that on its own
schedule. Same treatment the health malus already gets a few lines above.
The hood is deliberately untouched.
The head flame was built inside SkeletonRace, a single MonoBehaviour that only
ever looks at Player.m_localPlayer, so the fire existed on one client and on one
player. Everyone else saw a bare skull. Same shape as the Draugh aura, same fix:
the build moves to SkeletonVisuals.HeadFlame, which takes a Player, and
RacesVisualController grows one for every remote skeleton it can see. Held per
player rather than statically - a static would hand the second skeleton in view
the first one is fire. Nothing is networked and nothing needs to be: the tier is
already on the ZDO, so each client works out for itself who should be alight.
The remote path also still collapsed the jaw at Fader, the charred-twitcher
leftover that was removed from the local path two commits ago - so other players
would have gone on seeing a Fader with no mandible. It is a restore there now
too.
Both halves of the dimming are reverted: scale to 1.8 and the torch light to half
range at 60% intensity. It was only turned down to get a clear look at the jaw
underneath, and the jaw is settled. The blaze is the point.
Fader collapsed the jaw bone deliberately: the charred twitcher it used to wear
there carried a jaw of its own and the two doubled up. That model is gone from
every tier now, and the skeleton worn in its place has a jaw that belongs on the
face - so tier 8 was losing its mandible for no reason. The collapse is gone and
what remains is a restore, so anyone left jawless by the old build gets it back
on their next frame.
Resetting to Human left a burning skull and an invisible jaw behind. Everything
the race puts on the player is taken off in one branch - the one entered the
moment IsSkeleton stops being true - and neither the head flame nor the jaw was
ever listed there. The flame was only ever switched off from inside the Skeleton
branch, which by then is unreachable, and the jaw was only restored at tiers
below 8, which a Human never evaluates. Both now come off with everything else,
alongside the body scale that already did.
The log settled it. All three skeleton models share one rig - 53 bones each, a
bone named Jaw in every one, and not a single bone falling through to the root -
which means the player rig has a real Jaw bone and the plain name match was
landing on it correctly all along. That is why the plain and poison skeletons
always looked right, and why pinning the skull group to the head deformed them.
Reverted; the parent walk stays for bones that genuinely match nothing.
Which leaves the real question: three models, one rig, one mapping, and only
Hildir wears its jaw wrongly. The difference has to be in how that jaw is posed
or bound rather than where it is mapped, so the diagnostic now prints the rest
transform of every skull bone alongside the player's own. One session loading a
working model and the broken one gives the exact correction instead of a third
guess at it.
The flame works - it resolved to the torch - but at 1.8 it was a white-hot bloom
that washed out the screen and hid the skull underneath, which is no way to judge
a jaw. Down to 1.1, with the torch light cut further.
The previous attempt only helped bones that matched nothing, and the mandible did
not move - which says the jaw was matching something directly all along, and
being bound to it. A creature jaw is authored against its own skull, so whatever
it lands on, a bone-for-bone match included, puts the mandible near the face
rather than on it.
Jaw, teeth, tongue and chin are now pinned to the head bone as a group, before
any name matching runs, so the skull renders as one piece. It cannot open any
more, which is a fair trade for being attached.
If that is still not it, the shape of the problem is not visible in a screenshot:
it matters whether the jaw has a bone at all, whether it matched, and what it
matched. The body build now reports exactly that, once per model per session -
every skull part and every bone that fell through to the root - so the next look
starts from data instead of another guess.
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.