What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
Gigacraft Admin Menu A3-Epoch is installed as mission-folder script code. Extract the gigacraft_admin_menu directory into the Epoch mission that your server actually loads, add two startup calls to that mission’s init.sqf, and replace the UID placeholders in tools.sqf and activate.sqf with your administrators’ Steam UIDs. Restart or reload the mission, then test both an authorized and an ordinary player account.
What the Gigacraft menu is
Gigacraft Admin Menu A3-Epoch is a small, legacy mission-script package for Arma 3 Epoch. The published archive is named gigacraft_admin_menu.7z; SourceForge lists it at 10.2 kB and records a registration or last-update date of 2015-02-12. That age matters: the package’s compatibility with current Arma 3 and Epoch builds is not established, so installation should be treated as a controlled test on your server rather than a guarantee of continued support.
This is not a server-side binary mod. Its files are placed in the mission directory, and the mission starts the scripts with execVM. Access is controlled by an explicit Steam UID allow-list inside the package. Anyone whose UID is not in that list should not receive the menu functions.
| Item | What the package provides |
|---|---|
| Deployment form | Mission-folder scripts, copied into the Epoch mission |
| Startup files | admin/activate.sqf and admin/loop.sqf, called from init.sqf |
| Authorization | Steam UID allow-list checked with getPlayerUID player |
| Advertised tools | Teleport, godmode, vehicle spawn, weapon spawn, group spawn, ESP, self or player healing, and spectating |
| Published age | Archive metadata dated 2015-02-12 |
Checks to make before editing the mission
Have these items ready before you change files:
- Access to the Epoch mission files selected by the server, either locally or through the hosting provider’s file manager, FTP, or deployment process.
- A way to extract a
.7zarchive without changing the internal folder structure. - A backup of the current mission directory and its
init.sqf. - The exact Steam UID for every person who should receive the menu.
- A non-administrator account or test player for checking that authorization is not accidentally open to everyone.
Confirm the mission identity before you copy anything. Epoch servers commonly have a server installation obtained through SteamCMD app ID 233780, but the menu belongs in the mission selected by the running server, not automatically in the server installation directory, an @Epoch mod directory, or an arbitrary working folder. If your host keeps several missions, note the one named in the active server configuration and work on that copy.
#1 Best Overall
- Player-driven story
- More than 70 weapons
- Over 100 different vehicles
- Massive online battles
- Game world of 225 square km
Also identify how your host expects mission changes to be deployed. Some hosts require an upload followed by a restart; others provide a repack or mission-selection step. The file edits are the same, but the activation procedure is host-specific.
Install Gigacraft step by step
1. Download and extract the archive
Obtain gigacraft_admin_menu.7z from the Gigacraft project’s SourceForge download area. Extract it into a temporary work directory first. After extraction, you should see a top-level directory named gigacraft_admin_menu. Do not copy only the files inside that directory while discarding the directory itself; the startup paths depend on that folder name.
Before proceeding, open the extracted tree and verify that it contains the admin subdirectory and the files referenced by the readme, including activate.sqf, loop.sqf, and tools.sqf. If your extraction utility creates an extra wrapper directory, navigate through it until the directory you copy is the one that directly contains admin.
2. Copy the directory to the mission root
Copy the complete gigacraft_admin_menu directory into the root of the Epoch mission folder loaded by the server. The resulting layout should be equivalent to:
your_epoch_mission/
├── init.sqf
├── description.ext
└── gigacraft_admin_menu/
└── admin/
├── activate.sqf
├── loop.sqf
└── tools.sqfThe names of other mission files may differ, but the important relationship is that init.sqf and gigacraft_admin_menu are siblings. Do not place the folder beside the mission, inside a server profile directory, or inside a mod directory unless your host’s mission layout explicitly makes that location the loaded 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
3. Add the two startup calls to init.sqf
Open the init.sqf belonging to that same mission. Add these lines, preserving the spelling, capitalization, quotation marks, and backslashes:
PC 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 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute[] execVM "gigacraft_admin_menu\admin\activate.sqf";
[] execVM "gigacraft_admin_menu\admin\loop.sqf";The readme identifies these as the Gigacraft startup calls. They can be placed with the mission’s other initialization code, but do not remove existing initialization statements. Save the file as plain text with the original .sqf extension. A common mistake is to paste the calls into a different mission copy, or to type forward slashes or a shortened path; either error prevents the scripts from being found.
If your existing init.sqf has conditional blocks, keep the two calls in a location that is executed during mission initialization. Do not put them inside a branch that runs only for a particular player type unless that is deliberately how your mission is designed.
4. Replace the UID placeholders
Open both of these files:
gigacraft_admin_menu\admin\tools.sqfgigacraft_admin_menu\admin\activate.sqf
In each file, find the UID condition containing #### placeholders. Replace the placeholders with the real Steam UID values for your administrators. Keep the array syntax intact. A completed condition has the same basic shape as:
if ((getPlayerUID player) in ["765...", "765..."]) then {Use one quoted string per UID, separate entries with commas, and keep the brackets. Do not replace the expression getPlayerUID player; that is the check the package uses to identify the current player. Make the same allow-list change in both files. Updating only one file can leave activation and tool access out of sync.
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
The ellipses in the example are illustrative, not characters to paste. Enter each administrator’s complete UID exactly as supplied by your server’s established identity records. If you are unsure which identifier your server uses, resolve that before editing rather than guessing from a display name; names can change, while the script compares the UID value.
Keep the edited files private. An allow-list is useful only if unauthorized players cannot obtain or alter the mission files, and publishing administrator UIDs unnecessarily makes future access reviews harder.
5. Save, deploy, and restart
Save the mission directory, then use your host’s normal upload, repack, or deployment process. Restart the server or reload the mission as required. A client reconnecting to an old mission instance will not prove that the new scripts are active, so schedule a clean restart and reconnect after the upload completes.
Record the exact mission copy and deployment time. If the menu does not appear, this makes it easier to distinguish an editing error from an upload or mission-selection problem.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Test both sides of the permission boundary
- Join with an account whose UID is in both allow-lists. Confirm that the menu initializes and that each function you intend to use can be opened without disrupting the session.
- Join with a non-authorized account. Confirm that the menu and its administrative functions are unavailable.
- Disconnect and reconnect, then repeat the check after a full server restart. This catches changes that were present only in a live editor or cached mission.
- Watch the server’s normal script or session logs while testing. Note the first error, file name, and line if initialization fails; later errors can be consequences of that first failure.
What the menu is intended to do
The package readme advertises the following functions. Their exact controls and behavior depend on the package scripts and the Arma 3/Epoch build in use, so verify each one on a test server before allowing routine use.
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
| Function | Practical use | Test consideration |
|---|---|---|
| Teleport | Move an administrator or selected player | Test destination handling and whether a player can be moved during combat or vehicle use |
| Godmode | Protect an administrator from normal damage while moderating | Check that it can be disabled and does not remain active after reconnecting |
| Vehicle spawn | Create a vehicle for administration or event work | Use a safe test area and verify the spawned object does not create persistent database clutter |
| Weapon spawn | Provide weapons for testing or moderation | Test on a controlled server so spawned gear does not affect ordinary players |
| Group spawn | Create or manage a group-related spawn action | Confirm the result matches your Epoch configuration before live use |
| ESP | Provide an enhanced view for moderation or locating entities | Check performance and disable it when not needed |
| Healing | Heal yourself or another player | Confirm the target selection and restrict use to moderation cases |
| Spectating | Observe players or the world while investigating an incident | Test entering and exiting spectator mode without leaving the administrator stuck in a camera state |
These powers can change the game state. Establish a written policy for who may use them, when spawning is allowed, and how interventions are logged. The package itself supplies an allow-list, not a complete staff-role or audit system.
Troubleshooting by symptom
The menu never appears for anyone
- Confirm the server loaded the mission you edited. Multiple Epoch mission folders are a frequent source of false fixes.
- Check that
gigacraft_admin_menuis directly besideinit.sqf, withadmin/activate.sqfandadmin/loop.sqfbeneath it. - Compare the two startup lines character by character with the supplied paths. A missing backslash, extra directory level, or changed capitalization can stop execution.
- Ensure both lines end with semicolons and that an earlier syntax error in
init.sqfis not preventing later statements from running. - Review the server’s normal script log for a missing-file or parse error and fix the first reported error before testing again.
An authorized administrator still has no access
- Verify that the complete UID, rather than a player name, appears in the arrays.
- Check both
tools.sqfandactivate.sqf; the same administrator must be allowed in each file. - Look for a missing quote, comma, or closing bracket in the condition.
- Reconnect after the mission has restarted. Existing sessions may still be running the previous mission state.
Every player appears to have access
- Inspect both UID conditions for an accidentally broad edit, such as removing the
in [...]test or placing code outside the conditional block. - Confirm that the test account is genuinely absent from both arrays.
- Restore the backed-up files if you cannot identify the change, then reapply one UID at a time and retest.
The menu opens but a function fails
Separate initialization from feature compatibility. If the menu opens but teleport, spawning, ESP, healing, or spectating produces an error, capture the first script error and the affected function. Because the archive dates from 2015, a function can be incompatible with a newer Arma 3 or Epoch build even when the startup calls work. Do not assume that changing unrelated mission settings will repair a feature-specific failure.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Remote-execution or configuration errors appear
Review the active mission’s description.ext, especially its CfgRemoteExec policy. Bohemia Interactive documents that mission-level remote-execution configuration can override mod settings, and its execution and whitelisting rules can prevent scripts from running as expected. Compare the policy in the mission actually loaded by the server, not an unused template. Change only the rules you understand, and retest with both account types after any change.
Security and server-configuration considerations
Epoch example configurations include administrative settings such as passwordAdmin, serverCommandPassword, and allowedPreprocessFileExtensions[] = {"sqf"}. Keep administrative passwords private and manage them separately from the mission files. The menu’s UID allow-list does not replace server-console credentials or protect a compromised host account.
Limit file access to trusted staff, keep a dated backup before each mission edit, and remove former staff UIDs promptly. Test powerful actions away from production players first. In particular, spawning and teleporting can alter the world or player experience even when the script is functioning exactly as designed.
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
Do not assume that a successful login proves security. Test with an account omitted from both arrays, and verify that no menu controls or administrative effects are available to it. If a host allows players to download or inspect mission files, review what that exposure means for your broader server security model.
Recommended Free Tools
Compatibility: what the 2015 date means
The archive’s 2015-02-12 date is a maintenance warning, not a current compatibility statement. There are no published independent performance, usage, or compatibility statistics for the package in the supplied material. Current Arma 3, Epoch, mission, and remote-execution changes may affect startup or individual tools.
Before adopting it on a live server, make a copy of the mission and test the complete cycle: clean startup, authorized access, denied access, each required function, disconnect/reconnect, and a full restart. Keep the previous mission ready so you can roll back quickly if the menu causes errors or unwanted state changes.
| Decision question | What Gigacraft requires | Why it matters |
|---|---|---|
| How is it maintained? | The published package is dated 2015-02-12 | Future Arma 3/Epoch compatibility is unverified |
| How are administrators selected? | Explicit Steam UID arrays in two script files | Staff changes require mission-file edits and redeployment |
| Where is it installed? | Inside the loaded mission folder | It is not a separately managed binary server mod |
| What controls execution? | Mission initialization plus the active remote-execution policy | description.ext rules can affect script behavior |
| What is the feature scope? | Moderation and spawning tools listed in the readme | Powerful functions need a staff policy and controlled testing |
Updating, removing, or rolling back
Updating
Do not overwrite a working installation blindly. Back up the entire mission and note the current archive contents, UID lists, and init.sqf lines. If a later package is ever supplied, compare its folder structure and readme with your current copy, then repeat the authorized and unauthorized tests after deployment.
Removing
- Back up the mission in its current state.
- Delete the two Gigacraft
execVMlines frominit.sqf. - Remove the
gigacraft_admin_menudirectory from the mission. - Restart or reload the mission and verify that no Gigacraft startup error remains.
Rolling back
Restore the complete backed-up mission, not just one script. A partial rollback can leave startup calls pointing to missing files or leave a changed UID condition in place. Restart after restoration and perform a short authorized/unauthorized test before reopening the server.
Installation checklist
- The archive was extracted without losing the top-level
gigacraft_admin_menudirectory. - The directory is in the root of the mission selected by the server.
init.sqfcontains both requiredexecVMcalls.- Every administrator’s complete Steam UID is present in both UID conditions.
- The edited mission was uploaded or repacked using the host’s required process.
- The server or mission was restarted after deployment.
- An authorized account was tested.
- A non-authorized account was tested and denied.
- The active remote-execution policy was reviewed if initialization or features failed.
- A clean backup exists for rollback.
Bottom line
For an Epoch mission that still accepts its 2015-era scripts, setup is straightforward: copy the folder, add the two initialization calls, and maintain matching Steam UID allow-lists in tools.sqf and activate.sqf. The difficult part is not extraction; it is proving that you edited the mission the server actually loads, that unauthorized players remain blocked, and that this legacy package still behaves safely under your current Arma 3, Epoch, and remote-execution configuration.
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.
