Skill Tree 1.8.1 – Sixth Sense / Stag perk causing client disconnects since Rust update 2636 (Nov 2026)

Hi imthenewguy,
Thanks for Skill Tree – it's a core part of our server. We're seeing a problem after the November 2026 forced wipe update, and we'd like to report it.
Environment

• Skill Tree 1.8.1
• Rust server version 2636 (protocol 2636.290.1), Oxide/uMod, forced wipe on 2026-11-06
  Symptom
  Players who have the "Sixth Sense" node unlocked are kicked within 5–20 seconds of joining, over and over. It only seems to happen when other players are nearby (for example, teammates standing next to them). The server console shows this client-side exception every time:
  <player> disconnecting: Exception (cs:170220): ArgumentException: An item with the same key has already been added. Key: NameTagVisCheck (UnityEngine.Transform)
  System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (...)
  QueryVisJobRunner.Register (QueryVis ...)
  Facepunch.UI.ESPPlayerInfo.(...) ()
  Facepunch.UI.ESPCanvas.Update ()
  We never saw this exception before update 2636. Within about 20 minutes of the wipe it had happened around 30 times across 3 players.
  What we think is going on
  Awareness.FindNearby() (Sixth Sense) runs every update interval. Each time, it:

1. sets PlayerFlags.IsAdmin on the player and calls SendNetworkUpdateImmediate()
2. sends ddraw.text for each tracked object
3. clears IsAdmin and calls SendNetworkUpdateImmediate() again
   It also does this when there is nothing to draw.
   Since 2636, it looks like the client registers nametag visibility checks (ESPPlayerInfo / NameTagVisCheck) for nearby players when it sees the admin flag. Repeatedly switching the flag on and off seems to register the same player twice, and the client throws and disconnects. We can't see the client code, so this is our best guess, but turning off Sixth Sense in the config stopped the kicks right away.
   The Stag perk of the Skinning ultimate ("Stag perk: Draw the enemy location?") uses the same admin-flag + ddraw pattern. It only draws when another team's player is within range, which matches the conditions of the crash, so we turned it off as well. Other places that use the same pattern (only when triggered): the Mining and Raiding ultimates, Sonar, Forager, Trap Spotter and Loot Spotter.
   Our temporary workaround

• Skill tree/Combat/nodes/Sixth Sense/enabled = false
• Ultimate settings/Ultimate settings for skinning/Stag perk: Draw the enemy location? = false
  Suggested fix
  Avoid the IsAdmin toggle entirely, for example by showing these markers as player pings instead of ddraw text:
• BasePlayer.AddPingAtLocation(BasePlayer.PingType, Vector3, float time, NetworkableId), or
• adding MapNote entries (isPing = true) for the owner only through the OnPlayerPingsSend hook, then calling player.SendPingsToClient(). This way teammates don't see them and nothing is stored in the player state.
  At the very least, skipping the toggle when there is nothing to draw would cut down how often it happens, but it would not fully prevent the crash.
  We can share more logs or test a build if that helps.
  Thanks for your time!

Very strange issue. I believe it has something to do with changes made this wipe to how admin flags work. I don't think admin flagging is required anymore for ddraw, so I will update it to remove the admin flagging component. I will look at pushing a release once wipe settles down and bugs stop flowing in. In the meantime, disable the skills you are having issues with (enabled: false).