- Alex -

Unturned - Workshop Error Fixes If you encounter any errors regarding Workshop Mods while joining our servers, you can try these solutions below. If you're still encountering the error, please send a message in #｜helpdesk so we can help! Unsubscribe from Problematic Workshop Mods Go to the Unturned Main Menu under Workshop - Manage - You can use this section to unsubscribe from problematic Workshop Mods (such as VirtualGarageUI). After unsubscribing, restart your game and try joining our server again to download a fresh copy of the Mods running on the server. You can also see when the last time your Workshop Mods were updated compared to what's on Steam. Verify Integrity of Game Files Close Unturned and Go to Steam - Library - Unturned - Properties - Installed Files - Verify integrity of game files. This can take a while but should fix most issues with the game. Remove Workshop Folder If the solutions above didn't work, you can try removing your Unturned Workshop folder by navigating to YOURDRIVELETTER:\Program Files (x86)\Steam\steamapps\workshop\content and deleting the 304930 folder - You should NOT do this while the game is running. After doing this try starting your game and joining our server again.

Changelog 3/8/25 All TF2 Servers are back online! Fixes Removed plugin Advanced Infinite Ammo - Caused servers to crash as soon as players joined Updated StAC to latest version

Changelog 2/14/25 Fixes Fixed Daily Restart schedules (Servers restart at 6:00AM CST)

Changelog 11/28/24 Fixes Fixed Free VIP and Gold VIP access on all servers Changed how chat tags work

Changelog 11/27/24 Fixes Fixed Footsteps plugin admin flag Fixed Ragdolls plugin admin flag Adjusted Store Credits Distributor to include Free VIP perks

Changelog 11/28/24 Top 20 VIP Benefits (BETA) Added Free VIP benefits for anyone who gets in the Top 20 players list on HLStatsX! For the available commands you can check the TF2/TF2C Commands List under Free VIP ! If you manage to get in the Top 20 players, it will take 1 minutes (Subject to change) for the server to update your permissions, and you will have to rejoin to get the full effects. Happy Hunting out there! Features Custom Ragdolls Halloween Footprints Killstreak Sheens Unusual Taunts Unusual Effects (Hats) Access to Vote Menu

Server Restart Schedules This post is continuously being updated as information changes, this can happen without warning. Last update 2/14/25. Assetto Corsa: Daily at 4:00AM BeamMP: Daily at 6:30AM TF2: Daily at 5:00AM - Announcements are made 5 minutes before the server restarts TF2 Classic: Daily at 6:00AM - Announcements are made 5 minutes before the server restarts Unturned: Daily at 6:00AM - Announcements are made 5 minutes before the server restarts, A server backup is also captured during this time

Git / Gitea Repository Usage Policy Repository Access, Security & Collaboration Public GGU policy — subject to revision as systems, responsibilities, and operational practices change. Public Transparency: This policy is intentionally published so the community can understand GGU's standards and accountability. Credentials, recovery material, private personnel records, and active security-sensitive details remain restricted. This policy defines acceptable use, security, permissions, and collaboration standards for GGU Git repositories hosted in Gitea or any future approved source-control platform. Scope This policy applies to all authorized repository users, including Leadership, Development, approved contributors, automation accounts, and authorized partners. Repository Access Access only repositories required for your responsibilities. Use the lowest permission level that supports your work. Repository Admin access should be limited to maintainers who need to manage settings or permissions. Private repository content must remain private unless publication is approved. Account Security Protect your Gitea account with strong credentials and two-factor authentication where supported. Protect SSH private keys and personal access tokens. Remove keys from lost or retired devices. Never place tokens, passwords, or private keys in repository content, issues, pull requests, or screenshots. Branches & Pull Requests Use feature/fix branches for changes that benefit from review. Respect protected branch requirements. Do not weaken branch protection merely to make one change easier. Use pull requests where review is required or appropriate. Describe what changed, why, and how it was tested. Direct Pushes Direct pushes to important branches should be restricted where appropriate. Even where technically allowed, contributors should use the repository's expected workflow. Commits Use meaningful commit messages. Keep commits understandable and reasonably focused. Do not deliberately hide unrelated changes inside a commit. Do not rewrite shared history without a clear reason and authorization. Do not commit generated binaries unless the repository intentionally tracks them. Secrets Critical: Secrets do not belong in Git history. If a secret is committed, rotate or revoke it immediately. Deleting it from the latest commit does not make it secret again. Use placeholders in tracked example configuration files. Use approved secret-management or deployment mechanisms for real credentials. Treat Gitea Actions secrets and deploy credentials as security-sensitive. Review public/open-source repositories carefully before publication. Pull Request Review Review should consider correctness, security, compatibility, configuration changes, migrations, deployment impact, testing, and rollback where relevant. Repository Permissions Where practical, use organization teams to manage access by responsibility. Permissions should be reviewed after role changes, project completion, extended inactivity, or security incidents. Releases & Tags Use consistent versioning where the project releases deployable versions. Do not casually move published release tags. Document breaking changes or required configuration migrations. Confirm release artifacts do not contain secrets. Force Pushes & History Rewriting Force-pushing protected or shared branches is prohibited unless explicitly authorized for an exceptional recovery case. Prefer revert commits for correcting changes that have already been shared. External Contributions External or partner contributions may be accepted when authorized and should follow the same security, review, and licensing standards as internal contributions. Repository Archival Retired repositories should normally be archived rather than deleted when they retain historical, operational, or recovery value. Document replacements and retirement status. Prohibited Use Publishing private GGU source without authorization. Committing secrets or private member data. Bypassing review or branch protection without authorization. Deleting repositories or history to conceal mistakes. Using GGU repositories to distribute malicious or unauthorized content. Copying third-party code or assets without respecting licensing requirements. Violations Violations may result in repository access removal, corrective action, disciplinary review, or additional action depending on severity. Related Documentation Source Code & Intellectual Property Policy GGU Branch & Pull Request Workflow Git Secrets & Environment File Guide Repository Permissions & Protection Guide Rollback & Revert Procedure Protect the codebase, preserve review, and keep repository history trustworthy.

GGU Git Repository - General Guide This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 1/22/25. Last Bot Update 1/22/25. This is a comprehensive guide for those who don't mind reading a wall of text, this guide cover everything from Generating an SSH key, Adding an SSH key to your GGU Git Repository Account, Verifying an SSH key and other Git processes such as Initializing a repository, Adding Files, Pushing, Pulling, Committing, Creating/Removing Branches and Troubleshooting. If you have any question, please contact us on our Discord server under #helpdesk. Generating a New SSH Key You can generate a new SSH key on your local machine. After you generate the key, you can add the public key to your account on git.gguclan.com to enable authentication for Git operations over SSH. Windows: Adding your SSH key to the ssh-agent Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. Windows: Adding a new SSH key to your account You can add an SSH key and use it for authentication, or commit signing, or both. Copy the SSH public key (.pub extension) to your clipboard If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. Go to c/Users/YOU/.ssh/ or c/Users/YOU/ and locate the newly generated SSH key (ssh_keyname.pub) and copy the contents (Ctrl + C) - Make sure to open with notepad In the upper right-hand corner of the GGU Git Repository, click on your profile picture and go to Settings. Navigate using the left-hand menu to SSH / GPG Keys When on that page you'll see 2 options - Manage SSH keys and Manage GPG Keys. Select "Add Key" next to Manage SSH Keys. From there you'll need to enter a "Key Name", This can be anything that is easily identifiable in case you use multiple keys. Paste the information you copied from ssh_keyname.pub and paste under "Content" and click "Add Key". Verifying a newly added SSH key Now we have to verify the SSH key that you just added before we can start using it. Click "Verify" Follow the instructions given by the Git Repository for Linux or use the command below for Windows using Git Bash - Enter your passphrase when prompted. Replace token with the token provided by the Git Repository. echo -n 'token' | ssh-keygen -Y sign -n gitea -f "C:\Users\YOU\.ssh\ssh_keyname" or "C:\Users\YOU\ssh_keyname" You should now see: -----BEGIN SSH SIGNATURE----- LOTS OF TEXT -----END SSH SIGNATURE----- Copy the SSH Signature and paste it into the Git Repository. If the process was completed correctly, you should see "SSH key "SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" has been verified." and should show "Verified Key" above the key name you provided. Creating/Initializing a Repository Now that we our SSH key generated and added to our account, we can start getting to work. Create a new repository on the GGU Git Repository webpage by going under the organization (Development) and clicking "New Repository". Give the new Repository a name using underscores or dashes for spaces (Good repository names use short, memorable and unique keywords.) and set a Description. You should now see some instructions; from this point you'll want to create a directory for your repository on your computer "C:\Users\YOU\project_name" or anywhere of your choice. Now navigate to the repository path on your computer and right click in a blank area and select "Open Git Bash Here". When the Git Bash comes up, Enter: git init This will initialize the directory you've selected as a directory Git can use; you should see a .git folder be created if you have "View hidden folders" turned on as confirmation. Now enter git checkout -b main Enter git add README.md This will create a README file in the repository directory and add the file to the push que. Enter git commit -m "First Commit" This will tell Git that you are ready to commit the changes to the repository and the reason for the commit. Enter git remote add origin ssh://server_info_from_git_repo/organization_name(Development)/repository_name.git Check your repository for the full path under the SSH option. HTTPS will not work properly and should not be used. Type in your passphrase when prompted - Note Git may ask if you want to trust ssh://server_info_from_git_repo/ with the server's footprint, type YES. Enter git push -u origin main Enter passphrase when prompted This will push the changes to the GGU Git Repository. You can check the repository via the webpage to confirm the changes were made or you can use #dev-git-changes on discord. General Git Commands Now that we've created and initialized a Repository we can start running normal Git commands, these will vary for the projects you're working on - These are the general commands. If you can't figure out how to use a command, Git Bash does a pretty good job of explaining why something isn't working properly. Start a working area (see also: git help tutorial) clone - Clone a repository into a new directory. init - Create an empty Git repository or reinitialize an existing one. Work on the current change (see also: git help everyday) add - Add file contents to the index. mv - Move or rename a file, a directory, or a symlink. restore - Restore working tree files. rm - Remove files from the working tree and from the index. Examine the history and state (see also: git help revisions) bisect - Use binary search to find the commit that introduced a bug. diff - Show changes between commits, commit and working tree, etc. grep - Print lines matching a pattern. log - Show commit logs. show - Show various types of objects. status - Show the working tree status. Grow, mark and tweak your common history branch - List, create, or delete branches. commit - Record changes to the repository. merge - Join two or more development histories together. rebase - Reapply commits on top of another base tip. reset - Reset current HEAD to the specified state. switch - Switch branches. tag - Create, list, delete or verify a tag object signed with GPG. Collaborate (see also: git help workflows) fetch - Download objects and refs from another repository. pull - Fetch from and integrate with another repository or a local branch. push - Update remote refs along with associated objects. Change git remote origin remote -v - View current remote origin. remote set-url origin <NEW_GIT_URL_HERE> - Change to a new remote origin. Troubleshooting These are general problems that you may encounter and how to solve them. fatal: The current branch main has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin main To have this happen automatically for branches without a tracking upstream, see 'push.autoSetupRemote' in 'git help config'.

GGU Git Repository Account - Add a New SSH Key to your account This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 1/22/25. Last Bot Update 1/22/25. This guide is to help you add a newly generated SSH key to your GGU Git Repository Account. If you need help generating a new SSH key and adding it to the ssh-agent, please visit the GGU Git Repository Account - Generate a New SSH Key Guide, if you have any questions, please go through our discord under #helpdesk. Adding a new SSH key to your account You can add an SSH key and use it for authentication, or commit signing, or both. Copy the SSH public key (.pub extension) to your clipboard If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. Go to c/Users/YOU/.ssh/ or c/Users/YOU/ and locate the newly generated SSH key (ssh_keyname.pub) and copy the contents (Ctrl + C) - Make sure to open with notepad In the upper right-hand corner of the GGU Git Repository, click on your profile picture and go to Settings. Navigate using the left-hand menu to SSH / GPG Keys When on that page you'll see 2 options - Manage SSH keys and Manage GPG Keys. Select "Add Key" next to Manage SSH Keys. From there you'll need to enter a "Key Name", This can be anything that is easily identifiable in case you use multiple keys. Paste the information you copied from ssh_keyname.pub and paste under "Content" and click "Add Key". Verifying a newly added SSH key Now we have to verify the SSH key that you just added before we can start using it. Click "Verify" Follow the instructions given by the Git Repository for Linux or use the command below for Windows using Git Bash - Enter your passphrase when prompted. Replace token with the token provided by the Git Repository. echo -n 'token' | ssh-keygen -Y sign -n gitea -f "C:\Users\YOU\.ssh\ssh_keyname" or "C:\Users\YOU\ssh_keyname" You should now see: -----BEGIN SSH SIGNATURE----- LOTS OF TEXT -----END SSH SIGNATURE----- Copy the SSH Signature and paste it into the Git Repository. If the process was completed correctly, you should see "SSH key "SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" has been verified." and should show "Verified Key" above the key name you provided.

GGU Git Repository Account - Generate a New SSH Key This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 1/22/25. Last Bot Update 1/22/25. These are the instructions for generating a new SSH key, adding the newly generated SSH key to the ssh-agent and adding the ssh key to your GGU Git Repository Account. If you have any questions, please use #helpdesk on our discord server. Generating a New SSH Key You can generate a new SSH key on your local machine. After you generate the key, you can add the public key to your account on git.gguclan.com to enable authentication for Git operations over SSH. Windows: Adding your SSH key to the ssh-agent Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. Windows:

Changelog 11/24/24 Rule Changes Updated rules to include Point Farming. Click here to read the updated rules page. Player Tracking Changes Changed minimum active players from 2 to 4 before the server starts tracking kills. Commands List Added more commands to Free VIP. Click here to read the updated commands list.

Changelog 11/16/24 Server Side Anti-Cheat Updated the Server side Anti-Cheat, detections should be more accurate now Player Tracking Changes The GameME player tracking server has been shut down after 10 years of support (BETA) HLStatsX has been setup and installed as the replacement for GameME, you can find the new webpage at https://gguclan.com/stats/ Command List Changes Added HLStatsX commands (Rank, Top10, ETC.)

Changelog 11/12/24 Bot Class Fix - 2Fort/Payload + Servers Added a plugin to fix bots randomly dying in spawn every couple of seconds while trying to figure out what class they can choose. (Bots will actually leave spawn now.)

Minecraft Rules Welcome to Golden Gamers United, the rules for our Minecraft server(s) are listed below. This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 10/13/24. No cheating, map exploits, scripts or hacking to give yourself an unfair advantage against other players. This includes ender pearl exploiting. No sharing links that contain cheats or other malicious content. No advertising/recruiting for other communities, servers or groups on GGU servers. No Ban Evasion - no making another account to get around an existing ban. No disrespect, respect your fellow players and community representatives! Don't promote Racism, Hate, and Harassment on our servers, this includes racial, homophobic or sexist terms. No server disruption, this includes Chat/Mic Spamming, Griefing, Trolling or abusing the report feature. No Threatening to DDoS our servers/other players, this will result in an immediate ban - even if it's a joke. No scamming/sharking/phishing other players or community representatives, this includes intentionally low balling the price of items or stealing players items by deceptive means. No impersonating other players/community representatives in GGU. English is GGU's preference for communication. Please use respective channels if you are using another language or refrain from using voice chat. No unnecessary drama, this includes heated conversations about politics or other subjects. No Doxing/illegal activities, this includes releasing any private information about another player/community representative.

BeamMP Rules Welcome to Golden Gamers United, the rules for our BeamMP server(s) are listed below. This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 10/13/24. No cheating, map exploits, scripts or hacking to give yourself an unfair advantage against other players. No sharing links that contain cheats or other malicious content. No advertising/recruiting for other communities, servers or groups on GGU servers. No Ban Evasion - no making another account to get around an existing ban. No disrespect, respect your fellow players and community representatives! Don't promote Racism, Hate, and Harassment on our servers, this includes racial, homophobic or sexist terms. No server disruption, this includes Chat/Mic Spamming, Griefing, Trolling or abusing the report feature. No Threatening to DDoS our servers/other players, this will result in an immediate ban - even if it's a joke. No scamming/sharking/phishing other players or community representatives, this includes intentionally low balling the price of items or stealing players items by deceptive means. No impersonating other players/community representatives in GGU. English is GGU's preference for communication. Please use respective channels if you are using another language or refrain from using voice chat. No unnecessary drama, this includes heated conversations about politics or other subjects. No Doxing/illegal activities, this includes releasing any private information about another player/community representative.

Control Center Usage Policy Administrative Access, Security & Acceptable Use Public GGU policy — subject to revision as systems, responsibilities, and operational practices change. Public Transparency: This policy is intentionally published so the community can understand GGU's standards and accountability. Credentials, recovery material, private personnel records, and active security-sensitive details remain restricted. The GGU Control Center provides administrative access to game servers and related services. This policy defines how that access may be used, who may use it, and the minimum security and accountability standards expected of authorized users. Scope This policy applies to anyone granted access to the GGU Control Center, including Leadership, Development, approved contributors, and authorized partners. Current GGU Leadership roles and holders are maintained at https://gguclan.com/ranks-and-roster/. Authorized Use Start, stop, restart, or otherwise manage services within your assigned responsibility. View console output and logs for troubleshooting and administration. Manage files for servers you are authorized to maintain. Use backups, schedules, startup settings, and variables within your assigned scope. Perform approved maintenance, updates, configuration changes, and deployments. Use server administration features required to support GGU operations. Least Privilege Access must be limited to the servers and capabilities required for the person's responsibilities. Holding a Leadership title does not automatically require or grant access to every server or node. Account Security Use your own account. Do not share Control Center credentials. Enable two-factor authentication where supported. Use a unique password and secure recovery methods. Do not share SFTP credentials, API tokens, or other access material through public or inappropriate channels. Report suspected compromise immediately. Do not remain signed in on shared or untrusted devices. Server Boundaries Administrative access is scoped. Do not access, inspect, or modify servers, files, databases, or services outside your assigned responsibility without authorization. Production Actions Avoid unnecessary restarts or service interruptions. Use normal stop/restart procedures before using forceful termination unless immediate termination is necessary. Back up or ensure rollback capability before high-impact file or configuration changes. Do not delete backups, databases, or production files without authorization and a clear reason. Do not modify node, Wings, host, or organization-wide infrastructure from a game-server context unless specifically authorized. Console & Command Use Run commands only for legitimate GGU operational purposes. Understand the expected effect before running destructive or high-impact commands. Do not experiment with privileged commands on production services when a safer test path exists. Preserve useful error output and logs when troubleshooting. File Management Make the smallest change necessary. Do not overwrite large directories blindly. Keep configuration syntax valid. Verify ownership and permissions when transferring files. Do not upload unknown or untrusted executables/scripts to production systems. Do not store credentials or secret values in public repositories. Backups & Recovery High-impact changes should have a reasonable recovery path. Depending on the service, that may be a Control Center backup, database backup, repository rollback, previous configuration, container/image rollback, or another documented recovery method. Auditing & Accountability Control Center actions may be logged. Authorized users are expected to act in a way that can be understood after the fact. Do not attempt to conceal administrative actions, alter logs to avoid review, or misrepresent what changed. Emergency Actions Immediate intervention is allowed when necessary to stop active damage, abuse, data loss, compromise, or major service disruption. Emergency action should be limited to what is necessary to stabilize the situation and should be documented afterward. Prohibited Use Using the Control Center for personal advantage, retaliation, harassment, or unauthorized experimentation. Accessing unrelated servers or private data without a legitimate operational reason. Sharing accounts or credentials. Granting panel access without approval. Deleting evidence or logs to conceal mistakes or misconduct. Intentionally disrupting GGU services. Bypassing access controls rather than requesting the permissions you actually need. Access Reviews & Removal Access should be reviewed after promotions, demotions, transfers, extended inactivity, security incidents, and departures. Permissions that are no longer required should be removed promptly. Violations Violations may result in corrective instruction, immediate access removal, suspension, demotion, removal from Leadership, removal from the community, or other action appropriate to the severity and circumstances. Exceptions Exceptions must have a legitimate operational reason and appropriate approval. High-risk exceptions should be documented. Related Documentation Production Access & Change Management Policy Access Request & Permission Change Guide GGU Leadership Incident Response Guide GGU Control Center SFTP Guide Use privileged access deliberately, securely, and only for GGU operations.

Changelog 6/28/24 Base Decay The base decay plugin appears to be working now thanks to the Developer of the plugin! (Not apart of our team) Garage Added new Garage plugin - VirtualGarage, this should fix the issue with vehicles being pulled out of the garage disappearing. Added new permissions for new Garage plugin. Changed Garage group priorities to fix a permissions issue. Changed old plugin commands to aid in migration - Refer to the guide below. ShopUI Fixed Shop command not working on Germany. Shop currently appears broken due a Development issue, waiting for the Dev to fix (Not apart of our team). Workshop Added Shark Plushies (https://steamcommunity.com/workshop/filedetails/?id=3289939742) Forums Updated Commands list to reflect new changes. (https://gguclan.com/forums/topic/84-unturned-commands-list/) Migration Instructions Use /garage1 to view the vehicles you have stored in the old garage. Use /gretieve1 "vehiclename" to pull your vehicle out of your old garage. Use /gadd "vehiclename" to add to the new garage. Use /garage to verify that you vehicle has been added to the new garage successfully. You can click on the vehicle name to pull it out.

Changelog 6/28/24 Economy Switched from RocketMod Uconomy to OpenMod Economy Removed $ as the currency symbol ($200), added MB as the currency symbol instead (200 MB) Killing a zombie/Balance changes no shows up in chat, so you go on a killing spree without missing out on the conversation! ShopUI The shop no longer crashes the servers, this is the main reason we changed to OpenMod Economy (Balances have been transferred over) Updated translation files to accommodate currency symbol change Hud Balance has been temporarily removed from the Hud due to Economy plugin change (Looking for a fix) Bans Bans will now use our Global Bans System (SourceBans) and should be visible on this page https://gguclan.com/bans (Thanks to `Mixy for creating the plugin) Things that are broken (Looking for a fix) Hud no longer reflects correct balance (As listed above) Some chat colors are missing on some dialogs Base decay plugin isn't working - Changed base "Base decay" from 1 week to 2 weeks (This was used as a fallback) Technical Information (For those who want the nitty gritty)

Changelog 6/20/24 ShopUI Added Arid Category Changed the order in which the categories were listed (General, Elver, Arid, Workshop Items) Moved Graphics Card item to Arid category

Changelog 6/17/24 ShopUI An updated version of the ShopUI Plugin has been released and applied to the servers, we shouldn't be crashing anymore - Due to lost items and the Shop being down for so long, everyone has received 500 metal bars for the inconvenience!

Changelog 6/16/24 Chat Chat colors have been fixed