M.O.B Project Arma Reforger Mod

Stops enemy players camping your main operating base. Cross into an enemy MOB and you get a full-screen warning, a spoken callout and a countdown. Stay too long and you die. Keep doing it and you get banned. HOW IT WORKS Each faction's HQ is detected automatically. There are no zones to place and no scenario to edit — it works on any Conflict map out of the box. - Enemies inside a MOB get 15 seconds to leave, with a countdown on screen and a voice warning - Leaving does not reset the timer. It holds for five minutes, so hopping in and out to dodge it does not work - After three deaths the warning drops to five seconds - On the fourth, the player is banned - Enemy MOBs are drawn on the map in red, so nobody gets to say they did not know Your own base is never marked and never dangerous to you. Players only ever see the zones that would actually kill them. BANS THAT SURVIVE A RESTART Reforger's built-in kick timeout only lasts as long as the server process, so a 24 hour ban applied that way disappears the next time the server bounces. MOB Guard keeps its own list on disk, keyed to the player's Bohemia account, and checks it on connect. Bans survive restarts, reconnects and name changes. To lift one, delete a line from a text file. DISCORD Optional. Point it at a webhook and it posts an embed when someone is banned — who, how many times, which server, how long. Useful when you run more than one server through one channel. SETUP Add the mod to your server's config.json and restart. Nothing else is required. On first boot it writes MOBGuardConfig.json into your server profile folder with working defaults. Everything is tuneable from there: zone radius, timers, strike counts, ban length, all wording, Discord webhook. There is also an optional setting that makes players invulnerable inside their own MOB, with a lockout so anyone who shoots loses the protection. It ships disabled. REQUIREMENTS Conflict, or any game mode built on it — HQ detection relies on the Conflict base system. Server-side enforcement; clients only receive what to display. --- I led with the drop-in angle and the persistent bans, because those are the two things that separate it from a scenario-specific script another owner could knock together — and "no scenario to edit" is the sentence that gets someone to actually try it.