Brings in v1.4.3-v1.4.5 work: Trol's Hammer, Bone Servants, War Vulture
craftability, and the Aswid/Fenrir timed-claws rework, on top of the
bugfixes merged into main since v1.4.2.
Resolved conflicts in 7 files where main's post-v1.4.2 fixes overlapped
war-vulture's claws rework:
- README.md, manifest.json: took war-vulture's v1.4.5 content (main
hadn't touched either since the v1.4.2 release).
- RacesOfValheim.cs: plugin version -> 1.4.5.
- RaceClaws.cs: kept war-vulture's lazy EnsureRoster() fix for the
Fenrir claw-registration bug over main's belt-and-suspenders
Register(this), and dropped the now-stale comment referencing the
removed static constructor. Main's SetupDragItem race-ownership fix
carried through untouched.
- AswidConfig.cs/AswidRace.cs/AswidPatches.cs: adopted war-vulture's
single-key design (I toggles both Vampiric Aura and Devour together)
to match the documented v1.4.5 trader-safety fix, removing a duplicate
AuraEnabled field the two branches had each declared independently.
Kept main's IsDownIgnoringHeldKeys() input fix on top.
- RaceCompendium.cs: kept main's fact-checked Aswid/Fenrir entries
(war-vulture's copies were pre-fix stubs, one referencing a
nonexistent variable) and layered in war-vulture's timed-claws
wording.
Build verified clean (0 errors) after resolution.
The eye frame was read from the head bone's pose ON THE FRAME THE EYES
WERE BUILT, snapped to the nearest axis, then cached for the life of the
eyes. Catch the head a few degrees into a turn and the snap picks the
neighbouring axis, and the pair stays wrong until something rebuilds it.
Each race met this separately and each added the same guard - do not
build while attached, mid-attack or asleep - which caught the loud cases
and left the quiet one: a race change rebuilds while the rig is still
settling, which is none of those three. That is why resetting into a
race could break the placement while logging out and back in silently
fixed it. The logout was never a fix, only a rebuild at a calmer moment,
and no fourth guard condition would have closed it - the read itself had
to stop depending on when it happens.
sharedMesh.bindposes[headBone] is the rig as authored: no animation in
it, no timing, the same answer on frame one and frame ten thousand. A
rebuild is now deterministic and a bad moment cannot exist. Falls back to
the live read, warning once, on a rig that carries no bind pose.
Lives in one shared RigBindPose rather than in three copies. The three
eye implementations are separate files by design - they differ in what
they hang and how it is coloured - but this is the one piece of maths
where a divergence would be a bug in whichever copy got fixed second,
and it had already been fixed twice. The three now-dead private
SnapToAxis copies go with it.
Also updates the Aswid eye defaults to the values dialled in on screen:
forward 0.013, height 0.004, yaw 22.068.
Scale is inherited, so source.localScale could not come across either:
it is authored under a parent that puts the object at 0.02 lossy scale,
and re-parenting it under a head bone at ~95 drew the mesh some 4750x
too big - an eye the size of the character, centred near the face,
therefore mostly inside the skull with the corners reading as flat
rectangles. "Wrong place" and "blocky" were one scale error seen from
two angles. Carries lossyScale (the size the game actually draws it at
on a real skeleton) over the new parent's scale instead.
The remaining offset would not compute cleanly from either rig, so it
was dialled in on screen and written down as the new defaults rather
than guessed at again - size 1.1, forward 0.01, separation 0.007, yaw
24.664, roll -180 (the socket arrives upside down on a player's head
bone; that is the half turn that rights it).
The sliders that found those numbers could not have: they were bound at
+/-0.1 m and 0.1-5x, nowhere near far enough to pull the pair out of the
skull, so they read as doing nothing at all. Widened to +/-0.5 m and
0.01-50x.
Eye Rotation Y is now mirrored - the left eye takes the negative - so
the pair toes in or out together instead of both turning off the same
shoulder. X and Z stay shared on purpose: both eyes pitching up is a
face looking up, where mirroring pitch or roll would cross them.
Confirmed correct in game.
player.transform (previous commit) fixed the frame used for the
shift/rotation config offsets, but that code path is inert at every
offset's default of 0 - so it never touched the actual bug. The real
placement came from source.localPosition, copied straight off the
Skeleton creature's eye_l/eye_r and reinterpreted under the player's
own head bone. That only works if the two rigs agree on scale, and
they do not: the Skeleton's rig measured 0.02 lossy scale at the eye
bone against this player rig's ~95-100, with nothing tying one
prefab's authored scale to another's. Taken as-is it put the eyes
roughly 0.2 world units off the head bone - visibly floating above
the face, on every single build, matching the "never fixes, not even
after logout" report exactly.
Eyes are now placed from the player's own measured frame and three
fixed constants (BaseEyeForward/Height/Separation) - the pre-rewrite
sphere code's own numbers, already tuned and playtested on this exact
rig. Still borrows eye_l/eye_r for their mesh and material (the actual
point of the rewrite - real lit sockets instead of painted spheres),
just not their transform.
Confirmed against real numbers from in-game diagnostic logging rather
than guessed a third time; that logging has been removed.
Both files built their eye holder's forward/up axes from headBone.root
- the top of whatever hierarchy the head bone (from
VisEquipment.m_bodyModel's own bone array) happens to sit in. That
does not reliably resolve back to the player, so the measurement came
out wrong on every single build rather than on an occasional
bad-timing one - which is why resetting the race or logging out never
fixed it for Aswid, only starting a fresh build at the same wrong
reference every time.
DvergarVisuals.BuildEyes already reads player.transform directly and
does not have this problem - its own eye glitches are the ordinary
bad-pose-timing kind the attach/attack/sleep guard mostly covers,
which is why relogging (a fresh, differently-timed build) usually
fixes it. AswidVisuals and SvermVisuals now do the same.
Also gives SvermVisuals.ApplyEyes the same attach/attack/sleep guard
Aswid and Dvergar already had before building fresh, which it was
missing entirely.
Brings in the Sverm race, the War Vulture flying mount, and Skadi's
Crystal Golem (replacing the Hidden Hollow). Resolved conflicts:
AswidVisuals.cs took war-vulture's skeleton-eye-light rewrite with
main's attach/attack/sleep timing guard re-applied on top, and
RaceCompendium.cs kept main's rewritten race entries while folding in
war-vulture's Sverm/War Vulture pages and the new Claws paragraphs for
Aswid and Fenrir.
The Vampiric Aura had no on/off switch - it always drains/executes
nearby targets in every form. I now toggles it (AswidRace.AuraEnabled,
on by default), matching the existing toggle pattern already used for
Devour.
Devour's own toggle moves off I to make room and stays on by default;
its keybind is unbound (KeyCode.None) rather than removed outright, so
it remains a real Configuration Manager entry for anyone who wants to
bind their own key to it.
AswidVisuals/DvergarVisuals measure which way the head bone faces
exactly once, the first time BuildEyes runs for a given character, by
reading the bone's live pose at that instant and snapping it to the
nearest axis - then cache the result for as long as the eyes exist.
Taken while sitting, attached, mid-attack or asleep, the head can be
turned away from the body's own forward, and the snap picks whichever
axis is closest to that pose - landing the eyes behind the skull
instead of on the face, and staying wrong for the rest of the session.
ApplyEyes now defers the first build while the player is attached,
attached to a ship, mid-attack or asleep, since it runs again on every
subsequent UpdateColors anyway. Reduces the obvious bad-timing cases;
does not by itself rule out a mistimed read during ordinary idle
animation, which would need the measurement moved to the model's bind
pose (animation-independent) to close out completely.
Also shrinks the Aswid's eyes by 10% (EyeSize 0.062 -> 0.0558), per
request.
Confirmed improved by playtest.
BepInEx's KeyboardShortcut.IsDown() ends in ModifierKeyTest, which
requires that no key outside the shortcut is currently held - it only
exempts the mouse buttons. That is right for a config-menu hotkey and
wrong for a game ability: holding W (or any other movement key) made
every bound ability in the mod stop responding, for every race, mouse
bindings included. Vanilla attacks kept working because they go
through ZInput, which is what made it look like a Skadi/dragon bug.
Adds RaceInput.IsDownIgnoringHeldKeys / IsPressedIgnoringHeldKeys -
main key down plus every modifier held, without the blocking rule -
and switches all 27 call sites across Aswid, Dvergar, Fenrir, Skadi,
Trenta and Trol over to them.
Arrived with the rebindable-keybind work that shipped in 1.4.0.
Same root cause as the Factions fix (9287bd0): mobToTrophyMap keyed the
Goblin family by "Fuling"/"FulingShaman"/"FulingBerserker" - none of which
are real prefab ids - instead of "Goblin"/"GoblinShaman"/"GoblinBrute".
The trophy icon lookup was unaffected (it already used the correct
TrophyGoblin/TrophyGoblinShaman/TrophyGoblinBrute ids on the dictionary's
value side), but the food-tuning block gated on
PrefabManager.Cache.GetPrefab<GameObject>(mobName) succeeding silently
never ran for any of the three - so their food fell back to generic
CookedMeat nutrition instead of a Goblin-scaled amount, and never got the
20-minute humanoid-prey burn time the "StartsWith Fuling" check was meant
to grant them. Renamed the check to "StartsWith Goblin" to match.
Verified in-game.
Adds AswidConfig.cs, following the SkadiConfig pattern: one Configuration
Manager section per topic (Keybinds, Passive Combat, Vampiric Aura,
Superhuman Senses, Eclipse, Devour, Domination), covering every tunable
number and all five ability keybinds (Bat Form, Mist Form, Eclipse, Tame,
Toggle Devour). Defaults match the previous hardcoded constants exactly.
Also fixes a real mismatch found along the way: the tame hover-text
hardcoded "[K] Tame" while the key that actually triggered taming was U.
Both now read the same configured Tame key, so the hint stays correct if
it's rebound.
Config sections are bound alphabetically by race (Aswid before Skadi) in
RacesOfValheim.Awake(), since Configuration Manager's category list
follows bind order.
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>
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.
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 [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.
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.
UnityEngine.Input reads the device directly, so abilities bound to keys
or mouse buttons kept firing with the map, the inventory, a chest, the
chat or a menu open - clicking an item in a container also swung the
transformed attack.
Route that input through Player.TakeInput, which is what Valheim runs
its own controls through and already reports false for those states
(InventoryGui covers the backpack and chests alike). Aswid's transform
keys were the only place already doing this; the shared helper replaces
that one-off and covers Skadi's cold spell, form keys, flight toggle,
form attacks and flight boost, Fenrir's form keys and the attacks of all
four form behaviors, Trol's rock throw and true form, and Aswid's devour
toggle.
Cultist fire is a held button, so it is gated per read rather than
around the block: opening a GUI mid-stream now falls through to
StopFire() instead of leaving the flames running.