- Alex Thunderhunter -

Changelog 3/22/25 Workshop Mod Removals Removed Trade Notifications (UI) due to a GUID issue cause by the recent update Removed Icy Votes UI due to a GUID issue cause by the recent update

Changelog 8/5/24 ShopUI Updated translation file to fix an issue with the shop not being displayed properly

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

GGU Git Repository Usage Policy This post is continuously being updated as information changes, this can happen without warning. Last update 1/22/25. Introduction This policy outlines the guidelines for contributing to and using our Git repository. By accessing or contributing to this repository, you agree to abide by the terms outlined below. Who falls under the scope of this policy? GGU Leadership Team (Staff, Manager, Senior Manager, Community Leader). GGU Development Team (Development - Anyone with access to the GGU Git Repository). Internal/External partners (Listed and Unlisted partners). Repository Content Open-Source Code: This repository may contain open-source code. Contributions to open-source code should adhere to the licensing terms specified in the respective project documentation. Ensure that you have the rights to contribute the code and that it does not infringe on any third-party rights. Closed Source Code: This repository may also host closed source code. Access to closed source code is restricted to authorized users only. Unauthorized access, copying, distribution, or modification of closed source code is strictly prohibited and will result in loss of access to the GGU Git Repository. Contribution Guidelines Coding Standards: Follow the coding standards and guidelines specified in the project documentation. Ensure that your code is well-documented and easy to understand. Pull Requests: Submit pull requests for code contributions. All pull requests will be reviewed by the repository maintainers. Changes may be requested before merging. Issue Reporting: Use the issue tracker to report bugs, request features, or ask questions. Be clear and concise in your descriptions. Licensing Open-Source Contributions: All contributions to open-source projects must include appropriate licensing information. Ensure that your contributions comply with the licensing terms of the project. Closed-Source Contributions: Contributions to closed source projects remain the intellectual property of the original author unless otherwise agreed upon. Code of Conduct Respect: Treat all users and contributors with respect. Harassment, discrimination, and abusive behavior will not be tolerated. Collaboration: Encourage a collaborative environment. Share knowledge and help others improve their contributions. Responsibility: Take responsibility for the quality and security of your contributions. Address issues promptly and follow best practices. Security Vulnerabilities: Report any security vulnerabilities immediately to the repository maintainers. Do not disclose vulnerabilities publicly until they have been addressed. Best Practices: Follow security best practices to protect the integrity of the code and data in the repository. Compliance Legal Compliance: Ensure that your contributions comply with all applicable laws and regulations. Do not include any content that is illegal or infringes on the rights of others. Policy Updates: This policy may be updated periodically. Check the repository documentation for the latest version of the policy. Auditing: Golden Gamers United (GGU) reserves the right to monitor and audit user activities to ensure compliance with this policy. Contact For any questions or concerns regarding this policy, please contact us via Discord under #helpdesk.

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:

Discord Dyno Bot Commands List - Staff+ This post is continuously being updated as methods/information changes, this can happen without any warning. Last update 12/04/24. Last Bot Update 12/04/24. If you need Server Manager or Community Manager access on any platform (including discord) please ping @ - Alex Thunderhunter - or @ Admiral MacK for help. ALL COMMANDS ARE TOGGLES which means you can add/revoke roles with the same command. If you have access to give a role, you have access to revoke it. When promoting anyone to a higher rank fully remove their previous access before granting their new access to prevent the spacer roles from breaking. Manager Roles ?manager <user> - Requires Sr. Manager ?devm <user> - Requires Sr. Manager ?csgosm <user> - Requires Sr. Manager ?outreachm <user> - Requires Sr. Manager ?tf2sm <user> - Requires Sr. Manager ?untsm <user> - Requires Sr. Manager Staff Roles ?staff <user> - Requires Manager ?csgostaff <user> - Requires CS:GO Manager ?mcstaff <user> - Requires MC Manager ?tf2staff <user> - Requires TF2 Manager ?untstaff <user> - Requires Unturned Manager Mod Roles ?mod <user> - Requires Manager ?csgomod <user> - Requires CS:GO Manager ?mcmod <user> - Requires MC Manager ?tf2mod <user> - Requires TF2 Manager ?untmod <user> - Requires Unturned Manager Development Roles ?coding <user> - Requires Dev Manager ?design <user> - Requires Dev Manager ?developer <user> - Requires Dev Manager Outreach Roles ?outreach <user> - Requires Outreach Manager Roster Roles ?member <user> - Requires Staff+ (Only necessary if someone already does not have it from sync) ?retired <user> - Requires Staff+ ?veteran <user> - Requires Staff+ If you're having an issue with the bot please message @ - Alex Thunderhunter - or @ Admiral MacK for help.