# Wiki In this wiki you get all important information about my plugins. {% hint style="info" %} If you can't find any answers to a question, just contact me on my Discord server in the Ticket Support. {% endhint %} {% hint style="warning" %} If you share the plugins in any way, offer them for paid or free download (with license or without) your access to my plugins will be revoked. {% endhint %} # License Why a license system? I'll tell you here! ## Why a license? {% hint style="info" %} The plugins are equipped with a license system to avoid leaks. {% endhint %} So that you have some time to set my plugins properly, each plugin has a so-called **public-license**, but this can also be locked at any time. If the license is locked, the plugin can't be activated and therefore can't be used anymore. With the public license, you can use the plugin for 7 days without having to do anything. With expiration of the 7 days, the use of the plugin is no longer possible. Therefore it is of advantage to request a private license within the 7 days in the ticket support on my Discord server. If you use a public license, you will find out below. ## Am I using a public license? To see if you are using a public license, you only have to look at the so-called identifier, which is formed by the first 4 letters.\ In this example the bold marked letters are the identifier: **L31V**-D46S-F5S3-FSE7 In der folgenden Tabelle, kannst du die Identifier der einzelnen Plugins einsehen: | Plugin | Identifier | | ------------------------ | ---------- | | LanguageAPI (Spigot) | L31V | | LanguageAPI (BungeeCord) | L31V | | BungeeSystem | GYM5 | # Get started Thank you for purchasing my LanguageAPI. {% hint style="info" %} ColorCodes are always defined with a & character. A list of possible ColorColdes can be found [here](https://htmlcolorcodes.com/minecraft-color-codes/). Please use the CHAT CODE column from the displayed table and replace the § character with the & character. {% endhint %} If you have downloaded the LanguageAPI and started the server, a folder named *LanguageAPI* should now have been created in your plugins folder. Now open this folder and edit the `config.yml`. ## Enter license Add your private license in the `config.yml`. If you don't have one yet, open a support ticket on my discord server. {% hint style="info" %} Why do I need a private license? The answer is [here](/general/lizenz) {% endhint %} ## Database Set the database type in `config.yml`. ### MySQL Set `database: "mysql"` to store your data in a `MySQL` database. You can access the data across servers. To connect to MySQL database open the file `mysql.yml` and enter your MySQL data. {% code title="mysql.yml" lineNumbers="true" %} ```yaml mysql: HOST: localhost PORT: '3306' DATABASE: database USER: root PASSWORD: password ``` {% endcode %} ### Config Set `database: "config"` to store your data locally on the server. This data can then only be accessed by this one server. For this purpose the plugin creates a folder named `database` in the plugins folder. In this folder the database file `database.db` will be created. ## BungeeCord? {% hint style="warning" %} If you have the LanguageAPI for BungeeCord as well, set the `bungeemode: true` {% endhint %} ## File system There are 2 different file systems. These are explained below. ### single The `single` file system simply means that all messages of all languages are contained in one file. Here is the example from the LanguageAPI: {% code title="messages.yml" lineNumbers="true" %} ```yaml english: command: noConsolCommand: "[LanguageAPI] Please go on the Server and try again!" usage: "%prefix% &cPlease use: &e/changelanguage " unknowLanguage: "%prefix% &cThe language: &e%language% &cdoes not exists!" correctlyUsage: "%prefix% &7Your language was change to &e%language%&7." isLanguageAlready: "%prefix% &cYour language is already: &e%language%&c." deutsch: command: noConsolCommand: "[LanguageAPI] Bitte gehe auf den Server und versuche es erneut!" usage: "%prefix% &cBitte nutze: &e/changelanguage " unknowLanguage: "%prefix% &cDie Sprache: &e%language% &cexistiert nicht!" correctlyUsage: "%prefix% &7Deine Sprache wurde zu &e%language% &7geändert." isLanguageAlready: "%prefix% &cDeine Sprache ist bereits: &e%language%&c." ``` {% endcode %} ### multi In the System `multi` file, each individual language gets its own file. The individual files are in the plugin folder in the `language` folder. This is easy to build: `.yml` Here is an example: {% code title="deutsch.yml" lineNumbers="true" %} ```yaml command: noConsolCommand: "[LanguageAPI] Bitte gehe auf den Server und versuche es erneut!" usage: "%prefix% &cBitte nutze: &e/changelanguage " unknowLanguage: "%prefix% &cDie Sprache: &e%language% &cexistiert nicht!" correctlyUsage: "%prefix% &7Deine Sprache wurde zu &e%language% &7geändert." isLanguageAlready: "%prefix% &cDeine Sprache ist bereits: &e%language%&c." ``` {% endcode %} {% code title="english.yml" lineNumbers="true" %} ```yaml command: noConsolCommand: "[LanguageAPI] Please go on the Server and try again!" usage: "%prefix% &cPlease use: &e/changelanguage " unknowLanguage: "%prefix% &cThe language: &e%language% &cdoes not exists!" correctlyUsage: "%prefix% &7Your language was change to &e%language%&7." isLanguageAlready: "%prefix% &cYour language is already: &e%language%&c." ``` {% endcode %} {% hint style="warning" %} It is important that the language is also entered in the `config.yml` under the point `supportedLanguages`. Pay attention to the upper and lower case! {% endhint %} ## Prefix The prefix is always set before each message from the LanguageAPI. You can change the prefix by changing the line `prefix: "&7[&6LanguageAPI&7]&r"`. ## Change language As the server owner, you have the option to allow or deny players to change their language. You do this by editing the line `changeLanguage: true`. If you set the setting to `false`, the players will no longer be able to change their language. {% hint style="info" %} It would be best if you have the same setting on all servers, i.e. all set to `true` or all set to `false`. {% endhint %} ## Alias You can edit the command to change the language. To do this, simply add more entries to the `aliases` setting or remove them. If you only want the default command, simply replace the list with `aliases: []`. Standardkonfiguration: {% code lineNumbers="true" %} ```yaml aliases: - "language" ``` {% endcode %} {% hint style="info" %} The standard command for changing the language is: `changelanguage` {% endhint %} ## Default language The default language is the language that every player automatically receives when they join the server for the first time. To change the default language, simply edit the line\ `defaultLanguage: "english"`. {% hint style="warning" %} The default language `must be` listed among the supported languages. You can find the supported languages [here](#supported-languages) {% endhint %} ## Supported languages Under Supported languages, you add the languages that your server network should support. You can also remove the supported languages. {% code lineNumbers="true" %} ```yaml supportedLanguages: - deutsch - english ``` {% endcode %} {% hint style="success" %} Now you know everything about the settings of the LanguageAPI and you can use it. To implement it in your own plugins, you can go to the API page and see what you can do with it. You can find the page [here](/languageapi/api#languageapi). {% endhint %} ## Default configuration {% code title="config.yml" lineNumbers="true" %} ```yaml # The standard license is only valid for 7 days. Please request your private license on my Discord (link: https://discord.herrtechniker.eu). # You have to present your bill to prove that you bought the LanguageAPI. license: "" # Insert "mysql" to use mysql (cross-server access) or insert "config" to use local database (only local servers have access) database: "mysql" # If you use the LanguageAPI for Bungeecord, please set 'bungeemode = true' # ATTENTION Pleasemake sure your database type is mysql! If not, an error will occur and the plugin will not start! bungeemode: false # If this option set 'single' the different languages are in one file # and will be listed like the following example: # english: # path1: # path1.1: x # path1.2: xy # path2: 4 # deutsch: # path1: # path1.1: x # path1.2: xy # path2: 4 # etc... # # If this option set 'multi' then every language has an own file # like for english: "english.yml" # or for deutsch "deutsch.yml" (german) # # !!!!ATTENTION!!!! # - the language path for the structure single has been the same name and spelling like in the list supportedLanguages # - the language file name for structure multi has been the same name and spelling like in the list supportedLanguages # - After changing the language structure, the file(s) will be deleted. Before that, make a backup to transfer the messages to the other structure. languageStructure: "single" prefix: "&7[&6LanguageAPI&7]&r" # enable the command to change your language changeLanguage: true # aliases for the language command aliases: - "language" # has also been listed in supportedLanguages defaultLanguage: "english" # List of all supported Languages supportedLanguages: - deutsch - english ``` {% endcode %} ## Command ### Syntax ``` /changelanguage ``` # API Here you can find possible interfaces of the LanguageAPI to be able to use them in your plugin. To include the LanguageAPI in your project, you can put the .jar file in the folder `recources` of your project and make this entry in the `pom.xml` under the dependencies: {% code title="pom.xml" lineNumbers="true" %} ```xml de.herrtechniker LanguageAPI 1.0-SNAPSHOT system ${project.basedir}/src/main/resources/LanguageAPI-1.0.0-SNAPSHOT-OBF.jar ``` {% endcode %} Or for the BungeeCord version: {% code title="pom.xml" lineNumbers="true" %} ```xml de.herrtechniker LanguageAPI 1.0-SNAPSHOT system ${project.basedir}/src/main/resources/LanguageAPI-Bungee-1.0.0-SNAPSHOT-OBF.jar ``` {% endcode %} ## LanguageAPI To see if the player is already registered in the database, you can check it with the following query. ```java LanguageAPI().getApi().isPlayerEntryExists(UUID uuid); // return boolean ``` To get the language of the player, you can query the following. ```java LanguageAPI().getApi().getPlayerLanguage(UUID uuid); // return String ``` To set the player's language, do the following. ```java LanguageAPI().getApi().setPlayerLanguage(UUID uuid, String language); ``` To change the language, you can simply do the following. ```java LanguageAPI().getApi().changePlayerLanguage(UUID uuid, String language); ``` To add a language that you want your server network to support, you can do the following. ```java LanguageAPI().getApi().addSupportedLanguage(String language); ``` Of course, you can also remove a language that you have supported and no longer want to support. To do this, simply execute the following. ```java LanguageAPI().getApi().removeSupportedLanguage(String language); ``` To see if the language is already supported, you can do the following. ```java LanguageAPI().getApi().isLanguageSupported(String language); // return boolean ``` To get all supported languages in one list, simply execute the following ```java LanguageAPI().getApi().getAllSupportedLanguage(); // return List ``` To see if the default language is set, do the following. ```java LanguageAPI().getApi().isDefaultLanguageSet(); // return boolean ``` To set the default language do the following. ```java LanguageAPI().getApi().setDefaultLanguage(String defaultLanguage); ``` To get the default language, perform the following. ```java LanguageAPI().getApi().getDefaultLanguage(); // return String ``` To change the default language, do the following. ```java LanguageAPI().getApi().changeDefaultLanguage(String defaultLanguage); ``` To see if the LanguageAPI is running in the `multi-file system`, run the following. ```java LanguageAPI().getApi().isMultiFile(); // return boolean ``` To get a message from the file from the `single-file system`, do the following. ```java LanguageAPI().getApi().getSingleFileMessage(String language, String path); // return String ``` To get a message from a file when `multi-file system` is enabled, do the following. Pass the name of the file as `fileName`. ```java LanguageAPI().getApi().getMultiFileMessage(String fileName, String language, String path); // return String ``` ## Namefetcher {% hint style="info" %} The Namefetcher is a "module" which stores the name and the corresponding UUID of the player. {% endhint %} To check if a player's entry already exists, do the following. ```java LanguageAPI().getApi().isNamefetcherEntryExists(UUID uuid); // return boolean ``` To check if a player's entry already exists, do the following. ```java LanguageAPI().getApi().isNamefetcherEntryExists(String name); // return boolean ``` To enter an entry in the Namefetcher for a player, do the following. {% hint style="warning" %} Make sure that there is only one entry per player, if possible. {% endhint %} ```java LanguageAPI().getApi().setNamefetcher(UUID uuid, String name); ``` To change a player's entry, for example if the player has changed his name, do the following. ```java LanguageAPI().getApi().changeNamefetcher(UUID uuid, String name); ``` To get the name of a player by UUID, do the following. ```java LanguageAPI().getApi().getName(UUID uuid); // return String ``` To get the UUID of a player by name, do the following. {% code fullWidth="false" %} ```java LanguageAPI().getApi().getUUID(String name); // return UUID ``` {% endcode %} # Get started Thank you for purchasing my BungeeSystem's. {% hint style="info" %} ColorCodes are always defined with a & character. A list of possible ColorColdes can be found [here](https://htmlcolorcodes.com/minecraft-color-codes/). Please use the CHAT CODE column from the displayed table and replace the § character with the & character. {% endhint %} If you downloaded the BungeeSystem and started the server, you should now have created a folder called *BungeeSystem* in your plugins folder. Now open this folder and edit the `config.yml`. ## Enter license Add your private license in the `config.yml`. If you don't have one yet, open a support ticket on my discord server. {% hint style="info" %} Why do I need a private license? The answer is [here](/general/lizenz) {% endhint %} `license: ""` ## Datenbank Set the database type in `config.yml`. ### MySQL Set `database: "mysql"` to store your data in a `MySQL` database. You can access the data across servers. To connect to MySQL database open the file `mysql.yml` and enter your MySQL data. {% code title="mysql.yml" lineNumbers="true" %} ```yaml mysql: HOST: localhost PORT: '3306' DATABASE: database USER: root PASSWORD: password ``` {% endcode %} ### Config Set `database: "sql"` to store your data locally on the server. This data can then only be accessed by this one server. For this purpose the plugin creates a folder named `database` in the plugins folder. In this folder the database file `database.db` will be created. ## Default language ### With LanguageAPI If you have my LanguageAPI for BungeeCord, you can omit the\ `defaultLanguage: "english"` item, since the player's language is managed through it. Just make sure that you have set all messages in the languages that are set in the `config.yml` of the LanguageAPI. single-file-system For example, if you support English, German and Spanish, in this case you will have to copy the messages to e.g. English and paste it at the end of the file and translate each language. multi-file-system Just like with the single file system you only have to copy the `english.yml` file and change it to the name of the language. In the example with the spanish language to `español.yml`. (If you have set the language as español in the `config.yml` of the LanguageAPI). {% hint style="info" %} Otherwise have a look at the language setting in LanguageAPI. [Click here](/languageapi/get-started) {% endhint %} ### Without LanguageAPI But if you didn't buy my LanguageAPI, you can set the default language of the BungeeSystem under `defaultLanguage: "english"`. This means that every player gets all messages of the plugin in this language. ## Servername Under the item `servername: "yourserver.com"` you can enter the name/domain name of your network. This name will be used by some modules. ## Modules Here you can find a list of all modules that are included in the BungeeSystem. On the next pages you will find more information about each module. * Auto broadcast * Broadcast * Chat * CloudNet * Discord Bot * FriendSystem * Joinme * Jumpto * Lobby * motd * Move * MSG * OnlineTeam * OnlineTime * Party * Ping * Pull * Punishment System * Ban * Mute * Other * Report * Teamchat {% hint style="info" %} You can enable or disable each module individually. For example, if you already have a friends system, you can leave the `friend: false` setting in `config.yml` set to false. Each module is turned off (disabled) by default. {% endhint %} ## Options In the `options` section you can set certain things for each module. ## Default configuration {% code title="config.yml" lineNumbers="true" %} ```yaml # The standard license is only valid for 7 days. Please request your private license on my Discord (link: https://discord.gg/pnXAbH4DtT). # You have to present your bill to prove that you bought the LanguageAPI. license: "" # Insert "mysql" to use mysql (cross-server access) or insert "sql" to use local database (only local servers have access) database: "mysql" # if LanguageAPI NOT enabled, what is the default-Language for this system (LanguageAPI by HerrTechniker) defaultLanguage: "english" # set her your server name. That can be displayed for example on the ban-/kick screen. servername: "yourserver.com" # prefix of the bungeesystem prefix: "&7[&6BungeeSystem&7]&r" # gave a player full rights of the BungeeSystem to execute every command (recommended for the owners) permission: "bungeesystem.*" # if you have the permission (see above) you will get an ingame message that a new update is released updater: false # Here you can enable every single module, that the BungeeSystem support modules: autoBroadcast: false broadcast: false chat: false cloudnet: v3: false discord: false friend: false joinme: false jumpto: false lobby: false motd: false move: false msg: false onlineteam: false onlinetime: false party: false partychat: false ping: false pull: false punishment: ban: false kick: false mute: false report: false teamchat: false # Here you can edit every setting from a module options: broadcast: prefix: "&7[&6Broadcast&7]&r" permission: "bungeesystem.broadcast.use" aliases: - "bc" chat: prefix: "&7[&fChat&7]&r" permission: "bungeesystem.switch.chat" # you can read every chat message on every server except for the ingame-chat. This chat is only readable on the server where the player is ingameChatName: "ingame" chats: - "bedwars" - "skywars" - "gungame" - "mlgrush" aliases: [] cloudnet: teamGroups: - "Owner" - "Admin" - "Moderator" - "Supporter" - "Developer" - "Builder" discord: prefix: "&5Discord &8|&r" # permission to execute '/link '-command and '/verify '-command permission: "bungeesystem.discordverify.use" # using webhook for the chat messages in discord instead of the bot. The message from the bot is everytime as an embed (recommed) usingWebhook: true # should be the message in an embed (for the webhook). usingEmbedForWebhook: false # if enabled and the module chat also then the Discord channels are added to the channels of the chat module switchChat: false # if enabled all attachments will be ignored. # If disabled the player will get a message that a user send a video or an image that can not be displayed in the minecraft chat. ignoreAttachments: false # set a time which effect the synchronisation between minecraft and discord. # That means every x seconds the system will look if their a new player that linked minecraft with discord and it will sync roles and other stuff. # sync time in seconds (default = 600 seconds => 10 minutes) syncTime: 600 # When the synchronisation is finished, should the player receive a message or not (true = the player receives a message) syncMessage: false # set a time which effect the synchronisation between minecraft and discord. # That means every x seconds the system checks if the player still has the same permissions. # If not, the rank is removed from Discord and reassigned to the rank the player has in Minecraft. # sync time in seconds (default = 1200 seconds => 20 minutes) repeatSyncTime: 1200 aliases: link: [] unlink: [] verify: [] discord: [] friend: prefix: "&7[&9Friends&7]&r" jumpToMessage: true # permission ; max Requests # -1 = unlimited defaultRequests: 100 maxRequests: - "bungeesystem.friends.requests.150;150" - "bungeesystem.friends.requests.256;256" - "bungeesystem.friends.requests.unlimited;-1" # permission ; max Friends # -1 = unlimited defaultFriends: 100 maxFriends: - "bungeesystem.friends.friends.150;150" - "bungeesystem.friends.friends.256;256" - "bungeesystem.friends.friends.unlimited;-1" # if cloudnet v3 is enabled, please insert the cloudnet task, if not insert server names # if player connect to this server/task, all friends will get the switch message. if the message is enabled with the friend toggleswitch command whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" aliases: - "freunde" - "freund" - "friends" joinme: prefix: "&7[&6JoinMe&7]&r" permission: "bungeesystem.joinme.use" permissionCooldown: "bungeesystem.joinme.cooldown" switchServerMessage: true availableSelfSetting: false # how long is the joinme available in seconds available: 20 # the global delay (in seconds) for the next joinme (-1 for disable) globalCooldown: 10 # the delay for the player (in seconds) for the next joinme (-1 for disable) defaultCooldown: 30 whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" aliases: - "jm" jumpto: prefix: "&7[&3JumpTo&7]&r" permission: "bungeesystem.jumpto.use" switchMessage: true aliases: - "jump" lobby: prefix: "&7[&6System&7]&r" switchMessage: false aliases: - "hub" - "leave" - "l" msg: prefix: "&6MSG &7|&r" aliases: [] motd: maintenance: permission: "bungeesystem.maintenance.use" aliases: - "wartung" move: prefix: "&7[&dMove&7]&r" permission: "bungeesystem.move.use" aliases: [] onlineteam: prefix: "&bTeamonline &7|&r" countOfTeamGroups: 6 teamGroups: 1: name: "&4Owner" permission: "bungeesystem.onlineteam.owner" 2: name: "&cAdmin" permission: "bungeesystem.onlineteam.admin" 3: name: "&1Moderator" permission: "bungeesystem.onlineteam.moderator" 4: name: "&9Supporter" permission: "bungeesystem.onlineteam.supporter" 5: name: "&bDeveloper" permission: "bungeesystem.onlineteam.developer" 6: name: "&2Builder" permission: "bungeesystem.onlineteam.builder" aliases: - "ao" - "adminonline" onlinetime: prefix: "&7[&bOnlineTeime&7]&r" show: seconds: true minutes: true hours: true days: true years: true aliases: - "ot" party: prefix: "&7[&5PARTY&7]&r" switchServerMessage: true # if cloudnet v3 in modules-section enabled, please enter the tasks where the party members do not connect with the party leader whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" # the value of default Members has a minimum of 2. By another unsupported value an error message will send with "Info defaultMembers error" defaultMembers: 8 maxMembers: - "bungeesystem.party.members.16;16" - "bungeesystem.party.members.32;32" - "bungeesystem.party.members.unlimited;-1" aliases: - "p" partychat: prefix: "&7[&5PartyChat&7]&r" aliases: - "pc" ping: prefix: "&7[&9Ping&7]&r" permission: "bungeesystem.ping.use" aliases: [] pull: prefix: "&7[&bPull&7]&r" permission: "bungeesystem.pull.use" aliases: [] punishment: ban: prefix: "&7[&6BanSystem&7]&r" autoBan: false # how many points for permanent ban permanent: 100 autoBanOperatorName: "AutoBanSystem" autoBanOperatorUUID: "00000001-0001-0001-0001-000000000001" autoBanReason: "auto ban" banReasons: 6 infoMessageOther: true webhook: false aliases: [] reduceBan: prefix: "&7[&6BanSystem&7]&r" infoMessageOther: true webhook: false aliases: [] tempBan: prefix: "&7[&6BanSystem&7]&r" infoMessageOther: true webhook: false aliases: [] unban: prefix: "&7[&6BanSystem&7]&r" infoMessageOther: true webhook: false aliases: [] banPoints: prefix: "&7[&6BanSystem&7]&r" aliases: [] # check command only activated, if ban or/and mute module is activated check: prefix: "&6Check &8|&r" aliases: [] history: prefix: "&6History &8|&r" aliases: - "h" kick: prefix: "&6Kick &8|&r" webhook: false aliases: - "k" mute: prefix: "&7[&6MuteSystem&7]&r" autoMute: false # how many points for permanent mute permanent: 100 autoMuteOperatorName: "AutoMuteSystem" autoMuteOperatorUUID: "00000002-0002-0002-0002-000000000002" autoMuteReason: "auto mute" muteReasons: 4 infoMessageOther: true webhook: false aliases: [] reduceMute: prefix: "&7[&6MuteSystem&7]&r" infoMessageOther: true webhook: false aliases: [] tempMute: prefix: "&7[&6MuteSystem&7]&r" infoMessageOther: true webhook: false aliases: [] unmute: prefix: "&7[&6MuteSystem&7]&r" infoMessageOther: true webhook: false aliases: [] mutePoints: prefix: "&7[&6MuteSystem&7]&r" aliases: [] report: prefix: "&7[&cReport&6System&7]&r" teamInfoMessage: true webhook: false aliases: - "r" reports: prefix: "&7[&cReport&6System&7]&r" aliases: [] permissions: ban: "bungeesystem.punishment.ban" banPoints: "bungeesystem.punishment.banpoints" unban: "bungeesystem.punishment.unban" mute: "bungeesystem.punishment.mute" mutePoints: "bungeesystem.punishment.mutepoints" unmute: "bungeesystem.punishment.unmute" check: "bungeesystem.punishment.check" history: "bungeesystem.punishment.history" kick: "bungeesystem.punishment.kick" reduceBan: "bungeesystem.punishment.reduceBan" reduceMute: "bungeesystem.punishment.reduceMute" tempMute: "bungeesystem.punishment.tempMute" tempBan: "bungeesystem.punishment.tempBan" # to report a player (player permission) report: "bungeesystem.punishment.report" # to see the reports and check them (team permission) reports: "bungeesystem.punishment.reports" punishmentBypass: "bungeesystem.punishment.punishmentbypass" teamchat: prefix: "&7[&5Teamchat&7]&r" permission: "bungeesystem.teamchat.use" aliases: - "tc" ``` {% endcode %} # Modules Here you can find the individual modules that the BungeeSystem has integrated. Each module is theoretically a separate plugin, which was put together in the BungeeSystem. On the following pages, you will find each module that is integrated in the BungeeSystem. {% hint style="info" %} ColorCodes are always defined with a & character. A list of possible ColorColdes can be found [here](https://htmlcolorcodes.com/minecraft-color-codes/). Please use the CHAT CODE column from the displayed table and replace the § character with the & character. {% endhint %} # AutoBroadcast ## broadcast.yml ### shuffle If shuffled is set to `true`, the messages are sent randomly.\ If shuffled is set to `false`, the messages are sent in sequence. ```yaml shuffled: true ``` ### intervall The interval indicates when a message is sent. ```yaml # intervall in seconds intervall: 300 ``` ## Default configuration ### broadcast.yml ``` random: shuffled: true # intervall in seconds intervall: 300 ``` {% file src="/files/MA0colUa3zqqQWP4MVcx" %} # Broadcast The broadcast module is a command with which you can send a message over your whole network. ## config.yml ### Prefix The prefix is exchanged in the message files with `%prefix%` (placeholder). If you run the command and enter the placeholder at the beginning of the message, it will be replaced with the prefix. This can be changed in the `config.yml`. ```yaml prefix: "&7[&6Broadcast&7]&r" ``` ### Permission To be able to execute the command for the broadcast module, you need the permission that is entered in `config.yml`. {% hint style="warning" %} The Permission is a BungeeCord Permission {% endhint %} ### Aliases You can also define so-called aliases that you can enter instead of /broadcast. For this you simply add further points under the point `aliases`. ```yaml aliases: - "bc" ``` ### Default configuration ```yaml broadcast: prefix: "&7[&6Broadcast&7]&r" permission: "bungeesystem.broadcast.use" aliases: - "bc" ``` ## commands ### Syntax ``` /broadcast ``` # Chat A module with which you have different chats. The player can also only read the messages from the selected chat. ## config.yml ### Prefix The prefix is exchanged with `%prefix%` (placeholder) in the message files. If you execute the command and enter the placeholder at the beginning of the message, it will be replaced with the prefix. This can be changed in `config.yml`. ```yaml prefix: "&7[&fChat&7]&r" ``` ### Permission To be able to execute the command for the chat module, you need the permission that is entered in `config.yml`. {% hint style="warning" %} Die Permission ist eine BungeeCord Permission {% endhint %} ```yaml permission: "bungeesystem.switch.chat" ``` ### ingameChatName Here you can define the chat name for the ingame chat, in other words the normal Minecraft chat. If you select this chat, you will only read the messages from the local server. ```yaml # you can read every chat message on every server except for the ingame-chat. This chat is only readable on the server where the player is ingameChatName: "ingame" ``` ### chats These are the chats you can choose between. ```yaml chats: - "bedwars" - "skywars" - "gungame" - "mlgrush" ``` ### Aliases You can also define so-called aliases that you can enter instead of /chat. To do this, simply add further points under the item `aliases`. ```yaml aliases: [] ``` ### Default configuration ```yaml chat: prefix: "&7[&fChat&7]&r" switchPermission: "bungeesystem.switch.chat" # you can read every chat message on every server except for the ingame-chat. This chat is only readable on the server where the player is ingameChatName: "ingame" chats: - "bedwars" - "skywars" - "gungame" - "mlgrush" aliases: [] ``` ## Command ### Syntax ``` /chat ``` # CloudNet v3 CloudNet v3 If you use CloudNet v3 you can enter the team groups here. These are then used by the BungeeSystem, for example in the Punishment module. There, the players who are in one of these groups cannot be banned or muted. # Discord Bot Here you can see all information about the Discord Bot from bungeeSystem. # Setup Setting up a Discord bot can be difficult for some people. However, if you know how, it's very easy. ## Preparation ### Create a bot #### **Step 1: Open website** Go to the following website: [Developers Application](https://discord.com/developers/applications) #### **Step 2: Create** Click on ***New Application*** at the top right

Erstelle eine neue Application

#### Step 3: Assign names Enter a name for the bot, accept the `Terms of Service` and the `Developer Policy`

Assigning a name to the application

#### **Step 4: Token reset** Reset token to display it. {% hint style="danger" %} Do not share your token, if you do, the person/people can start your bot and do bad things with it. {% endhint %}

Token Reset

#### **Step 5:** Confirm reset Confirm reset and then copy token {% hint style="danger" %} Save the token, as we will need it later! {% endhint %}

Confirm reset

#### **Step 6:** Invite Next, you create an invitation link
#### **Step 7:** Next, copy the link and open it in a new window. #### **Step 8: Select server**
In the next window, click on Authorize.
The bot should now be visible on your Discord server. #### **Developer Mode** Now activate the *Developer Mode* to set up the Discord Bot module correctly. You can activate developer mode in the settings under Advanced.
# Discord Settings Here you will find everything you need to know about the configuration file discord-settings.yml ## Configuration (discord-settings.yml) ### token Here you have to copy the bot token which you should save in [step 5](/bungeesystem/module/discord-bot/setup#step-5-confirm-reset) of the setup. ```yaml token: "" ``` ### state *state* is the online status of the bot (green, yellow or red circle). The following statuses can be entered here: * ONLINE * IDLE * DO\_NOT\_DISTURB * INVISIBLE ```yaml state: "ONLINE" ``` ### activity Enter the type of activity here. The following types can be entered here: * PLAYING * LISTENING * WATCHING * CUSOM ```yaml activity: "PLAYING" ``` ### content *content* is the value, i.e. what is displayed after the activity. ```yaml content: "Minecraft" ``` ### guildID Replace the `-1` here with the ID of your server (Guild)
```yaml guildID: -1 ``` ### replaceName If activated, after linking between Discord and Minecraft, the Discord name will be replaced with the name of the Minecraft account. ```yaml replaceName: false ``` ### link Here you can enter the invitation link to your Discord. {% hint style="info" %} If you want the link to be displayed in color in Minecraft chat, simply place the corresponding ColorCodes in front of it.\ ColorCodes are always defined with an `&` character. A list of possible ColorColdes can be found here. Please use the `CHAT CODE` column from the displayed table and replace the `§` sign with the `&` sign. {% endhint %} ```yaml link: "" ``` ### commands #### onlinetime Set enabled `true` if you want to enable the command. With the slashcommand `/onlinetime` you can see the onlinetime from a Minecraft player or a Discord user ```yaml commands: onlinetime: enabled: true show: seconds: true minutes: true hours: true days: true years: true ``` ### chats You can allow players to display messages from Minecraft in Discord and from Discord in Minecraft. Only enter the chats that players are allowed to use for this purpose. Replace the *name* with the name you want the player to see in the command and the channelID with the ID of the Discord chat. {% hint style="danger" %} The specified Discord chat has to be a text channel! {% endhint %} ```yaml channels: countOfChannels: 2 ingameChatName: "ingame" channelList: 1: name: "chat" channelID: -1 2: name: "techporn" channelID: -1 ``` {% hint style="warning" %} The `Chat` module must be activated in `config.yml` for this! {% endhint %} ### syncDiscord The players have the possibility to connect to Discord. To grant this, you only need to add the team groups and the community groups here. Also create roles on the Discord server of your network that are named like the Minecraft groups. Copy the role ID and paste it. You must also enter the number of team groups and community groups. {% hint style="warning" %} The list of groups starts at 1 {% endhint %} ```yaml syncDiscord: countOfTeamGroups: 6 countOfCommunityGroups: 1 defaultColor: "&7" defaultGroup: "Player" # if a player unlink his account, which role will he get defaultRoleID: -1 # replace '-1' with the id of the roles of your Discord Server # if you want you can edit the permission for the groups # the potency is for the weighting of the roles the smaller the number the higher the rank roles: community: 1: name: "Premium" potency: 7 color: "&6" roleID: -1 permission: "bungeesystem.discord.premium" 2: name: "Player" potency: 8 color: "&7" roleID: -1 permission: "bungeesystem.discord.player" teamGroups: 1: name: "Owner" potency: 1 color: "&4" roleID: -1 permission: "bungeesystem.discord.owner" 2: name: "Admin" potency: 2 color: "&c" roleID: -1 permission: "bungeesystem.discord.admin" 3: name: "Moderator" potency: 3 color: "&1" roleID: -1 permission: "bungeesystem.discord.moderator" 4: name: "Supporter" potency: 4 color: "&9" roleID: -1 permission: "bungeesystem.discord.supporter" 5: name: "Developer" potency: 5 color: "&b" roleID: -1 permission: "bungeesystem.discord.developer" 6: name: "Builder" potency: 6 color: "&4" roleID: -1 permission: "bungeesystem.discord.builder" ``` ### Default configuration ```yaml # to use the discord bot, please create a discord app here https://discord.com/developers/applications # after that go to "bot" and enable under Privileged Gateway Intents the points "SERVER MEMBERS INTENT", "MESSAGE CONTENT INTENT" and "PRESENCE INTENT" # furthermore paste your discord token here and invite the bot to your discord server. # # If the plugin was started and the module "discord verify" is enabled the bot will be started automatically token: "" # available states are ONLINE, IDLE, DO_NOT_DISTURB, INVISIBLE or leave empty for default (online) state: "ONLINE" # for example: # activity: "PLAYING" # content: "Minecraft" # available activities are PLAYING, LISTENING, WATCHING or CUSTOM # by CUSTOM the field content can be empty because only the content of the field 'activity' will be displayed # or leave empty for no activity activity: "PLAYING" content: "Minecraft" # replace '-1' with the id of the guild of your Discord Server guildID: -1 # If enabled, the Discord name will be replaced with the Minecraft account name. replaceName: false # enter your Discord invite link here # if you want to show the url in color in the minecraft chat please enter before the url a colorcode link: "" commands: onlinetime: enabled: true show: seconds: true minutes: true hours: true days: true years: true # you can choose which channel are available to write between discord and Minecraft # it would be advantageous if no images were allowed to be broadcast in these channels. # !!the name of the channel has to be in lower case!! # syntax: # name: "name of the channel" # channelID: -1 channels: countOfChannels: 2 ingameChatName: "ingame" channelList: 1: name: "chat" channelID: -1 2: name: "techporn" channelID: -1 syncDiscord: countOfTeamGroups: 6 countOfCommunityGroups: 1 defaultColor: "&7" defaultGroup: "Player" # if a player unlink his account, which role will he get defaultRoleID: -1 # replace '-1' with the id of the roles of your Discord Server # if you want you can edit the permission for the groups # the potency is for the weighting of the roles the smaller the number the higher the rank roles: community: 1: name: "Premium" potency: 7 color: "&6" roleID: -1 permission: "bungeesystem.discord.premium" 2: name: "Player" potency: 8 color: "&7" roleID: -1 permission: "bungeesystem.discord.player" teamGroups: 1: name: "Owner" potency: 1 color: "&4" roleID: -1 permission: "bungeesystem.discord.owner" 2: name: "Admin" potency: 2 color: "&c" roleID: -1 permission: "bungeesystem.discord.admin" 3: name: "Moderator" potency: 3 color: "&1" roleID: -1 permission: "bungeesystem.discord.moderator" 4: name: "Supporter" potency: 4 color: "&9" roleID: -1 permission: "bungeesystem.discord.supporter" 5: name: "Developer" potency: 5 color: "&b" roleID: -1 permission: "bungeesystem.discord.developer" 6: name: "Builder" potency: 6 color: "&4" roleID: -1 permission: "bungeesystem.discord.builder" ``` ## Commands ### Syntax | Command | Description | | ------------------------ | -------------------------------------------------------------------------------------------- | | /discord | Receive the invitation link to the Discord server | | /link \ |

Enter your UserID or your username (not nickname)
see here

| | /verify \ | Enter the verification code sent to you by the Discord bot to end the linking process | | /unlink | Disconnect the connection with your Discord account | | /chat \ | Write from Minecraft to Discord and the other way too | ## Username

What is the username

# config.yml Hier findest du die Einstellung zum Discord Bot in der config.yml ## Konfiguration (config.yml) ### Prefix The prefix is exchanged in the message files with `%prefix%` (placeholder). If you run the command and enter the placeholder at the beginning of the message, it will be replaced with the prefix. This can be changed in the `config.yml`. ```yaml prefix: "&5Discord &8|&r" ``` ### Permission To be able to execute the command for the Discord Bot Verify module, you need the permission that is entered in `config.yml`. ```yaml permission: "bungeesystem.discordverify.use" ``` ### usingWebhook If you have selected a Discord channel via the `Chat` module, there are 2 options for transmitting the message to the Discord channel.\ Option 1: Via a webhook\ Option 2: Via the DiscordBot Wenn usingWebhook aktiviert ist, wird die Möglichkeit 1 genommen. ```yaml usingWebhook: true ``` ### usingEmbedForWebhook If this is activated, the message is transmitted in an embed via the webhook. If the setting is deactivated, the message is transmitted as a normal Discord message. {% hint style="info" %} The design of the embed can be changed in the message files. {% endhint %} ```yaml # should be the message in an embed (for the webhook). usingEmbedForWebhook: false ``` ### switchChat Offer your players on your server the possibility to change the chat in Minecraft to read messages on Discord and the other way around. ```yaml switchChat: true ``` ### ignoreAttachments If activated, the system checks whether the message sent in a Discord channel that can be selected via the chat module contains an image or a video. If this is the case, it will be ignored and the player who selected the channel will not receive a message. If disabled and this happens as described above, the player will receive a message instead of the image or video that an image/video has been sent and that he should open Discord if he wants to see it. ```yaml # if enabled all attachments will be ignored. # If disabled the player will get a message that a user send a video or an image that can not be displayed in the minecraft chat. ignoreAttachments: false ``` ### syncTime The syncTime (synchronization time) indicates the interval at which the system checks whether a new player has been verified. {% hint style="info" %} The time is entered in seconds. {% endhint %} ```yaml syncTime: 600 ``` ### syncMessage Here you can set whether the player receives a notification when synchronization is complete. ```yaml syncMessage: false ``` ### repeatSyncTime The repeatSyncTime is a method that checks whether the player still has the same rights as on Discord. If not, these are updated. {% hint style="info" %} The repeatSyncTime is specified {% endhint %} ```yaml repeatSyncTime: 1200 ``` ### aliases You can also define so-called aliases that you can enter instead of /link, /unlink, /verify or /discord. To do this, simply add further points under the item `aliases`. ```yaml aliases: link: [] unlink: [] verify: [] discord: [] ``` ## Default configuration ```yaml discord: prefix: "&5Discord &8|&r" # permission to execute '/link '-command and '/verify '-command permission: "bungeesystem.discordverify.use" # using webhook for the chat messages in discord instead of the bot. The message from the bot is everytime as an embed (recommed) usingWebhook: true # should be the message in an embed (for the webhook). usingEmbedForWebhook: false # if enabled and the module chat also then the Discord channels are added to the channels of the chat module switchChat: false # if enabled all attachments will be ignored. # If disabled the player will get a message that a user send a video or an image that can not be displayed in the minecraft chat. ignoreAttachments: false # set a time which effect the synchronisation between minecraft and discord. # That means every x seconds the system will look if their a new player that linked minecraft with discord and it will sync roles and other stuff. # sync time in seconds (default = 600 seconds => 10 minutes) syncTime: 600 # When the synchronisation is finished, should the player receive a message or not (true = the player receives a message) syncMessage: false # set a time which effect the synchronisation between minecraft and discord. # That means every x seconds the system checks if the player still has the same permissions. # If not, the rank is removed from Discord and reassigned to the rank the player has in Minecraft. # sync time in seconds (default = 1200 seconds => 20 minutes) repeatSyncTime: 1200 aliases: link: [] unlink: [] verify: [] discord: [] ``` # discord-setting.yml Hier findest du die Standard Konfigurationsdatei vom Discord Bot {% file src="/files/8jg9vWadammt3kdTIa4E" %} {% code title="discord-settings.yml" lineNumbers="true" %} ```yaml # to use the discord bot, please create a discord app here https://discord.com/developers/applications # after that go to "bot" and enable under Privileged Gateway Intents the points "SERVER MEMBERS INTENT", "MESSAGE CONTENT INTENT" and "PRESENCE INTENT" # furthermore paste your discord token here and invite the bot to your discord server. # # If the plugin was started and the module "discord verify" is enabled the bot will be started automatically token: "" # available states are ONLINE, IDLE, DO_NOT_DISTURB, INVISIBLE or leave empty for default (online) state: "ONLINE" # for example: # activity: "PLAYING" # content: "Minecraft" # available activities are PLAYING, LISTENING, WATCHING or CUSTOM # by CUSTOM the field content can be empty because only the content of the field 'activity' will be displayed # or leave empty for no activity activity: "PLAYING" content: "Minecraft" # replace '-1' with the id of the guild of your Discord Server guildID: -1 # If enabled, the Discord name will be replaced with the Minecraft account name. replaceName: false # enter your Discord invite link here # if you want to show the url in color in the minecraft chat please enter before the url a colorcode link: "" commands: onlinetime: enabled: true show: seconds: true minutes: true hours: true days: true years: true # you can choose which channel are available to write between discord and Minecraft # it would be advantageous if no images were allowed to be broadcast in these channels. # !!the name of the channel has to be in lower case!! # syntax: # name: "name of the channel" # channelID: -1 channels: countOfChannels: 2 channelList: 1: name: "chat" webhook: "" channelID: -1 2: name: "techporn" webhook: "" channelID: -1 syncDiscord: countOfTeamGroups: 6 countOfCommunityGroups: 1 defaultColor: "&7" defaultGroup: "Player" # if a player unlink his account, which role will he get defaultRoleID: -1 # replace '-1' with the id of the roles of your Discord Server # if you want you can edit the permission for the groups # the potency is for the weighting of the roles the smaller the number the higher the rank roles: community: 1: name: "Premium" potency: 7 color: "&6" roleID: -1 permission: "bungeesystem.discord.premium" 2: name: "Player" potency: 8 color: "&7" roleID: -1 permission: "bungeesystem.discord.player" teamGroups: 1: name: "Owner" potency: 1 color: "&4" roleID: -1 permission: "bungeesystem.discord.owner" 2: name: "Admin" potency: 2 color: "&c" roleID: -1 permission: "bungeesystem.discord.admin" 3: name: "Moderator" potency: 3 color: "&1" roleID: -1 permission: "bungeesystem.discord.moderator" 4: name: "Supporter" potency: 4 color: "&9" roleID: -1 permission: "bungeesystem.discord.supporter" 5: name: "Developer" potency: 5 color: "&b" roleID: -1 permission: "bungeesystem.discord.developer" 6: name: "Builder" potency: 6 color: "&4" roleID: -1 permission: "bungeesystem.discord.builder" ``` {% endcode %} # Friend System A friends system needs every Minecraft network. ## config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it just write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ### jump To Message If this value is set to `true`, the message you find under `options.friend.jumpToMessage` will be sent. If the value is set to `false`, it will not be sent. ### Default Requests Here you can set how many friend requests each player has by default. Default: `defaultRequests: 100` ### Max Requests Here you can set, based on permissions, the maximum number of friend requests from a player. Default: 
# permission ; max Requests
# -1 = unlimited
maxRequests:
    - "bungeesystem.friends.requests.150;150"
    - "bungeesystem.friends.requests.256;256"
    - "bungeesystem.friends.requests.unlimited;-1"
### Max Friends Here you can set the maximum number of friends of a player based on permissions. Default: ```yaml # permission ; max Friends # -1 = unlimited maxFriends: - "bungeesystem.friends.friends.150;150" - "bungeesystem.friends.friends.256;256" - "bungeesystem.friends.friends.unlimited;-1" ``` ### Whitelist If you are using CloudNet v3, the first step is to enable the CloudNet v3 module under modules in `config.yml`. Next, you enter all tasks of CloudNet under the item whitelist, where a player is allowed to get the message from his friends, which is in the message file under `command.friend.switch.message`. ```yaml whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" ``` ### Aliases You can also define so-called aliases that you can enter instead of /friend. For this you simply add further points under the point `aliases`. ```yaml aliases: - "freunde" - "freund" - "friends" ``` ### Default configuration {% code title="config.yml" lineNumbers="true" %} ```yaml friend: prefix: "&7[&9Friends&7]&r" jumpToMessage: true # permission ; max Requests # -1 = unlimited defaultRequests: 100 maxRequests: - "bungeesystem.friends.requests.150;150" - "bungeesystem.friends.requests.256;256" - "bungeesystem.friends.requests.unlimited;-1" # permission ; max Friends # -1 = unlimited defaultFriends: 100 maxFriends: - "bungeesystem.friends.friends.150;150" - "bungeesystem.friends.friends.256;256" - "bungeesystem.friends.friends.unlimited;-1" # if cloudnet v3 is enabled, please insert the cloudnet task, if not insert server names # if player connect to this server/task, all friends will get the switch message. if the message is enabled with the friend toggleswitch command whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" aliases: - "freunde" - "freund" - "friends" ``` {% endcode %} ## Kommandos ### Syntax | command | Explanation | | ------------------------ | -------------------------- | | /friend help \ | Shows the help pages 1-2 | | /friend add \ | Add a friend | | /friend remove \ | Remove a friend | | /friend accept \ | Accept a friend request | | /friend deny \ | Reject a friend request | | /friend acceptall | Accept all friend requests | | /friend denyall | Reject all friend requests | | /friend list | Lists all friends | | /friend requests | Lists all friend requests | | /friend clear | Remove all friends | | /friend jump | Jump to a friend | | /friend togglerequest | Enable/Disable | | /friend togglejump | Enable/Disable | | /friend togglenotify | Enable/Disable | | /friend toggleswitch | Enable/Disable | # Joinme Create a "link" where other players can jump into your rounds. ## config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&6JoinMe&7]&r" ``` ### Permission Here you can enter the permission that the player needs to use the joinme command. ```yaml permission: "bungeesystem.joinme.use" ``` ### Permission Cooldown Here you can enter the permission the player needs to use the cooldown setting of the joinme command. {% hint style="info" %} But for this the setting `availableSelfSetting` must be set to `true`. {% endhint %} ```yaml permissionCooldown: "bungeesystem.joinme.cooldown" ``` ### switchServerMessage If this setting is set to `true`, the player who clicked on the joinme message will see the message that he switched servers. ```yaml switchServerMessage: true ``` ### availableSelfSetting If this setting is `true`, each player can set the countdown (countdown in seconds) for his next joinme. ```yaml availableSelfSetting: false ``` ### available Here you can set how long a joinme is available. The time is given in seconds. ```yaml # how long is the joinme available in seconds available: 20 ``` ### globalCooldown This setting specifies when the next join can be created. (specifications in seconds) ```yaml # the global delay (in seconds) for the next joinme (-1 for disable) globalCooldown: 10 ``` ### defaultCooldown The `defaultCooldown` is the time in seconds that must elapse before the player can create a new joinme again. (-1 to disable) ```yaml # the delay for the player (in seconds) for the next joinme (-1 for disable) defaultCooldown: 30 ``` ### whitelist The whitelist contains the servers where you can execute the joinme command.\ If CloudNet v3 is enabled, you have to enter the task name here.\ If CloudNet v3 is not activated, enter the individual names of the servers as they are entered in the config of the BungeeCord server. ```yaml whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" ``` ### Aliases You can also define so-called aliases that you can enter instead of /joinme. For this you simply add further points under the point `aliases`. ```yaml aliases: - "jm" ``` ### Default configuration ```yaml prefix: "&7[&6JoinMe&7]&r" permission: "bungeesystem.joinme.use" permissionCooldown: "bungeesystem.joinme.cooldown" switchServerMessage: true availableSelfSetting: false # how long is the joinme available in seconds available: 20 # the global delay (in seconds) for the next joinme (-1 for disable) globalCooldown: 10 # the delay for the player (in seconds) for the next joinme (-1 for disable) defaultCooldown: 30 whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" aliases: - "jm" ``` ## Command ### Syntax | | | | --------------------------- | ------------------------------------------------------------ | | /joinme send | Create joinme | | /joinme join \ | join a joinme | | /joinme cooldown \ | Set the cooldown to x seconds (`availableSelfSetting: true`) | # Jumpto Jump to any player ## config.yml ### Prefix The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&3JumpTo&7]&r" ``` ### Permission Here you can enter the permission that the player needs to be able to use the jumpto command. ```yaml permission: "bungeesystem.jumpto.use" ``` ### switchServerMessage If this setting is set to `true`, when jumping to a player, the message that he has changed the server is displayed. ```yaml switchMessage: true ``` ### Aliases You can also define so-called aliases that you can enter instead of /jumpto. To do this, simply add more points under the item `aliases`. ```yaml aliases: - "jump" ``` ### Default configuration ```yaml jumpto: prefix: "&7[&3JumpTo&7]&r" permission: "bungeesystem.jumpto.use" switchMessage: true aliases: - "jump" ``` ## Command ### Syntax ``` /jumpto ``` # Lobby Enter /lobby to access the lobby of the server network ### Prefix The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&6System&7]&r" ``` ### switchServerMessage If this setting is set to `true`, when jumping to a player, the message that he has changed the server is displayed. ```yaml switchMessage: true ``` ### Aliases You can also define so-called aliases that you can enter instead of /lobby. To do this, simply add more points under the item `aliases`. ```yaml aliases: - "hub" - "leave" - "l" ``` ### Default configuration ```yaml lobby: prefix: "&7[&6System&7]&r" switchMessage: false aliases: - "hub" - "leave" - "l" ``` ## lobby.yml You can define your fallback servers in the lobby.yml under `plugins/BungeeSystem/modules/`. ### normal If you are using CloudNet v3, enter your LobbyTask under server. ```yaml server: "Lobby" ``` However, if you only use BungeeCord, list all lobby servers as in the example here: ```yaml server: - "ServerName-1" - "ServerName-2" ``` ### silent If you have silent lobbies, you must first set `enabled: false` to `true`. Then set the `server` item as [normal](#normal). So that your players can now be automatically connected to the silent server, you must enter the permission that the player requires.\ `priority` means which server should be prioritized. ### premium If you have premium lobbies, set them up in exactly the same way as the [silent](#silent) lobby. {% hint style="info" %} The priority is essentially about which server/servertask the player is sent to if silent and premium lobby is activated and the player has both permissions. {% endhint %} ### Default lobby.yml ```yaml fallbacks: normal: # if using CloudNet v3 please insert task name # if using only BungeeCord please insert server names # server: # - "ServerName-1" # - "ServerName-2" # etc server: "Lobby" silent: enabled: false server: "SilentLobby" # for no permission please leave empty permission: "bungeesystem.lobby.silent" # lowest = 1 # The lower the number, the higher the priority priority: 1 premium: enabled: false server: "PremiumLobby" permission: "bungeesystem.lobby.premium" priority: 2 ``` ## Command ### Syntax ``` /lobby ``` # motd Here you can define your motd of the server. ## config.yml ### permission Is required to be able to join the server when it is in maintenance. ```yaml permission: "bungeesystem.maintenance.use" ``` ### Aliases You can also define so-called aliases that you can enter instead of /maintenance. To do this, simply add further points under the `aliases` item. ```yaml aliases: - "wartung" ``` ## motd.yml ### maxPlayers Set the maximum number of players allowed to join the server here. ```yaml maxPlayers: 100 ``` ### whitelist Add player names here that are still allowed on the server during maintenance work.\ Here is an example: ```yaml whitelist: - "Spieler1" - "Spieler2" - "Spieler3" ``` ```yaml whitelist: [] ``` ### maintenance #### enabled If this value is set to `true`, the BungeeCord server goes into maintenance mode. ```yaml enabled: false ``` #### motds Set the motd of the server when it is undergoing maintenance. ```yaml motds: firstLine: "&b&o■ &8┃ &b&lBungeeSystem &8&l» &7&ov1.1.0 &8┃ &b&o■" secondLine: " &4&lMaintenance" protocolText: "&8➜ &c&lMaintenance &8┃ &c✘" ``` ### motd Set the motd of the server when it is not undergoing maintenance. ```yaml motds: firstLine: "&b&o■ &8┃ &b&lBungeeSystem &8&l» &7&ov1.1.0 &8┃ &b&o■" secondLine: " &7Created by &8● &4&lHerrTechniker" ``` ### Default configuration #### config.yml ```yaml motd: maintenance: permission: "bungeesystem.maintenance.use" aliases: - "wartung" ``` #### motd.yml ```yaml maxPlayers: 100 whitelist: [] maintenance: enabled: false motds: firstLine: "&b&o■ &8┃ &b&lBungeeSystem &8&l» &7&ov1.1.0 &8┃ &b&o■" secondLine: " &4&lMaintenance" protocolText: "&8➜ &c&lMaintenance &8┃ &c✘" motds: firstLine: "&b&o■ &8┃ &b&lBungeeSystem &8&l» &7&ov1.1.0 &8┃ &b&o■" secondLine: " &7Created by &8● &4&lHerrTechniker" ``` {% file src="/files/FqZ9WWfHsdYt7Iz3BUYu" %} ## Command ### Syntax ``` /maintenance ``` # Move Schiebe einen Spieler zu einem anderen oder auf einen Server ### Prefix The prefix is exchanged with `%prefix%` (placeholder) in the message files. If you execute the command and enter the placeholder at the beginning of the message, it will be replaced with the prefix. This can be changed in `config.yml`. ```yaml prefix: "&7[&dMove&7]&r" ``` ### Permission To be able to execute the command for the Move module, you need the permission that is entered in `config.yml`. {% hint style="warning" %} The permission is a BungeeCord permission {% endhint %} ```yaml permission: "bungeesystem.move.use" ``` ### Aliases You can also define so-called aliases that you can enter instead of /move. To do this, simply add further points under the `aliases` item. ```yaml aliases: [] ``` ### Default configuration ```yaml move: prefix: "&7[&dMove&7]&r" permission: "bungeesystem.move.use" aliases: [] ``` ## Command ### Syntax ``` /move player /move server ``` # MSG Write private messages to other players ## config.yml ### Prefix The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`. ```yaml prefix: "&6MSG &7|&r" ``` ### Aliases You can also define so-called aliases that you can enter instead of /msg. To do this, simply add more points under the item `aliases`. ```yaml aliases: [] ``` ### Default configuration ```yaml msg: prefix: "&6MSG &7|&r" aliases: [] ``` ## Command ### Syntax ``` /msg ``` # Onlineteam A command to see every team member who is online. ## config.yml ### Prefix The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`. ```yaml prefix: "&bTeamonline &7|&r" ``` ### countOfTeamGroups Here you specify how many team groups you have on your network. Here is an example of the groups: Owner, Admin, Developer, Builder, Moderator, Supporter, etc. ```yaml countOfTeamGroups: 6 ``` ### teamGroups In the configuration teamGroups you define the name + prefix of the group, as well as the permission the player must have to be displayed when executing the command. {% hint style="warning" %} The important thing is that, as shown below, you start with the number 1 and end with the number you specified in the `coutOfTeamGroups` option. {% endhint %} ```yaml teamGroups: 1: name: "&4Owner" permission: "bungeesystem.onlineteam.owner" 2: name: "&cAdmin" permission: "bungeesystem.onlineteam.admin" 3: name: "&1Moderator" permission: "bungeesystem.onlineteam.moderator" 4: name: "&9Supporter" permission: "bungeesystem.onlineteam.supporter" 5: name: "&bDeveloper" permission: "bungeesystem.onlineteam.developer" 6: name: "&2Builder" permission: "bungeesystem.onlineteam.builder" ``` ### Aliases You can also define so-called aliases that you can enter instead of /onlineteam. To do this, simply add more points under the item `aliases`. ```yaml aliases: - "ao" - "adminonline" ``` ### Default configuration ```yaml onlineteam: prefix: "&bTeamonline &7|&r" countOfTeamGroups: 6 teamGroups: 1: name: "&4Owner" permission: "bungeesystem.onlineteam.owner" 2: name: "&cAdmin" permission: "bungeesystem.onlineteam.admin" 3: name: "&1Moderator" permission: "bungeesystem.onlineteam.moderator" 4: name: "&9Supporter" permission: "bungeesystem.onlineteam.supporter" 5: name: "&bDeveloper" permission: "bungeesystem.onlineteam.developer" 6: name: "&2Builder" permission: "bungeesystem.onlineteam.builder" aliases: - "ao" - "adminonline" ``` ## Command ### Syntax ``` /onlineteam ``` # Onlinetime With the Onlinetime module, players can view their time spent on your network. ## ## config.yml ### Prefix The prefix is used by default with every message. It can be set in the message files at the beginning of each message. To set it, simply write `%prefix%` (placeholder). This will then be exchanged by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&bOnlineTeime&7]&r" ``` ### show Under the configuration show you can set which "values" the player can see when entering the command. ```yaml show: seconds: true minutes: true hours: true days: true years: true ``` {% hint style="info" %} If the player has been on the server for only 1 minute, only 1 minute will be displayed. The same is if the player was online for 1 day, 2 hours 42 minutes and 9 seconds, only that will be displayed. {% endhint %} ### Aliases You can also define so called aliases which you can enter instead of /onlinetime. For this you simply add further points under the point `aliases`. ```yaml aliases: - "ot" ``` ### Default configuration ```yaml onlinetime: prefix: "&7[&bOnlineTeime&7]&r" show: seconds: true minutes: true hours: true days: true years: true aliases: - "ot" ``` ## Command ### Syntax ``` /onlinetime ``` # Party Play with other players so that only one needs to go on the server and everyone else follows. ## Party ### config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&5PARTY&7]&r" ``` ### switchServerMessage If this setting is set to `true`, the message that the party has changed the server will be displayed when the server is changed. ```yaml switchServerMessage: true ``` ### Whitelist If you are using CloudNet v3, the 1st step is to enable the CloudNet v3 module under modules in `config.yml`. Then enter the task name here. If CloudNet v3 is not enabled, you enter the individual names of the servers as they are entered in the config of the BungeeCord server. ```yaml # if cloudnet v3 in modules-section enabled, please enter the tasks where # the party members do not connect with the party leader whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" ``` ### defaultMembers Here you enter the default size of the party's each player may have. {% hint style="warning" %} The minimum number of the party has to be 2! {% endhint %} ```yaml # the value of default Members has a minimum of 2. By another unsupported value a # error message will send with "Info defaultMembers error" defaultMembers: 8 ``` {% hint style="info" %} With a value of `-1`, there is no limit to the maximum number of players in a party. {% endhint %} ### maxMembers Here you can define how many players can be in a party using bungeecord permissions. The structure is as follows: `permission;number of players` ```yaml maxMembers: - "bungeesystem.party.members.16;16" - "bungeesystem.party.members.32;32" - "bungeesystem.party.members.unlimited;-1" ``` ### Aliases You can also define so-called aliases that you can enter instead of /party. For this you simply add further points under the point `aliases`. ```yaml aliases: - "p" ``` ### Default Configuration ```yaml party: prefix: "&7[&5PARTY&7]&r" switchServerMessage: true # if cloudnet v3 in modules-section enabled, please enter the tasks where the party members do not connect with the party leader whitelist: - "BedWars4x1" - "BedWars4x2" - "BedWars4x4" - "MLGRush" - "GunGame" # the value of default Members has a minimum of 2. By another unsupported value a error message will send with "Info defaultMembers error" defaultMembers: 8 maxMembers: - "bungeesystem.party.members.16;16" - "bungeesystem.party.members.32;32" - "bungeesystem.party.members.unlimited;-1" aliases: - "p" ``` ### Commands #### Syntax | Command | Explanation | | ----------------------- | -------------------------------- | | /party help | Displays the help page | | /party list | Shows all players in the party | | /party leave | Leave a party | | /party toggleinvites | Enable/Disable party invitations | | /party accept \ | Accept a party invitation | | /party deny \ | Deny a party invitation | | /party kick \ | Exclude a player from your party | | /party invite \ | Invite a player to your party | ## Partychat Party chat is for sending messages to the party. Players can see these when they are in the party. ### config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&5PartyChat&7]&r" ``` ### Aliases You can also define so-called aliases that you can enter instead of /partychat. For this you simply add further points under the point `aliases`. ```yaml aliases: - "pc" ``` ### Default configuration ```yaml partychat: prefix: "&7[&5PartyChat&7]&r" aliases: - "pc" ``` ### Command #### Syntax ``` /partychat ``` # Ping The "ping" is the number of milliseconds it takes for an action to register on the server. ## config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&9Ping&7]&r" ``` ### Aliases You can also define so-called aliases that you can enter instead of /ping. For this you simply add further points under the point `aliases`. ```yaml aliases: [] ``` ### Permission To use the command `/ping` the player needs this bungeecord permission. By default this permission is set, but you can change it: ```yaml permission: "bungeesystem.ping.use" ``` ### Default configuration ```yaml ping: prefix: "&7[&9Ping&7]&r" permission: "bungeesystem.ping.use" aliases: [] ``` ## Command ### Syntax ``` /ping ``` # Pull Spieler ### Prefix The prefix is exchanged with `%prefix%` (placeholder) in the message files. If you execute the command and enter the placeholder at the beginning of the message, it will be replaced with the prefix. This can be changed in `config.yml`. ```yaml prefix: "&7[&bPull&7]&r" ``` ### Permission To be able to execute the command for the pull module, you need the permission that is entered in `config.yml`. {% hint style="warning" %} The permission is a BungeeCord permission {% endhint %} ```yaml permission: "bungeesystem.pull.use" ``` ### Aliases You can also define so-called aliases that you can enter instead of /pull. To do this, simply add further points under the `aliases` item. ```yaml aliases: [] ``` ### Default configuration ```yaml pull: prefix: "&7[&bPull&7]&r" permission: "bungeesystem.pull.use" aliases: [] ``` ## Command ### Syntax ``` /pull ``` # Punishment Das Punishment-System (Bestrafungssystem) ist eine Reihe an verschiedenen Modulen. Das Punishment System beinhaltet folgende Module: * [Ban System](/bungeesystem/module/punishment/ban) * [Mute System](/bungeesystem/module/punishment/mute) * [Check System](/bungeesystem/module/punishment/anderes/check) * [History System](/bungeesystem/module/punishment/anderes/history) * [Kick System](/bungeesystem/module/punishment/anderes/kick) # BanSystem Schließe Spieler von deinem Netzwerk aus. The following modules are integrated in the BanSystem: * [Ban](/bungeesystem/module/punishment/ban/ban) * [ReduceBan](/bungeesystem/module/punishment/ban/reduceban) * [TempBan](/bungeesystem/module/punishment/ban/tempban) * [UnBan](/bungeesystem/module/punishment/ban/unban) # Ban Exclude players from your network if they have done things they are not supposed to do. ## config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&6BanSystem&7]&r" ``` ### permanent Here you can enter how many Ban Points a player needs to be permanently banned. ```yaml # how many points for permanent ban permanent: 100 ``` ### autoBanOperatorName Here you specify the name that will be displayed on the ban screen when the player is banned for having too many ban points. ```yaml autoBanOperatorName: "AutoBanSystem" ``` ### autoBanOperatorUUID Here you specify the UUID of the [above operator name](#autobanoperatorname). ```yaml autoBanOperatorUUID: "00000001-0001-0001-0001-000000000001" ``` ### autoBanReason Here you specify the reason when the player is automatically banned from the system. ```yaml autoBanReason: "auto ban" ``` ### banReasons Here you enter how many ban reasons you want to define. You can change these in the[ message files](/bungeesystem/messages-files). ```yaml banReasons: 6 ``` ### infoMessageOther Here you can choose whether the team members of your network should receive a message when a player is banned. ```yaml infoMessageOther: true ``` ### Aliases You can also define so-called aliases that you can enter instead of /ban. For this you simply add further points under the point `aliases`. ```yaml aliases: [] ``` ### Default configuration ```yaml punishment: ban: prefix: "&7[&6BanSystem&7]&r" # how many points for permanent ban permanent: 100 autoBanOperatorName: "AutoBanSystem" autoBanOperatorUUID: "00000001-0001-0001-0001-000000000001" autoBanReason: "auto ban" banReasons: 6 infoMessageOther: true webhook: false aliases: [] ``` ## Command ### Syntax ``` /ban ``` # ReduceBan Reduce the ban of a player ## config.yml ### Prefix The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`. ```yaml prefix: "&7[&6BanSystem&7]&r" ``` ### infoMessageOther Here you can choose whether the team members of your network should receive a message when a player is banned. ```yaml infoMessageOther: true ``` ### Aliases You can also define so-called aliases that you can enter instead of /reduceBan. For this you simply add further points under the point `aliases`. ```yaml aliases: [] ``` ### Default configuration ```yaml punishment: reduceBan: prefix: "&7[&6BanSystem&7]&r" infoMessageOther: true webhook: false aliases: [] ``` ## Command ### Syntax ``` /reduceBan