How to Mod Dragon's Dogma 2 with Universal Modder

To mod Dragon's Dogma 2 with AI, install REFramework, have Universal Modder write a small Lua script, and confirm that script loads before you change a skill. The agent inspects the API, writes the script and interprets its logs; you run each test in the game. Use the general tutorial to prepare a reversible experiment.

Can Universal Modder mod Dragon's Dogma 2?

Yes, through a RE Engine → REFramework → Lua route. One released project changes Blink Strike; another adds an aimed teleport spell. Both run in Windows single player; check other skills, patches and platforms against your own setup.

REFramework supports Dragon's Dogma 2 and exposes a scripting API plus tools for inspecting game objects.

Keep experiments in local single player; a scanner finding no anti-cheat does not make networked use safe.

If you want to compare Lua workflows, Project Zomboid uses its own mod system rather than REFramework. For another action RPG, the Elden Ring guide explains a distinct offline native-code and data route. Check the game guide directory when choosing a project; knowing Lua does not make one game's APIs transferable to another.

What you need

The released teleport projects run on dd2.exe 3.2.0.0, Steam build 24831693 and REFramework revision 0a07faae. Check your current game and the chosen mod's release notes instead of installing an old binary to match.

Both teleport projects use the _ScriptCore terrain-query helper. That is a project dependency, not a requirement of every REFramework Lua file.

Step-by-step

1. Establish a working baseline

Start the unmodified game and record the exact behavior you want to change. Close it and back up the relevant saves. Choose a small, repeatable situation away from important progression. Write an expected result that you can actually observe.

2. Load REFramework by itself

Use the framework's own release and installation instructions for this game. For the non-VR build, place its dinput8.dll in the game directory. Test the framework before adding another script, and record its version. Follow the official REFramework instructions.

3. Prove that one Lua file loads

Create a project-owned script that only reports its name and version, with no game-state changes. REFramework offers two loading routes: ScriptRunner → Run Script for a selected file, or automatic loading from reframework/autorun. Confirm one copy runs once. See the Lua loading documentation.

This test separates a path or syntax error from a problem in the eventual mechanic. See the CLI and discovery reference if the agent is unsure which installation it is inspecting.

4. Inspect before calling game methods

Have the agent identify the relevant object and method in your installed version using REFramework's inspection tools. Ask for evidence of the parameter types, lifecycle and original behavior. For a first change, prefer one small display or setting adjustment over teleporting the player or replacing input handling.

Keep the code in version control and review the diff. Do not accept a method solely because its name sounds appropriate; a wrong signature can fail differently from a missing method.

5. Test one change and keep the log

Exercise the same action with the experiment disabled and enabled. Repeat after a restart and check that the logged script version matches the file you edited. Preserve a short reproduction sequence and the complete relevant log before changing anything else. Use debugging prompts to ask for one hypothesis at a time.

6. Test removal

Exit the game and remove only your own Lua file from automatic loading. Keep any shared library that other mods still require. Verify the original behavior using the pre-change environment and save. Do not remove the entire reframework directory just to disable one script.

Example prompts

Use these as development requests:

Use Universal Modder to inspect my Dragon's Dogma 2 setup. Record dd2.exe and
REFramework versions, active scripts and dependencies. First create a diagnostic
Lua script that reports only its own version. After I confirm it loads, propose
one small reversible feature and show the API evidence and test plan.

My script loads but the changed skill behaves incorrectly. Compare one disabled
run and one enabled run. Check the active script version, method parameter types
and the point in the action lifecycle where the change occurs. Preserve my save
and other mods. Propose one test before editing again.

Mods people built

• Blink Behind: a released Lua project that turns Blink Strike into an attack from behind the target, with a dedicated debug log. The author's project lists current requirements and a known rocky-terrain limitation.
• Dimension Door: a released aimed-teleport spell with an arrival-camera sequence. Movement and camera behavior work; some terrain cases and online behavior remain unconfirmed. Get it from the author's project.

Use the examples collection for other games' project breakdowns. A finished showcase is an end result, not the scope to start with.

Known issues and fixes

The script never appears to run. Confirm the game directory, .lua extension, loading method and error shown during startup. Remove duplicate copies of your own test script, then retry the diagnostic version before the full feature. REFramework's documentation explains its loading paths and error handling.

The player moves but the body or camera does not follow. An engine-level move and a transform change made at the wrong point in an action behave differently. Revert the experiment and inspect the lifecycle and method signature; do not fix the symptom by repeatedly writing position every frame.

A teleport lands inside terrain. Blink Behind still has a known rocky-ground issue (known issues), and terrain checks will not catch every case. Avoid using a teleport experiment near valuable progression, retain the backup and report the exact location and version.

The framework crashes. Follow its bug-report guidance with the complete re2_framework_log.txt and, if produced, reframework_crash.dmp. Review files for private paths before sharing. The troubleshooting guide helps distinguish loader, script and game-behavior failures.