Universal Modder Updates
These are selected changes from the Universal Modder repository, each linked to the commit that introduced it. Dates use Asia/Shanghai (UTC+8) and mark when a change landed in the repository, which can be later than the game experiment behind it.
Use the installation guide for current setup, the CLI reference for command behavior and the examples for documented projects.
October 10, 2026: scanner and console improvements
The CLI began configuring its output streams for UTF-8, and game detection expanded to nested executable locations while avoiding common installer and redistributable folders. The same change added ZenGin detection and a Gothic 1/2 playbook, giving reconnaissance a more specific route for those installations. View the commit.
October 10, 2026: Minecraft/GTA field note gains reproduction details
The Minecraft/GTA passthrough note gained an October 9 second-PC report using an AMD GPU, along with launcher, build-environment and cleanup observations. The note separates the working composited view from features that were not retested on that machine; our Minecraft/GTA example guide covers both and the open installer issues. View the commit.
October 8, 2026: more guidance for planning game mashups
The mashup-mods material gained technique notes, a table of projects and a route-planning checklist. The additions address bridge contracts, frame compositing, collision, installer behavior and how strongly a project's evidence supports its claims, helping readers compare approaches before committing to a two-game build. View the commit.
October 8, 2026: forty field notes added
A repository change added 40 game and technique notes from a reverse-engineering workspace, spanning file formats, modding routes and engine-specific findings. Treat each one as a starting point and check its status before reusing its steps. View the commit.
October 7, 2026: a game-research skill joins the toolkit
The project added game-research-websearch to its skills and README. Its documented scope includes finding community material, using archived sources and service APIs, handing off sign-in requirements and preserving evidence, which supports the research stage before an agent selects a modding route. View the commit.
October 6, 2026: Claude plugin stops declaring a fixed version
The Claude plugin manifest's fixed 0.2.0 field was removed so the plugin integration could track commits. This was a plugin-manifest change, not a new Python CLI release; record the result of um --version separately when diagnosing an installation. View the commit.
October 5, 2026: OpenCode project configuration added
The repository added opencode.json to connect the skills and fal MCP server when OpenCode runs inside a clone. The README and agent instructions were updated with that route; the installation overview explains the current setup and its checks. View the commit.
October 1, 2026: broader agent integrations and shared field notes
The commit titled “v0.2” expanded the project beyond its initial Claude-focused setup with agent integration files, a shared knowledge base and the Minecraft/GTA example. Its timestamp is September 30 at 23:38 UTC, which is October 1 in the timezone used here; “v0.2” is the commit's label rather than a GitHub Release. View the commit.
Mod hub and release status
The README announces the mod hub as upcoming, with no launch date yet. Until it launches, there is no hub for downloading or publishing mods.
The project has not published GitHub Releases or tags, so follow development through commits and use the installation guide for current setup routes.
Follow a change on GitHub
Read the full commit history for changes omitted from this selection. Before updating an existing project, preserve its source and record the game, loader and toolkit versions; then repeat the checks relevant to the changed component.
For practical next steps, compare the Terraria example, AoE2 civilization example and Minecraft/GTA example, or use a planning prompt to investigate how a change affects your setup.