The field guide / Universal Modder

How to merge games with AI

Last updated:

Merging games with AI means asking a coding agent to build a mod that brings one game’s content, simulation or live output into another. It is not a single universal conversion command. Universal Modder’s mashup-mods skill helps choose an approach for the games and behaviour you want.

This guide supports single-player modding only, with games you own. Install Universal Modder before using these prompts.

Decide what you want to merge

Call the game you play in the host and the game contributing something the guest. Do you want a vehicle’s appearance, its handling, or the whole guest simulation? The skill makes this question the starting point because each answer can require a different build.

Ask your agent to find field notes for both games and engines, identify your installed versions, and explain the closest existing project. A field note is a starting point, not proof that a different setup works.

Choose the lightest suitable approach

Port content or a mechanic

Build new host content that follows the guest’s design: for example, a vehicle or weapon. The host’s mod API supplies the runtime. This can avoid running a second game. The skill treats it as the lightest pattern when it delivers the intended result.

Run both games and bridge them

A passthrough build runs both sides and exchanges state or rendered output. In the skill’s Minecraft–GTA V example, the host supplies camera and ground information; Minecraft contributes colour and depth, and gameplay events cross the bridge. Aligning cameras, collision and timing is part of the work.

Embed a guest library

The skill also describes a guest runtime packaged as a library. The host provides input and collision; the library returns guest state and geometry. This needs an appropriate guest implementation rather than an arbitrary pair of game executables.

Rebuild a runtime or only its rules

A complete rebuilt runtime offers more control but is the heaviest pattern in the skill. A narrower option rebuilds the guest’s rules as a simulation and uses the host as the view. The Bloons TD 6–Minecraft note is the listed example of that rules-focused approach.

Start with a plan and one working slice

  1. Search prior work. Compare the knowledge base entries for the host, guest and engines.
  2. Protect your saves. Back them up before changes and use a safe test setup.
  3. Write the bridge contract. Decide which side controls the player, how coordinates map, and what happens when updates arrive late or a process stops.
  4. Pick a small proof. For a two-process bridge, the skill starts with one cube from one process appearing at the right place in the other. Then add position updates and collision.
  5. Verify in the real game. Compare screenshots and behaviour against the intended result before adding features. Record what worked and what remains untested.

The skill calls for recording the route in MODLOG.md and crossing-state decisions in docs/CONTRACT.md. Have the agent explain its plan and required installs before it builds.

Copy-paste prompts

These are original prompts based on the skill’s planning process, not terminal commands. Replace the bracketed names with games you own.

I own [host game] and [guest game]. For single-player, bring [one vehicle or mechanic] from the guest into the host. Search the knowledge base for both games and engines, identify my versions, and choose the lightest route. Explain the plan, back up saves before changes, and propose one small in-game test before building.
Plan a single-player two-game mashup of [host] and [guest]. First decide whether we need the guest simulation or only its look. Document player ownership, coordinate mapping, timing and shutdown behaviour. Begin with one object placed correctly in the host, then verify collision in the real game. Record anything untested.

For asset generation, use the fal API key guide or the README’s local ComfyUI image route.

Documented mashup examples

The following are project reports and index entries. We have not run these mods ourselves.

  • Minecraft inside GTA V story mode: the README describes camera, ground and event exchange, with Minecraft colour and depth composited into GTA’s frame. README example.
  • Halo Warthog in Minecraft: appears in the README showcase and “Try it” prompt. The knowledge index separately lists a broader Halo 3 content-port note. Halo note.
  • Portalcraft: the README and knowledge index list real Minecraft inside Portal 2 as a passthrough mod. Portalcraft note.
  • Bloons TD 6 inside Minecraft: the skill and index describe guest rules running as a headless simulation, with Minecraft supplying the view. Bloons note.

The index marks those four game notes “working”. That is the contributors’ status, not independent verification by this site. Full notes for the Bloons and GTA V examples are now available in our Minecraft guide and GTA V guide; the Halo and Portalcraft summaries here remain index-based.

Limits and safety

A successful build or a synthetic test is not a real in-game run. The skill explicitly separates those evidence levels. Keep the intended behaviour narrow, measure the bridge’s timing, and verify the actual host and guest interaction.

Use backups, owned installations and a single-player test environment. The README says the agent asks before installing loaders into game folders or driving your mouse and keyboard. A showcase clip does not establish compatibility with your installed versions or guarantee a finished mod.

Sources

Frequently asked questions

Can AI merge any two games automatically?

The project documents several mashup patterns, not a universal one-command merger. The route depends on the games, their modding interfaces and the behaviour you want to combine.

Does a working field note guarantee my setup will work?

No. A contributor status describes their reported result. Identify your installed versions and verify a small slice in the actual game.