🌌 Get ready to dive into a world of excellence in hosting. 💻⚙️ Here, you can explore outstanding performance, customize your server, and enjoy the peace of securely storing your files in the cloud. 😉

🙌 We're excited to have you on board. Join our community to share achievements, make new friends, and have incredible experiences! 🤝💬

🌟 Our team is here to assist you anytime. If you have questions or need support, feel free to contact us. 🆘 We are committed to making your stay at HidenCloud the best hosting experience possible. 💪💙

So, buckle up, get comfortable, and get ready for hours of seamless hosting and camaraderie in our HidenCloud community. ☁️✨

At HidenCloud, each contracted service can be in different states depending on its life cycle and user actions. Below are these states and their meanings:

1. Activated

• Description: This is the normal state of a service that is up and running. It means the service is active, and all associated invoices have been paid. The client has full access to the service and all its functionalities.

2. Suspended

• Description: A service enters a suspended state when there is an unpaid service invoice.

• Important Details:

  • Access: Nothing is deleted, but access to the service is unavailable.

  • Reason for Suspension: The suspension is probably due to an unpaid invoice. If payment is not made within 5 days, the service will be Terminated.

  • Client Notification: "The due date for this service was {due_date}. We regret to inform you that your service has been suspended due to a missed payment. To avoid termination, please settle/pay any outstanding invoice within {suspended_after} days from the due date. If payment is not received within this timeframe, your service will be terminated, resulting in the deletion or revocation of all data, files, and licenses associated."

3. Canceled

• Description: A service is in a canceled state when the user has decided to discontinue the service, but it has not yet been terminated.

• Important Details:

  • Access: Nothing is deleted, but the service is scheduled to be terminated, access to the service is available.

  • Client Notification: "This service is scheduled to be terminated on {terminated_at}. If you have changed your mind, you can undo the cancellation before this date. If no action is taken, your service will be suspended and terminated. All files and data belonging to this service will be permanently deleted."

4. Terminated

• Description: This state indicates that the service has been completely removed and cannot be recovered.

• Important Details:

  • Access: The service has been erased and cannot be undone.

  • Client Notification: "This service was terminated. Termination can occur for various reasons, such as not paying on time or canceling the service. All data/files/licenses belonging to this service have been deleted or revoked. This process is irreversible."

We offer you the opportunity to enhance your experience with additional services. Follow these simple steps to purchase additional services:

Check out our additional extras here: Extras Root VPS Extras:

Step 1: Log In

Step 2: Navigate to the Tickets Page

Once logged in, look for the "Tickets" tab in the main menu and click on it.

Step 3: Create a New Ticket

Within the Tickets page, find and select the option to "Create Ticket" or "Create New Ticket."

Step 4: Select Extra/Additional Services Category

When in the ticket creation section, choose the category "Extra / Additional Services" to specify that you are interested in additional services.

Step 5: Fill in Ticket Information

Now, complete the requested information in the ticket form:

• Subject: Specify the additional service you want to acquire.

• Order: Specify the server on which you want to add this additional service.

• Comment: Provide a detailed description of what you need and how much you need. Include any relevant additional information.

Step 6: Submit the Ticket

Once you have filled in all the fields, click on the "Submit" button to create the ticket.

Step 7: Payment and Invoice Entry

After submitting the ticket, you will receive a message in your inbox with the corresponding invoice for the requested additional service. Open the invoice and make the payment following the provided instructions.

Step 8: Monthly Update

The cost of the additional service will be added to the value you already pay monthly for our main services.

And that's it! Now you are ready to enjoy your additional services on HidenCloud. If you have any questions or issues, feel free to create another ticket in the corresponding category. Thank you for choosing HidenCloud!

Step 2: Go to the Tickets Page After logging in, locate the "Tickets" tab in the main menu and click on it.

Step 3: Create a New Ticket Within the Tickets page, find and select the option "Create Ticket" or "Create New Ticket".

Step 4: Select Ticket Category While in the ticket creation section, choose the category that best fits your issue or question. The available categories are as follows:

1. General Questions: Use this category for general inquiries about the service, system operation, or any other questions not specific to technical support or billing.

2. Technical Support: Select this category if your inquiry is related to technical issues, errors, or if you need assistance with the technical configuration of services.

3. Billing Support: If your question involves billing topics, payments, or any financial matters, choose this category.

4. Account Support: Use this category if you need help managing your account, such as changes to personal information, account updates, or access issues.

5. Other Support: If your inquiry doesn't fit into any of the above categories, you can use this option to provide detailed information about your situation.

6. Additional / Extra Services: Choose this category if you are interested in acquiring additional services not included in your current plan. Here, you can specify the additional service you want to add, the server you want to implement it on, and provide additional details.

Step 5: Fill in Ticket Information Complete the required information in the ticket form, including the subject, order number, and a detailed comment describing your request or issue.

Step 6: Submit the Ticket Once you have filled out all the fields, click the "Submit" button to create the ticket and send your request to the appropriate support team.

Step 2: Navigate to the Services Section Once in the control panel, locate and click on the section labeled "Services." Here, you'll find different categories that match your needs.

Step 3: Select a Category and Plan Explore the available categories and choose the one that best suits your requirements. Within each category, there are different plans. Click on the plan that interests you to get more details.

Step 4: Read the Plan Description Upon selecting a plan, a page with detailed information about the services included in that plan will open. Carefully read the description to ensure it meets your needs.

Step 5: Complete the Options After deciding on a plan, click on the "Get Started" or similar button. You will be guided to complete necessary options, such as payment information, entering any coupons (if you have one), and selecting the server location. Make sure to provide accurate information.

Step 6: Finalize the Payment Once you've completed all the required options, you'll be redirected to the payment page. Choose your preferred payment method and follow the instructions to complete the transaction. Confirm all details before finalizing the payment.

Step 7: Receipt of Invoice and Credentials After making the payment, you'll receive a detailed invoice in your email. Review the invoice to confirm the transaction. Additionally, you will receive the credentials needed to access the control panel of the purchased service.

¡Done! Now you can access the HidenCloud control panel with the provided credentials and start configuring and managing the acquired service according to your needs. If you encounter any issues during the process, feel free to contact HidenCloud's technical support for further assistance.

Enable Two-Factor Authentication (2FA) on HidenCloud

1. Sign In:

   • Log in with your username and password.

2. Access Account Settings:

   • Once logged in, click on your profile picture in the upper-right corner of the screen.

3. Navigate to Account Settings:

   • Look for the option that says "Account Settings" and click on it.
4. Enable Two-Factor Authentication (2FA):

   • Within Account Settings, locate the box that says "Two-Factor Authentication" and click the "Enable" button.
5. Scan the QR Code:

   • A QR code will appear on the screen. You can scan this code with your preferred authenticator app (such as Google Authenticator or Authy). Alternatively, you can manually enter the provided code.

6. Set Up the Authenticator App:

   • Open your authenticator app and scan the QR code or manually enter the provided code.

7. Save Backup Codes:

   • After configuring authentication, HidenCloud will provide you with a set of backup codes. These codes are crucial in case you lose access to your authenticator app.

   • Save these codes in a secure place. You can print them, store them in a secure password manager, or note them down in a safe location.

8. Complete the Process:

   • After entering the authenticator app code and saving the backup codes, click "Continue" or "Save" to complete the process.

You're done! You have now enabled two-factor authentication on your HidenCloud account. Remember that in the future, you will need the authenticator app, and in case of emergencies, the backup codes to access your account. Keep these items secure!

We are pleased to have you here! This comprehensive resource serves as your ultimate guide to everything related to HidenCloud, and now it also includes detailed information on various specific categories to enhance your experience. Explore below:

We encourage you to thoroughly explore this resource to familiarize yourself with all policies, terms, and frequently asked questions. If you have more questions or need assistance, our support team is always available to help.

Please note that the information provided here is accurate as of its last update.

Thank you for choosing HidenCloud. We are excited to offer you exceptional hosting services and ensure a seamless experience. Welcome to the HidenCloud community!

At HidenCloud, we understand the importance of providing flexible and secure payment options for our hosting services. Therefore, we currently offer three different payment methods to suit the needs and preferences of our clients: PayPal (One-Time Payment), PayPal (Subscription), and HidenCloud Balance. Below are the details of these methods:

1. PayPal & Card (One-Time Payment)

• Description: This option allows customers to make a one-time payment for hosting services without committing to a subscription. It's ideal for those who prefer to make payments as they require the service, without long-term commitments.

• How It Works: The customer selects the services they wish to purchase and makes a one-time payment through PayPal. The client must renew the service manually as well as make the corresponding payment manually.

2. PayPal & Card (Subscription)

• Description: For customers who prefer the convenience of automatic payments, we offer a subscription option through PayPal. This mode ensures continuous service renewal without the need to remember to make manual payments.

• How It Works: The customer sets up a recurring subscription in PayPal, authorizing HidenCloud to charge the service cost periodically (e.g., monthly or annually). The client should NOT renew the service manually. Paypal is responsible for making the payment automatically.

3. HidenCloud Balance

• Description: This option allows users to load funds into their HidenCloud account, which can be used to pay for future services. It's a convenient way to manage expenses and maintain budget control.

• How It Works: The customer adds an amount of money to their HidenCloud balance, which is then automatically deducted when purchasing or renewing services. The client must renew the service manually as well as make the corresponding payment manually.

4. Bank Transfer and Revolut.

• Description: This option allows customers to make payments using traditional bank transfers or through the Revolut platform.

• How It Works: If you want to pay with bank transfer or Revolut, please contact elk sports and support will give you the details. Please note that this process is manual.

Card Compatibility and Payment Ease with PayPal

To ensure maximum convenience and accessibility, our payments via PayPal are compatible with a wide range of credit and debit cards, including:

• Visa

• MasterCard

• American Express

• Discover

• National and international bank cards

Furthermore, it's important to note that it is not necessary to have or create a PayPal account to make a payment. Customers can opt to pay as guests, using just their credit or debit card on PayPal's secure platform.

If you wish to delete your HidenCloud account, please follow the steps below:

1. Log in to the HidenCloud Dashboard

   • Open your web browser and navigate to the HidenCloud website.

   • Enter your username and password to log in to your account.

2. Access Your Profile

   • Once logged in, click on your profile icon located at the top right corner of the dashboard.

3. Navigate to Account Settings

   • From the dropdown menu, select "Account Settings."

4. Scroll to the Bottom of the Page

   • On the Account Settings page, scroll down to the bottom.

5. Click the Delete Account Button

   • At the bottom of the page, you will find the "Delete Account" button. Click on it.

6. Confirm Account Deletion

   • You will receive a confirmation email. Follow the instructions in the email to confirm the deletion of your account.

   • Your account will be scheduled for deletion and will be permanently deleted within 72 hours.

Important Notes

• Accidental Deletion: If you initiated the deletion process by mistake, you have the option to undo the deletion. Simply follow the instructions in the confirmation email or contact HidenCloud support for assistance.

• Support Assistance: If you encounter any issues or require further assistance, please reach out to our support team. You can contact support through the HidenCloud website or directly via email.

Account created with Oauth (Google / Discord)?

At HidenCloud we have two types of VPS:

Non-Root VPS and Root VPS

Non-Root VPS Extras: Extras

Root VPS Extras:

IP:

Included 1 IPv4 and 1 IPv6 for any server.

First two: Each IPv4 is 5€. Each IPv6 is 3€

From the third:Each IPv4 is 4€. Each IPv6 is 2€

Bandwidth:

Included 20TB for any server (Exceptions: 30TB in VPS: DAM-Dragon, 40TB in VPS: DAM-Titan and 50TB in VPS: DAM-Behemoth).

+10€ per extra TB

Backup:

Included 2 Backups for any server.

+10€ per extra Backup

ROOT VPS - Available Images:

x86 - System:
- Ubuntu 20.04
- Debian 11
- Rocky Linux 8
- CentOS Stream 9
- Ubuntu 22.04
- Rocky Linux 9
- AlmaLinux 8
- AlmaLinux 9
- Debian 12
- Fedora 39
- Fedora 40
- Ubuntu 24.04

x86 - App:
- LAMP
- WordPress
- Jitsi
- Nextcloud
- Docker CE
- GitLab
- Prometheus & Grafana
- WireGuard
- Owncast
- Photoprism
- RustDesk

---

ARM - System:
- CentOS Stream 9
- Debian 11
- Rocky Linux 8
- Rocky Linux 9
- Ubuntu 20.04
- Ubuntu 22.04
- AlmaLinux 8
- AlmaLinux 9
- Debian 12
- Fedora 39
- Fedora 40
- Ubuntu 24.04

ARM - App:
- Jitsi
- Owncast
- RustDesk
- Nextcloud
- LAMP
- WordPress
- WireGuard
- Docker CE
- Prometheus & Grafana
- Photoprism
- GitLab

ROOT VPS - Available ISOs:

x86:
- 3CX v20 Debian12 (amd64)
- Windows Server 2016 English
- Securepoint UTM v12.5.4.1 Installer x86_64
- Windows Server 2016 Russian
- Windows Server 2016 Language Pack
- OPNsense 24.7 (amd64)
- SystemRescueCD (2018-04-02)
- virtio-win-0.1.240.iso
- FreePBX 2104 (amd64)
- Windows Server 2019 German
- Windows Server 2019 English
- pfSense CE 2.7.2 (amd64)
- Windows Server 2016 German (70528)
- Windows Server 2019 Russian
- Debian 12.4 (amd64/netinstall)
- Windows Server 2022 English
- Ubuntu 22.04.3 Live Server (amd64)
- Ubuntu 20.04.6 Live Server (amd64)
- TrueNAS SCALE 22.12.0
- SystemRescueCD (2024-08-29)
- mfsBSD 13.1 (amd64)
- Windows Server 2022 Russian
- NetBSD 9.2 (amd64/bootonly)
- FreeBSD 13.4 (amd64/bootonly)
- Proxmox Mail Gateway 8.0 ISO Installer
- virtio-win-0.1.248.iso
- Proxmox backup Server 3.1
- IPFire 2.29 (amd64)
- OpenBSD 7.5 (amd64)
- Debian 11.9 (amd64/netinstall)
- Alpine Virtual 3.20 (x86_64)
- NixOS 24.05 (x86_64/minimal)
- openSUSE Leap 15.6 (amd64)
- Fedora CoreOS v40.20240709.3.1 (amd64)
- Fedora  40-1.14 (amd64)
- FreeBSD 13.3 (amd64/bootonly)
- Archlinux 2024.08.01 (amd64)
- Kali Linux 2024.2 installer (amd64)
- FreeBSD 14.1 (amd64/bootonly)
- Clonezilla 3.1.3 (amd64/live)
- AlmaLinux 9.4 (amd64/boot)
- Rocky 9.4 (amd64/boot)
- Rocky 8.10 (amd64/boot)

---

ARM:
- Ubuntu 22.04.3 Live Server (arm64)
- Debian 12.4 (arm64/netinstall)
- FreeBSD 13.4 (arm64/bootonly)
- OpenBSD 7.5 (arm64)
- IPFire 2.29 (arm64)
- Alpine Virtual 3.20 (aarch64)
- NixOS 24.05 (arm64/minimal)
- openSUSE Leap 15.6 (arm64)
- Fedora CoreOS v40.20240709.3.1 (arm64)
- Fedora  40-1.14 (arm64)
- FreeBSD 13.3 (arm64/bootonly)
- FreeBSD 14.1 (arm64/bootonly)
- AlmaLinux 9.4 (arm64/boot)
- Rocky 9.4 (arm64/boot)
- Rocky 8.10 (arm64/boot)
- Ubuntu 24.04 Live Server (arm64)

DEMO: Non-Root VPS:

DEMO: Root VPS:

DEMO: How to Install Windows:

Why Has My Server Been Deleted or Account Restricted?

At Hidencloud, we strive to provide a reliable and free hosting service. However, there are several reasons why a server may be deleted. Below are the most common circumstances that can lead to your server being removed:

1. Weekly Renewal Not Completed:

   • Free servers on Hidencloud must be renewed every 7 days from the Hidencloud dashboard. If the renewal is not completed within this period, the server will be automatically suspended.

   • If not renewed within five days after suspension, the server will be permanently deleted and cannot be recovered.

   • On paid servers, the expected payment has simply not been made and within five days after suspension, the server will be permanently deleted and cannot be recovered.

   • In the event that your services are deleted, we will not be held responsible for any data, backup or progress lost.

2. Free Service Limit:

   • Only one free service per user is allowed at any given time. If it is detected that a user has more than one active free service, the system will automatically terminate the first or the first few services activated to comply with this policy.

   • This is done to ensure fair and equitable access to all users.

3. Violation of Usage Policies:

   • Any use that violates our acceptable use policies, such as hosting illegal content, warez, proxies, IRC, or bit torrents, can result in the immediate deletion of the server.

   • Excessive resource usage that negatively affects other users on shared servers is also prohibited.

4. Resource Abuse:

   • If a server continuously consumes excessive resources (more than 25% of the total available resources on shared servers), we reserve the right to delete the server to maintain system performance and stability.

5. Multiple Account Usage:

   • The use of multiple accounts to access free services is not allowed. If a user is found to have multiple accounts, Hidencloud reserves the right to delete all related accounts without prior notice.

   • Notifications will be sent to all email addresses associated with the multiple accounts, requesting that only one account be retained to comply with the service policy.

6. DDoS Attacks and Illegal Behavior:

   • Any attempt to launch or conduct a denial-of-service (DDoS) attack from our servers will result in immediate deletion of the server.

   • Additionally, using the server for cryptocurrency mining, hacking, or engaging in any other illegal activities is strictly prohibited and will result in immediate server deletion and potential future access bans.

   • We take this policy very seriously, your server, account and associated services will be deleted immediately, permanently and without prior notice and you will not be able to use our services ever again.

What to Do If Your Server Has Been Deleted

If your server has been deleted and you need more information or assistance, we recommend following these steps:

1. Check Your Dashboard:

   • Review notifications and the status of your server on the Hidencloud dashboard to understand the specific reason for the deletion, as well as your email.

2. Contact Technical Support:

   • If you are unsure why your server was deleted or need additional help, please contact our technical support team.

   • You can reach us through Contact and Help

   • We remind you that if your server has been deleted (Terminated), support cannot recover your data.

Our team is available to help you and ensure you have a satisfactory experience with our services.

Updating Email Adress

To update the email associated with your HidenCloud account, follow these steps:

1. Click on your profile picture in the HidenCloud portal and select [Account Settings].

2. Scroll down to [Update Email Address].

3. Enter your current password in [Current Password] and provide your new email in the [New Email Address] field.

Updating Password in the Billing Portal

To change your password for the Billing Portal:

1. Click on your profile picture in the HidenCloud portal and select [Account Settings].

2. Scroll down to [Update Password].

3. Enter your current password in [Current Password], and fill in the [New Password] and [Confirm Password] fields.

Contact and Support

If the issue persists after trying all the steps above, reach out to HidenCloud support:

2. • A detailed explanation of the issue.

   • Steps you’ve already attempted.

Our team will work with you to resolve the problem and restore your server as quickly as possible.

The Game Panel

After carefully following all the steps to create an account and acquire a server, you will have full access to a section that will keep all your properties readily available.

Using the Console

Once you access the created server, you will have complete control of the console screen, allowing you to manage everything using commands and interact with the buttons [Start], [Restart], [Stop], and [Kill].

Editing Server Settings

By going to [Settings] > [Startup Parameters] in the sidebar, you’ll find a section where you can modify some of the server's basic startup parameters, such as memory usage, Java version, etc. Each game has its own modifiable parameters.

Connect to Your Server

To access the server in-game, all you need to do is click in the top left corner where the host IP is located, copy it to the clipboard, and paste it into the multiplayer menu of the corresponding game.

How to Cancel a Service

1. Log in to HidenCloud and go to [Account], which will take you directly to the [Control Panel], where all your active servers are listed.

2. Select the active server whose service you wish to terminate.

3. Choose [Cancel] and accept all terms and conditions. The access period for the server will end with the current billing cycle.

FAQ

Contact and Support

If the issue persists after trying all the steps above, reach out to HidenCloud support:

2. • A detailed explanation of the issue.

   • Steps you’ve already attempted.

Our team will work with you to resolve the problem and restore your server as quickly as possible.

Changing Your Server's Location

Considerations Before Proceeding

1. Location Availability: Servers can only be relocated if the selected location is available.

2. IP Address and Port Change: When changing locations, your server's IP address and port will change. This change is irreversible.

3. Backups Not Migrated: Existing backups will not be transferred to the new location. Be sure to download and save your data before proceeding.

Steps to Request a Relocation

1. For Free Servers

   • Access the [Control Panel].

   • Select the free server.

   • Click [Cancel].

   • Wait for the service to be fully canceled, then request a new server, selecting a different location.

2. For Paid Servers

   • Include the following details in the ticket:

     • Server UUID.

     • Associated email.

     • New location.

   • Wait for the ticket approval and enjoy improved ping in the new location.

Free Subdomain (Free Service)

To create a subdomain, go to the HidenCloud panel, enter the server, go to the "Tools" section in the menu and then to "Subdomain Manager" there click the "Create" button and follow the steps.

Free Service Domains: hidenfree.com, hidengame.com, hidenmc.com, hidenhosting.com, hidenhosting.net

Premium Subdomain (Paid Service)

1. Then find your order / service

2. Click on Manage

3. Scroll down...

1. Enter the subdomain and domain you want and click update.

2. Please remember that you can update it at any time and that you cannot use an already used subdomain and domain.

Paid Service Domains: hidenfree.com, hidengame.com, hidenhosting.com, hidenhosting.net, hidenmc.com, hidenplay.net, hidenrp.com, hidenserver.com, servegame.net, servegame.pro, servemc.net, serveminecraft.com, serverrp.com

To access the server console and manage your server, follow these steps:

2. Once you've successfully logged in, you'll be taken to the dashboard or main page. On this page, you should see a list of the available servers associated with your account. Each server will likely be displayed with its name, status, and some basic information.

3. Identify the server you want to manage and select its name from the list. This action will take you to a more detailed view of the server, where you can access various settings and configurations.

4. Depending on the platform's layout and features, you may find a menu or sidebar with different sections or options related to server management. Look for the option that provides access to the server console.

5. Click on the server console option to access the command-line interface or other tools to interact directly with the server.

6. From the server console, you can execute commands, manage files, install software, and perform various administrative tasks.

Remember to be cautious while using the server console, as some operations can have significant consequences on the server's functionality and security. Always ensure that you have the necessary knowledge and authorization to perform the tasks you intend to carry out.

If you encounter any issues or need further assistance with server management, consult the platform's documentation or contact their support team.

Adding Sub-Users to the server

2. Navigate to Subusers In the sidebar, go to [Management] > [Subusers].

3. Create a New Sub-User

   • Click the [Create] button.

   • Enter the email address or username of the person you want to add.

   • Assign the desired permissions from the available list.

4. Save and Add the Sub-User

   • Click [Add New Subuser] to save the changes and add the person to your server.

5. User Activation

   • The added sub-user will receive an email with instructions to activate their account and gain access to your server.

Configurable Sub-User Permissions

• Support OP Access

• Control

• Subuser

• Allocation

• Startup Parameters

• Database

• File Manager

• Schedule

• Backup

• Details

• Audit Log

• Modpack Manager

• Plugin Manager

• Health Monitor

• Reinstall

• Subdomain Manager

Creating Your Databases

2. Navigate to the Databases Section Go to [Management] > [Databases] in the sidebar.de bases de datos mediante [Management] > [Databases].

3. Create a New Database

   • Host: Select a host close to your location or your main server to minimize latency.

   • Name: Specify a unique name for your database.

   • Connections From: This field is set to % by default to allow connections from any IP address. You can restrict access to specific IP addresses if preferred.

4. Configure Your Application or Service Update your application to connect to the newly created database.

Resetting a Database Password

If you need to reset a database password, follow these steps:

2. Navigate to the Databases Section Go to [Management] > [Databases].

3. Reset the Password

   • Locate the database you wish to reset the password for.

   • Select [Reset Password].

   • Update the configuration files of your applications or services using this database with the new password.

Using the JDBC Connection String

Java-based applications often require a JDBC connection string to interact with your MySQL database. HidenCloud provides this string, containing all necessary details for the connection.

2. Locate the JDBC Connection String

   • Navigate to [Management] > [Databases] in the sidebar.

   • Find your desired database, and the JDBC connection string will be available to copy and use in your application.

HidenCloud simplifies database management, enabling you to configure and maintain your infrastructure effortlessly. For further assistance, refer to the official documentation or contact HidenCloud's technical support team.

Creating a Backup

1. Navigate to [Management] > [Backups] in the sidebar.

2. Click [Create].

3. Provide a name for the backup and select [Submit].

Restoring a Backup

This option allows you to revert the server to the desired saved version.

1. Navigate to [Management] > [Backups] in the sidebar.

2. Click the [Deploy] button.

Downloading a Backup

1. Navigate to [Management] > [Backups] in the sidebar.

2. Click the [Deploy] button.

Locking a Backup

This feature prevents accidental deletion or modification of a backup you want to preserve.

1. Navigate to [Management] > [Backups] in the sidebar.

2. Click the [Deploy] button.

Creating Schedule Tasks

• Navigate to the Scheduling Section In the left sidebar, go to [Management] > [Schedules].

• Configure a New Task

  • Click the [Create Task] button and fill in the following fields:

    • Task Name: Specify a name to identify the action.

    • Frequency: Choose when and how often the task should run (e.g., hourly, daily, or on a custom schedule).

    • Command or Action: Define the command or action to execute, such as custom scripts, server restarts, or clearing temporary data.

    • Notifications: Enable notifications to receive alerts when the task completes or fails.

Edit or Delete Scheduled Tasks

2. Navigate to Scheduled Tasks Go to [Management] > [Schedules].

3. Locate the Task

   • To edit, click the [Edit] button, make the necessary changes, and save.

   • To delete, click the red trash icon and confirm the action.

View Tasks History

HidenCloud logs each execution of scheduled tasks, allowing you to monitor their performance and troubleshoot issues if necessary.

1. Access the Scheduled Tasks Section Go to [Management] > [Schedules].

2. View Execution Logs

   • The task list displays:

     • Date and Time of each execution.

     • Status (e.g., completed, failed).

     • Error Details, if applicable.

Uploading Files from the HidenCloud Panel

2. Navigate to the File Manager In the left sidebar menu, go to [Management] > [File Manager] to access the file manager.

3. Upload Files

   • Click the three dots at the top right and select [Upload].

   • Choose the desired files from your computer.

   • You can select multiple files if needed.

4. Organize Your Files Once uploaded, you can move, rename, or delete files as necessary. The file manager includes tools to efficiently organize your project.

Uploading Files via SFTP

1. Obtain Your SFTP Credentials

   1. In the panel, go to [System] > [SFTP Details].

   2. Copy the provided credentials:

      1. SFTP address

      2. Port (HidenCloud SFTP port is 2022)

      3. Username and password

2. Set Up the SFTP Client

   1. Download and install an SFTP client like FileZilla or WinSCP.

   2. Enter the credentials into the corresponding fields.

3. Connect and Upload Files

   1. Once connected, drag and drop files from your device to the server.

   2. Organize the files into the correct folders as needed for your project.

Editing and Managing Files

The HidenCloud file manager also includes tools for making changes directly to files:

• Integrated Text Editor: Allows you to edit configuration files like .json, .yml, or .php directly from the panel.

• File Permissions: Modify read, write, and execute permissions as needed for your project.

Errors:

1. “There was an exception while attempting to communicate with the daemon.”

2. “We’re having some trouble connecting to your server, please wait…”

3. “You do not have permission to access the websocket for this server.” (If you continue to see this error after five minutes, your server may be bugged, please contact support.)

Explanation:

These three errors all indicate the same issue: you cannot control the server from the panel at this moment. This typically occurs when the node is oversaturated. To prevent further saturation, control of the server from the panel is blocked.

Despite these errors, you can still use SFTP, and if the server was online, it will continue running normally. We recommend reloading the page later and trying again until the error disappears. If the error persists for a long time, please contact support.

To enable "Toggle Support OP," follow these simple steps:

1. Navigate to the "Configuration" section in your server's control panel.

2. Look for the "Advanced" category and click on it.

3. Inside the "Advanced" category, you will find the "Toggle Support OP" option.

4. Click the "Enable" button next to "Toggle Support OP."

Enabling "Toggle Support OP" will grant specific administrative privileges to support staff, allowing them to access and assist you with your server-related queries and issues. This feature is designed to streamline support processes and ensure a smoother and more efficient resolution of any server-related concerns. However, it's essential to exercise caution and only grant access to trusted support personnel to maintain the security and integrity of your server. By following these steps, you can seamlessly enable "Toggle Support OP" and receive the help you need to optimize your server's performance.

Introduction

When hosting a Minecraft server on HidenCloud, the platform automatically detects and uses the most suitable Java version for your server's Minecraft version. However, there may be situations where you need to change the Java version manually. This could be due to performance reasons, compatibility with specific mods or plugins, or personal preference.

This guide will walk you through the process of changing the Java version on your HidenCloud server.

Prerequisites

• Ensure you have access to your HidenCloud server's control panel.

• Familiarity with navigating through server files is advantageous.

Steps to Change Java Version

Initial Setup

1. Start Your Server: When you start your server for the first time, HidenCloud prompts you to select the Java version.

2. Select Java Version: Choose the desired Java version from the options provided. This selection will determine the Java version used by your server. For example if you want Java 16 you just need to enter the number 4 in the console.

Changing Java Version Post Setup

If you've already set up your server and wish to change the Java version, follow these steps:

1. Access Server Files: Log in to your HidenCloud server control panel.

2. Navigate to Server Files: Go to the directory where your server files are stored. Management -> File Manager.

3. Locate the disable_prompt_for_java_version File: This file is created after your initial Java version selection.

4. Delete the File: Remove the disable_prompt_for_java_version file from your server files. This action re-enables the Java version selection prompt.

Restart and Select New Java Version

1. Restart Your Server: After deleting the file, restart your server.

2. Select New Java Version: Upon restart, HidenCloud will prompt you to select the Java version again. Choose the new Java version you wish to use.

Important Notes

• Changing the Java version can affect your server's performance and compatibility with certain Minecraft versions, mods, or plugins.

• Ensure that the Java version you select is compatible with the version of Minecraft you are running.

• If you encounter issues after changing the Java version, consider reverting to the previously used version or consulting HidenCloud's support.

Conclusion

Changing the Java version on your HidenCloud server is a straightforward process. By following these steps, you can customize your server's Java environment to suit your specific needs or preferences.

Support

If you have any questions or encounter any issues, please contact HidenCloud support for assistance.

Recent Changes?

If you made a change just before the crashes began, try reverting that change to see if the problem persists.

Schedule Regular Restarts

If crashes happen occasionally (e.g., every few days), scheduling regular restarts may help.

2. Set up an automatic restart at intervals suited to your needs.

Why It Helps:

• Resolves memory leaks on long-running servers.

• Handles delayed actions on servers with many mods or players.

• Fixes errors in plugins for modded servers.

Update Your Server

Ensure that the game hosted on your server is up to date.

1. Check for updates on official platforms, such as the game developers’ Discord or HidenCloud community.

2. Restart your server to apply updates in most cases.

3. For specific games, HidenCloud provides detailed update guides.

Update Your Plugins

If your server uses plugins (e.g., for Minecraft, CS2, or other modded games), outdated plugins can cause crashes.

1. Identify the plugins installed on your server.

2. Download the latest version of each plugin from its official source.

3. Replace old files with the updated versions and restart your server.

Contact and Support

If the issue persists after trying all the steps above, reach out to HidenCloud support:

2. • A detailed explanation of the issue.

   • Steps you’ve already attempted.

Our team will work with you to resolve the problem and restore your server as quickly as possible.

With these solutions, you should be able to address most server crash issues. If you have further questions or need advanced support, remember that we’re here to help!

To find the uuid of the server simply go to the system part, then server details and then you will find the UUID.

Find the server uuid next to the name.

Find the UUID of the server in the url or link: https://panel.hidencloud.com/server/<uuid>

Experiencing high ping and packet loss can be frustrating, but understanding the causes and solutions will help you restore a smooth experience. This guide explains how to identify and effectively resolve these issues with HidenCloud.

What Is Ping?

Ping measures the time it takes for your device to send a packet of data to a server and receive a response, measured in milliseconds (ms).

• Acceptable ping: Below 100 ms.

• Ideal ping: Below 70 ms.

• Excellent ping: Below 50 ms.

Key Factors:

• The primary factors affecting ping are the distance between the server and the player and the network routes used.

• Internet speed does not directly impact ping.

What Is Packet Loss?

Packet loss occurs when data sent from your device fails to reach the server, leading to issues like rubber banding (erratic in-game movements).

Common Causes:

• Congestion at your Internet Service Provider (ISP).

• Network routing issues.

• Incorrect server configurations, especially when advanced parameters have been modified.

How to Resolve High Ping and Packet Loss

• Common Causes:

  • Routing problems specific to your ISP.

  • Significant distance between the player and the server.

  Quick Solutions:

  1. Use a VPN or a free tool like Cloudflare Warp. These can improve routing and reduce ping instantly.

  2. MTR Report: If the issue persists, affected players can submit an MTR report to help us diagnose the problem:

     • Download WinMTR.

     • Enter the server IP and click Start.

     • Run the test for a few minutes, then click Stop and save the report in .TXT format.

     • Submit the report as a support ticket in HidenCloud.

  The report helps us work with our network providers to analyze the issue. While a definitive solution isn’t guaranteed, we’ll investigate thoroughly.

When All Players Occasionally Experience Issues:

Possible Causes:

• Updates or backups being installed on shared servers.

• Mitigation of a DDoS attack.

Recommended Actions:

• These interruptions are usually temporary and resolve automatically.

• If problems persist for an extended period, contact our support team.

Contact and Support

If high ping or packet loss consistently affects all server players, reach out to our support team:

How to Allow Players to Join Your Minecraft Server from Any Version

At times, you or your players might wish to establish a connection to your server using varying Minecraft versions. Achieving this is feasible through a plugin known as ViaVersion, enabling players to link up with the server using different versions.

Which plugins do you need?

Depending on the server and client versions you wish to support, you may need to install one, two, or all three Via Plugins. The chart below shows version compatibility if ViaVersion is installed.

2. Log in with your account, if it is the first time you will have the username and password in the email or on the dashboard.

3. Select the server you want to change the version or type of Minecraft game on.

4. Now go to configuration and then to advanced parameters.

5. Then where it says "Install Different Edition" select the edition (type) and the version you want to install.

6. Activate "Format" in case you want to delete all the old files and make a new installation and then click on Install. This process can take several seconds.

Adding an Unlisted Launcher/Version/Type

If you need to install a launcher/version/type that is not listed by HidenCloud, follow these steps:

Launcher Download:

• Go to the official website of the launcher you wish to install. For example, if you want to install Magma, visit their site and download the version you prefer.

Uploading the .jar File:

• Upload the downloaded .jar file to your server on HidenCloud. It is recommended to delete all existing files to avoid compatibility issues.

Renaming the File:

• Once the file is uploaded, change its name to "server.jar". This will ensure that HidenCloud recognizes the file as the main launcher.

• If you prefer not to change the name of the file, you can specify the new name (for example, "magma.jar") in the server's startup parameters.

These steps will allow you to use any launcher, even if it is not directly listed on the HidenCloud panel, providing you with the flexibility to customize your Minecraft server according to your specific preferences and needs.

Forge Installation Video

Tutorial: Installing a Plugin / Mod on a Minecraft Server

Prerequisites:

• Access to the Minecraft server you wish to configure.

Step 1: Log in to the Control Panel

2. Enter your login credentials (username and password) in the corresponding fields.

3. Click the "Log In" button to access the control panel.

Step 2: Accessing Server Files

1. Once logged in, you'll be directed to the control panel.

2. In the main menu, look for and select the Minecraft server you wish to configure.

3. Within the server's control panel, find the "Management" or "Administration" section.

4. Within this section, select the "File Manager" option.

Step 3: Installing the Plugin

1. Once in the "File Manager", you'll see a list of all files belonging to the Minecraft server.

2. Locate and enter the directory or folder where plugins are stored. This directory is usually named "plugins" or "plugins".

3. Within the plugins folder, click on the "Upload" or "Upload files" button.

4. Select the plugin file you wish to install from your local computer.

5. Once the file has been successfully uploaded, you'll see the plugin in the list of files within the plugins folder.

Step 4: Restarting the Server

1. After uploading the plugin file, return to the main control panel of the server.

2. Look for the option to restart the server. This may be labeled as "Restart", "Stop" and then "Start", or something similar.

3. Confirm that you wish to restart the server.

4. Once the server has restarted successfully, the plugin will be installed and ready to use.

That's it! You've successfully installed a plugin on your Minecraft server using the control panel provided by HidenCloud. You can now configure and manage the plugin as needed to enhance the security and gaming experience on your server.

2. Access the server: Select your Minecraft server.

3. File Manager: Within the server management, look for the "Management" category and within it, find the "File Manager" option. This tool will allow you to access all server files, including configuration files.

4. Locate the configuration file: Once inside the file manager, search for the Minecraft server configuration file. This file is usually named "server.properties".

5. Edit the server.properties file: Right-click on the "server.properties" file and select the option to edit it. This will open the file in a text editor within the control panel.

6. Find the online mode setting: Within the "server.properties" file, look for the line that says online-mode=true. This line determines whether the server requires premium authentication or not. If you want to disable online mode, change true to false. If you want to enable online mode, make sure it is set to true.

7. Save the changes: Once you have made the modification, save the changes to the "server.properties" file.

8. Restart the server: To apply the changes, it will be necessary to restart the Minecraft server. You can do this from the HidenCloud control panel by searching for the option to restart the server.

9. Verify the configuration: After restarting the server, make sure to verify that the online mode is configured according to your preferences by reviewing the "server.properties" file again.

If you prefer to use FTP configuration, the steps would be similar, but instead of accessing the file through the control panel, you would use an FTP client to connect to the server and edit the "server.properties" file directly from your computer. In both cases, it is important to be careful when editing configuration files to avoid issues with server operation.

2. Log in with your account, if it is the first time you will have the username and password in the email or on the dashboard.

3. Select the server you want to change the version or type of Minecraft game on.

4. Now go to configuration and then to startup parameters.

5. Here you can edit all the parameters available for your server.

6. For the Java flags, we recommend not touching them if you do not know what is happening since it can affect the performance of the server, we recommend reading the following part to obtain more knowledge about JVM Startup Flags.

Recommended JVM Startup Flags

Use these flags exactly, only changing Xmx and Xms. These flags work and scale accordingly to any size of memory, even 500MB but modern Minecraft versions will not do well with such low memory.

Recommended Memory

We recommend using at least 6-10GB, no matter how few players! If you can't afford 10GB of memory, give as much as you can, but ensure you leave the operating system some memory too. G1GC operates better with more memory.

However, more memory does not mean better performance above a certain point. Eventually you will hit a point of diminishing returns. Going out and getting 32GB of RAM for a server will only waste your money with minimal returns.

If you are running with 12GB or less memory for MC, you should not adjust these parameters.

If you are using an Xmx value greater than 12G

If you have and use more than 12GB of memory, adjust the following:

• -XX:G1NewSizePercent=40

• -XX:G1MaxNewSizePercent=50

• -XX:G1HeapRegionSize=16M

• -XX:G1ReservePercent=15

• -XX:InitiatingHeapOccupancyPercent=20

Explanation of these changes:

• Base flag set aims for 30/40 to reduce risk of to space issues. With more memory, less of an issue. We can give more to new generation with 40/50, as well as reduce reserve percent since the default reserve will already be larger.

• Region Size increase helps reduce humongous allocations, and speeds up remarking. We need a smaller region size at smaller heaps to ensure an adequate amount of regions available

• We can start looking for old generation memory to reclaim with more of a delay with IHOP at 20 since we have more old generation available to space on CPU.

Java GC Logging

Are you having old gen issues with these flags? Add the following flags based on your java version to enable GC Logging:

Java 8-10

Java 11+

GC logging does not hurt your performance and can be left on at all times. The files will not take up much space (5MB)

Technical Explanation of the Flags

1. -Xms matching -Xmx -- Why: You should never run your server with the case that -Xmx can run the system completely out of memory. Your server should always be expected to use the entire -Xmx! You should then ensure the OS has extra memory on top of that Xmx for non MC/OS level things. Therefore, you should never run MC with -Xmx settings you can't support if java uses it all. Now, that means if -Xms is lower than -Xmx YOU HAVE UNUSED MEMORY! Unused memory is wasted memory. G1 operates better with the more memory it's given. G1 adaptively chooses how much memory to give to each region to optimize pause time. If you have more memory than it needs to reach an optimal pause time, G1 will simply push that extra into the old generation, and it will not hurt you The fundamental idea of improving GC behavior is to ensure short-lived objects die young and never get promoted. With the more memory G1 has, the better assurance you will get that objects are not getting prematurely promoted to the old generation. G1 Operates differently than previous collectors and is able to handle larger heaps more efficiently.

   If it does not need the memory given to it, it will not use it. The entire engine operates differently and does not suffer from too large of heaps, and this is industry-wide accepted information that under G1 to keep Xms and Xmx the same!

2. UnlockExperimentalVMOptions -- needed for some the below options

3. G1NewSizePercent: These are the important ones. You now can specify percentages of an overall desired range for the new generation. With these settings, we tell G1 to not use its default 5% for new gen, and instead give it 40%! Minecraft has an extremely high a memory allocation rate, ranging to at least 800 Megabytes a second on a 30 player server! And this is mostly short-lived objects (Block Position).

   Now, this means MC REALLY needs more focus on New Generation to be able to even support this allocation rate. If your new gen is too small, you will be running new gen collections 1-2+ times per second, which is awful. You will have so many pauses that TPS has risk of suffering, and the server will not be able to keep up with the cost of GC's. Then combine the fact that objects will now promote faster, resulting in your Old Gen growing faster. Given more New Gen, we are able to slow down the intervals of Young Gen collections, resulting in more time for short-lived objects to die young and overall more efficient GC behavior.

4. G1MixedGCLiveThresholdPercent: Controls when to include regions in Mixed GC's in the Young GC collection, keeping Old Gen tidy without doing a normal Old Gen GC collection. When your memory is less than this percent, old gen won't even be included in 'mixed' collections. Mixed are not as heavy as a full old collection, so having small incremental cleanups of old keeps memory usage light.

   Default is 65 to 85 depending on Java Version, we are setting to 90 to ensure we reclaim garbage in old gen as fast as possible to retain as much free regions as we can.

5. G1ReservePercent=20: MC Memory allocation rate in up-to-date versions is really insane. We run the risk of a dreaded "to-space exhaustion" not having enough memory free to move data around. This ensures more memory is waiting to be used for this operation. Default is 10, so we are giving another 10 to it.

6. MaxTenuringThreshold=1: Minecraft has a really high allocation rate of memory. Of that memory, most is reclaimed in the eden generation. However, transient data will overflow into survivor. Initially played with completely removing Survivor and had decent results, but does result in transient data making its way to Old which is not good.Max Tenuring 1 ensures that we do not promote transient data to old generation, but anything that survives 2 passes of Garbage Collection is just going to be assumed as longer-lived.

   Doing this greatly reduces pause times in Young Collections as copying data up to 15 times in Survivor space for a tenured object really takes a lot of time for actually old memory. Ideally the GC engine would track average age for objects instead and tenure out data faster, but that is not how it works.

   Considering average GC rate is 10s to the upwards of minutes per young collection, this does not result in any 'garbage' being promoted, and just delays longer lived memory to be collected in Mixed GC's.

7. SurvivorRatio=32: Because we drastically reduced MaxTenuringThreshold, we will be reducing use of survivor space drastically. This frees up more regions to be used by Eden instead.

8. AlwaysPreTouch: AlwaysPreTouch gets the memory setup and reserved at process start ensuring it is contiguous, improving the efficiency of it more. This improves the operating systems memory access speed. Mandatory to use Transparent Huge Pages

9. +DisableExplicitGC: Many plugins think they know how to control memory, and try to invoke garbage collection. Plugins that do this trigger a full garbage collection, triggering a massive lag spike. This flag disables plugins from trying to do this, protecting you from their bad code.

10. MaxGCPauseMillis=200: This setting controls how much memory is used in between the Minimum and Maximum ranges specified for your New Generation. This is a "goal" for how long you want your server to pause for collections. 200 is aiming for at most loss of 4 ticks. This will result in a short TPS drop, however the server can make up for this drop instantly, meaning it will have no meaningful impact to your TPS. 200ms is lower than players can recognize. In testing, having this value constrained to an even lower number results in G1 not recollecting memory fast enough and potentially running out of old gen triggering a Full collection. Just because this number is 200 does not mean every collection will be 200. It means it can use up to 200 if it really needs it, and we need to let it do its job when there is memory to collect.

11. +ParallelRefProcEnabled: Optimizes the GC process to use multiple threads for weak reference checking. Not sure why this isn't default...

12. G1RSetUpdatingPauseTimePercent=5: Default is 10% of time spent during pause updating Rsets, reduce this to 5% to make more of it concurrent to reduce pause durations.

13. G1MixedGCCountTarget=4: Default is 8. Because we are aiming to collect slower, with less old gen usage, try to reclaim old gen memory faster to avoid running out of old.

14. G1HeapRegionSize=8M+: Default is auto calculated. SUPER important for Minecraft, especially 1.15, as with low memory situations, the default calculation will in most times be too low. Any memory allocation half of this size (4MB) will be treated as "Humongous" and promote straight to old generation and is harder to free. If you allow java to use the default, you will be destroyed with a significant chunk of your memory getting treated as Humongous.

Using Large Pages

For Large Pages -- It's even more important to use -Xms = -Xmx! Large Pages needs to have all the memory specified for it, or you could end up without the gains. This memory will not be used by the OS anyway, so use it.

Additionally, use these flags (Metaspace is Java 8 Only, don't use it for Java7): -XX:+UseLargePagesInMetaspace

Transparent Huge Pages

Controversial feature but may be usable if you can not configure your host for real HugeTLBFS. Try adding -XX:+UseTransparentHugePages but it's extremely important you also have AlwaysPreTouch set. Otherwise, THP will likely hurt you. We have not measured how THP works for MC or its impact with AlwaysPreTouch, so this section is for the advanced users who want to experiment.

Understanding the Issue: Out of Memory Error and Server Restarts

At HidenCloud, we prioritize the smooth operation and reliability of your server. However, you may occasionally encounter server restarts due to an "Out of Memory" (OOM) error. This is commonly related to the way Java, the programming language used by many applications including Minecraft, manages memory.

The OOM Killer

A critical system component to understand is the OOM Killer. This is a mechanism in the Linux operating system, which HidenCloud servers utilize, designed to handle low memory situations. When your server consumes all available memory, the OOM Killer is triggered to free up resources. It does this by terminating processes, which can unfortunately include your server, leading to restarts.

Adjusting Memory Settings to Prevent OOM

To mitigate this issue, it’s essential to configure your server's memory settings correctly. Java, by default, can use all available memory, which might trigger the OOM Killer. You can adjust these settings through two key parameters:

• Xms (Initial Memory Allocation): This setting determines the initial amount of memory Java allocates on startup. (You can't modify this)

• Xmx (Maximum Memory Allocation): This is the maximum amount of memory Java is allowed to use. (You can modify this)

You can modify the server RAM (Xmx) through: Server -> Configuration -> Startup Parameters -> SERVER_MAC_RAM Variable.

SERVER_MAX_RAM Variable

The SERVER_MAX_RAM parameter in HidenCloud controls the maximum RAM allocated to Java servers, impacting the Garbage Collector (GC) performance. By default, it is set to "total server RAM - 512MB" to reserve some memory for system processes. Setting this value too high can lead to longer GC pauses, while too low can cause more frequent GC runs, both affecting performance. It should not exceed the RAM allocated to your server, as this may trigger the OOM Killer and stop the server.

To set this variable, YOU MUST FOLLOW THE FOLLOWING SCHEME: -Xmx{RAM_in_megabytes}M. For example: -Xmx2048M.

Recommended Configuration

When configuring these settings, it's crucial to allocate less memory than the total available on your server. For example, if your server has 8000M of memory:

• Do Not Allocate the Full 8000M to Java: This leaves no memory for other essential system processes, risking an OOM situation.

• Allocate Around 6500M for Java: This creates a buffer of approximately 1500M, ensuring there is memory available for the operating system and other processes.

This configuration helps in preventing the server from using all available RAM, reducing the likelihood of the OOM Killer being activated.

If the Issue Persists

If your server continues to experience restarts due to memory issues:

• Consider upgrading your plan to one that has more ram.

• Disabling the OOM Killer: As a last resort, HidenCloud support can disable the OOM Killer for your server. However, this is generally not recommended as it can lead to system instability.

Final Recommendations

• Regularly monitor your server’s memory usage.

• Consult with HidenCloud support for optimal memory settings.

• Consider upgrading your server plan if memory issues persist.

By following these guidelines and adjusting your server’s memory settings, you can significantly reduce the occurrence of "Out of Memory" errors and server restarts, ensuring a smoother and more reliable experience on HidenCloud.

Note for users that are on vanilla, Fabric or Spigot (or anything below Paper) - go to your server.properties and change sync-chunk-writes to false. This option is forcibly set to false on Paper and its forks, but on other server implementations you need to switch this to false manually. This allows the server to save chunks off the main thread, lessening the load on the main tick loop.

Intro

There will never be a guide that will give you perfect results. Each server has their own needs and limits on how much you can or are willing to sacrifice. Tinkering around with the options to fine tune them to your servers needs is what it's all about. This guide only aims to help you understand what options have impact on performance and what exactly they change. If you think you found inaccurate information within this guide, you're free to open an issue or set up a pull request to correct it.

Preparations

Server JAR

Your choice of server software can make a huge difference in performance and API possibilities. There are currently multiple viable popular server JARs, but there are also a few that you should stay away from for various reasons.

Recommended top picks:

You should stay away from:

• Any paid server JAR that claims async anything - 99.99% chance of being a scam.

• Bukkit/CraftBukkit/Spigot - Extremely outdated in terms of performance compared to other server software you have access to.

• Many forks further downstream from Pufferfish or Purpur will encounter instability and other issues. If you're seeking more performance gains, optimize your server or invest in a personal private fork.

1. LuckPerms: This plugin is an excellent permission management tool. It allows assigning specific permissions to players and groups of players, helping to control who can access certain features and commands on the server.
2. WorldGuard: WorldGuard provides world-level protection, meaning you can define regions and set specific permissions within those regions. This is useful for safeguarding important areas like player bases or key structures against damage or unwanted alterations.
3. CoreProtect: This plugin tracks all actions performed on the server, such as placing or breaking blocks, and provides tools to undo unauthorized changes. It's an invaluable tool for investigating cheating or vandalism incidents.
4. AntiCheat: Anti-cheat plugins like AntiCheat help detect and prevent players from using cheats or hacks. These plugins typically include a variety of automatic detections for things like illegal flying, increased speed, and unfair combat.
5. LoginSecurity: To protect player accounts, a plugin like LoginSecurity can be useful. It adds additional security measures to the login process, such as secure passwords and two-factor authentication, to prevent accounts from being compromised.

Chunky Plugin: Pre-generating your world

spark will load the next time your server (re)starts.

INTRODUCTION

What is BungeeCord?

BungeeCord is a server type for Minecraft that allows you to connect several servers together, so players can transfer between them without having to disconnect from the server.

BungeeCord is not a plugin

Users that are new to BungeeCord commonly assume that BungeeCord is a plugin for Spigot or Craftbukkit. This is not the case. Instead, BungeeCord is a server type, in the same way Spigot and Craftbukkit are.

BungeeCord cannot run Spigot or Craftbukkit plugins

Although it is developed and maintained by the Spigot team, BungeeCord is not Minecraft software and does not share any of the Spigot or Craftbukkit code. This means Spigot plugins are not compatible with BungeeCord. BungeeCord does support plugins, however only plugins that have been specifically developed for BungeeCord are compatible with BungeeCord.

BungeeCord cannot run worlds, players, etc

Since BungeeCord is not Minecraft software and does not run any of the Minecraft code, worlds and players cannot actually exist on a BungeeCord instance. BungeeCord is not a Minecraft server — rather, it is a proxy that simply bridges the connection between the player and server. It pretends to be a Minecraft server, but it isn’t. It’s only purpose is to forward you to one of the Minecraft servers under the network — if no servers are connected to the BungeeCord instance, the player will simply be disconnected upon joining as there is no Minecraft server under the network for them to actually play on.

BungeeCord requires a minimum of 3 servers

Your BungeeCord network will need a server for each of the servers you wish to run, plus an additional server to run BungeeCord.

The minimum requirements for a BungeeCord setup is as follows:

• Two Minecraft servers that you wish to connect together (typically running Spigot).

• An additional Minecraft server to run the BungeeCord Software.

BungeeCord cannot be used as a Hub or Lobby server — you would need an additional server, running Minecraft software (Spigot) to do this.

anti-xray.enabled

Good starting value: true

nether-ceiling-void-damage-height

Good starting value: 127

If this option is greater that 0, players above the set y level will be damaged as if they were in the void. This will prevent players from using the nether roof. Vanilla nether is 128 blocks tall, so you should probably set it to 127. If you modify the height of the nether in any way you should set this to [your_nether_height] - 1.

In addition, adding the beta flag --add-modules=jdk.incubator.vector before -jar in your startup flags can improve performance. This flag enables Pufferfish to use SIMD instructions on your CPU, making some maths faster. Currently, it's only used for making rendering in game plugin maps (like imageonmaps) possibly 8 times faster.

"Too good to be true" plugins

Plugins removing ground items

Mob stacker plugins

It's really hard to justify using one. Stacking naturally spawned entities causes more lag than not stacking them at all due to the server constantly trying to spawn more mobs. The only "acceptable" use case is for spawners on servers with a large amount of spawners.

Plugins enabling/disabling other plugins

What's lagging? - measuring performance

mspt

Paper offers a /mspt command that will tell you how much time the server took to calculate recent ticks. If the first and second value you see are lower than 50, then congratulations! Your server is not lagging! If the third value is over 50 then it means there was at least 1 tick that took longer. That's completely normal and happens from time to time, so don't panic.

Spark

Timings

Way to see what might be going on when your server is lagging are Timings. Timings is a tool that lets you see exactly what tasks are taking the longest. It's the most basic troubleshooting tool and if you ask for help regarding lag you will most likely be asked for your Timings. Timings is known to have a serious performance impact on servers, it's recommended to use the Spark plugin over Timings and use Purpur or Pufferfish to disable Timings all together.

Preface

The most important thing

Keep up to date on your server software. There are exploits that are fixed in newer versions of the software, even if it's not announced. If you are running a server, you should be running the latest version possible to avoid critical vulnerabilities.

Exploits

Armor stand lag machines

Armor stands can be used to create lag machines. This is done by placing huge amounts of armor stands and forcing them to move via water, pistons or other means. This can be fixed by disabling armor stand tick and collision lookups. This will cause armor stands to not being able to be pushed or pulled (even by gravity).

paper-world-defaults.yml

entities:
  armor-stands:
    do-collision-entity-lookups: false
    tick: false

Book exploits

Books are a common target for exploitation techniques, and have been used for all sorts of nasty things in the past including duplication exploits, crash exploits, and forcing servers to run out of memory while producing massive amounts of chunk data.

Option 1

Moderately reducing page-max can mitigate most book exploits without affecting vanilla clients.

paper-global.yml

item-validation:
  book-size:
    page-max: 1024

Option 2

Disabling books completely prevents the most book exploits (as long as plugins don't create non-standard books). Pufferfish config option prevents players from writing to the book, therefore ruling out anything that requires player input to work.

pufferfish.yml

enable-books: false

Collision lag machines

This exploit is similar to the armor stand one, but instead of armor stands, it uses entities that can be pushed by other entities. This can be fixed by setting a smaller limit on how many entities can collide with a singular entity. You can set the max-entity-collisions to 2 to still have relatively natural behavior, or set it to 0 to completely disable collisions. The option to fix climbing bypassing cramming rule is also available, but it's disabled by default.

paper-world-defaults.yml

collisions:
  max-entity-collisions: 2
  fix-climbing-bypassing-cramming-rule: true

Command suggestion packet spam

Some commands on the server might have a lot of logic involved with their command suggestions. This can be exploited by sending a lot of packets that request the server to send suggestions for the command. This can be mitigated by setting packet limit for command suggestions that is just slightly above fast rate of typing commands, so normal players won't be affected.

paper-global.yml

packet-limiter:
  overrides:
    ServerboundCommandSuggestionPacket:
      action: DROP
      interval: 1.0
      max-packet-rate: 15.0

Command spam

While even spigot will protect you from this exploit, there's a slight oversight that will enable a single command to be usable to perform this one. To fix this, simply remove /skill command from the spam exclusions list in spigot.yml.

spigot.yml

commands:
  spam-exclusions: []

Join spam

Sometimes shear quantity of players joining the server can cause the server to lag out. This is especially true for bot attacks and moments after server restart. This can be fixed by setting max joins per tick. Players joining will be delayed in time so server can properly tick between handling them. If joins still overwhelm the server, you can also enable max-joins-per-second in purpur.yml that will make it so value from paper config will be applied per second instead of per tick.

paper-global.yml

misc:
  max-joins-per-tick: 3

purpur.yml

settings:
  network:
    max-joins-per-second: true

Neighbor update lag machines

Limiting the amount of consecutive neighbor updates before skipping additional ones. Moderately reducing this value has no game impact and helps alleviate various 'neighbor update lag machines'.

server.properties

max-chained-neighbor-updates=10000

Projectile suspension

Projectiles can be suspended in bubble columns indefinitely. They can also be transported into unloaded chunks in mass. If anyone loads the chunk with amassed projectiles, server can crash due to loading too many things at once. This can be stopped by limiting how much time projectiles can exist in the world and how many of them are saved and loaded with a chunk. If the timeout is applied to ender pearls, it will prevent usage of ender pearl suspension contraption.

paper-world-defaults.yml

chunks:
  entity-per-chunk-save-limit:
    arrow: 8
    ender_pearl: 8
    experience_orb: 8
    fireball: 8
    small_fireball: 8
    snowball: 8

pufferfish.yml

entity_timeouts:
  ARROW: 200
  EGG: 200
  ENDER_PEARL: 200
  SNOWBALL: 200

Recipe book spam

Malicious players can use auto clicker or a mod to switch between recipe book recipes extremely quickly. This is pretty expensive operation for the server and can cause huge slowdowns. This is actually fixed in default paper config, but older configs might not have it added, so make sure it's there.

paper-global.yml

packet-limiter:
  overrides:
    ServerboundPlaceRecipePacket:
      action: DROP
      interval: 4.0
      max-packet-rate: 5.0

Treasure search

When new treasure map is generated, usually via cartographer villager or opening a chest with treasure map in it, the server searches for the treasure that map should lead to. This search is done in a way that in most cases causes a lot of chunks loading and possibly generating them. This search can halt the server for long enough that watchdog process kills it. It can also be triggered by feeding dolphins fish.

Option 1

To fix this one you basically have to disable treasure maps and dolphins searching for treasure. This is the recommended and 100% effective solution.

paper-world-defaults.yml

environment:
  treasure-maps:
    enabled: false

purpur.yml

world-settings:
  default:
    mobs:
      dolphin:
        disable-treasure-searching: true

Option 2

Alternatively, you can keep the maps enabled, but set up vanilla world border and make sure your world is pregenerated within the border. Then you can just make sure that already discovered treasures are valid as the search result. This will prevent the treasure search from loading chunks that are not generated.

paper-world-defaults.yml

  treasure-maps:
    find-already-discovered:
      loot-tables: true
      villager-trade: true

Managing server performance and security requires careful consideration of various exploits and mechanisms that can impact gameplay and stability. From managing entity interactions to controlling chunk loading during treasure hunts, administrators must implement strategic configurations and updates.

Ensuring that server configurations, such as disabling treasure map searches or limiting entity interactions, align with performance goals can mitigate potential slowdowns or crashes caused by intensive operations. Additionally, keeping server software updated with the latest patches and configurations is crucial to safeguard against new exploits and vulnerabilities.

By balancing functionality with performance optimizations, server administrators can provide a stable and enjoyable experience for players while maintaining security and preventing disruptive gameplay issues.

The server icon is the image that will appear next to your server’s name in the server list.

Steps:

1. Create the Icon:

   • Create or find an image you want to use as the server icon.

   • The image must be exactly 64x64 pixels in size.

   • The image must be in PNG format (filename.png).

2. Rename the Image:

   • Rename the image to server-icon.png. The name must be exactly like this.

3. Move the Image to the Server Directory:

   • Place the server-icon.png file in the root directory of your Minecraft server. This is the same directory where the server.properties file is located.

4. Restart the Server:

   • Restart your Minecraft server for the icon to update and appear in the server list.

GameUserSettings.ini Resetting on Server Restart

GameUserSettings.ini is one of the primary files for making configuration changes to an ARK:Survival Evolved servers. If your GameUserSettings.ini file is resetting on server restart, this usually means there is an error in the file. This is often due to either a syntax error, or required settings missing from the file.

Before making any modifications to this file, please create a backup of it so you can restore it in case the file is reset again.

Below we have included which settings you will want to change to get the best performance possible with minimal effect on your gameplay.

To use these settings, stop your server from your control panel then click on the tabs below to show the optimized settings for each file. These files can be found in the File Manager tab on your Control Panel. However, the paper files are located in the “config” directory. You can open them in the online web editor by clicking on the “edit” button to the far right of the file. Once you are done editing be sure to click the green “Save” button, then restart the server for the changes to take effect.

use-alternate-keepalive

Good starting value: true

simulation-distance

Good starting value: 4

Simulation distance is distance in chunks around the player that the server will tick. Essentially the distance from the player that things will happen. This includes furnaces smelting, crops and saplings growing, etc. This is an option you want to purposefully set low, somewhere around 3 or 4, because of the existence of view-distance. This allows to load more chunks without ticking them. This effectively allows players to see further without the same performance impact.

view-distance

Good starting value: 7

This is the distance in chunks that will be sent to players, similar to no-tick-view-distance from paper.

The total view distance will be equal to the greatest value between simulation-distance and view-distance. For example, if the simulation distance is set to 4, and the view distance is 12, the total distance sent to the client will be 12 chunks.

view-distance

Good starting value: default

This value overwrites server.properties one if not set to default. You should keep it default to have both simulation and view distance in one place for easier management.

delay-chunk-unloads-by

Good starting value: 10s

This option allows you to configure how long chunks will stay loaded after a player leaves. This helps to not constantly load and unload the same chunks when a player moves back and forth. Too high values can result in way too many chunks being loaded at once. In areas that are frequently teleported to and loaded, consider keeping the area permanently loaded. This will be lighter for your server than constantly loading and unloading chunks.

max-auto-save-chunks-per-tick

Good starting value: 8

Lets you slow down incremental world saving by spreading the task over time even more for better average performance. You might want to set this higher than 8 with more than 20-30 players. If incremental save can't finish in time then bukkit will automatically save leftover chunks at once and begin the process again.

prevent-moving-into-unloaded-chunks

Good starting value: true

When enabled, prevents players from moving into unloaded chunks and causing sync loads that bog down the main thread causing lag. The probability of a player stumbling into an unloaded chunk is higher the lower your view-distance is. entity-per-chunk-save-limit

Good starting values:

    area_effect_cloud: 8
    arrow: 16
    dragon_fireball: 3
    egg: 8
    ender_pearl: 8
    experience_bottle: 3
    experience_orb: 16
    eye_of_ender: 8
    fireball: 8
    firework_rocket: 8
    llama_spit: 3
    potion: 8
    shulker_bullet: 8
    small_fireball: 8
    snowball: 8
    spectral_arrow: 16
    trident: 16
    wither_skull: 4

With the help of this entry you can set limits to how many entities of specified type can be saved. You should provide a limit for each projectile at least to avoid issues with massive amounts of projectiles being saved and your server crashing on loading that. You can put any entity id here, see the minecraft wiki to find IDs of entities. Please adjust the limit to your liking. Suggested value for all projectiles is around 10. You can also add other entities by their type names to that list. This config option is not designed to prevent players from making large mob farms.

max-loads-per-projectile

Good starting value: 8

spawn-limits

Good starting values:

    monsters: 20
    animals: 5
    water-animals: 2
    water-ambient: 2
    water-underground-creature: 3
    axolotls: 3
    ambient: 1

ticks-per

Good starting values:

    monster-spawns: 10
    animal-spawns: 400
    water-spawns: 400
    water-ambient-spawns: 400
    water-underground-creature-spawns: 400
    axolotl-spawns: 400
    ambient-spawns: 400

This option sets how often (in ticks) the server attempts to spawn certain living entities. Water/ambient mobs do not need to spawn each tick as they don't usually get killed that quickly. As for monsters: Slightly increasing the time between spawns should not impact spawn rates even in mob farms. In most cases all of the values under this option should be higher than 1. Setting this higher also allows your server to better cope with areas where mob spawning is disabled.

mob-spawn-range

Good starting value: 3

entity-activation-range

Good starting values:

      animals: 16
      monsters: 24
      raiders: 48
      misc: 8
      water: 8
      villagers: 16
      flying-monsters: 48

You can set what distance from the player an entity should be for it to tick (do stuff). Reducing those values helps performance, but may result in irresponsive mobs until the player gets really close to them. Lowering this too far can break certain mob farms; iron farms being the most common victim.

entity-tracking-range

Good starting values:

      players: 48
      animals: 48
      monsters: 48
      misc: 32
      other: 64

This is distance in blocks from which entities will be visible. They just won't be sent to players. If set too low this can cause mobs to seem to appear out of nowhere near a player. In the majority of cases this should be higher than your entity-activation-range.

tick-inactive-villagers

Good starting value: false

This allows you to control whether villagers should be ticked outside of the activation range. This will make villagers proceed as normal and ignore the activation range. Disabling this will help performance, but might be confusing for players in certain situations. This may cause issues with iron farms and trade restocking.

nerf-spawner-mobs

Good starting value: true

despawn-ranges

Good starting values:

      ambient:
        hard: 72
        soft: 30
      axolotls:
        hard: 72
        soft: 30
      creature:
        hard: 72
        soft: 30
      misc:
        hard: 72
        soft: 30
      monster:
        hard: 72
        soft: 30
      underground_water_creature:
        hard: 72
        soft: 30
      water_ambient:
        hard: 72
        soft: 30
      water_creature:
        hard: 72
        soft: 30

per-player-mob-spawns

Good starting value: true

This option decides if mob spawns should account for how many mobs are around target player already. You can bypass a lot of issues regarding mob spawns being inconsistent due to players creating farms that take up the entire mobcap. This will enable a more singleplayer-like spawning experience, allowing you to set lower spawn-limits. Enabling this does come with a very slight performance impact, however it's impact is overshadowed by the improvements in spawn-limits it allows.

max-entity-collisions

Good starting value: 2

update-pathfinding-on-block-update

Good starting value: false

Disabling this will result in less pathfinding being done, increasing performance. In some cases this will cause mobs to appear more laggy; They will just passively update their path every 5 ticks (0.25 sec).

fix-climbing-bypassing-cramming-rule

Good starting value: true

Enabling this will fix entities not being affected by cramming while climbing. This will prevent absurd amounts of mobs being stacked in small spaces even if they're climbing (spiders).

armor-stands.tick

Good starting value: false

In most cases you can safely set this to false. If you're using armor stands or any plugins that modify their behavior and you experience issues, re-enable it. This will prevent armor stands from being pushed by water or being affected by gravity.

armor-stands.do-collision-entity-lookups

Good starting value: false

Here you can disable armor stand collisions. This will help if you have a lot of armor stands and don't need them colliding with anything.

tick-rates

Good starting values:

  behavior:
    villager:
      validatenearbypoi: 60
      acquirepoi: 120
  sensor:
    villager:
      secondarypoisensor: 80
      nearestbedsensor: 80
      villagerbabiessensor: 40
      playersensor: 40
      nearestlivingentitysensor: 40

This decides how often specified behaviors and sensors are being fired in ticks. acquirepoi for villagers seems to be the heaviest behavior, so it's been greately increased. Decrease it in case of issues with villagers finding their way around.

dab.enabled

Good starting value: true

dab.max-tick-freq

Good starting value: 20

Defines the slowest amount entities farthest from players will be ticked. Increasing this value may improve the performance of entities far from view but may break farms or greatly nerf mob behavior. If enabling DAB breaks mob farms, try decreasing this value.

dab.activation-dist-mod

Good starting value: 7

Controls the gradient in which mobs are ticked. Decreasing this will activate DAB closer to players, improving DAB's performance gains, but will affect how entities interact with their surroundings and may break mob farms. If enabling DAB breaks mob farms, try increasing this value.

enable-async-mob-spawning

Good starting value: true

If asynchronous mob spawning should be enabled. For this to work, the Paper's per-player-mob-spawns setting must be enabled. This option does not actually spawn mobs asynchronous, but does offload much of the computational effort involved with spawning new mobs to a different thread. Enabling this option should not be noticeable on vanilla gameplay.

enable-suffocation-optimization

Good starting value: true

This option optimises a suffocation check (the check to see if a mob is inside a block and if they should take suffocation damage), by rate limiting the check to the damage timeout. This optimisation should be impossible to notice unless you're an extremely technical player who's using tick-precise timing to kill an entity at exactly the right time by suffocation.

inactive-goal-selector-throttle

Good starting value: true

Throttles the AI goal selector in entity inactive ticks, causing the inactive entities to update their goal selector every 20 ticks instead of every tick. Can improve performance by a few percent, and has minor gameplay implications.

zombie.aggressive-towards-villager-when-lagging

Good starting value: false

entities-can-use-portals

Good starting value: false

This option can disable portal usage of all entities besides the player. This prevents entities from loading chunks by changing worlds which is handled on the main thread. This has the side effect of entities not being able to go through portals.

villager.lobotomize.enabled

Good starting value: true

This should only be enabled if villagers are causing lag! Otherwise, the pathfinding checks may decrease performance.

Lobotomized villagers are stripped from their AI and only restock their offers every so often. Enabling this will lobotomize villagers that are unable to pathfind to their destination. Freeing them should unlobotomize them.

villager.search-radius

Good starting values:

          acquire-poi: 16
          nearest-bed-sensor: 16

Radius within which villagers will search for job site blocks and beds. This significantly boosts performance with large amount of villagers, but will prevent them from detecting job site blocks or beds that are further away than set value.

merge-radius

Good starting values:

      item: 3.5
      exp: 4.0

This decides the distance between the items and exp orbs to be merged, reducing the amount of items ticking on the ground. Setting this too high will lead to the illusion of items or exp orbs disappearing as they merge together. Setting this too high will break some farms, as well as allow items to teleport through blocks. There are no checks done to prevent items from merging through walls (unless Paper's fix-items-merging-through-walls setting is activated). Exp is only merged on creation.

hopper-transfer

Good starting value: 8

Time in ticks that hoppers will wait to move an item. Increasing this will help improve performance if there are a lot of hoppers on your server, but will break hopper-based clocks and possibly item sorting systems if set too high.

hopper-check

Good starting value: 8

Time in ticks between hoppers checking for an item above them or in the inventory above them. Increasing this will help performance if there are a lot of hoppers on your server, but will break hopper-based clocks and item sorting systems relying on water streams.

alt-item-despawn-rate

Good starting values:

      enabled: true
      items:
        cobblestone: 300
        netherrack: 300
        sand: 300
        red_sand: 300
        gravel: 300
        dirt: 300
        short_grass: 300
        pumpkin: 300
        melon_slice: 300
        kelp: 300
        bamboo: 300
        sugar_cane: 300
        twisting_vines: 300
        weeping_vines: 300
        oak_leaves: 300
        spruce_leaves: 300
        birch_leaves: 300
        jungle_leaves: 300
        acacia_leaves: 300
        dark_oak_leaves: 300
        mangrove_leaves: 300
        cactus: 300
        diorite: 300
        granite: 300
        andesite: 300
        scaffolding: 600

This list lets you set alternative time (in ticks) to despawn certain types of dropped items faster or slower than default. This option can be used instead of item clearing plugins along with merge-radius to improve performance.

redstone-implementation

Good starting value: ALTERNATE_CURRENT

Replaces the redstone system with faster and alternative versions that reduce redundant block updates, lowering the amount of logic your server has to calculate. Using a non-vanilla implementation may introduce minor inconsistencies with very technical redstone, but the performance gains far outweigh the possible niche issues. A non-vanilla implementation option may additionally fix other redstone inconsistencies caused by CraftBukkit.

hopper.disable-move-event

Good starting value: false

InventoryMoveItemEvent doesn't fire unless there is a plugin actively listening to that event. This means that you only should set this to true if you have such plugin(s) and don't care about them not being able to act on this event. Do not set to true if you want to use plugins that listen to this event, e.g. protection plugins!

hopper.ignore-occluding-blocks

Good starting value: true

Determines if hoppers will ignore containers inside full blocks, for example hopper minecart inside sand or gravel block. Keeping this enabled will break some contraptions depending on that behavior.

tick-rates.mob-spawner

Good starting value: 2

This option lets you configure how often spawners should be ticked. Higher values mean less lag if you have a lot of spawners, although if set too high (relative to your spawners delay) mob spawn rates will decrease.

optimize-explosions

Good starting value: true

Setting this to true replaces the vanilla explosion algorithm with a faster one, at a cost of slight inaccuracy when calculating explosion damage. This is usually not noticeable.

treasure-maps.enabled

Good starting value: false

Generating treasure maps is extremely expensive and can hang a server if the structure it's trying to locate is in an ungenerated chunk. It's only safe to enable this if you pregenerated your world and set a vanilla world border.

treasure-maps.find-already-discovered

Good starting values:
      loot-tables: true
      villager-trade: true

Default value of this option forces the newly generated maps to look for unexplored structure, which are usually in not yet generated chunks. Setting this to true makes it so maps can lead to the structures that were discovered earlier. If you don't change this to true you may experience the server hanging or crashing when generating new treasure maps. villager-trade is for maps traded by villagers and loot-tables refers to anything that generates loot dynamically like treasure chests, dungeon chests, etc.

tick-rates.grass-spread

Good starting value: 4

Time in ticks between the server trying to spread grass or mycelium. This will make it so large areas of dirt will take a little longer to turn to grass or mycelium. Setting this to around 4 should work nicely if you want to decrease it without the decreased spread rate being noticeable.

tick-rates.container-update

Good starting value: 1

Time in ticks between container updates. Increasing this might help if container updates cause issues for you (it rarely happens), but makes it easier for players to experience desync when interacting with inventories (ghost items).

non-player-arrow-despawn-rate

Good starting value: 20

Time in ticks after which arrows shot by mobs should disappear after hitting something. Players can't pick these up anyway, so you may as well set this to something like 20 (1 second).

creative-arrow-despawn-rate

Good starting value: 20

Time in ticks after which arrows shot by players in creative mode should disappear after hitting something. Players can't pick these up anyway, so you may as well set this to something like 20 (1 second).

disable-method-profiler

Good starting value: true

This option will disable some additional profiling done by the game. This profiling is not necessary to run in production and can cause additional lag.

dolphin.disable-treasure-searching

Good starting value: true

Prevents dolphins from performing structure search similar to treasure maps

teleport-if-outside-border

Good starting value: true

Allows you to teleport the player to the world spawn if they happen to be outside of the world border. Helpful since the vanilla world border is bypassable and the damage it does to the player can be mitigated.

In conclusion, optimizing your server settings is crucial for maintaining smooth gameplay and preventing performance issues like lag and TPS drops. Each adjustment should be carefully considered based on your server's specific needs and player activity. By fine-tuning configurations such as view distance, spawn limits, and tick intervals, you can strike a balance between performance and gameplay experience. Remember to regularly monitor your server's performance metrics after making changes to ensure they have the desired effect. With these optimizations in place, your server can provide a more enjoyable and stable environment for players.

Set up the BungeeCord Server

• Place the Bungeecord file inside your FIle Manger directory.

Configure the BungeeCord Server

• Stop the BungeeCord server if it is currently running.

• Open the config.yml file located in the same directory as the BungeeCord jar file using a text editor.

• Open the config.yml text file and start editing the contents, only edit the items listed. Do not delete or move any of the other existing text:

• Save the changes made to the configuration file.

  Connect Minecraft Servers to BungeeCord

  • Start each Minecraft server that you want to connect to the BungeeCord proxy. Ensure that the servers are running on different ports.

  • In the BungeeCord config.yml file, add the details of each Minecraft server under the servers section. Include the server name, SERVER IP, and port for each server.

  • The Server IP can be found in the console tab on your server.

  • Click the Server IP to copy it to your clipboard.

    • The server section of your config should look something like this:

    Copy

Steps:

1. Open the server.properties File:

   • Go to the root directory of your server and open the server.properties file using any text editor.

2. Find the motd Field:

   • In the file, look for the line that says motd=. This is where you can add your server’s description.

3. Write the Description:

   • Write the text you want to appear in the server list after motd=. Example:
4. Customize with Colors and Formatting (Optional):

   • You can use color and formatting codes with the § symbol followed by a number or letter. Here are some examples:

     • §1 = Dark Blue

     • §2 = Dark Green

     • §4 = Dark Red

     • §l = Bold text

     • §o = Italic text

     Example of a MotD with colors:
5. Save the Changes:

   • Save the server.properties file after editing.

6. Restart the Server:

   • Finally, restart your server so the changes to the MotD take effect and show up in the server list.

Other formatting / information:

Hosting the resource pack

Firstly, you’ll need somewhere to host the resource pack, this needs to be a direct download link which rules out lots of sites such as Mediafire, or Google Drive.

Option 1 (Recommended)

One option is to use a site meant for resource pack hosting such as MCPacks.

2. Drag the ZIP file of the pack you wish to use, onto the Choose File button

3. Click Upload

4. The site will give you the details in the following format, you can proceed to the Adding the resource pack section:

Adding the resource pack

Once you have the resource pack details from following one of the methods above, you will need to add it to your server.properties file. To do so, you’ll need to do the following:

2. Edit the server.properties file.

3. Find the resource-pack= line and change it to resource-pack=https://www.dropbox.com/s/abcd12345678/PureBDcraft%20128x%20MC116.zip?dl=1, or whatever your link is

4. Find the resource-pack-sha1= line and change it to resource-pack-sha1=7e8434889947b3417aded72e2495b0b85a7aef72, or whatever your hash is

5. Reboot the server

Allowing resource packs on the client

You’ll need to make sure that, in the server entry, Server Resource Packs are set to either Prompt or Enabled, if it’s set to disabled it will not work. By default it should be Prompt which means it asks.

How to Find Your Tribe or Player ID in ARK: Survival Evolved

Many of ARK's admin or "cheat" commands in ARK: Survival Evolved require a PlayerID or TribeID number to function effectively. You'll quickly realize that the number they are asking for is not the Steam64ID or any other Steam ID number if you are familiar with it. Those numbers are the UE 4 ID numbers, assigned by the game engine itself to every player or clan. This guide will show you how to find those numbers for a clan or player on your HidenCloud server.

Finding the ID numbers will require the use of administrator commands, so you should have set an Administrator password on your HidenCloud server, and then enable cheats for your identity. The following section tells you how to do both if you already have no idea how.

The admin password for your server can be set in the "Game Settings" section of the "Advanced" tab of the "HidenCloud" control panel. Make sure to hit the save button at the bottom of the page after entering a password, and then restart the server. It won't properly set the administrator password unless the server is restarted afterward. The admin password can also be set in the config file called "GameUserSettings.ini."

ARK Console Bar: Interface with your ARK server. When you load into the game, hit the tab key to open the console window in-game, appearing as a dark bar at the very bottom edge of the screen. If you hit tab a second time, the entire top half of the screen will be the console window, with a dark bar near the center for entering commands, showing the previous commands you've entered on the top half of the screen.

The extended window is very useful for catching mistakes entering an admin command earlier, which may have caused it not to work. For example, I repeatedly type "cheats" instead of "cheat" while entering commands. "cheat" works. "cheats" with the 's' at the end is wrong, and the entire command is ignored. Hitting tab again closes the console, or hitting escape.

Enable Cheats for Your Character: When you have the console open, enter the following command to activate "cheats" in-game.

If entered correctly, you are now an administrator and can use the "cheat" commands! You typically receive no confirmation message when the administrator is turned on. You can check if it worked by hitting tab again and typing "cheat fly" in the console bar to verify that you are an administrator. You should see the message "You feel much lighter," and if you hit the jump key, you will soar into the air! Type "cheat walk" to turn off fly mode if needed later.

Floating in midair is a great way not to get hindered in-game while entering admin/cheat commands.

Use the SetCheatPlayer Command: Hit tab again, and type this command (NOTE: for this command, you don't need to type "cheat" or "admincheat" before it as you do for most cheat commands):

To turn off the HUD, use the same command "setcheatplayer" but with nothing or false after it.

Finding a TribeID Identifier: With the "setcheatplayer" HUD turned on, just look at any tribe-related structure to see a "Tribe" number in the middle of the screen near the bottom. The "Tribe" number is the UE4 ID number in ARK for that clan.

Finding PlayerID Numbers: When you have the TribeID, use the following command, replacing (TribeID) with your TribeID as previously obtained.

Now that you have a TribeID and a PlayerID, you can correctly use many of the ARK admin/cheat commands.

Creation of Resources for HidenCloud Plans: BUDGET

In HidenCloud, the resources for plans are created according to specific optimization rules. Below are the detailed rules for the "BUDGET" plan:

1. Adjusted Price: The price is calculated at a rate of €1 per GB of RAM allocated.

   • Formula: Price = €1 * GB of RAM

2. CPU-Cores: The number of CPU-Cores is determined by the following formula:

   • Formula: CPU-Cores = (RAM // 8) + 1

   • Where RAM // 8 is the integer division of the amount of RAM in GB by 8.

3. Databases: The number of available databases is calculated by adding the CPU-Cores to the integer division of the amount of RAM in GB by 4.

   • Formula: Databases = (RAM // 4) + CPU-Cores

   • Where RAM // 4 is the integer division of the amount of RAM in GB by 4.

4. Storage: The storage space (in GB) is determined by adding the result of the integer division of RAM in GB by 2 to the product of CPU-Cores multiplied by 5.

   • Formula: Storage = (RAM // 2) + (CPU-Cores * 5)

   • Where RAM // 2 is the integer division of the amount of RAM in GB by 2.

5. Backup: The backup space is equal to the storage.

   • Formula: Backup = Storage

Budget SoftwareServers Specs:

Creation of Resources for HidenCloud Plans: BUDGET

In HidenCloud, the resources for plans are created according to specific optimization rules. Below are the detailed rules for the "BUDGET" plan:

1. Adjusted Price: The price is calculated at a rate of €1 per GB of RAM allocated.

   • Formula: Price = €1 * GB of RAM

2. CPU-Cores: The number of CPU-Cores is determined by the following formula:

   • Formula: CPU-Cores = (RAM // 8) + 2

   • Where RAM // 8 is the integer division of the amount of RAM in GB by 8.

3. Databases: The number of available databases is calculated by adding the CPU-Cores to the integer division of the amount of RAM in GB by 4.

   • Formula: Databases = (RAM // 4) + CPU-Cores

   • Where RAM // 4 is the integer division of the amount of RAM in GB by 4.

4. Storage: The storage space (in GB) is determined by adding the result of the integer division of RAM in GB by 2 to the product of CPU-Cores multiplied by 5.

   • Formula: Storage = (RAM // 2) + (CPU-Cores * 5)

   • Where RAM // 2 is the integer division of the amount of RAM in GB by 2.

5. Backup: The backup space is equal to the storage.

   • Formula: Backup = Storage

Budget GameServers Specs:

Install the local Java binary allows you to have multiple versions of Java in a Windows environment without having to modify the system environment variables.

Step 1: Download the Binary First, you need to download the binary for the Java version you want to install. To do this, go to the official Oracle website and find the corresponding version. Download the JDK .zip file for the Windows version.

Step 2: Extract the File

Navigate to the location where the .tar.gz file was downloaded, then extract the content to a location of your choice. You might choose to create a folder named "Java" in your home directory and extract the content there.

Step 3: Access the Binary

The Java binary will be in the resulting folder, which will consist of various files and directories. If you've followed these steps, it should be named something like jre1.8.0_202 or jdk1.8.0_181, with the version varying. Within this folder, you'll find another one called "bin." This is the folder containing the binaries that allow you to run Java locally. The two executables included in the binary are java.exe and javaw.exe (java.exe will execute the file with the Java console, while javaw.exe will execute the file without the visual Java console, hiding it).

Step 4: Using Local Java

Instead of changing your system's environment variables, all you need to do to use this local Java installation is refer directly to it when entering commands. For example, if you want to compile a Java file, the normal command would be "java TestFile.java." However, if you want to use the local Java, you need to specify the full path to your Java binary.

Instead of just "java," the command should look something like this:

C:\Users[your username][path to the extracted binary folder]\jre1.8.0_202\bin\java.exe TestFile.java 

In our case, it might look like this:

C:\Users\YourUsername\Desktop\Test\jre1.8.0_202\bin\java.exe TestFile.java 

This will compile the file using the Java binary you extracted, not the one installed in the system's environment variables.

Step 5: Create a Batch File (.bat extension)

To avoid typing out the full path each time, you can create a batch file in the same directory where your .java files are located. This batch file can contain the complete command, so you only need to run the batch file to compile your Java files.

An example of a batch file for a Minecraft server USING the binary directly (locally) might be:

@echo off
:start
"C:\Users\[your user]\[path to the folder where you extracted the binary]\jre1.8.0_202\bin\java.exe" -Xms1G -Xmx2G -jar spigot.jar nogui
timeout 10
goto start

• -Xms1G -Xmx2G -jar spigot.jar nogui timeout 10 goto start

• -Xms1G is the argument that sets the minimum amount of RAM allocated to your Minecraft server (in this case, 1 gigabyte).

• -Xmx2G is the argument that sets the maximum amount of RAM your Minecraft server can use (in this case, 2 gigabytes).

goto start is used to restart the server in case of crashes, bugs, or restarts.

If the binary folder (jre1.8.0_202) is in the same folder as the Minecraft server, you can use the following code:

@echo off
:start
"jre1.8.0_202\bin\java.exe" -Xms2G -Xmx27G -jar spigot.jar nogui
timeout 10
goto start

Since the binary is in the same folder as the server, Windows will use the dynamic path to find the file. This way, you don't have to specify the entire path, just the path starting from the folder where the batch file is located.

An example of a batch file for a Minecraft server NOT USING the binary directly (locally) and using Windows environment variables could be:

@echo off
:start
java -Xms1G -Xmx2G -jar spigot.jar nogui
timeout 10
goto start

Creation of Resources for HidenCloud Plans: PREMIUM

In HidenCloud, the resources for plans are created according to specific optimization rules. Below are the detailed rules for the "PREMIUM" plan:

1. Price: The price is calculated directly based on the amount of RAM allocated, at a rate of €2,5 per GB of RAM.

   • Formula: Price = €2,5 * GB of RAM

2. CPU-Cores: The number of CPU-Cores is determined by the following formula:

   • Formula: CPU-Cores = (RAM // 4) + 2

   • Where RAM // 4 is the integer division of the amount of RAM in GB by 4.

3. Databases: The number of available databases is calculated by multiplying the integer division of the amount of RAM in GB by 4 by 2, and then adding the CPU-Cores.

   • Formula: Databases = (RAM // 4) * 2 + CPU-Cores

   • Where RAM // 4 is the integer division of the amount of RAM in GB by 4.

4. Storage: The storage space (in GB) is determined by multiplying the integer division of RAM in GB by 4 by 10, and then adding the product of CPU-Cores multiplied by 5.

   • Formula: Storage = (RAM // 4) * 10 + (CPU-Cores * 5)

   • Where RAM // 4 is the integer division of the amount of RAM in GB by 4.

5. Backup: The backup space is equal to the storage.

   • Formula: Backup = Storage

Premiium GameServers Specs: