Gigacraft Admin Menu A3-Epoch is installed as mission-folder scripts, not as a server-side binary mod. Download and extract gigacraft_admin_menu.7z, place the resulting gigacraft_admin_menu directory in the root of the Epoch mission actually loaded by your server, add two startup calls to that mission’s init.sqf, and replace the UID placeholders in two script files with the Steam UIDs of your administrators.
Godlike.Host offers hosted Arma 3 servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The package advertises teleport, godmode, vehicle and weapon spawning, group spawning, ESP, healing and spectating. It was published in 2015, however, so compatibility with current Arma 3 and Epoch builds is not established. Make a backup, test on a non-production mission, and be prepared to remove the calls if the menu conflicts with your current remote-execution policy.
As an Amazon Associate I earn from qualifying purchases.
What Gigacraft Admin Menu is—and what it is not
Gigacraft Admin Menu A3-Epoch is a small SQF mission script package distributed as gigacraft_admin_menu.7z. SourceForge lists the archive at 10.2 kB and records 2015-02-12 as its registration and last-update date. The accompanying readme identifies the authors as RHE24 and Stefan and says the package is based on the Arma 3 Wiki.
Because the files are copied into the mission directory and started from init.sqf, this is a mission-level script installation. It is not a separately loaded binary mod, and it does not replace Epoch’s server configuration. Every mission that needs the menu must contain the folder and startup calls, and a mission change can therefore remove the menu even when the server itself has not changed.
#1 Best Overall
- Player-driven story
- More than 70 weapons
- Over 100 different vehicles
- Massive online battles
- Game world of 225 square km
The readme lists these functions:
- Teleporting.
- Godmode.
- Vehicle spawning.
- Weapon spawning.
- Group spawning.
- ESP.
- Healing yourself or another player.
- Spectating.
Those are advertised capabilities, not a guarantee that every function works on a current build. The archive’s age means that script commands, network restrictions, or Epoch changes can affect individual tools.
Check the server and mission before changing files
Do the preparation on a copy of the mission when possible. A failed script call can prevent a mission from initializing, and a typo in a UID allow-list can make an authorized administrator appear to have no access.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Confirm the Epoch installation
Epoch server installations use SteamCMD application ID 233780. The server directory should contain the Epoch files, configuration, and the mission files selected by the server’s startup parameters. The application ID alone does not identify the mission you must edit; you need the mission name and path that the running instance actually loads.
Back up the complete mission
- Copy the complete mission directory, including
init.sqf,description.ext, and any existing custom folders. - Keep a second copy of the original archive and the unmodified mission outside the live server directory.
- Record the current startup parameters and the selected mission so you can undo the change without guessing.
Keep server credentials private
Epoch’s example configuration includes passwordAdmin and serverCommandPassword. Do not place either password in the mission files, publish them in support posts, or give them to ordinary players. The Gigacraft allow-list is separate: it authorizes specific Steam UIDs for the menu and does not replace your server’s administrative passwords.
Download and extract the package
- Download
gigacraft_admin_menu.7zfrom the Gigacraft Admin Menu A3-Epoch project on SourceForge. - Extract the archive with an application that supports 7z files. Preserve the directory structure rather than copying individual SQF files.
- Inspect the extracted result. You should have a top-level directory named
gigacraft_admin_menucontaining anadminsubdirectory and files such asactivate.sqf,loop.sqf, andtools.sqfunder that subdirectory.
If extraction creates a nested path such as gigacraft_admin_menu/gigacraft_admin_menu/admin, use the inner directory as the package root. The path referenced by the startup calls must resolve to gigacraft_admin_menuadminactivate.sqf and gigacraft_admin_menuadminloop.sqf relative to the mission root.
Rank #2
- System: Intel Core i5-13400F 2.5GHz 10 Cores | Intel B760 Chipset | 16GB DDR5 | 1TB PCIe 4.0 NVMe SSD | Windows 11 Home
- Graphics: NVIDIA GeForce RTX 5060 8GB Graphics | 1x HDMI | 2x DisplayPort
- Connectivity: 1 x USB-C 3.2 | 2 x USB-A 3.2 | 6 x USB-A 2.0 | 1 x LAN | WiFi 6 | Bluetooth 5.3 | 7.1 Channel Audio
- Tempered Side Case Panel | Custom RGB Lighting | Keyboard and Mouse
- 1 Year Parts & Labor Warranty, Free Lifetime Tech Support
Place the folder in the mission root
Copy the extracted gigacraft_admin_menu directory directly into the root of the Epoch mission folder selected by the server. “Mission root” means the same directory that contains that mission’s init.sqf; it does not mean the server’s general root, the Epoch mod directory, or the profile directory.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchA correct layout is conceptually similar to:
<selected mission>
├─ init.sqf
├─ description.ext
└─ gigacraft_admin_menu
└─ admin
├─ activate.sqf
├─ loop.sqf
└─ tools.sqfDo not rename the folder unless you also change both startup paths and every internal reference that expects the original name. Keeping the supplied name removes one source of path errors.
Add the two startup calls to init.sqf
Open the init.sqf in the same mission root and add the two calls supplied by the readme. They can be placed with the mission’s other initialization code; retain any existing statements and semicolons.
[] execVM "gigacraft_admin_menu\admin\activate.sqf";
[] execVM "gigacraft_admin_menu\admin\loop.sqf";The first call starts the activation script and the second starts the loop script. Use the path exactly as shown, including the double backslashes and the terminating semicolons. In SQF source, the doubled backslash represents the directory separator in the string. A missing backslash, a misspelled folder, or a call placed in a different mission’s init.sqf can leave the menu inactive.
Do not add the calls to a server configuration file or to an unrelated mod’s initialization file. They are mission-script calls and must execute as part of the selected mission.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- System: Intel i7-10700F 2.9GHz (4.8GHz Max Turbo) | 16GB DDR4 RAM | 480GB SSD | 2TB HDD | Genuine Windows 10 Home 64-bit
- Graphics: NVIDIA GeForce RTX 2060 6GB Dedicated Gaming Video Card | VR Ready | 1x DVI | 1x HDMI | 1x Display Port
- Connectivity: 4 x USB 3.0 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000 | Audio: 7.1 Channel
- Special Add-Ons: Tempered Glass RGB Gaming Case | 802.11AC Wi-Fi Included | 16 Color RGB Lighting Case | Free iBuyPower Gaming Keyboard and RGB Gaming Mouse | No Bloatware
- Warranty: 1 Year Parts and Labor plus Free Lifetime US Tech Support | Assembled in the U.S.A
Add administrator Steam UIDs
Gigacraft authorizes users with an explicit Steam UID allow-list. The scripts call getPlayerUID player and compare the result with the values you provide. A player is not authorized merely because they know the menu key or have an Epoch server password.
Edit both required files
- Open
gigacraft_admin_menuadmintools.sqf. - Find the UID condition containing the package’s
####placeholders. - Replace each placeholder with the administrator’s complete Steam UID.
- Repeat the same replacement in
gigacraft_admin_menuadminactivate.sqf. - Save both files without changing the surrounding condition or array syntax.
The resulting condition should have this form:
if ((getPlayerUID player) in ["765...", "765..."]) then {
// existing Gigacraft code
};Use quotation marks around every UID and commas between entries. Keep the values as strings; removing the quotes changes the expression and can cause an error. Do not include a display name, Steam profile URL, server password, or trailing spaces in place of the UID.
Verify the UID value
Obtain the value from a trusted in-game or server administration method that displays the player’s Steam UID. Copy it exactly, including every digit. If a player has more than one Steam account, each account needs its own entry. If you remove an entry, that account loses menu authorization after the mission reloads.
Keep the two lists synchronized
The authorization check appears in both tools.sqf and activate.sqf. Treat the lists as a pair. Adding a UID to only one file can produce partial behavior: activation may be denied, or the menu may appear without its tools being authorized. After editing, compare the arrays character by character and retain the same administrator set in both places.
Repack, restart, and perform a controlled test
- Save
init.sqf,tools.sqf, andactivate.sqf. - Repack or upload the mission using the method required by your host. If your host expects a PBO, rebuild it from the edited mission directory while preserving the relative paths.
- Verify that the server startup configuration still selects the mission you edited.
- Restart the server or reload the mission so the new scripts are read. A client reconnect without a mission reload may still be using the old mission data.
- Join with an authorized account and check that the menu initializes.
- Join with a non-authorized account or ask a trusted tester to do so. Confirm that the administrative functions are not exposed to that account.
Test in a safe area first. Vehicle, weapon, and group spawning can alter the live world, while teleport and godmode can affect gameplay. Remove test objects and restore the backup if the mission behaves unexpectedly.
Rank #4
- System: Intel Core i9-13900KF 3.0GHz (8plus16) Cores | Intel Z690 Chipset | 16GB DDR5 | 1TB PCIe NVMe SSD | Genuine Windows 11 Home 64-bit
- Graphics: NVIDIA GeForce RTX 4070 Ti 12GB Video Card | 1x HDMI | 2x DisplayPorts
- Connectivity: 6 x USB 3.1 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000 | 802.11AC Wi-Fi | Audio: 7.1 Channel | Keyboard and mouse
- Special feature: Liquid cool CPU | 3-Piece Panoramic Tempered Glass Front/Side Case Panel | Custom RGB Case Lighting | USB Gaming Keyboard | 7 Colors RGB Gaming Mouse
- 1 year parts and labor | Free lifetime tech support
What each advertised function is for
| Function | Typical administrative use | Operational caution |
|---|---|---|
| Teleport | Move an administrator to an incident or relocate a player for support. | Confirm the destination before moving a player or vehicle; an unsafe location can cause immediate damage. |
| Godmode | Inspect a dangerous area without normal player damage. | Use only while investigating. Leaving it active can invalidate a moderation or survival test. |
| Vehicle spawn | Create a vehicle for an event, recovery, or controlled test. | Spawned objects can persist in the database or affect server performance depending on Epoch behavior. |
| Weapon spawn | Equip an administrator or test a loadout. | Do not use on a public server without a documented moderation policy. |
| Group spawn | Create AI or groups for an event or troubleshooting scenario. | Additional entities can create cleanup and performance work. |
| ESP | Observe player or object locations while investigating an incident. | Restrict use to authorized staff because it reveals information ordinary players should not receive. |
| Healing | Restore an administrator or another player after an accidental event. | Record interventions if your server uses a formal moderation process. |
| Spectating | Watch a situation without physically joining it. | Exit the spectator mode using the menu’s available control before resuming normal play. |
The table describes the purpose implied by the readme; it does not add features beyond the package’s advertised list. The exact controls and presentation are defined by the legacy scripts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot a menu that does not appear
Nothing happens for an authorized administrator
- Confirm the player’s UID is complete and quoted in both
tools.sqfandactivate.sqf. - Check that the two
execVMcalls are in the selected mission’sinit.sqf, not a similarly named mission. - Check the folder spelling and case:
gigacraft_admin_menuadminactivate.sqfandgigacraft_admin_menuadminloop.sqf. - Confirm that the edited mission was repacked and uploaded after the changes.
- Restart or reload the mission rather than relying on a client reconnect.
The server reports a missing script or path
Compare the archive’s extracted tree with the path in init.sqf. The admin directory must be inside gigacraft_admin_menu, and both directories must be below the mission root. Remove accidental nesting, such as an extra archive-name directory, and repack the mission with the corrected structure.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThe menu appears, but tools fail
First compare the UID arrays in tools.sqf and activate.sqf. Then inspect the active mission’s description.ext and remote-execution policy. Bohemia Interactive’s CfgRemoteExec documentation notes that mission-level configuration can override mod settings and that execution and whitelisting rules affect script behavior. A current Epoch mission may therefore restrict a legacy script even though the files load successfully.
Do not disable remote-execution protections globally as a first response. Identify which call is rejected, make the narrowest policy change your server’s security model permits, and retest with a non-admin account. If you cannot establish a safe rule, roll back the menu instead of weakening the entire server.
Only some administrators work
Compare the failing account’s UID with the string in each allow-list. Common causes are a truncated value, a copied profile name instead of a UID, a missing comma between entries, or an edit made in one file but not the other. Have the affected administrator reconnect after the mission reloads.
Best Value
- Dress in style for duty on Everon. Built to answer the call of military service and survive arma for days at a time, so take a day off the battlefield duty and dress to impress your squad with our low weight but high cool reforger inspired army design.
- Compatible with all versions of arma so PC gamers and console soldiers can spend dayz in reforger gaming in comfort and style on Everon. A great gamer gift for any military army simulator player.
- 8.5 oz, Classic fit, Twill-taped neck
The wrong mission keeps loading
Use the server’s startup parameters and host control panel to identify the selected mission. A correctly edited mission has no effect if the server is loading another map, an alternate difficulty folder, or a different PBO. Apply the folder and init.sqf changes to the mission that is actually selected, then restart.
Recommended Free Tools
Remote-execution and security considerations
The UID allow-list is an access gate, not a complete security architecture. Anyone who can modify the mission files can change the list, and any script vulnerability in a legacy package remains a risk to every authorized account.
- Limit write access to the mission and PBO files to trusted operators.
- Keep
passwordAdminandserverCommandPassworddifferent from Steam credentials and out of shared documentation. - Use the narrowest CfgRemoteExec permissions that allow the menu to function.
- Review the active mission’s remote-execution settings after every Epoch or Arma update.
- Maintain an audit note for who receives a UID entry and when it is removed.
- Test privileges with both an authorized and an unauthorized account after changes.
Because the package is from 2015, do not assume that an absence of an immediate error means the scripts are safe for a public production server. Treat it as legacy code and keep a tested rollback.
Compatibility with current Arma 3 and Epoch builds
No independent usage, performance, or compatibility statistics were published with the package information. The only dated archive evidence is the 2015-02-12 registration and update record. Consequently, compatibility with your current Arma 3 executable, Epoch release, host, and mission configuration must be established by your own controlled test.
Check these points before adopting it on a long-running server:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Whether the current mission still permits the script calls used by the package.
- Whether CfgRemoteExec rules allow the required remote execution.
- Whether the current Epoch database and object lifecycle handle spawned entities as expected.
- Whether the menu’s controls remain usable with your current client version and key bindings.
- Whether the package conflicts with other mission-level admin or event scripts.
If any of those checks fail and there is no narrowly scoped fix, remove the two startup calls and the copied folder, restore the backup, and use an actively maintained administration framework that fits your security requirements. The decision should be based on maintenance date, current-build compatibility, UID-versus-role authorization, remote-execution controls, feature scope, and whether you want mission edits or a separately managed mod.
Remove the menu or roll back safely
- Stop the server or take the mission offline.
- Restore the backed-up
init.sqf, or delete only the two GigacraftexecVMlines. - Remove the
gigacraft_admin_menudirectory from the mission if no other script depends on it. - Repack and upload the mission using the host’s required process.
- Restart and verify that ordinary gameplay works and that no Gigacraft files are being called.
Keeping the original backup lets you re-test a corrected installation without reconstructing the mission from memory.
Installation checklist
- Archive:
gigacraft_admin_menu.7zextracted without losing its directory structure. - Location:
gigacraft_admin_menuis directly under the selected Epoch mission root. - Startup: Both required
execVMcalls are present in that mission’sinit.sqf. - Authorization: Every administrator’s quoted Steam UID appears in both
tools.sqfandactivate.sqf. - Deployment: The edited mission was repacked, uploaded, and reloaded.
- Testing: Authorized and unauthorized accounts were tested separately.
- Security: Epoch passwords remain private and remote-execution rules were reviewed rather than broadly disabled.
- Rollback: An untouched mission backup is available.
Following that sequence gives you the intended Gigacraft installation while making the package’s legacy status and security limits explicit.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
