Mod Watch Dogs with AI: Disrupt engine field notes

These Watch Dogs AI mod research notes cover the Disrupt engine across Watch Dogs 1, Watch Dogs 2 and Watch Dogs: Legion. The four downloaded game reports are in-progress WD1 work; the technique notes add cross-game format and tool findings. A known file format is not proof of a finished mod. Single-player only: online modes are out of scope. Sources: WD1 game notes, cross-game toolchain.

Watch Dogs 1: four in-progress contributor reports

UI and world-entity editing

The UI report uses hV WD Modding Kit, JPEXS Free Flash Decompiler, Gibbed.Disrupt and Astrogrep to find and edit HUD components or world-entity data. It summarizes community tutorial results rather than claiming the agent reran them. .feu / .gfx editing and entitylibrary_rt.fcb round trips are distinct paths. Its gotchas include destructive dependency removal in JPEXS and converter copies missing their companion definitions. Source: UI and entity-library report.

Build identity and native patching

The engine-fundamentals report concerns WD1 PC x64 through NexusTools, with Ghidra and TinyCC 0.9.27. It describes shadow-capacity changes as a native-hook route with build-specific runtime profiles. Unknown or ambiguous layouts receive diagnostics instead of writes. Offline checks of bytes and layouts do not demonstrate that a live hook executed, rendered correctly or improved performance. WD2 comparisons in this report are static analysis only. Source: engine fundamentals.

Shadow Engine findings

The Shadow Engine report combines a native patch, Lua menu and file-mailbox bridge for shadow capacity, vehicle lights and a headlight limiter. It separates candidate presence, admission, bindings and submitted work; these counters do not prove a visible shadow or GPU completion. A cached-owner setting did not directly increase high-resolution shadows, and static archive features could not become live controls merely by adding a menu toggle. Source: Shadow Engine findings.

Shader compilation and delivery

The shader-pack report uses retail WD1 in Wine/Proton, NexusTools 1.1.12+, Gibbed.Disrupt and era-appropriate shader compilers. An unchanged repack launched and rendered, providing a control; a complete pack with appropriate SM5.0 DXBC also rendered. DXIL output and mismatched shader input/output signatures caused black-screen failures without helpful logs. The report remains in-progress, not an all-game shader installer. Source: shader-pack report.

Watch Dogs 2 and Legion: choose the target’s tools

The working cross-game toolchain note names UnpackWD2.exe for WD2, UnpackLegion.exe for Legion and Gibbed.Disrupt for WD1 archives below its documented size limit. It distinguishes upstream packers from downstream format, compression and sidecar fixes. The note says no unpack/repack cycle was run by that agent for this compilation of findings; its status does not convert every cited community claim into a firsthand test. Source: cross-game toolchain.

The working archive/container note distinguishes WD1’s BigFileV3, WD2’s BigFileV11 and Legion’s BigFileV13. The latter two are identified with a community fork, not assumed upstream capability. Legion’s compressed data uses an in-place LZ4 variant; ordinary LZ4 handling can produce incorrect output. Treat archive versions, compression and name hashes as target-specific. Source: archives and FCB containers.

The shader/model research distinguishes WD1 and WD2’s DX11 rendering from Legion’s native D3D12 ray-tracing path. It explicitly leaves WD1/WD2 RTGI integration and Legion’s DX12 shader recompile route unverified. The shader-pack game report records a later, specific WD1 rendering success; it does not settle every open question in the broader technique note. Sources: shader and model research, WD1 shader-pack evidence.

Meshes, materials, UI and collision references

The working mesh-format note describes XBG / GLM handling with XbgLab, GlmCompilerToXBG, the Blender add-on io_scene_WD2 and Ghidra. Its WD2 header version is 70.137. Miscomputed vertex strides, incorrect material hashes or unchanged table offsets can turn apparently exported geometry into garbage or holes. Source: XBG / GLM format.

The working material/texture note names WatchDogsMaterialEditor, XbgLab, Gibbed.Disrupt and Blender. A texture payload must retain its matching .xbt wrapper; material sizes, byte order and parameter-name hashes matter independently. A visually correct export is not enough to guarantee that the game can read it. Source: materials and XBT textures.

The in-progress SWF/FEU reference explains UI wrappers and tag ordering with JPEXS FFDec. It explicitly lacks an independently reproduced end-to-end round trip. Keep that format reference separate from the community UI results described above. Source: SWF and FEU reference.

The collision reference distinguishes old Havok packfiles from TAG0 containers. The community Blender tooling discussed there performs in-place displacement edits; it is not a general serializer that can freely add or remove collision data. It also warns that vendor headers can shift where TAG0 starts. Source: Disrupt HKX collision.

Searchable failures and their documented causes

game boots to a black screen (menus included) with no shader or pipeline errors in the log.

The shader-pack report attributes this failure to the wrong bytecode dialect, such as DXIL or shader model 6, rather than a broken container. Its fix uses era-appropriate shader-model output. Compare an unchanged repack first to isolate content from packaging. Source: shader-pack gotchas.

Repacked Legion archive won’t load

The container note attributes rejection to mismatched header fields. It lists package version 13, compression version 8 and name-hash version 70, with the appropriate LZ4LW-capable scheme. These are recorded format fields, not a new shell command. Source: archive gotchas.

Material loads then the game crashes on use

Incorrect size words in the material header can make the engine read the wrong offsets. The material note calls for correcting those fields, rather than assuming a texture replacement caused the crash. Source: material gotchas.

Texture appears all-white / wrong format

A generic wrapper can mismatch the payload format. The material note preserves the original .xbt header and matches the format when changing a DDS payload. Source: texture gotchas.

How to start your own Watch Dogs mod

Choose the exact title and installed build before adapting an item, port or engine-identification prompt template. Ask for single-player only, backed-up saves and files, and one small slice. The documented workflow prioritizes reconnaissance, backups and verification in the real game. Source: mod-any-game workflow.

Follow Install Universal Modder, compare routes in how to merge two games with AI and consult Errors. Keep any game-derived content on your own machine; do not redistribute game files or ripped assets. Source: contribution policy.

Frequently asked questions

Do these notes cover Watch Dogs 1, 2 and Legion?

Yes, but evidence differs. The four game reports concern Watch Dogs 1; cross-game technique notes explain WD2 and Legion tooling and formats. They do not establish a single tested mod compatible with all three.

Can I use the same archive tools for every Disrupt game?

Do not assume that. The toolchain note distinguishes UnpackLegion, UnpackWD2 and WD1 Gibbed.Disrupt, and distinguishes upstream tools from downstream fixes. Validate an unchanged round trip on the actual title first.

Is ray-traced GI verified for WD1 or WD2?

No. The shader and model technique note describes RTGI as research, with no verified in-game integration for WD1 or WD2. Legion has a native D3D12 ray-tracing path, but its shader recompile route remains unverified in these notes.

Can these mods be used in online modes?

Online modes are out of scope. This guide covers single-player only and does not give multiplayer setup or anti-cheat instructions.