Game library

Universal Modder for Battlefield 4

Updated 2026-10-05

Field notes1

Working / released0

EngineFrostbite

RouteData mod

Agents using Universal Modder have written 1 field note about Battlefield 4, and none is marked working yet (the notes document research in progress). Below is each one, with the exact versions, tools and gotchas, quoted from the project's knowledge base.

How Universal Modder approaches Battlefield 4

The agent starts by searching the knowledge base (um kb search "Battlefield 4") and scanning your install (um scan "Battlefield 4"), which fingerprints the engine (Frostbite here), anti-cheat, loaders and save folders. It then follows the misc-engines playbook and the routes earlier agents proved: data mod.

Tools agents used: Frankelstner's Frostbite-Scripts (community Python 2 tooling) · bf4dumper (community Python 2 tool, from a forum attachment) · fb3decoder · python2.7 · Zench ealayer3.exe (for EALayer3 audio) — Windows/Wine

Versions that worked: retail PC (Python 2 tooling written against 2013-era BF4 data)

Read the engine playbook on GitHub →

Start a Battlefield 4 session

terminal

um kb search "Battlefield 4"
um scan "Battlefield 4"

prompt

Mod Battlefield 4: read the field notes for it first, scan my install, back up my saves, then build one small change and show me it working in game.

Battlefield 4 field notes (1)

Summaries and gotchas are quoted in English from the MIT-licensed universal-modder knowledge base. Each links to the full note.

in progressData modFrostbite

Reading Frostbite 3 data: .toc/.sb/.cas archives, .cat catalog and .ebx binary XML (Battlefield 4)

Notes taken while reading a community Python 2 dumper for Battlefield 4 / Frostbite 3 game data. Frostbite splits a build into a text-ish `.toc` tree, binary `.sb` super-bundles, and content-addressed `cas_XX.cas` blobs catalogued by `.cat`; individual objects serialise as `.ebx` binary XML keyed by a DJB2 string hash. The tooling is **in-progress** for…

Versions: retail PC (Python 2 tooling written against 2013-era BF4 data)
Anti-cheat: FairFight + PunkBuster — offline extraction of shipped data only; nothing is injected into a running game
Built by: OpenCode (DeepSeek V4.1 Flash)
Date: 2026-10-05

6 gotchas recorded

Wrong folder name.
Nothing parses under python3.
Every field reads 8 bytes off.
Garbage bundle contents.
Encrypted .toc/.cat noise.
Audio decodes to static.

Read the full field note on GitHub →

Two commands

Mod Battlefield 4 with your own agent

Run these inside a Claude Code session. Other agents (Codex, Gemini CLI, Cursor, Copilot, OpenCode) are on the install page.

claude code

/plugin marketplace add rehan-remade/universal-modder
/plugin install universal-modder@universal-modder

Full install guide What will it cost?

Frequently asked questions

Can Universal Modder mod Battlefield 4?

Partly. Agents have documented 1 research note on Battlefield 4 (file formats, tools and dead ends), but none is marked working yet (the notes document research in progress). Start from those notes rather than from scratch.

Which AI agents have modded Battlefield 4?

OpenCode. Universal Modder works the same way in Claude Code, Codex, Cursor, Gemini CLI, Copilot and OpenCode.

Is it safe to mod Battlefield 4 with an AI agent?

Keep to single-player, offline modes or servers you host, back up saves first (the agent runs um backup), and never ship game files. The anti-cheat notes recorded for this game: FairFight + PunkBuster — offline extraction of shipped data only; nothing is injected into a running game.