👁️ WubarrksEye (TheEye)

"Stop guessing what the IL does. Stop decompiling 130,000 lines just to find out if CanSenseTarget is virtual or static. The truth is in the assembly, and now it's in your hands."

📣 All my mods are alive, updated, and on Hexium

Every Wubarrk mod is maintained and published only on Hexium. If you got one somewhere else, it is stale. Current roster as of this release:

Valheim 1.0 lands and every one of these gets re-verified against it with this tool. 2.2.0 took the baseline; 2.3.0 survives the new build and tells you which mods did not.

WubarrksEye (TheEye) is a deterministic, cross-platform Valheim extraction tool. It is, without exaggeration, a vibe coder's wet dream. But let's be real, with this data at your fingertips you're not just a vibe coder anymore. You're an AI-augmented game mod designer, and your dreams can come true. When Valheim 1.0 drops and the API shifts under everyone's feet, this is the tool that maps the new world, tells you exactly what changed against your pre-1.0 baseline, and feeds it straight to your AI pair programmer.

Forget hand-grepping decompiled source for hours. Forget guessing why your Harmony patches misfire because you bound the wrong overload, or realising months later that your custom monster AI was inert because vanilla's Character.OnDamaged never fires for most creatures. TheEye gives you the ground truth of the game's architecture, serialized data, method call graphs and live world state, straight from memory.

This isn't a dumper. It's an autopsy table for the game engine, and as of 2.3.0 it comes with a before/after report and a mod impact report.

⚔️ What's new in 2.3.0 (the 1.0 migration release)

Built against the 1.0 public-test build (0.221.13, network version 37) and verified headless on both the last pre-1.0 server and the playtest server.

🛡️ Survives the build change

0.221.13 moved sectors from Vector2i to Vector2s, replaced the seven ZDOExtraData.Get*s(ZDOID) readers with one GetData(out ...), and turned World.m_worldVersion into an enum. Every member TheEye touches that moved is now late-bound: it is looked up by name at first use and a missing one costs one field in one record, never a whole extractor. Manifest.json gains a Compatibility section listing every game member TheEye relies on and whether this build has it, and the BepInEx log says the same at startup.

🧩 ModImpact_Dump.json — which of your mods break on this build

Every plugin BepInEx loaded, plus any folder you point it at ([ModImpact] ScanPluginDirs or dump_eye scan=<dir>), is read with Mono.Cecil and every reference it makes into a game assembly is resolved against the running build. Per plugin: the exact unresolved methods, fields and types, the plugin methods that use them, every [HarmonyPatch] target that is missing or now ambiguous (a new overload appeared), and whether a preloader patcher such as Valheim10Compatibility bridged the gap in memory. Then the live Harmony patch map: who patches which game method. Run it from a clean profile with scan= pointing at your mod-manager profile's plugins folder and you have the day-one breakage list without loading a single mod. What it cannot see: targets found by string name or TargetMethod() show as Unchecked, and a field whose type changed is not bridgeable by any preloader, only by the mod (on 1.0 that is VisEquipment's item fields and the ZoneSystem / ZDOMan sector containers).

🧬 IL fingerprints: Huginn now sees body changes

Each API type carries a MethodBodies table, a hash of every method's normalized IL (opcodes, resolved operand names, relative branch targets). A method whose signature did not move but whose code did now shows up as BodyChanged. That is most of what a game update is (392 of the changes between 0.221.12 and 0.221.13), and it is what transpilers and behaviour-dependent patches trip over.

🐦‍⬛ Huginn's Report, classified

CHANGED API records carry a Members list that names each change the way an assembly differ would: Added, Removed, SignatureChanged, BodyChanged, TypeOnlyRipple (only Vector2i/Vector2s or Int16/Int32 moved) and Renamed (same IL fingerprint under a new name). Huginn_Summary.json gets a Breaking block (types and members removed, signature changes, ripples, RPCs and ZDOVars and console commands removed, plugins broken).

📝 Huginn_Report.md

The report a person reads first: both builds identified, per-file counts, breaking changes grouped by type, body-only changes, additions, registry changes by source, new items and prefabs, and the mod impact table with the unresolved references ranked by how many plugins need them (the bridge priority list).

🧠 Schema-aware diff

Upgrading TheEye between two dumps no longer turns every record CHANGED. A top-level field that exists in only one side's schema is excluded from the comparison and listed once per file as SchemaAdded / SchemaRemoved. Your 2.2.0 baseline stays useful.

🔑 ZDO keys resolve

Every string literal in the game and plugin assemblies is hashed (plus the _u / _i pair suffixes ZDO.GetHashZDOID builds) into the ZDO key reverse map. Most of the #hash keys in a modded dump now have names. New SectorIndex field on 0.221.13+.

🎛️ Console

dump_eye scan=<dir> noimpact, plus the 2.2.0 options. The active-area override finds InActiveArea / OutsideActiveArea overloads by name, so it works on both sides of the Vector2s change.

⚔️ What's new in 2.2.0 (the pre-1.0 baseline release)

🧾 Manifest.json — every dump knows what build it came from

Valheim stamps every DLL 0.0.0.0. So TheEye now writes, before anything else, the game version string with build hash, the Steam buildid, the md5 and size of every DLL in Managed/, the BepInEx version and every loaded plugin, the world name, seed and global keys, and the options used. A dump from a contaminated profile is visible on sight.

🐦‍⬛ Huginn's Report — a real diff, not a line hash

Every record in every file is keyed on its identity (type name, prefab name, ZDO UID, _Source/_Key). Huginn now says, per file, exactly which records were ADDED, REMOVED and CHANGED, and for CHANGED lists the field-level deltas with old and new values. Huginn_Summary.json has the counts. Pick the baseline: dump_eye baseline=<dir> or the config. Run it after 1.0 against your pre-1.0 dump and read the summary first.

🗺️ API dump rewritten

Full member surface per type: fields with modifiers and constant values, properties with accessor visibility, events, constructors, full method signatures with virtual / override / abstract, interfaces, attributes, nested types, enum values. Members are keyed by name so a renamed overload is one line in the diff. Game assemblies only by default; the 20,000-type mscorlib noise is gone.

📚 Registry_Dump.json — where a new biome shows up first

Enums with values, the ZDOVars hash table, console commands with cheat/server/admin flags, spawn tables, creature spawners, environments and biome weather, raids, piece tables with every piece and its costs, skill definitions, and the full localization table.

🧬 ZDO dump that means something

Prefab hash resolved to a name, rotation, sector, persistence, revisions, creation time, and every key/value the ZDO carries with hashes mapped back to ZDOVars names (health, owner, items...). The session-long ZNetScene active-area override that forced every object in the world to instantiate is now off by default.

📡 RPC names in the call graph

Every ZNetView / ZRoutedRpc / ZRpc.Register string literal, and the method that registers it. A renamed RPC breaks every mod that Invoke()s it by name; now it is one diff line.

🖥️ Headless

A dedicated server has no console to type into. [Automation] AutoDumpOnWorldLoad = true dumps once the world is populated, and AutoDumpQuit exits afterwards. One-shot server baseline.

🧹 Determinism and hygiene

UTF-8 without BOM (line splitters were dropping the first record). Types, prefabs, items, ZDOs and indexes sorted. Invariant-culture round-trip floats. Two dumps of the same build on the same world are byte-identical, and that was verified.

⚔️ Features carried forward

🕸️ Deep Call-Graph Extraction

Walks the method IL and emits call and field-access edges. Does an override call base? Which overload does a call site really reach, static or instance? Who calls method X? All in CallGraph_Dump.json, with call vs callvirt on every edge and a CalledBy inverted index.

💎 Serialized Value Extraction

Declarations tell you a field exists; Values_Dump.json tells you what is in it. Every item, recipe, status effect, prefab component, vegetation and location entry, flattened to dotted paths, cycle-safe, with per-entry budgets so it never explodes.

🚀 Zero-Stall Background Architecture

Coroutine-batched, RAM-profile scaled, cancellable, streamed straight to disk. The game keeps rendering, the server keeps ticking. A full dump on a dedicated server takes about a minute.

🍗 Guide to Extraction

• Launch the Game and load a world. (API and call graph work from the main menu; everything else needs a world.)
• Run the Dump: dump_eye in the F5 console, or F8 → Start Dump. eye_status shows progress. F9 toggles the HUD.
• Options: dump_eye baseline=<dir> nodiff noml nozdo noscene noloc
• Review the Goods: BepInEx/config/WubarrksEye_Dumps/<timestamp>/. AgentML_Complete_Dump.zip bundles everything as one minified JSONL plus the manifest for machine ingestion.
• Write Better Mods, you vibe coder you.

What You Will Find Inside

🔎 Why Before You Grep The Decompile

API_Dump.json answers three questions without reading a line of decompiled source:

1. Which type declares a member. Members are DeclaredOnly, so if m_targetCreature sits under MonsterAI it is not on BaseAI. Binding the wrong type throws MissingFieldException into a catch that swallows it.
2. The full overload set with complete parameter types.
3. virtual / override / abstract, derived from GetBaseDefinition().

CallGraph_Dump.json answers method body questions reflection cannot see:

• ChainsToBase: Humanoid.OnDamaged does not call base, so a patch on Character.OnDamaged never fires for most creatures. Player.OnDamaged does.
• Calls[].Op: call vs callvirt, which is how you tell a base chain from re-dispatch, and a static target from an instance one.
• CalledBy and RpcRegistration indexes.
• ModImpact_Dump.json: one record per plugin with Unresolved, Bridged, PatchTargets.Problems and Status, then HarmonyPatch index records and a ModImpactSummary.
• Huginn_Report.md, Huginn_Summary.json, Huginn_Diff_Report.jsonl when a baseline exists.

Accessibility is the runtime assembly's. Projects compiling against a publicized assembly_valheim see private members here as directly callable.

🧭 Taking a baseline before Valheim 1.0

1. Copy the game folder first. Steam overwrites it on launch day and the old build is gone.
2. Dump on a clean profile (BepInEx + TheEye only). Manifest.json lists every plugin, so contamination is at least visible.
3. Dump from the main menu, from inside a world, and from your dedicated server if you patch server code.
4. After the update: dump_eye baseline=<your pre-1.0 dump> scan=<your profile's BepInEx/plugins> and read Huginn_Report.md first. The mod impact table at the bottom is the list of mods to fix or bridge; the Breaking block in Huginn_Summary.json is the count.

⚙️ Configuration (wubarrk.theeye.cfg)

⚠️ Dependencies: BepInEx, Newtonsoft.Json (installed automatically as the JsonDotNET dependency)

📜 License

MIT. Copyright (c) 2026 Ross G. Support development at https://www.patreon.com/c/WubarrkDev