Milsim Creator Framework-Core

MILSIM CREATOR FRAMEWORK - CORE MODULE Core is the shared layer the other MCF modules run on. It adds no gameplay by itself, and there is nothing to place in your world to switch it on - it attaches itself to whatever game mode your mission uses, whether that is the vanilla Game Master one, Conflict, Combat Ops or somebody else's modded game mode. WHAT IT PROVIDES Persistent storage - Key-value store written to the server profile - Survives mission restart and server restart - Each module keeps its own namespace Screens on world objects - Puts a real UI layout on a prop: a board, a monitor, a sheet of paper - Built when a player comes close, torn down when the last one leaves - Per-object read range, fade distance, refresh rate and sharpness Event layer - Publish and subscribe by name - Every publisher and subscriber registers at start-up, so a chain that can never fire is reported then instead of during a session Tick and budget management - Critical and cosmetic work on separate intervals, so a mission with a lot of scripted props does not spend its frame on things nobody is looking at Self-test suite - Runs inside a live session with real connected players, because replication faults do not show up in a single-player editor - Each check logs what it measured and what a failure would cost a player Also: logging behind one switch, object identity, Game Master attribute plumbing, and the data set registry the Mission Data screen reads. DOCUMENTATION AND BUG REPORTS https://github.com/olmopje/milsim-creator-framework/wiki The wiki covers both halves of every module: what you set up in the Workbench and what you do in Game Master. "Your First Mission" walks from an empty world to something playable. Bugs and requests: https://github.com/olmopje/milsim-creator-framework/issues Tell us what you did, what happened and what you expected. If you can, attach the [MCF] lines from your log - every part of the framework writes one when it starts and another...