Universal Modder supported games

Universal Modder includes engine playbooks, game field notes and worked examples. These are different kinds of evidence. An engine playbook explains a possible route. A field note describes work on a particular setup. An example directory contains code and instructions that you can inspect.

None of those automatically establishes compatibility with every edition, update or multiplayer mode. Before trying a mod, compare the game version, operating system, loader and testing scope with your own setup. The official knowledge index is the best starting point for finding a game-specific note.

The three examples below are documented by the upstream project. We reviewed their source instructions on October 10, 2026. We have not independently run these games or reproduced the mods.

These are upstream-reported setups, not a compatibility guarantee. The source links and caveats appear in each section below.

The Fal Arsenal example is a tModLoader mod with weapons, enemies and a boss. Its README identifies the source showcase setup as single-player tModLoader 2026.07 on Terraria 1.4.4. It also explains that parts of the original showcase tooling were removed or retained as reference material.

The example is useful for understanding a conventional mod project: source code, sprite layout, build instructions and a known loader. Its assets were generated with fal and processed into the frame layout the game expects. That does not mean you must generate new art just to inspect how the code works.

The README explicitly says multiplayer was not tested. It also warns that explosions change the world. Use a spare world, read the actual installation instructions and keep your important saves out of the first experiment.

What to verify: your Terraria version, tModLoader version, source folder layout, build process and enabled-mod state. If your setup differs from the recorded one, treat that as a compatibility question to investigate, not as a promise that the example will build unchanged.

A smaller learning task: inspect one weapon or one sprite's path through the project before trying to customize the entire arsenal. Keep the original example intact in a separate workspace so you can compare changes.

The Age of Empires II DE example documents a civilization called San Franciscans. Upstream describes an in-game test in September 2026 and presents the project as a template for a custom civilization.

The example includes a Robotaxi unit, Delivery Drones and a Transamerica Pyramid wonder. Its documented route combines generated assets, 3D-to-sprite rendering and game data changes. The files show how these parts meet; this is more involved than swapping a single image.

A detail worth noticing before you customize it: the example takes over the Burgundians' civilization slot. The README says it applies when the data mod is selected in the skirmish lobby. Do not interpret it as a new civilization that automatically appears in every game mode without affecting an existing slot.

What to verify: your DE build, profile paths, the data-mod selection, the underlying civilization slot and the sprite-generation dependencies. Read the current README's lessons and build steps before copying a generated directory into your game.

A smaller learning task: inspect one data change and the resulting skirmish behavior. Leave the full asset pipeline until you understand how the mod is selected and removed.

The Minecraft/GTA V passthrough example runs Minecraft alongside GTA V story mode and exchanges information between them. It is a code example with several interacting components, not a universal one-click installer.

Upstream records Minecraft Java 26.3 with GTA V Legacy on Steam, game build 3889, ScriptHookV 3889.0 and ReShade 6.8.0 in September 2026. Those details matter. The documented test is not evidence that GTA V Enhanced, another Minecraft version or a different loader combination behaves the same way.

The example handles camera synchronization, image compositing and events between the games. A failure can therefore come from the connection, game versions, rendering configuration or a component that did not load. A missing block or HUD cannot be diagnosed from the project name alone.

What to verify: ownership and normal operation of both games, the exact editions, loader versions and each component's startup instructions. Keep it in the documented story-mode context. Do not carry this setup into GTA Online.

A smaller learning task: read the architecture and confirm you understand the dependencies before attempting the build. For a first modding session, a single-game loader example has fewer moving parts.

Search the knowledge base by game name and then by engine. Read the actual note, including its version and verification section. A matching title in the index is a lead; the note tells you what was attempted and what was checked.

If there is no note for your game, the next task is recon. Ask the agent to identify the engine, available community loaders and a permitted local modding route. It may produce a useful research plan without producing a working mod in that session.

Do not turn an engine category into a long list of guaranteed supported games. Changes in packaging, protection, loader support and game code can alter the route even between updates of the same title.

If you already have a matching game and documented route, use the first-mod workflow to establish backups and a small test. If the example requires unfamiliar tooling, check requirements and costs before installing it.

If an example fails, save the exact version details and identify the last working stage. The troubleshooting guide will help you prepare a useful report without claiming an unverified fix.