chore(logging): strip the AswidDebug tracing and silence the visual hider
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.
This commit is contained in:
parent
3d0964ca80
commit
c3a3bd2864
4 changed files with 11 additions and 72 deletions
|
|
@ -17,9 +17,9 @@ namespace RacesOfValheim
|
|||
/// </summary>
|
||||
public class PlayerVisualHider : MonoBehaviour
|
||||
{
|
||||
// TEMPORARY: tracing for the transform-visibility work. Flip to false once multiplayer
|
||||
// transforms are confirmed good, along with the rest of the debug logging in 1.3.9.
|
||||
public const bool Diagnostics = true;
|
||||
// Tracing for the hide/show paths. Off by default; flip to true if a transformed body
|
||||
// ever shows up again and the log should name which path did it.
|
||||
public static bool Diagnostics = false;
|
||||
|
||||
// VisEquipment rebuilds item visuals whenever gear changes and they come back visible, so
|
||||
// the hidden set has to be re-swept rather than applied once.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue