Outdated 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 matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Gigacraft Admin Menu A3-Epoch is installed as a mission-folder script. Extract the gigacraft_admin_menu directory into the Epoch mission that your server loads, add two startup calls to that mission’s init.sqf, and replace the placeholder Steam UIDs in the menu’s authorization checks. After uploading the edited mission and restarting it, test with both an authorized and an ordinary player.
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 is a legacy release, so installation is straightforward but compatibility with a modern Arma 3/Epoch build is not guaranteed. Follow the deployment and troubleshooting checks below rather than assuming that a successful file upload means the menu is working safely.
As an Amazon Associate I earn from qualifying purchases.
What Gigacraft Admin Menu is
Gigacraft Admin Menu A3-Epoch is a collection of SQF mission scripts, not a compiled server binary and not a separately loaded Arma 3 mod. The published archive is named gigacraft_admin_menu.7z. SourceForge lists it at 10.2 kB and records 2015-02-12 as its registration and last-update date. The accompanying readme identifies the project authors as RHE24 and Stefan and says it is based on the Arma 3 Wiki.
Because the files live inside the mission, the menu starts when that mission starts. A different mission, a different instance directory, or a server configuration that selects another mission will not load the files you edited. The authorization logic is also inside the mission: the scripts call getPlayerUID player and compare the result with a hard-coded allow-list.
#1 Best Overall
- Player-driven story
- More than 70 weapons
- Over 100 different vehicles
- Massive online battles
- Game world of 225 square km
| Item | Established detail |
|---|---|
| Package | gigacraft_admin_menu.7z |
| Published archive size | 10.2 kB, according to SourceForge metadata |
| Registration/last update | 2015-02-12 |
| Delivery model | Mission-folder SQF scripts |
| Advertised tools | Teleport, godmode, vehicle spawn, weapon spawn, group spawn, ESP, self or player healing, and spectating |
| Authorization | Steam UID allow-list evaluated with getPlayerUID player |
No independent performance, usage, or current-build compatibility statistics are published. Treat the feature list as what the readme claims, not as a guarantee that every function works on your particular server.
Before you edit anything
Confirm the server and mission
Locate the server instance that actually runs your Epoch mission. Epoch installations use SteamCMD app ID 233780 and contain the Epoch files and configuration in the server directory. Hosts arrange those directories differently, so use the instance’s control panel, startup script, or configuration file to identify the active mission folder. Do not edit a template, backup, or unused test instance.
Make a complete copy of the mission directory before changing it. Keep the backup outside the upload directory and record the original init.sqf, description.ext, and any existing UID checks. If the mission fails to load after an edit, restoring those files gives you a known-good rollback.
Check the required file type
The menu is SQF code. Epoch’s example server configuration includes allowedPreprocessFileExtensions[] = {"sqf"}; keep SQF processing enabled in the active configuration. The same example includes passwordAdmin and serverCommandPassword. Store both values privately and never paste them into a public support post, mission download, or screenshot.
Use a text editor that preserves plain text
Open SQF files in an editor that does not add rich-text formatting or silently change quotation marks. Preserve the existing line endings and capitalization. A missing semicolon, an unmatched brace, or a “smart” quote can prevent a mission script from compiling even though the folder appears in the right place.
Download and extract the package
- Download
gigacraft_admin_menu.7zfrom the Gigacraft project page on SourceForge. - Extract the archive locally with a 7z-compatible extractor.
- Inspect the extracted result before uploading it. You should have a directory named exactly
gigacraft_admin_menu, containing anadminsubdirectory and the scripts referenced by the readme. - If extraction creates an extra wrapper directory, open it and move the actual
gigacraft_admin_menudirectory up one level. The mission must not end up with a path such asgigacraft_admin_menu/gigacraft_admin_menu/adminunless the scripts and startup calls are adjusted to match.
Keep the original archive until the server has been tested. It is useful for comparing a modified file with the distributed version if a later change introduces an error.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #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
Copy the folder into the active Epoch mission
Copy the entire extracted gigacraft_admin_menu directory into the root of the Epoch mission folder loaded by the server. “Root” means the same top-level mission directory that already contains init.sqf, not the server’s general root, an @Epoch mod directory, or a database folder.
After copying, the important paths should look like this:
<active mission>/init.sqf
<active mission>/gigacraft_admin_menu/admin/activate.sqf
<active mission>/gigacraft_admin_menu/admin/loop.sqf
<active mission>/gigacraft_admin_menu/admin/tools.sqfThe readme’s instruction to “extract to our Mission Folder” means this mission-root placement. If the host uses a packed PBO, edit the unpacked mission source and repack it using the host’s documented method; do not assume that uploading a loose folder beside the PBO changes the mission that clients receive.
Add the two startup calls
Open the init.sqf in the same mission root and add the following lines. The safest location is after any existing initialization that must run first, while retaining the file’s original commands and terminating each new statement with a semicolon.
Recommended Free Tools
[] execVM "gigacraft_admin_menu\admin\activate.sqf";
[] execVM "gigacraft_admin_menu\admin\loop.sqf";These are the startup calls supplied by the readme. activate.sqf performs the menu activation logic, while loop.sqf supplies the recurring behavior needed while a player is connected. Do not replace init.sqf wholesale with these two lines; merge them into the existing mission initialization.
Check the path spelling
- Use the directory name
gigacraft_admin_menuexactly, including underscores. - Use the
adminsubdirectory exactly. - Use
activate.sqfandloop.sqfwith the same capitalization as the extracted files. - In SQF string paths, retain the double backslashes shown above.
If the mission already has an init.sqf call that starts another administration framework, leave it in place while testing Gigacraft separately. Two systems may expose overlapping actions or authorization rules, making a failure difficult to diagnose.
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
Replace the Steam UID placeholders
The distributed scripts contain a UID condition with #### placeholders. Edit both gigacraft_admin_menu\admin\tools.sqf and gigacraft_admin_menu\admin\activate.sqf. Replace every placeholder in the relevant allow-list with the actual Steam UID of each administrator.
The resulting condition must preserve the array and string syntax, for example:
if ((getPlayerUID player) in ["765...", "765..."]) then {
// existing Gigacraft code remains here
};Obtain and verify each UID
- Have the administrator join the server with the Steam account that should receive access.
- Use your normal server-side method for displaying or logging
getPlayerUID player, or obtain the account’s SteamID64 from a trusted account record. - Copy the digits exactly, without spaces, punctuation, or a profile URL.
- Compare the value against the UID shown in server logs for that player. A different Steam account, family-shared account, or test account has a different identifier.
- Add each UID as a quoted string separated by commas inside the same array.
Do not remove the getPlayerUID player call or change the comparison to a player name. Names can change; the package’s authorization model is an explicit UID allow-list. Keep the list as narrow as possible because every UID entered in both files receives the menu’s privileged actions.
Keep the two checks synchronized
The package’s readme calls for changing the UID condition in both files. If an administrator is added to one file but not the other, activation and tool access can disagree. After editing, search both files for #### and for the UID array, then confirm that the intended list appears in each location.
Repack, upload, and restart
- Save all edited files as plain text.
- Run a quick path check against the extracted mission: verify that
init.sqfis besidegigacraft_admin_menu, and that the three admin scripts are inside the expected subdirectory. - Repack the mission into the format required by your host, commonly a PBO, or upload the loose mission directory if that is how the host serves it.
- Replace the active mission on the server while it is stopped, following the host’s backup and permissions procedure.
- Start or restart the server and make sure its mission-selection setting points to the edited mission.
- Wait for the mission to initialize before judging the result. A server restart that loads an older mission copy will appear identical to an installation that was never made.
Keep the administrative passwords out of the mission archive and out of any client-downloadable text. The menu’s UID list is necessarily present in mission files, so consider who can download or inspect that mission when deciding which accounts receive elevated powers.
Test the installation safely
Test with an authorized account
- Join with a Steam account whose UID is present in both allow-lists.
- Open the menu using the package’s in-game activation method and confirm that the expected controls appear.
- Test one low-impact function first, such as opening the interface or observing a player list.
- Test teleport, healing, spawning, ESP, godmode, and spectating individually in a controlled area. Record which actions work and whether any produce script errors.
- Leave and rejoin to verify that the menu initializes consistently rather than working only after a manual action.
Test with a non-admin account
Join with an account that is not in the UID arrays. That player should not receive the administrative functions. If the menu appears for the test account, stop the server and inspect both authorization conditions before allowing normal play. A broad or malformed condition can grant powers to everyone.
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
Watch server and client logs
Look for missing-file, undefined-variable, syntax, or remote-execution messages during mission startup and when each function is used. Note the exact script path and line number. A clean server start does not prove that every button works; many actions execute only after the administrator selects them.
Understand the server-side security context
Epoch’s example configuration exposes passwordAdmin, serverCommandPassword, and the SQF preprocess extension allow-list. These settings are separate from Gigacraft’s UID check. A person who knows the server command password is not automatically added to the menu’s UID array, and adding a UID to the array does not grant the server’s command password.
Arma 3’s remote-execution policy can also affect mission scripts. Bohemia Interactive’s CfgRemoteExec documentation notes that mission-level configuration can override mod settings and that execution and whitelisting rules determine which scripted commands are permitted. Review the active mission’s description.ext and its remote-execution policy if the menu initializes but an action does nothing, produces a remote-execution error, or works for one build and not another.
Limit privileged access
- Use individual Steam UIDs rather than a shared account.
- Remove former administrators from both files immediately.
- Do not publish the mission archive with the UID list intact if the list identifies private staff accounts.
- Test spawning and teleport functions away from public events so a mistake does not disrupt players.
- Keep a dated backup of the last known-good mission and the exact UID list used in production.
Troubleshooting by symptom
The server starts, but no menu appears
- Confirm that the running mission is the one containing the edited
init.sqf. Check the server’s mission-selection parameter and the loaded mission name in startup output. - Verify that both
execVMlines are present, complete, and terminated with semicolons. - Check the relative path from the mission root. The expected path is
gigacraft_admin_menu/admin/activate.sqf, not a path under the server root or an Epoch mod folder. - Inspect logs for a file-not-found or syntax error and correct the first reported error before chasing later messages.
Only some administrators can use it
Compare the affected account’s logged UID with the quoted strings in both activate.sqf and tools.sqf. Look for a missing digit, an extra space, mismatched quotation marks, or an account that joined through a different Steam identity. Synchronize the arrays, repack the mission, and restart it after making the correction.
The menu appears for everyone
Stop the server immediately if unauthorized players can access privileged tools. Inspect the if ((getPlayerUID player) in [...]) then { condition for an accidentally removed in test, an empty condition that defaults to true, or a misplaced brace that puts the menu code outside the authorization block. Restore the backup if necessary, then retest with two deliberately different accounts.
An action opens but does nothing
Check the client and server logs at the moment the action is selected. Review description.ext for CfgRemoteExec restrictions and confirm that the current Arma 3/Epoch build permits the command the script is trying to execute. Because the package dates from 2015, a command that was accepted by its original environment may be restricted or changed in a later build. Do not disable remote-execution protections globally just to make one button work; first determine which function is blocked and whether a maintained replacement is safer.
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 mission fails to load after editing
Restore the backed-up init.sqf and confirm that the server starts without Gigacraft. Reapply only the two startup lines, checking quote marks, backslashes, and semicolons. If the failure returns, compare the edited file byte-for-byte with the backup and inspect the first syntax error in the log. A malformed UID array or an unmatched brace in either admin script can also prevent initialization.
Free tools Windows power users keep installed
One-click scans. No signup required.
Compatibility and maintenance expectations
The archive’s 2015-02-12 update date makes it legacy software. No source in the published material verifies operation on a current Arma 3 or Epoch build, and no independent performance or compatibility measurements are available. Before putting it on a live public server, test the exact game branch, Epoch files, mission framework, and remote-execution settings you intend to run.
After an Arma 3, Epoch, or mission-framework update, repeat the authorized and non-admin tests. Pay special attention to spawning, spectating, ESP, and any action that invokes remote execution. Keep a change log containing the game/server version, mission revision, UID-list revision, and observed errors so that a future failure can be tied to a specific update.
How this setup differs from a newer administration framework
If you are deciding whether to keep Gigacraft or migrate, evaluate the actual operating requirements rather than the menu’s button count. Gigacraft edits the mission directly and authorizes users with a static UID list. A newer framework may instead be maintained as a separately managed mod, use server roles, or provide explicit remote-execution whitelists. Those approaches can reduce mission edits but add their own installation, update, and configuration responsibilities.
| Decision axis | Gigacraft characteristics | Question to ask before migrating |
|---|---|---|
| Maintenance | Published archive last updated 2015-02-12 | Is the alternative maintained for the exact Arma 3/Epoch build? |
| Authorization | Steam UID allow-list in mission SQF | Do you need roles, groups, expiration, or centralized staff management? |
| Security controls | Depends on mission code and active CfgRemoteExec policy | Can the alternative document command whitelists and denial behavior? |
| Deployment | Copy a folder and edit init.sqf, activate.sqf, and tools.sqf |
Would a separately versioned mod be easier for your host to update? |
| Feature scope | Teleport, godmode, spawning, ESP, healing, and spectating are advertised | Which functions are essential, and are they tested on your server? |
Do not add a second framework merely to obtain a newer interface without first resolving overlapping key binds, duplicated event handlers, and competing permission checks. Run one administration system at a time during compatibility testing.
Quick Recap
Production checklist
- Back up the active mission and identify the mission selected at startup.
- Extract the archive so the real
gigacraft_admin_menudirectory is at mission root. - Confirm
admin/activate.sqf,admin/loop.sqf, andadmin/tools.sqfexist beneath that directory. - Add both supplied
execVMcalls to the active mission’sinit.sqf. - Replace every
####placeholder in both authorization files with verified Steam UIDs. - Preserve the array syntax, quoted strings, braces, and semicolons.
- Check SQF preprocessing and the mission’s CfgRemoteExec rules.
- Repack or upload using the host’s required method, then restart the mission.
- Test with one authorized account and one account that is not authorized.
- Record the result and retain a rollback copy before opening the server to normal players.
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.
