- Alex -

GGU Metamod and SourceMod Installation Guide This guide is continuously being updated as information changes, this can happen without warning. Last update 9/22/25. Introduction This guide provides comprehensive instructions for installing Metamod:Source and SourceMod on your Source engine game servers. These powerful tools allow server administrators to install plugins, modify gameplay mechanics, and enhance server management capabilities. Who can install Metamod and SourceMod? - GGU Leadership Team (Staff, Manager, Senior Manager, Community Leader) - GGU Development Team - Server owners and administrators with proper file access (Outside of GGU) - Internal/External partners with authorized server management permissions Supported Game Engines and Prerequisites Compatible Games: - Counter-Strike: Source, Counter-Strike: Global Offensive - Team Fortress 2, Left 4 Dead 2 - Garry's Mod, Half-Life 2: Deathmatch - Day of Defeat: Source, and other Source engine games Requirements: - Active Source engine game server - SFTP or FTP access to server files - Server restart capabilities - Basic knowledge of file directory structure Step 1: Download Required Files Download Metamod:Source: - Visit: https://www.sourcemm.net/downloads.php - Select your operating system (Linux or Windows) - Download the latest stable release - Extract the archive to a temporary folder Download SourceMod: - Visit: https://www.sourcemod.net/downloads.php - Select your operating system (Linux or Windows) - Download the latest stable release - Extract the archive to a temporary folder Step 2: Install Metamod:Source Connect to Your Server: - Use SFTP to connect to your game server - Navigate to your game server's root directory - Locate the game folder (e.g., csgo, tf, left4dead2) Upload Metamod Files: - From your extracted Metamod archive, upload the entire "addons" folder - Merge it with any existing "addons" folder in your game directory - The structure should look like: /game/addons/metamod/ Step 3: Install SourceMod Upload SourceMod Files: - From your extracted SourceMod archive, upload the "addons" and "cfg" folders - Merge with existing folders in your game directory - The structure should include: /game/addons/sourcemod/ Verify Installation Structure: Your game directory should now contain: - /addons/metamod/ - /addons/sourcemod/ - /cfg/sourcemod/ Step 4: Configure Admin Access Edit admins_simple.ini: - Navigate to /addons/sourcemod/configs/ - Open admins_simple.ini - Add your Steam ID and permissions: "STEAM_1:0:12345678" "99:z" - Save the file Alternative: Use admins.cfg: - For more advanced admin configuration - Edit /addons/sourcemod/configs/admins.cfg - Follow the detailed examples in the file Step 5: Restart and Test Restart Your Server: - Stop your game server completely - Wait 10-15 seconds - Start your server again - Monitor the server console for any error messages Test Installation: - Connect to your server - Type "sm version" in console (as admin) - Type "meta version" in console (as admin) - You should see version information for both tools Common Installation Issues Server Won't Start: - Check that you downloaded the correct OS version (Linux/Windows) - Verify gameinfo.txt syntax is correct - Ensure file permissions are set properly (755 for directories, 644 for files) Commands Not Working: - Verify your Steam ID is correctly added to admins_simple.ini - Check that SourceMod loaded successfully in server console - Ensure you have the proper admin flags assigned Plugin Errors: - Check /addons/sourcemod/logs/ for error details - Verify plugin compatibility with your game and SourceMod version - Remove problematic plugins temporarily to isolate issues Security and Configuration Guidelines - Always download Metamod and SourceMod from official sources only - Regularly update both tools to the latest stable versions - Use strong admin passwords and limit admin access appropriately - Golden Gamers United (GGU) configuration files may not be modified or removed unless given explicit permission from the GGU Leadership Team (Manager+) - Create backups of your server files before installation - Monitor server logs regularly for any suspicious activity Plugin Management Best Practices Installing Plugins: - Place .smx files in /addons/sourcemod/plugins/ - Place configuration files in /cfg/sourcemod/ - Place data files in /addons/sourcemod/data/ - Always read plugin documentation before installation Plugin Safety: - Only install plugins from trusted sources - Test plugins on a development server first - Keep plugin databases and configurations backed up - Remove unused plugins to improve performance Useful Commands for Server Management Basic Commands: - sm plugins list (List all loaded plugins) - sm plugins load <plugin> (Load a specific plugin) - sm plugins unload <plugin> (Unload a specific plugin) - sm config (Reload SourceMod configuration) Admin Commands: - sm_admin (Open admin menu) - sm_kick <player> (Kick a player) - sm_ban <player> <time> (Ban a player) - sm_map <mapname> (Change map) Reporting and Support - Report installation issues to the GGU Leadership Team immediately (If a part of the GGU Leadership or Development teams) - Include error logs and server console output when seeking help - Document any server crashes or performance issues after installation - Golden Gamers United (GGU) reserves the right to monitor and audit server modifications to ensure compliance with hosting policies Conclusion By following this installation guide and adhering to GGU's server management policies, administrators can successfully deploy Metamod:Source and SourceMod to enhance their game servers. These tools provide powerful server management capabilities while maintaining the security and stability that Golden Gamers United (GGU) is committed to providing for all hosted servers.

GGU Control Center SFTP Connection Guide This guide is continuously being updated as information changes, this can happen without warning. Last update 9/27/25. Introduction This guide provides step-by-step instructions for connecting to your Control Center server(s) via SFTP (Secure File Transfer Protocol). SFTP allows you to securely transfer files to and from your server, manage your server files, and perform essential administrative tasks. Who can use SFTP access? - GGU Leadership Team (Staff, Manager, Senior Manager, Community Leader) - GGU Development Team - Internal/External partners with authorized access Prerequisites and Requirements - Active Control Center server with SFTP access enabled - Valid server credentials (username, password, host, port) - SFTP client software (FileZilla, WinSCP, or command line) - Stable internet connection Getting Your SFTP Connection Details From Pelican Panel Dashboard: 1. Log into your Pelican Panel 2. Navigate to your server dashboard 3. Look for the "Settings" or "SFTP Details" section 4. Note the following information: - Host/Server Address: sftp.ovh1.gguclan.com - Port: 2022 (default SFTP port for Pelican) - Username: Your server identifier (e.g., username.shortuuid) - Password: Your panel account password Example Connection Details Host: sftp.ovh1.gguclan.com Port: 2022 Username: username.shortuuid Password: YourPanelPassword123 Method 1: FileZilla (Recommended for Beginners) Download and Install FileZilla: - Download from: https://filezilla-project.org/ - Install the client version (not server) Configure Connection: - Open FileZilla - Go to File → Site Manager - Click "New Site" and name it (e.g., "GGU Minecraft Server") - Enter your connection details: • Protocol: SFTP - SSH File Transfer Protocol • Host: sftp.ovh1.gguclan.com • Port: 2022 • Logon Type: Normal • User: username.shortuuid • Password: YourPanelPassword123 Connect: - Click "Connect" - Accept the host key if prompted (first connection only) - You should see your server files in the remote directory panel Method 2: WinSCP (Windows Only) Download and Install WinSCP: - Download from: https://winscp.net/ Create New Session: - Open WinSCP - File protocol: SFTP - Host name: sftp.ovh1.gguclan.com - Port number: 2022 - User name: username.shortuuid - Password: YourPanelPassword123 Save and Connect: - Click "Save" to store the session - Click "Login" to connect Method 3: Command Line (Advanced Users) Linux/Mac Terminal: sftp -P 2022 [email protected] Windows PowerShell/Command Prompt: sftp -oPort=2022 [email protected] Common SFTP Commands Navigation Commands: - pwd (Show current directory) - ls (List files and folders) - cd foldername (Change to directory) - cd .. (Go up one directory) File Transfer Commands: - get filename (Download file from server) - put filename (Upload file to server) - get -r foldername (Download entire folder) - put -r foldername (Upload entire folder) File Management Commands: - mkdir foldername (Create directory) - rmdir foldername (Remove empty directory) - rm filename (Delete file) - rename oldname newname (Rename file) Security and Best Practices - Always use SFTP (not FTP) for secure encrypted transfers - Never share your SFTP credentials with unauthorized users - Regularly change your panel password for security - Create backups before making major file changes - Golden Gamers United (GGU) configuration files may not be modified or removed unless given explicit permission from the GGU Leadership Team (Manager+) - Log out of SFTP sessions when finished Troubleshooting Common Issues Connection Refused Error: - Check if the server is online in Pelican Panel - Verify the host address and port number - Ensure your firewall isn't blocking the connection Authentication Failed: - Double-check your username and password - Ensure your account has SFTP permissions - Try resetting your panel password Host Key Verification: - Accept the host key on first connection - If key changed, contact GGU Leadership Team File Management Guidelines - Always backup important files before editing - Use proper file permissions when uploading files - Avoid uploading unnecessarily large files - Keep your server files organized in appropriate directories - Monitor disk space usage to prevent server issues - In the event of an accidental deletion or data loss, users must immediately notify the GGU Leadership Team to initiate the restoration process Reporting and Compliance - Report connection problems to the GGU Leadership Team - Include error messages and connection details when seeking help - Document any suspicious activity or unauthorized access attempts - Golden Gamers United (GGU) reserves the right to monitor and audit user activities on its servers to ensure compliance with security policies Conclusion By following this guide and adhering to GGU's security policies, users can safely connect to their Control Center server(s) via SFTP and manage their server files effectively. Golden Gamers United (GGU) is committed to providing secure and reliable services for all users and partners.

Global Moderation Review Hub Usage Guide This comprehensive guide covers all features and procedures for using the Global Moderation Review Hub. This guide is for Mod+ who need to manage bans, mutes, and web moderations across multiple game servers. The system supports Discord ID, Steam ID, TeamSpeak UUID, Minecraft UUID, Hytale UUID and IP-based punishments with full Forums integration. This guide is continuously being updated as features and procedures change. Last updated: 01/31/26. System Overview & Permissions Permission Groups and Access Levels Guest: View-only access to public ban information Registered Users: Can post comments on bans for an appeal or add evidence Moderators: Can add bans/mutes, requires Server Teams group for web moderations Staff: Can add bans/mutes and approve appeals, requires Server Teams group Managers: View-only without Server Teams, full access with Server Teams Senior Managers: Full access to all features without team restrictions Community Leaders: Full unrestricted access to all system features Server Teams: Secondary group required for Mods/Staff/Managers to perform ban actions Supported Games and Platforms Supported Games: Counter-Strike: Source Counter-Strike: Global Offensive Discord Hytale Team Fortress 2 Team Fortress 2 Classic Left 4 Dead 2 Garry's Mod Minecraft TeamSpeak Unturned Assetto Corsa Web Bans (Forum-based violations) Player Identifier Types: Steam ID: STEAM_0:X:XXXXXXX, [U:1:XXXXXXX], or SteamID64 format TeamSpeak ID: UUID format (a1b2c3d4-e5f6-7890-abcd-ef1234567890) Minecraft ID: Username or UUID format IP Address: IPv4 format for network bans Adding Bans and Mutes Steam ID Based Punishments Required Information: Player's Steam ID (any format accepted) Player's current name Violation reason Duration (30 seconds to permanent) Server where violation occurred Supporting evidence (demos, screenshots) Procedure: Navigate to "Add Ban" or "Add Mute" section Select punishment type (Ban/Mute) Choose Steam ID as identifier type Enter Steam ID in any supported format Fill in player name and reason Set duration using presets or custom time Select target server or "All Servers" Upload evidence files (demos, screenshots) Submit punishment for approval Notes: The system automatically converts between Steam ID formats and will attempt to link the punishment to the player's IPS forum account if they have linked their Steam profile. TeamSpeak ID Based Punishments Required Information: Player's TeamSpeak UUID Player's TeamSpeak nickname Violation reason Duration Evidence (chat logs, recordings) Procedure: Select "TeamSpeak ID" as identifier type Enter UUID in format: a1b2c3d4-e5f6-7890-abcd-ef1234567890 Complete remaining fields as with Steam ID punishments Notes: The system will attempt to match the UUID to forum accounts with linked TeamSpeak profiles. Minecraft ID Based Punishments Required Information: Minecraft username or UUID Violation details Server information Supporting evidence Procedure: Select "Minecraft ID" as identifier type Enter username or UUID Complete punishment details Notes: The system will attempt to match the UUID to forum accounts with linked Minecraft profiles. Web-Based Punishments Permission Requirements: Mod+: Must have Server Teams Secondary group Senior Managers+: No team restrictions Procedure: Select "Web Moderation" Target player by Steam, Teamspeak or Minecraft ID/UUID Specify platform-specific violation details Upload evidence (screenshots, chat logs) in a new post on the ban Duration Management Available Duration Presets 30 Seconds 1 Minute 5 Minutes 10 Minutes 30 Minutes 1 Hour 2 Hours 3 Hours 6 Hours 12 Hours 1 Day 2 Days 3 Days 1 Week 2 Weeks 1 Month 3 Months 6 Months 1 Year Permanent Custom Duration Input Supported Units: Seconds Minutes Hours Days Weeks Months Years Usage: Enter a number and select the time unit from the dropdown menu Evidence and File Management Supported File Types .dem files (Source Engine demos) .jpg, .jpeg, .png, .gif, .webp (Image files) .mp4 (Video files) File Size Limit: 50MB per file Evidence Requirements Minimum Evidence Required: For Cheating: Demo file showing cheat usage For Chat Violations: Screenshots of chat messages For Voice Violations: Video recordings For Game Exploits: Demo or video showing the exploit Best Practices: Include player's Steam ID in screenshots Show server information and timestamp Capture before, during, and after the violation Include any warnings given to the player Approval and Management Procedures Ban Approval Process Who Can Approve: Staff + with Server Teams Senior Managers - No team restriction Community Leaders - No team restriction Approval Actions Available: Approve: Approve the ban as submitted Approve with Modifications: Change duration, reason, or scope Deny: Reject the ban with reason Approval Workflow: Review submitted evidence thoroughly Check player's previous ban history Verify punishment fits the violation severity Ensure proper evidence standards are met Make approval decision with clear reasoning Leadership Panel Access Features Available: Advanced search and filtering Approval history tracking System statistics and reporting Post Management and Moderation Comment System Who Can Comment: Registered users and above Banned players (for appeals) Staff members (for clarification) Comment Features: Rich text editor with formatting options File attachment support Automatic forum account linking Role-based styling and badges Post Hiding and Moderation Who Can Hide Posts: Staff+ with Server Teams group - Level 1 hiding, Only Staff+ can see these posts Managers+ with Server Teams group - Level 2 hiding, Only Manager+ can see these posts Reasons to Hide Posts: Inappropriate content or language Personal information exposure Spam or irrelevant comments Sensitive evidence that should be staff-only Advanced Features Ban Duration Countdown Timers Features: Live countdown for temporary bans Visual indicators for ban status Automatic status updates Color-coded expiration warnings Notification System System Features: Real-time notifications for ban/mute events Automatic alerts for approval status changes Integration with forum notification system Notification Types: New Ban/Mute Submissions: Alerts Staff+ when new punishments are submitted for approval Approval Status Changes: Notifies submitters when bans/mutes are approved/denied Notification Recipients: Staff+: Get alerts for pending reviews, approvals and denials Notification Settings: Forum Notifications: Automatic IPS notification system integration Email Alerts: Optional email notifications for critical events Troubleshooting and Common Issues File Upload Issues Problem: File upload fails Solutions: Check file size (must be under 50MB) Verify file type is supported Try uploading one file at a time Use a different file format if possible Steam ID Format Issues Problem: Steam ID not recognized Solutions: Try different Steam ID formats (STEAM_0:X:X, [U:1:X], or SteamID64) Use a Steam ID converter tool Copy the ID directly from the game console Verify the ID belongs to the correct player Best Practices and Guidelines Evidence Collection Always record demos for suspected cheating Take screenshots of chat violations immediately Include context before and after the violation Document any warnings given to the player Verify player identity before submitting punishment Professional Communication Use clear, professional language in ban reasons Be objective and factual in comments Avoid personal attacks or inflammatory language Provide constructive feedback when denying appeals Maintain confidentiality of sensitive information System Integration Features Invision Community Forum Integration Automated Features: User authentication through IPS login system Automatic permission checking based on user groups Role-based styling and access badges Cross-platform account linking and identification Integrated file upload system using IPS attachment handling Multi-Server Network Support Capabilities: Network-wide ban synchronization Server-specific punishment targeting Real-time server status monitoring Cross-game punishment tracking Centralized moderation dashboard For technical support or questions about this system, contact the Development Team or Senior Manager+. This guide covers the primary features and procedures - additional functionality may be available depending on your access level and system configuration. System Version: Global Moderation Review Hub v2026.01 | Guide Version: 1.0

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:

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.