PlayerServers/PlayerServers-Wiki-Archive
4
0
Fork 0
forked from Upstream/playerservers-wiki
Code Pull Requests Activity

GitBook: [#86] Added beta warnings

Browse Source
This commit is contained in:
OpenSource 2022-09-02 04:26:45 +00:00 committed by gitbook-bot
parent 54a0b46fc0
commit 50b6abdfb6
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
5 changed files with 26 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
overview/config.md
View File

@ -1,5 +1,9 @@
# 📜 Current Config files
{% hint style="info" %}
The below page explains how to use this feature on PlayerServers 3. This is only relevant if you're a beta tester. To view this page for PlayerServers 3, click [here.](../legacy/config.md)
{% endhint %}
Below you can see the contents of the newest BungeeCord PlayerServers configuration file.
{% hint style="info" %}

4
overview/installation/docker-installation.md
View File

@ -6,6 +6,10 @@ description: >-
# 🛳 Docker configuration
{% hint style="info" %}
The below page explains how to use this feature on PlayerServers 3. This is only relevant if you're a beta tester. This feature does not exist on the public release yet.
{% endhint %}
## Introduction
Docker adds a secure isolation layer to your PlayerServers, so you can safely allow players to install all sorts of plugins without being afraid of them breaking something. 

10
overview/installation/multi-node-support.md
View File

@ -7,6 +7,10 @@ description: >-
# ⌨ Multi-Node Support
{% hint style="info" %}
The below page explains how to use this feature on PlayerServers 3. This is only relevant if you're a beta tester. To view this page for PlayerServers 3, click [here](../../legacy/multi-node-support.md).
{% endhint %}
## Requirements
* Purchased PlayerServers. This addon is free of charge
@ -20,8 +24,12 @@ The installation process for PlayerServers Daemon is pretty straight forward. Th
After that's done, create a folder Daemon. Download the following jar file and drop it into your Daemon folder:
{% file src="../../.gitbook/assets/PlayerServersDaemon.jar" %}
Daemon v3 (for PlayerServers v3 Beta)
{% endfile %}
{% file src="../../.gitbook/assets/Daemon-v1.1 (1).zip" %}
Daemon v1.1 - Release
Daemon v1.1 - Release (for PlayerServers v2)
{% endfile %}
After that's done, run it for the first time by using `java -Xmx200M -jar Daemon.jar` in order to let it generate the required files. Now exit it by typing in `exit`. After that's done, configure both multinode.yml inside your `BungeeCord/plugins/PlayerServers/multinode.yml` and your Daemon config.toml which will be generated in your Daemon root directory. It is important to include the same token inside both configs!

6
overview/installation/pterodactyl-configuration.md
View File

@ -7,4 +7,8 @@ description: >-
# 🌐 Pterodactyl configuration
## Work in progress
{% hint style="info" %}
The below page explains how to use this feature on PlayerServers 3. This is only relevant if you're a beta tester. This feature does not exist on the public release yet.
{% endhint %}
## This page is work in progress.

4
overview/limitations/permission-based-ram-1.md
View File

@ -4,6 +4,10 @@ description: Learn how to make a permission-based CPU system for your players
# Permission-based CPU
{% hint style="info" %}
The below page explains how to use this feature on PlayerServers 3. This is only relevant if you're a beta tester. This feature is not available in the public release yet.
{% endhint %}
## Introduction
We know that making a permission-based CPU system is a crucial to our customers and could be greately used for safety of your infrastructure and preventing overload as well as for stores in order to motivate players to upgrade to a higher rank, so we've implemented a permission-based CPU system. In this tutorial, you'll learn how to configure it for your needs.