Content Injection: Mods & Scenarios
The lifeblood of the Arma 3 ecosystem is its creative community. Whether you are building a casual “King of the Hill” environment or managing a hardcore “MilSim” unit, you will need to master the installation of custom modifications (@Mods) and scenario mission files (.pbo). This guide explains the correct workflow for deploying these assets to your FREAKHOSTING server.
Difficulty
Intermediate
Time
10 Minutes
Installing Mods (@ModName)
Mods are typically downloaded via the Steam Workshop and must be manually synchronized with your server to ensure performance and security.
Locate Mod Folders
Subscribe to your desired mods on the Steam Workshop. On your local PC, navigate to the Arma 3 directory (usually
!Workshop is a hidden folder) and find the folders prefixed with @.Upload to Server Root
Using SFTP or the File Manager, upload the entire mod folder (e.g.,
@ACE3) to the root directory of your server.Manage Security Keys
Open the mod’s internal
keys folder. Upload the .bikey file inside to the server’s root /keys/ directory. This allows players to pass the Signature Verification.Installing Missions (Mission.Map.pbo)
A mission file is a single package containing all the scripts, unit placements, and objectives for a specific scenario.
Prepare the PBO
Ensure your mission file follows the standard naming convention:
MissionName.MapName.pbo (e.g., Antistasi.Altis.pbo).Automate Loading (Optional)
To make this mission load automatically on boot, update the
class Missions block in your server.cfg.Need Extra Help?
If you encounter any issues, our support team is ready to assist:- Live Chat: Quick assistance via our website.
- Support Ticket: Open a Ticket
- Discord: Join our Community
- Email: [email protected]
Last Updated: January 2026 | Arma 3: Deployment complete.