Home

Milsim Creator Framework

A mission framework for Arma Reforger, for co-op groups who want to author a story live in Game Master instead of scripting one beforehand. It does not depend on Scenario Framework, Ci5 or GME.

It is on the Workshop, and it is early. Search for Milsim Creator Framework; there are two entries and you need both. Expect rough edges and expect things to change between versions. Getting Started has the loading instructions.

What it does

Intel is a thing you carry, not a notification. Letters, notepads, phones and laptops lie in the world; a player picks one up, reads it, walks it back to the operations board and logs it. From there a commander writes an order in five-paragraph format, gives it a place on the map, and hands it to the force. Someone accepts it, writes back what they intend to do, and the commander closes it when it is done.

That is what MCF is for: making what a unit knows, and what it has been told to do, into things that exist in the world and can be lost.

The modules

Module	What it gives you
Core	Storage that survives a restart, screens on world objects, the event layer. Intelligence needs it.
Intelligence	Intel you can pick up and carry, the operations board, a map board, and the Game Master tools to author and manage it all.

Load both. Nothing has to be placed in the world to switch them on — each attaches itself to whatever game mode your mission uses.

Coming later

Two more modules are built and running, and are not part of this release:

• Objectives — placeable trigger and logic nodes: proximity, cone, line of sight, AND/OR/counter, recipes, objectives.
• AI — shout, surrender, restrain and escort. Civilian behaviour, patrol points, ambient actors. Conversations with any character in the game, gated on trust and fear, are part of this module too.

They are held back until they have had the same testing as these two. This wiki will grow a page for each when they ship.

Where to start

Building a mission for the first time: Getting Started, then Your First Mission. That second page walks you from an empty world to something playable — a letter hidden in the world, carried back, logged, turned into an order, accepted and completed.

Looking for one specific thing: go to the module page. Each has the same two halves — what you place and configure in the Workbench, and what you do with it in Game Master once the mission is running.

About the state of things

Everything this wiki describes as working has been watched running in a live session with connected players, not just compiled. That is a real distinction in Enfusion: a replication fault compiles perfectly and only fails when a second player is there.

There is an automated test suite that runs inside a live session with two players on two factions. It currently passes 16 of 17 checks. The one that fails is a device profile not reaching the second client within 16 seconds, which is a streaming problem rather than a logic one.

What is still open, said plainly:

• A commander cannot delegate an order. Accepting a job yourself is the only way an order gets assigned. Until that changes the board is a noticeboard rather than a chain of command.
• Late join has not been tested. A client arriving into a mission that already has authored intel should work and has never been watched.
• Role restrictions resolve correctly but have never refused anything.
• Dropped intel objects do not respawn after a restart. The board record survives; the physical document does not.

Reporting something

Bug reports and requests go in the issue tracker. Tell us what you did, what happened, and what you expected — and if you can, the [MCF] lines from your log. Every part of the framework writes one when it starts and another when it fires, and those lines are usually the whole answer.

License: Arma Public License (APL).