Generelle Server & Plugin Befehle General Server & Plugin Commands

📂 Aktuelle Server-Struktur 📂 Current Server Structure

Existierende Welten: Existing Worlds:

  • lobby (Spawn & Hub)
  • world, world_nether, world_the_end (Survival)
  • world_EW_Castles (BedWars Map)

Geschützte Regionen: Protected Regions:

  • lobby_main (in Weltin world: lobby) - Kompletter SchutzFull protection
  • lobbyportal (in Weltin world: world) - Portal-Area
  • pagoda (in Weltin world: world) - Tempel-Schutz (Kein Abbau/PvP)Temple Protection (No Build/PvP)

📦 Installierte Plugins 📦 Installed Plugins

Plugin Name Funktion / BeschreibungFunction / Description
AngelChestSpeichert Inventar in Kiste bei Tod.Stores inventory in chest on death.
BedWars / SBAMinigame-Logik. Steuert Arenen, Shops, Teams.Minigame logic. Controls arenas, shops, teams.
BlueMap3D Web-Map (High Quality).3D Web-Map (High Quality).
bStatsMetriken (irrelevant für Gameplay).Metrics (irrelevant for gameplay).
ChunkyWorld-Generation Tool.World generation tool.
CitizensNPC-Management (Lobby/Shops).NPC management (Lobby/Shops).
DecentHologramsHologramme (Texte).Holograms (Floating text).
DirectionHUDZeigt Kompass/Richtung oben am Bildschirm.Shows compass/direction at top of screen.
FastAsyncWorldEditLeistungsstarker World-Editor (FAWE).High-performance world editor (FAWE).
floodgateAuth-Bridge für Bedrock.Auth-bridge for Bedrock.
Geyser-SpigotCrossplay-Bridge (Bedrock Spieler).Crossplay bridge (Bedrock players).
GeyserUpdaterAuto-Updater für Geyser beim Start.Auto-updater for Geyser on startup.
LuckPermsRechte-System (Admin, VIP, etc.).Permission system (Admin, VIP, etc.).
Multiverse-CoreWelten-Management.World management.
Multiverse-Inv...Inventar-Trennung zwischen Welten.Inventory separation between worlds.
Multiverse-Nether...Verknüpft Nether/End mit Welten.Links Nether/End to worlds.
Multiverse-PortalsPortale für Teleportation.Portals for teleportation.
PlaceholderAPIVariablen-Schnittstelle.Variable interface.
PluginPortalPlugin-Marktplatz im Spiel (Installieren/Updaten).In-game plugin marketplace (Install/Update).
sparkPerformance-Profiler.Performance profiler.
squaremap2D Web-Map (Schneller als BlueMap).2D Web-Map (Faster than BlueMap).
ToolStatsZeigt Statistiken auf Werkzeugen (Gebaute Blöcke etc.).Shows stats on tools (Blocks mined etc.).
ViaBackwardsErlaubt älteren Clients den Beitritt.Allows older clients to join.
ViaVersionErlaubt neueren Clients den Beitritt.Allows newer clients to join.
VoidGenGenerator für leere Welten.Void world generator.
WorldGuardRegion-Schutz (Lobby sichern).Region protection (secure lobby).
Hinweis zu Geyser/Floodgate:Note regarding Geyser/Floodgate:
Der GeyserUpdater sorgt dafür, dass Geyser bei jedem Neustart aktuell ist. The GeyserUpdater ensures Geyser is up-to-date on every restart.

Multiverse & NetherPortals (Welten)

# Multiverse Core /mv tp world_name # Teleportieren /mv list # Liste aller Welten /mv create name normal # Neue Welt erstellen /mv import ordner normal # Welt importieren /mv set spawn # Welt-Spawn setzen # Multiverse NetherPortals (Verknüpfung) # 1. HINWEG (Von Oberwelt nach Nether/End) /mvnp link nether world world_nether /mvnp link end world world_the_end # 2. RÜCKWEG (Wichtig für korrekten Spawn!) /mvnp link nether world_nether world /mvnp link end world_the_end world # Info anzeigen /mvnp show
Portal-Koordinaten (1:8 Regel): Wenn ein neues Portal entsteht statt beim Haus: Das Nether-Portal steht falsch. Es muss bei Oberwelt-Koords / 8 stehen.

Chunky (Welt-Generierung)

Warum Chunky?

Verhindert Server-Lags beim Fliegen (Elytra), indem die Welt vorgeneriert wird. Ohne Chunky muss die CPU Gelände live berechnen (Lag!).

Richtige Reihenfolge:

# 1. Oberwelt (Priorität 1) chunky world world chunky radius 5000 chunky start # 2. Nether (Priorität 2) chunky world world_nether chunky radius 5000 chunky start # 3. The End (Priorität 3) chunky world world_the_end chunky radius 5000 chunky start # Verwaltung chunky pause # Vor Neustart pausieren! chunky continue # Nach Neustart fortsetzen chunky progress # Fortschritt anzeigen

Schutz & Bauen (WorldGuard & FAWE)

# WorldGuard (Regionen schützen) # 1. Markieren mit Holzaxt (//wand) -> Pos1 & Pos2 # 2. Vertikal erweitern: //expand vert /rg define lobby_main # Region erstellen /rg flag lobby_main build deny # Bauen verbieten /rg flag lobby_main pvp deny # PvP verbieten /rg flag lobby_main interact allow # Knöpfe erlauben /rg bypass # Admin-Modus (Bauen trotz Schutz) # FAWE (Terraforming - Pinsel) # Werkzeug (Schwert/Schaufel) in die Hand nehmen! /br sphere stone 4 # Stein-Kugel Pinsel /mask 0 # Maske: Nur Luft ersetzen /br smooth 5 # Glätten /none # Pinsel löschen # FAWE (Schematics Import) # Upload .schem file to 'plugins/FastAsyncWorldEdit/schematics' //schem load <name> # Load into clipboard //rotate 90 # Optional: Rotate //paste # Paste at your location //undo # Undo if wrong

BlueMap (3D Web-Map)

# Rendering Global /bluemap stop # Pausiert alles (auch nach Neustart) /bluemap start # Setzt alles fort # Map Reset (Welt neu rendern) /bluemap purge world # Löscht Map-Daten -> Rendert SOFORT neu! # Map Updates verhindern /bluemap freeze world # Keine Updates mehr für diese Welt /bluemap unfreeze world # Updates wieder aktivieren

NPCs, Hologramme & Portale

# Multiverse Portals (Teleporter) # Mit Holzaxt markieren (wie WorldGuard) /mvp create name w:zielwelt /mvp remove name /mvp select name # Citizens (NPCs) /npc create "&cName" --type villager /npc look # NPC schaut Spieler an /npc skin SkinName /npc cmd add -p bw join castles # Befehl hinzufügen # DecentHolograms (Schwebender Text) /dh create name "Zeile 1" /dh line add name "Zeile 2" /dh move name here /dh delete name # Vanilla Text Display (Ohne Plugin) /summon text_display ~ ~ ~ {text:{"text":"TEXT","color":"green","bold":true}} /kill @e[type=text_display,distance=..3,limit=1] # Löschen (daneben stehen!)

Verwaltung & Utility (LuckPerms, Maps, etc.)

# LuckPerms (Rechte) /lp editor # Web-Editor öffnen (Empfohlen!) /lp user <Name> parent set <Gruppe> /lp group <Gruppe> permission set <Recht> # PluginPortal (Installer) /pp search <Name> # Plugin suchen /pp install <Name> # Installieren # Squaremap (2D Karte) /squaremap fullrender world /map hide # Spieler verstecken # DirectionHUD & ToolStats /dh toggle # Kompass an/aus /tstats # Item-Stats anzeigen # Admin Basics /gamemode creative /whitelist add <Name> /gamerule doMobSpawning false

⚰️ AngelChest & Bedrock Crossplay ⚰️ AngelChest & Bedrock Crossplay

✅ Config Fix Applied (2026-01-08)

Das "Item-Verlust" Problem wurde durch eine Config-Änderung behoben.

Die Ursache: Bedrock-Spielernamen beginnen mit einem Punkt (z.B. .Kamechan42). AngelChest nutzte den Spielernamen direkt als Dateinamen für die Kiste. Auf dem Linux-Betriebssystem des NAS (QNAP) werden Dateien, die mit einem . beginnen, als "Versteckte Systemdateien" behandelt. Das Plugin erstellte die Datei, konnte sie aber Sekunden später nicht mehr "sehen", was zum Absturz und Item-Verlust führte.

Die Lösung: Wir haben in der Config ein Prefix hinzugefügt: chest-filename: "ac_{player}...".
Dadurch heißen die Dateien jetzt ac_.Kamechan42... und sind für Linux und das Plugin sichtbar.
The "Item Loss" issue was fixed via config change.

The Cause: Bedrock usernames start with a dot (e.g., .Kamechan42). AngelChest used the username directly as the filename. On the NAS Linux OS, files starting with . are treated as "Hidden System Files". The plugin created the file but couldn't "see" it seconds later, causing a crash and item loss.

The Fix: We added a prefix in the config: chest-filename: "ac_{player}...".
Files are now named ac_.Kamechan42... and are visible to Linux and the plugin.

📄 Komplette config.yml anzeigen (Backup)
######################### ##### AngelChest ##### ######################### # written by mfnalex / JEFF Media GbR # Support: https://discord.jeff-media.com ##### WARNING! ##### # This file contains UTF8 symbols! You MUST use a proper text editor like Notepad++ to edit this file! # If you use some kind of "online editor", your file is likely to break and reset to the default values! # If this [♥] doesn't look like a heart, you MUST use another text editor, because yours doesn't support UTF-8! ##### WARNING! ##### ############################# ##### Permissions ##### ############################# # The following permissions are available: # # angelchest.use Spawns AngelChest on death instead of dropping the items # angelchest.protect The AngelChest is locked for other players # angelchest.protect.ignore Players can open other player's locked AngelChests # angelchest.fetch Allows the player to teleport their chests to them # angelchest.tp The player can teleport to their AngelChests # angelchest.preventvictimchest Prevents players getting killed by this player to get an AngelChest spawned # angelchest.preview Allows the player to preview their AngelChests' contents in /acgui # angelchest.toggle Allows to enable/disable AngelChest per player # angelchest.ignorepreventbuilding Allows to build in the radius around other player's AngelChests (see prevent-building-in-radius) # angelchest.others Allows to run /actoggle, /aclist, /actp, /acfetch and /acunlock for other players # angelchest.reload Allows reloading the config using /acreload # angelchest.debug Allows to use the debug command /acdebug # angelchest.version Allows to use the version command /acversion # The following permissions are given to everyone by default: # # angelchest.list Allows to use the list command /aclist (also requires angelchest.use) # angelchest.gui Allows to use the GUI command /acgui (also requires angelchest.use) # angelchest.unlock Allows the player to unlock their protected chests using /acunlock # angelchest.open Allows the player to open a nearby AngelChest using /acopen ############################# ##### Player Commands ##### ############################# # The following player commands are available: # # /acgui Permission: angelchest.use # Opens the AngelChest GUI, listing all your AngelChests with buttons for teleporting to, # fetching and unlocking each chest # # /aclist Permission: angelchest.use # Shows a list of your AngelChests, including links for teleporting to, fetching and # unlocking each chest. This is basically the "chat-only" version of /acgui # # /acopen Permission: angelchest.open (and angelchest.open.) # Opens a nearby AngelChest without having to physically interact with it. # # /acfetch [chestID] Permission: angelchest.fetch # Teleports one of the chests to the player # # /actp [chestID] Permission: angelchest.tp # Teleports the player to one of their chest # # /acunlock [chestID] Permission: angelchest.protect and angelchest.unlock # Unlocks one of your AngelChests if you have the angelchest.protect permission # # /actoggle [player] Permission: angelchest.toggle # Enables/disables AngelChest for this player. # Also requires permission angelchest.others when changing other player's settings. ############################# ##### Admin Commands ##### ############################# # The following player commands can also be used by admins/console to specify a target player: # # /aclist Permissions: angelchest.use and angelchest.others # Shows a list of 's AngelChests, including links for # teleporting to, fetching and unlocking each chest. # # /acfetch [targetPlayer] Permissions: angelchest.fetch and angelchest.others # Teleports one of 's chests to [targetPlayer], or to # the command sender if [targetPlayer] is not specified. If ran # from console and [targetPlayer] is not specified, the chest will # be teleported to its owner. # # /actp [targetPlayer] Permissions: angelchest.tp and angelchest.others # Teleports [targetPlayer] to one of 's chests, or to # the command sender if [targetPlayer] is not specified. If ran # from console and [targetPlayer] is not specified, the chest owner # will be teleported. # # /acunlock Permissions: angelchest.protect, angelchest.unlock and angelchest.others # Unlocks one of 's AngelChests # The following admin commands are available: # # /acgraveyard Permission: angelchest.admin # Manage graveyard settings # # /acadmin Permission: angelchest.admin # Admin commands # # /acversion Permission: angelchest.version # Prints plugin version, whether you have the Plus version and what server software # you are using. # # /acreload Permission: angelchest.reload # Reloads the config # # /acdebug Permission: angelchest.debug # AngelChestMain debug command. Enter /acdebug for more information # Note: You can add new command aliases, see "Command Settings" at about line 800 in this config.yml ############################ ##### Information ##### ############################ # You can use color codes everywhere. # # Hex colors can be used in three different styles: # - <#ff0000>Your Text # - &#ff0000Your Text # - &x&f&f&0&0&0&0Your Text # # You can also use gradients, for example: # - <#ff0000> Red to white <#/ffffff> # - <#ff0000> Red to white <#/ffffff> to red <#/ff0000> # # PlaceholderAPI works in most messages, but not all. Let me know when I missed a message. # ItemsAdder emojis & similar features from other plugins should also work, if not: https://discord.jeff-media.com :) # # AngelChest also has builtin PlaceholderAPI placeholders, see here: https://github.com/mfnalex/AngelChest/blob/master/PlaceholderAPI.md ############################ ##### General settings ##### ############################ # After this amount of seconds, the AngelChest is automatically destroyed # and drops its contents. Use 0 for infinite duration. # You can override this for certain players by setting up groups and # giving players the angelchest.group. permission. See # groups.example.yml for more information. # Default is 600 seconds = 10 minutes angelchest-duration: 0 # The "angelchest-duration" (see above) for players who died in PvP. # Use 0 for infinite duration. # When set to -1, it uses the same value as the normal "angelchest-duration" setting. angelchest-duration-in-pvp: -1 # If players have their chests protected (angelchest.protect permission), # you can define a duration in seconds to automatically unlock the chests. # Use 0 to never automatically unlock chests. # You can override this for certain players by setting up groups and # giving players the angelchest.group. permission. See # groups.example.yml for more information. # Default is 0 = never # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! unlock-duration: 0 # When set to true, countdowns (angelchest-duration, angelchest-duration-in-pvp, unlock-duration) # only count down while the player is online ("online time"). # When set to false (default), countdowns use "real time" # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! suspend-countdowns-when-player-is-offline: false # The maximum amount of AngelChests a player may have at the same time. # If a player dies again so that they would exceed this number, the # first created AngelChest is either destroyed or drops its contents. # (See option below) # You can override this for certain players by setting up groups # and giving players the angelchest.group. permission. # See groups.example.yml for more information. max-allowed-angelchests: 5 # When a player has reached the above defined "max-allowed-angelchests" limit, # their oldest AngelChest is either destroyed (without dropping its contents) # or dropping all its contents. # When set to "drop", the oldest AngelChest will drop its contents once the # limit is reached. # When set to "delete", the oldest AngelChest will disappear without dropping # anything max-allowed-angelchests-behaviour: drop # When true, the AngelChest drops its contents when it expires # When false, all contents disappear drop-contents-when-expired: true # You can disable spawning the AngelChest when a player has been killed by # another player. By default, the AngelChest will always spawn. allow-angelchest-in-pvp: true # When set to true, AngelChests created by players who died in PVP will not # be protected from other players. dont-protect-chest-if-player-died-in-pvp: false # When true, the XP (see "xp-percentage" below) is collected, too. # When false, XP drops normally # When set to "nopvp", the XP is not collected if the player died during PvP. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! (Free version always stores the vanilla XP amount) collect-xp: true # Amount of XP the player keeps within their chest on death. # 1.0 = 100%, 0.5 = 50%, etc. # When set to 0, all XP is lost. # When set to -1, use vanilla amount # You can override this for certain players by setting up groups # and giving players the angelchest.group. permission. # See groups.example.yml for more information. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! (Free version always uses vanilla XP amount) xp-percentage: -1 # Global chance for spawning an AngelChest # 1.0 = 100%, 0.5 = 50%, 0.01 = 1% # Example: setting this to 1.0 will always spawn a chest, setting it to # 0.5 will only spawn it with a probability of 50% # You can override this for certain players by setting up groups and # giving players the angelchest.group. permission. See # groups.example.yml for more information. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! spawn-chance: 1.0 # You can define an amount of item stacks that will be randomly lost on death. # You can also adjust the item loss individually for each group. See groups.example.yml # You can also add the letter "p" to the end of the number to use percentages. # E.g. when using "0.2p", 20% of item stacks will be lost. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! random-item-loss: 0 # When false, random-item-loss deletes full stacks (e.g. you have one full stack of cobblestone, and one full stack dirt, # and random-item-loss is "0.5p", then one of those stacks will be deleted fully. # If true, the stacks will be split and you will lose e.g. 40 cobblestone and 22 dirt. random-item-loss-split-stacks: false # When true, all items that would be lost due to "random-item-loss" will be dropped instead of just be removed random-item-loss-drop: false # When set to true, the random-item-loss defined above will NOT apply to enchanted items! # That means that enchanted items will always be stored in the AngelChest regardless of random item loss chance. random-item-loss-ignores-enchanted-items: false # When set to true, the random-item-loss defined above will NOT apply to shulkerboxes! random-item-loss-ignores-shulkerboxes: false # When set to higher than 0, players dying outside of PvP will get a cooldown before the next AngelChest can be spawned (in seconds) # This is separate from the "pvp-cooldown". ## PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! cooldown: 0 # When set to higher than 0, players dying in PvP will get a cooldown before the next AngelChest can be spawned (in seconds) # This is separate from the (non-pvp) "cooldown". # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! pvp-cooldown: 0 # When set to true, players will receive a message telling them where the AngelChest # is located, including clickable links to teleport, fetch or unlock the chest if # the player has permission for those commands. show-location: true # When set to true, players will receive the list of AngelChests again after rejoining. show-location-on-join: true # Whether to show a message to the AngelChest owner when other players open or empty their chest # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! show-message-when-other-player-opens-angelchest: true show-message-when-other-player-empties-angelchest: true # When true, dead players will automatically get the AngelChest GUI opened after # they respawn if they have at least one AngelChest. # Possible values: # true - Opens the main GUI showing all AngelChests or the latest if you only have one # latest - Opens the GUI showing the latest AngelChest only # false - Do not open the GUI automatically # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! show-gui-after-death: false # When "show-gui-after-death" is enabled ("latest" or "true"), only show the GUI if the # player has access to either teleport or fetch the chest. If not, do not open the GUI only-show-gui-after-death-if-player-can-tp-or-fetch: true # You can choose the Material to use for the AngelChest, # e.g. CHEST, ENDER_CHEST, OBSIDIAN, ... # It's also possible to use custom heads here, or custom blockdata, or even blocks from ItemsAdder and Oraxen. # # Note for ItemsAdder users: ItemsAdder blocks are 100% supported! ItemsAdder furniture is experimental. # Note for Oraxen users: Oraxen blocks and Oraxen furniture are 100% supported! # Note for Nexo users: Nexo blocks and Nexo furniture are experimental. # # IMPORTANT: You must use "double quotes" here! # # Examples: # material: "DIRT" (will use a dirt block) # material: "head:player" (will use the player's head) # material: "head:somebase64string" (will use that custom base64 texture) # material: "minecraft:red_candle[candles=3,lit=true]" (will use 3 red, lit candles) # material: "itemsadder:iasurvival:ruby_ore" (will use Ruby Ore from ItemsAdder) # material: "oraxen:ruby_ore" (will use Ruby Ore from Oraxen) # material: "nexo:ruby_ore" (will use Ruby Ore from Nexo) #material: "CHEST" #material: "head:player" #material: "head:eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZmViY2M2YmYzYTA5Yzg5MTQ1OWVjODYyYWMzOWU0Mzc1Y2MyZGRiYmYzODg0OTZjOGU0YmNjY2ExZTI4OThlIn19fQ==" #material: "MOSSY_COBBLESTONE_WALL" material: "SKELETON_SKULL" # You can choose another Material to use for unlocked AngelChests. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! use-different-material-when-unlocked: false material-unlocked: "ENDER_CHEST" # When true, AngelChest will spawn the chest at the last location where a player was standing # before he died in the void. When false, the chest will spawn at Y=1 void-detection: true # When true, AngelChest will avoid spawning a chest inside lava seas and instead spawns it nearby lava-detection: true # When false, AngelChests will not be spawned for players who died in lava # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! allow-chest-in-lava: true # When false, AngelChests will not be spawned for players who died in the void # NOTE: The vanilla /kill command will cause void damage, so when you set this to # false, using /kill or /minecraft:kill will prevent the AngelChest from spawning # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! allow-chest-in-void: true # When set to a value above 0, players will get invulnerability for this amount of seconds # after teleporting themselves to their chest. # Consider to only use this when you set a price for teleporting the chest, otherwise it # could be abused. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! invulnerability-after-tp: 0 # When set to true, players will NOT get their armor equipped automatically on fast-looting # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! In the free version, auto-equipping is # always allowed. prohibit-auto-equip: false # You probably don't want your AngelChest to spawn on blocks like GRASS_PATH, FARMLAND, etc. # as that would destroy those blocks. You can blacklist them here so AngelChest searches # for a spot nearby. dont-spawn-on: - FARMLAND - GRASS_PATH - DIRT_PATH - LAVA # You can specify inside which existing blocks the AngelChest may spawn. If the block where # the player died is not in this list, AngelChest searches for a spot nearby. only-spawn-in: - AIR - CAVE_AIR - WATER - SNOW - SHORT_GRASS # When the block where the player died doesn't match "dont-spawn-on" and "only-spawn-in" # we will search for another block inside max-radius. Default is 10 blocks. # If there is absolutely no free space inside this radius, the chest # is spawned exactly where the player died and may replace an existing block, so # do not set this value too low. max-radius: 10 # Searches for a new chest location if there isn't at least this amount of air above the chest. minimum-air-above-chest: 0 # When enabled, and a player dies in lava, the chest will always spawn on at least the player's # Y level, to avoid them being spawned in some caves below a lava ocean avoid-lava-oceans: false # When absolutely no block inside "max-radius" is found, and the block where the player # died is bedrock, we can search for another block to replace instead of bedrock. never-replace-bedrock: true # Remove curse of vanishing / curse of binding items from the chest? remove-curse-of-vanishing: true remove-curse-of-binding: false # When true, totems of undying will work in every inventory slot # When false, they only work in the hand/off-hand slot (vanilla default) totem-of-undying-works-everywhere: true # When true, players who have an AngelChest spawned will be shown the Totem of Undying animation # If you are using a custom resource pack, you can also enter a custom model data to change # the appearance of the totem # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! play-totem-animation: false totem-custom-model-data: 0 # When enabled, AngelChest will handle player respawns. They will be automatically respawned after death once # the delay (see option below) has expired auto-respawn: false # When auto-respawn is true, you can define a delay in seconds before the player is respawned. auto-respawn-delay: 10 # When a player decides to disable AngelChests from spawning using /actoggle and the following option # is set to true, then all existing AngelChests from this player will be broken and drop its # contents. If the player had to pay money for having the chest spawned and you set "refund-expired-chests" # to true, the player still will not be refunden as it was their own decision to have their chests broken. using-actoggle-breaks-existing-chests: true # When true, AngelChest loads all chunks asynchronously to avoid lags when players are teleporting # to one of their chests. This only works on Paper and its forks, but you do NOT have to disable # this if you do not use Paper. On very slow servers, users could experience a small pause # between starting the teleport and actually being teleported when this is enabled. This is NO lag, # it's just AngelChest waiting for the server to load the chunks instead of "force loading" them. # If you don't know what this means: just leave it enabled async-chunk-loading: true # Should we check for updates? # When enabled, a message is printed in the console if a new version has # been found, and OPs will be notified when they join the server. # When set to true, we will check for updates on startup and every X hours # When set to on-startup, we will only check on startup # When set to false, don't check for updates check-for-updates: false # When check-for-updates is true, AngelChest will check every X hours check-interval: 24 ########################################### #### Prevent building near AngelChests #### ########################################### # When higher than 0, players cannot place blocks within this radius around other player's AngelChests # Players with permission "angelchest.ignorepreventbuilding" are not affected by this prevent-building-in-radius: 0 # When higher than 0, players cannot break blocks within this radius around other player's AngelChests # Players with permission "angelchest.ignorepreventbuilding" are not affected by this prevent-breaking-in-radius: 0 # When true, "prevent-building-in-radius" and "prevent-breaking-in-radius" only applies to protected chests. # When false, it applies to unlocked chests too only-prevent-building-in-radius-for-protected-chests: true ######################### #### Death maps #### ######################### # You can make players get a map with their AngelChest location when they respawn. # This allows them to easily go back to their death location. # Note: If you still get death maps, even though this option is set to false, you probably have another plugin # causing this (ItemsAdder maybe?). # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! death-maps: false # When set to true, death Maps created by AngelChest will never be put into any # AngelChests on the next death. This avoids filling up inventories when dying several times in a row. dispose-death-maps: true # You can change the marker type to be used. See here for a list of valid marker types in the latest MC version: # https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/map/MapCursor.Type.html death-map-marker: RED_X death-map-name: "AngelChest" death-map-lore: "X: {x}\nY: {y}\nZ: {z}" ######################### #### Player heads #### ######################### # You can have AngelChest drop the player's head when they die. # Important: If you want to use a player head for the chest itself, see the "material" option instead. # Note: The head will only drop if the player has an AngelChest spawned. # That means that no heads will drop when the player does not have the # angelchest.use permission, if they don't have enough money for the chest, # or if they die in a blacklisted world / region etc. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! drop-heads: false # When set to true, heads are only dropped when a player dies in PvP only-drop-heads-in-pvp: true # Time in seconds since the last PVP hit until a player is not considered to be in PVP anymore # If set to 0, only the last hit is considered only-drop-heads-in-pvp-cooldown: 10 # When set to true, heads are dropped next to the AngelChest instead of being put inside dont-store-heads-in-angelchest: true # The head's name and lore. Set to an empty string ("") to disable. # You can use any PAPI placeholder and the following placeholders: # {player} Name of the player who died # {deathcause} Name of the killer, or LAVA, VOID etc. when not killed in PvP head-name: "{player}'s head" head-lore: "Brutally murdered\nby {deathcause}" ######################### #### Graveyards #### ######################### # PREMIUM FEATURE: Only available in AngelChest Plus! # You can define graveyards to use for spawning AngelChests instead of the player's # death location. # IMPORTANT: Please see the graveyards.example.yml file for more information. # Everything defined here are the GLOBAL graveyard settings. You can define # individual graveyards in the graveyards.yml file. You must rename the # graveyards.example.yml file to graveyards.yml to enable Graveyard features. # When enabled, player's AngelChests will NOT be spawned in the graveyards, but # at their death location. The graveyards will then only be used to respawn players # after they died. All defined "grave locations" will then be used as possible # respawn points, unless a global spawn has been set for that graveyard. # When this is enabled, players will also respawn at graveyards even when # they didn't get an AngelChest because their inventory was empty. use-graveyard-only-as-respawn-point: false # What happens when the closest graveyard in the current world is full? # When true, AngelChest will search for the next graveyard in the same world. # When false, or when all graveyards in this world are full, see option below try-closest-graveyard: true # What happens when all graveyards in this world are full, or when there are no # graveyards defined for this world? # When true, AngelChest will try to bury the player at the global graveyard. # When false, or when the global graveyard is also full, see option below try-global-graveyard: true # What happens when the global graveyard is full too? # When true, AngelChest will spawn the chest at the player's death location. # When false, the player will die like in vanilla and does not get any AngelChest. fallback-to-deathlocation: true ######################### #### Economy #### ######################### # You can set up a certain price for some actions. This will only work if you # use Vault and a supported economy plugin. # If you need more options to adjust the prices for certain actions, please # leave a message in the SpigotMC discussion or open an issue at GitHub. # If you request a feature in the review section, it will probably be ignored. # You can also adjust those prices individually for each group. See groups.example.yml ###### Using Percentages/Min/Max Prices ##### # In AngelChest Plus, you can also use percentages of the player's balance: # price-example1: 50% (50% of player's balance) # # It is also possible to define a minimum and/or maximum price: # price-example2: 10%,min=1000 (10%, but at least 1000) # price-example3: 50%,max=1000 (50%, but at most 10000) # price-example4: 30%,min=500,max=10000 (30%, but at least 500 and at most 10000) # # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! ###### Using Items instead of money ##### # You can also use certain items that have to be "paid" with instead of money. # See items.yml file for more information # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! ##### # How much does it cost to teleport yourself to one of your AngelChests? # If you want to use an item, simply use "price-teleport: item-name" (see items.yml) (Premium version only) price-teleport: 0 # How much does it cost to teleport your AngelChests to you? # I suggest you make this cheaper than "price-teleport" because teleporting to # your death location is probably more useful than just getting your stuff back. # If you want to use an item, simply use "price-fetch: item-name" (see items.yml) (Premium version only) price-fetch: 0 # How much does it cost to spawn the AngelChest? The amount will automatically # be taken from the player on death if they have enough money, otherwise # the chest will not spawn and the items drop normally # If you want to use an item, simply use "price: item-name" (see items.yml) # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! price: 0 # You can refund the price when a player does not to open their AngelChest # before it expires refund-expired-chests: false # How much does it cost for a player to open a chest? Each player will only be # charged once per chest. # If you want to use an item, simply use "price-open: item-name" (see items.yml) # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! price-open: 0 # When set to true, players must confirm teleporting to or fetching a chest if you set a price for those actions # by entering the same command again or by clicking on a text message in the chat confirm: true # When set to true, no player will be able to place ANY custom AngelChest items. prevent-placing-custom-items: true # The format used to display prices in chat messages or GUIs. # Must be valid format for Java's String#format() method. # Only change this if you know what you are doing! # The default is %,.2f which means two decimal places and a comma as thousands separator. # If you want to use dots as thousands separator, use %.,2f price-format: "%,.2f" ################################# #### Max. TP/Fetch distance ##### ################################# # If the following options are set to false, players will have to be in the same # world to teleport to or to fetch their chests allow-tp-across-worlds: true allow-fetch-across-worlds: true # You can set a max distance for players who want to tp or fetch their AngelChest. # If set to 0, players can teleport/fetch regardless of the distance to their chest. # When using this, consider to disallow TPing or fetching between worlds because # otherwise players could just bypass this by going into another world. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! Free version will always use 0 max-tp-distance: 0 max-fetch-distance: 0 # The maximum allowed distance for players to use /acopen. Can be overriden # using permission "angelchest.open.", e.g. "angelchest.open.5" for 5 blocks max-open-distance: 5 # You can also set a minimum distance to avoid players teleporting to their chest or # fetching it, for example to avoid them accidentally clicking the link twice and # having to pay the price again. min-distance: 0 # When set, a player has to stand still for this amount of seconds before they # get teleported # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! tp-wait-time: 0 # Which color to use for the teleportation bossbar. # See here for possible values: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/boss/BarColor.html tp-bossbar-color: GREEN ################################# #### Sounds for TP / Fetch ##### ################################# # You can have sound effects when fetching or teleporting to your chests, if you feel like it. # See here for the sound names of the current version: # https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Sound.html # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! Free version will always use 0 play-sound-on-tp: true play-sound-on-fetch: true sound-effect: ENTITY_EXPERIENCE_ORB_PICKUP sound-volume: 1.0 sound-pitch: 1.0 sound-channel: BLOCKS ######################### #### Disabled items #### ######################### # Some plugins have items that you automatically get back after death. To # avoid those from being duplicated, you can just enter their material # type here. Future versions will also allow to filter for items by # lore or custom name and more 3rd party plugins hooks # You can also use blacklist.yml for more detailed filtering. It allows you # to filter items by name, lore, PDC Keys (or NBT tags), custom model data, # and more. It also lets you allow to define whether blacklisted items should # drop normally or be deleted. # Example: # disabled-materials: # - WOODEN_HOE # - COMPASS disabled-materials: ######################### #### Disabled worlds #### ######################### # You can disable AngelChest for certain worlds. Each world's name has to # be on a separate line, starting with a hyphen and followed by a space # Example: # # disabled-worlds: # - world_nether # - world_the_end disabled-worlds: ########################## #### WorldGuard Flags #### ########################## # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! # AngelChestPlus currently has one custom WorldGuard flag: # allow-angelchest: # Whether or not spawning of AngelChests is allowed in a region (Default: allow) ########################## #### WorldGuard #### ########################## # You can disable AngelChest for certain WorldGuard region. Each region's name has to # be on a separate line, starting with a hyphen and followed by a space # Example: # # disabled-worldguard-regions: # - spawn # - pvparena disabled-worldguard-regions: # If, for some reason, you get errors using WorldGuard and AngelChest together, you can # disable the WorldGuard integration, but this will also mean you cannot disable # AngelChest in certain regions. If you get errors, please open an issue at github # or join our discord: https://discord.jeff-media.de disable-worldguard-integration: false ######################### ## Protection plugins ## ######################### # AngelChest can check if a player has permissions to place blocks where he died. If # the player is prohibited from placing blocks there, AngelChest will not spawn a # chest if the following option is set to true. # Fetching chests into areas where players cannot build will also be prohibited. only-spawn-chests-if-player-may-build: false # When true, AngelChest additionally calls a BlockPlaceEvent to check if a player is allowed # to build at a certain location. Only enable this if "only-spawn-chests-if-player-may-build" # isn't working for you. only-spawn-chests-if-player-may-build-check-blockplaceevent: false ######################### ## Other plugins ## ######################### # AngelChest can hook into certain 3rd party plugins to improve the chest # generation. None of those plugins is required, and you do NOT have to # disable the integration if a certain plugin is not installed. # Some plugins add additional drops to the death of a player. AngelChest can detect # those. If you experience any duplication issues, try disabling this setting. detect-additional-drops: true # If you use a plugin that logs player deaths, you can set this option to true. # This will however prevent the "slot" option in blacklist.yml to work and might also # cause issues with other plugins. dont-clear-inventory: false # Some plugins offer a telekinesis enchant that prevent getting AngelChests spawned # when a player with telekinesis kills another player. # This is intended behaviour. If you still want the victim to get an AngelChest, # you can disable telekinesis for PVP kills in your enchantment plugins' config. # You also have to set the following option to true. # If you simply set this to true WITHOUT telling your enchantment plugin to not # make telekinesis work on players, you MIGHT be getting duplicated items! ignore-telekinesis: false # When you have Slimefun installed, AngelChest can check for "Soulbound" items # and prevent those from being put into the chest. use-slimefun: true # When you have ExecutableItems installed, AngelChest can check for "Keep on Death" # items and prevent those from being put into the chest. use-executableitems: true # There are many other plugins adding "Soulbound" items. AngelChest can try # to detect those as well and prevent those from being put into the chest. check-generic-soulbound: true # EliteMobs' soulbound feature is a bit different. Those items will NOT be # kept on death, but they would be detected by the generic soulbound detection. # If you set the following option to false, EliteMobs' soulbound items will # behave like "normal" soulbound items, meaning they will be kept in your # inventory on death. If the option is set to true, the items will behave # like normally when using EliteMobs: the items will go into the chest like # regular items. exempt-elitemobs-soulbound-items-from-generic-soulbound-detection: true # When using Lands, and the player gets killed by another player they are # at war with, they will not get a death chest when set to true # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! lands-dont-protect-when-at-war: false # Some plugins make you keep your items on death, e.g. Essentials when you are /op. # AngelChest respects that, but you can also set the following option to true to always # get a chest, regardless of the keepInventory flag. # Note that many plugins (including EssentialsX) also clear your drops list for # totally retarded reasons, although it's not needed and prevents AngelChest # from detecting the drops. If you get the message that your inventory was empty # on death, try setting the "event-priority" below to LOWEST, then raise it slowly # to the highest possible value where it still works. ignore-keep-inventory: true # If set to true, AngelChest will try to only spawn chests INSIDE the world border as dictated by WorldBorderAPI. # If set to false, AngelChest doesn't care about what WorldBorderAPI says. use-worldborder-api: true # When true, players who are currently in combat cannot fast-loot AngelChests combatlogx-prevent-fastlooting: false # Placement settings when using Nexo or oraxen furniture as chest material # See here for valid BlockFaces: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/block/BlockFace.html nexo-oraxen-furniture-yaw: 0 nexo-oraxen-furniture-face: DOWN # You can define the priority on which AngelChest detects the player's drops. When you use plugins to # manipulate what items a player drops on death, consider setting this to a high value (e.g. HIGHEST # or MONITOR). # If you experience problems with some items not being put into the chest but being dropped next to it, # try to lower the priority of AngelChest until the drops get detected. # If you have problems with the chest not spawning at all (but remaining in the player's inventory), # consider using a low priority (e.g. LOWEST) # Available priorities (from high to low): MONITOR, HIGHEST, HIGH, NORMAL, LOW, LOWEST # I HIGHLY SUGGEST YOU LEAVE THIS ON HIGHEST! ONLY CHANGE THIS IF KNOW WHAT YOU ARE DOING! # WHEN IN DOUBT, CONTACT ME ON DISCORD: https://discord.jeff-media.de event-priority: HIGHEST # Some outdated plugins cause trouble when interacting with invisible armor stands (holograms). # Only set the following option to "true" if you really know what you are doing! disable-interacting-with-holograms: false # If true, AngelChest tries to ignore deaths of NPCs (players that aren't actual players) try-to-ignore-npc-deaths: true # Miscellaneous plugins might cause issues when not force-closing inventories on AngelChest spawn. # Normally, you don't want to change these options and keep them both enabled. force-close-open-inventory-on-angelchest-spawn: true call-inventory-close-event-manually-if-needed: true ######################### ##### Localization ###### ######################### # In the following configuration sections, you can use color and # formatting codes for all text messages. # Available color codes: # &0 Black &6 Gold &c Red # &1 Dark Blue &7 Gray &d Light Purple # &2 Dark Green &8 Dark Gray &e Yellow # &3 Dark Aqua &9 Blue &f White # &4 Dark Red &a Green # &5 Dark Purple &b Aqua # Available formatting codes: # &k Obfuscated &m Strikethrough # &l Bold &o Italic # &n Underline &r Reset ######################### ##### Hologram ###### ######################### # {player} The player's name. # {time} Time until the chest despawns # {items} Number of items the chest contains # {xp} Number of XP the chest contains # {deathcause} Name of the killer, or LAVA, VOID etc. when not killed in PvP # {protected} Protection status - PREMIUM FEATURE - see option below! # \n New line # The default hologram contains all options mentioned above except {protected} # The hologram text also allows you to use PlacerholderAPI placeholders # Use an empty string to disable the hologram. #hologram-text: "&a&l[AngelChest]&r\n&b{player}\n&7{items} items / {xp} XP\n&6{time}\n&cKilled by {deathcause}" hologram-text: "&7✝ &8Hier ruht &7✝\n&c{player}\n&8Gestorben durch {deathcause}\n&7(Rechtsklick zum Aufheben)" # This text is added to the hologram where you have {protected} in your "hologram-text" # and if your AngelChest is protected and auto unlocking is disabled. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! hologram-protected-text: "&cProtected" # This text is added to the hologram where you have {protected} in your "hologram-text" # and if your AngelChest is protected and auto unlocking is enabled. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! hologram-protected-countdown-text: "&cProtected for {time}" # This text is added to the hologram where you have {protected} in your "hologram-text" # and if your AngelChest is unprotected. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! hologram-unprotected-text: "&aUnprotected" # If you think the hologram is displayed too high, you can change this number. # For example -0.5 means the hologram will be moved 0.5 blocks down hologram-offset: 0.0 # The distance between each hologram line hologram-offset-per-line: 0.25 ######################### ##### Charges ###### ######################### # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! # When the Charges System is enabled, players require a "Charge" to get an AngelChest spawned. # Charges are like a virtual currency and can be currently only acquired through the /acadmin command, so you # can sell them to players or give them away as rewards, or whatever. # When a player dies, they will be charged one charge for the chest to spawn. # When they don't have a charge, the chest will not spawn and the items will drop normally. # Additional settings you have set still apply though, so if you set a price for the chest to spawn, # they still have to pay that amount. A charge will only be used if the chest successfully spawned. # Commands available (also work for offline Players if they have played before): # /acadmin charges get - Get the amount of charges a player has # /acadmin charges set - Set the amount of charges a player has # /acadmin charges add - Add charges to a player # /acadmin charges remove - Remove charges from a player # If this system is disabled, no charges will be required. enable-charges-system: false ######################### ##### GUI ###### ######################### # PREMIUM FEATURE: THE WHOLE GUI IS ONLY AVAILABLE IN AngelChestPlus! # When set to true, players can fast-loot the AngelChest using rightclick (or shift-rightclick, see option below) # When set to false, players cannot fast-loot and always get the GUI displayed when opening a chest # When set to "force", players will always fast-loot chests and will never see the GUI. allow-fastlooting: true # When true, players can open the AngelChest GUI using shift-rightclick and fast-loot the chest via rightclick # When false, players can open the AngelChest GUI using rightclick and fast-loot the chest via shift-rightclick gui-requires-shift: true # You can use custom materials or base64 strings to customize the GUI buttons. # You can for example use this website: https://minecraft-heads.com/custom-heads # At the bottom of each head's page, copy the string at Other -> Value gui-button-back: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvODY0Zjc3OWE4ZTNmZmEyMzExNDNmYTY5Yjk2YjE0ZWUzNWMxNmQ2NjllMTljNzVmZDFhN2RhNGJmMzA2YyJ9fX0=" gui-button-info: "PAPER" gui-button-teleport: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZGZlYjM5ZDcxZWY4ZTZhNDI2NDY1OTMzOTNhNTc1M2NlMjZhMWJlZTI3YTBjYThhMzJjYjYzN2IxZmZhZSJ9fX0=" gui-button-fetch: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZGZlYjM5ZDcxZWY4ZTZhNDI2NDY1OTMzOTNhNTc1M2NlMjZhMWJlZTI3YTBjYThhMzJjYjYzN2IxZmZhZSJ9fX0=" gui-button-unlock: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvOGFkOTQzZDA2MzM0N2Y5NWFiOWU5ZmE3NTc5MmRhODRlYzY2NWViZDIyYjA1MGJkYmE1MTlmZjdkYTYxZGIifX19" gui-button-preview: "BOOK" gui-button-preview-placeholder: "GRAY_STAINED_GLASS_PANE" gui-button-confirm-info: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvYjZlNTIyZDkxODI1MjE0OWU2ZWRlMmVkZjNmZTBmMmMyYzU4ZmVlNmFjMTFjYjg4YzYxNzIwNzIxOGFlNDU5NSJ9fX0=" gui-button-confirm-accept: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvY2UyYTUzMGY0MjcyNmZhN2EzMWVmYWI4ZTQzZGFkZWUxODg5MzdjZjgyNGFmODhlYThlNGM5M2E0OWM1NzI5NCJ9fX0=" gui-button-confirm-decline: "eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZTljZGI5YWYzOGNmNDFkYWE1M2JjOGNkYTc2NjVjNTA5NjMyZDE0ZTY3OGYwZjE5ZjI2M2Y0NmU1NDFkOGEzMCJ9fX0=" ##### Inventory title in the GUI main menu gui-title-main: "&4&l[&c&lAngelChest&4&l]" ##### Name and lore of the AngelChest items in the GUI main menu # {id} is the number of the chest # {time} is the amount of time left # {x} {y} {z} are the coordinates # {world} is the world's name # \n is a newline gui-chest-name: "§6AngelChest #{id}" gui-chest-lore: "§4{time}\n§aX: §f{x}\n§aY: §f{y}\n§aZ: §f{z}\n§f{world}" ##### Inventory title in GUI after selecting a specific chest # {id} is the number of the chest # {player} is the owner's name # {time} is the amount of time left gui-title-chest: "&4&l[&c&lAngelChest&4&l] &c#{id} &4| &c{time}" ##### Chest inventory name # {player} is the owner's name angelchest-inventory-name: "&4&l[&c&lAngelChest&4&l] &b{player}&r" ##### Button names and lore # Placeholders available in "gui-info-lore", "gui-teleport", "gui-teleport-lore", "gui-fetch" and "gui-fetch-lore": # {price} is the teleportation price # {currency} is the currency's name # {balance} is the player's current balance # You can use \n for newlines in lores gui-back: "&6Back" gui-info: "&6Info" gui-info-lore: "§6You are about to spend {price}{currency}." gui-teleport: "&6Teleport" gui-teleport-lore: "§6You are about to spend {price}{currency}." gui-fetch: "&6Fetch" gui-fetch-lore: "§6You are about to spend {price}{currency}." gui-unlock: "&6Unlock" gui-accept: "&aAccept" gui-decline: "&cDecline" gui-preview: "&6Preview" ######################### ##### Other ###### ######################### ##### AngelChest list (/aclist) settings # {id} is the number of the chest # {x} {y} {z} are the coordinates # {world} is the name of the world # {time} is the amount of time left # \n is a new line. angelchest-list: "[{id}] {time} &aX:&f {x} &aY:&f {y} &aZ:&f {z} | {world} " ##### Clickable Links when running /acinfo or /aclist link-unlock: "&5[Unlock]&r" link-fetch: "&6[Fetch]&r" link-teleport: "&6[TP]&r" # When set to true, the links in the chat for teleportation, fetching or unlocking # an AngelChest will be sent on a separate line show-links-on-separate-line: false # Whether AngelChest should automatically prefix all messages add-prefix: true prefix: "&b[&aAngelChest&b] &r" ############################ ##### Command settings ##### ############################ # You can change the command aliases for all player commands here. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! # Commands that can be used instead of /acgui command-aliases-acgui: - angelchestgui # Commands that can be used instead of /aclist command-aliases-aclist: - acinfo - ac - angelchest - angelchestinfo - angelchestlist command-aliases-acopen: - angelchestopen # Commands that can be used instead of /acfetch command-aliases-acfetch: - acretrieve - angelchestfetch - angelchestretrieve # Commands that can be used instead of /actp command-aliases-actp: - acteleport - angelchesttp - angelchestteleport # Commands that can be used instead of /acunlock command-aliases-acunlock: - angelchestunlock - unlockchest - unlock # Commands than can be used instead of /actoggle. command-aliases-actoggle: - angelchesttoggle # Commands that can be used instead of /acreload command-aliases-acreload: - angelchestreload # Commands that can be used instead of /acdebug command-aliases-acdebug: - acd ######################### ##### Misc ##### ######################### # When set to true, the AngelChest will be placed at the exact location where the player died + the given offset ("absolute mode") # When set to "false", the offset will be applied to the adjusted chest location (after void fixing, etc.) ("relative mode") fixed-chest-offset: false fixed-chest-offset-value-x: 0 fixed-chest-offset-value-y: 0 fixed-chest-offset-value-z: 0 # Interval between checking if a block has changed after the chest has been placed block-change-check-tick-interval: 40 # When true, AngelChest will always set a chest's blockstate to its original blockstate when despawning a chest, # even if the block has changed meanwhile. This should only happen if /setblock is used, or if another plugin replaces # the chest's block. always-reset-block-to-original: false # When true, AngelChest will move the chest one block up if the chest's block has been replaced with another block # after the chest was created. This should only happen if /setblock is used, or if another plugin replaces # the chest's block. # If the chest already is at the highest possible building height, the chest will stay at its current location. move-chest-when-block-gets-changed: false # Whether to show a console message when a player opens an AngelChest console-message-on-open: false # Log all created AngelChests, including content, death location, death cause, death time and player' inventory content. # Also logs what items have been put into the chest and when a chest has been emptied. # Note: Taking out single items from the chest is currently NOT logged! That will be added in the future. # PREMIUM FEATURE: ONLY AVAILABLE IN AngelChest Plus! log-angelchests: false # The amount of hours until log files are removed again. Set to -1 to never remove the log files purge-logs-older-than-x-hours: 48 # The amount of hours inbetween each attempt to remove old log files. Set to -1 to only remove on startup purge-logs-every-x-hours: 1 # File names for the log files. Available placerholders: # {player} - Player's name # {uuid} - Player's UUID # {world} - World nane # {date} - Date and time log-filename: "{player}_{world}_{date}.log" # File names for the AngelChest files. Available placerholders: # {player} - Player's name # {uuid} - Player's UUID # {world} - World nane # {x}, {y}, {z} - Coordinates chest-filename: "ac_{player}_{world}_{x}_{y}_{z}.yml" # Undocumented settings tp-distance: 2 tp-no-safe-space-y-offset: 1 ######################### ##### Messages ###### ######################### message-all-your-angelchests-were-already-unlocked: "&eAll your AngelChests were already unlocked." message-angelchest-created: "&aAn Angel collected your stuff and put it into a chest located at the place of your death." message-angelchest-disappeared: "&cYou were too slow... Your AngelChest has disappeared and dropped its contents." message-error-players-only: "&cError: This command can only be used by players." message-inventory-was-empty: "&eAn Angel searched for your stuff but could not find anything." message-not-allowed-to-break-other-angelchests: "&cYou are not allowed to break this AngelChest." message-not-allowed-to-open-other-angelchests: "&cYou are not allowed to open this AngelChest." message-unlocked-more-angelchests: "&aYou have unlocked %d AngelChests." message-unlocked-one-angelchest: "&aYou have unlocked your AngelChest." message-you-dont-have-any-angelchests: "&eYou don't have any AngelChests." message-you-got-part-of-your-inventory-back: "&eYou got a part of your inventory back, but some items are still in the AngelChest." message-you-got-your-inventory-back: "&aYou got your inventory back!" message-angelchest-location: "&eLocations of your AngelChests:" message-not-enough-money: "&cYou don't have enough money." message-not-enough-money2: "&cAn Angel tried to collect your stuff but you didn't have enough money." message-please-select-chest: "&7Please specify which AngelChest you would like to select." message-already-unlocked: "&cThis AngelChest is already unlocked." message-too-many-angelchests: "&cYou had more AngelChests than your Angel could handle... Your oldest AngelChest has exploded." message-no-angelchest-in-pvp: "&cAn Angel tried to collect your stuff but was put to flight by the presence of your killer." message-angelchest-retrieved: "&aAngelChest retrieved!" message-confirm: "&6You are about to spend {price}{currency}. Click this message to continue." message-paid-open: "&8You spent {price}{currency} to open an AngelChest." message-unlocked-automatically: "&8Your AngelChest has been unlocked automatically." message-angelchest-opened: "&6{player} has opened your AngelChest." message-angelchest-emptied: "&c{player} has emptied your AngelChest." message-spawn-chance-unsuccessful: "&cYour Angel forgot to collect your stuff, unlucky!" message-no-permission: "&cYou do not have the permission to use this command." message-invulnerable: "&a&lYou are invulnerable for {time}." message-vulnerable: "&c&lYou are no longer invulnerable." message-tp-across-worlds-not-allowed: "&cYou cannot teleport to your AngelChest across worlds." message-fetch-across-worlds-not-allowed: "&cYou cannot fetch your AngelChest across worlds." message-max-tp-distance: "&cYou cannot teleport to AngelChests more than {distance} blocks away." message-max-fetch-distance: "&cYou cannot fetch AngelChests more than {distance} blocks away." message-angelchest-disabled: "&cYou are no longer protected by Angels." message-angelchest-enabled: "&aYou are now protected by Angels." message-angelchest-fetched: "&aAngelChest fetched succesfully." message-angelchest-teleported: "&aSuccessfully teleported you to your AngelChest." message-min-distance: "&cYou already are nearby your AngelChest." message-buried-in-graveyard: "&aAn Angel collected your stuff and buried it at &6{graveyard}." message-cant-fetch-here: "&cYou cannot fetch your AngelChest here." message-teleporting: "&aTeleporting to AngelChest..." message-angelchest-disabled-others: "&c{player} is no longer protected by Angels." message-angelchest-enabled-others: "&a{player} is now protected by Angels." message-has-no-item: "&cYou need at least one {item}&r&c to do this." message-has-no-item2: "&cAn Angel tried to collect your stuff but you didn't have any {item}&r&c." message-cooldown: "&cAn Angel tried to collect your stuff but was still too tired to do so." message-pvp-cooldown: "&cAn Angel tried to collect your stuff but was still too tired to do so." message-cant-build-in-radius: "&cYou cannot place blocks in the vicinity of other player's AngelChests." message-no-charges-left: "&cAn Angel tried to collect your stuff but you didn't have any charges left." message-cant-build: "&cAn Angel tried to collect your stuff but couldn't enter that place." message-no-chest-nearby: "&cThere's no AngelChest nearby." ######################### ##### Done! ##### ######################### # Debug mode - you probably do not want this. debug: false verbose: false # NEVER CHANGE THE VALUES BELOW! plugin-version: 13.9.4 config-version: 202501310953

Wichtige Befehle (Rettung)Important Commands (Rescue)

Falls eine Kiste im Void schwebt oder nicht erreichbar ist, nutze diese Befehle. If a chest is floating in the void or unreachable, use these commands.

Command Description
/acfetch [ID] Der wichtigste Befehl! Teleportiert die Kiste zu DIR. (Alias für Restore) Most important! Teleports the chest to YOU. (Alias for Restore)
/acgui Öffnet grafisches Menü (einfachste Methode). Opens GUI menu (easiest method).
/aclist [Player] Listet Kisten auf. Zeigt die IDs (Nummern). Lists chests. Shows the IDs (numbers).
/acopen [ID] Öffnet Kiste aus der Ferne (Remote). Opens chest remotely.
/acunlock [ID] Entsperrt Kiste für andere Spieler. Unlocks chest for others.
Hinweis: Der Befehl /acrestore existiert NICHT. Nutze immer /acfetch. Note: The command /acrestore does NOT exist. Always use /acfetch.

Admin Notfall-PlanAdmin Emergency Plan

# 1. Kiste finden (als Admin) /aclist .Kamechan42 -> Zeigt Liste, z.B. "Chest #1" # 2. Kiste retten (zu dir holen) /acfetch .Kamechan42 1 # Wenn /aclist leer ist: # Dann wurden die Daten durch den Crash gelöscht. # Einzige Lösung: Gamemode Creative und Items manuell geben.

BlueMap Turbo Rendering (PC Offloading) BlueMap Turbo Rendering (PC Offloading)

Das KonzeptThe Concept

Das NAS ist zu langsam für Renderings (Tage). Der Desktop-PC (i5 11500F) schafft es in Stunden. The NAS is too slow for rendering (days). The Desktop PC (i5 11500F) does it in hours.

  1. Daten vom NAS holen.Fetch data from NAS.
  2. Auf PC rendern (100% CPU).Render on PC (100% CPU).
  3. Ergebnis zurückschieben.Push result back.

1. Vorbereitung (NAS)1. Preparation (NAS)

# 1. Server STOPPEN! stop # 2. Ordner kopieren Kopiere den kompletten Server-Ordner (UUID) vom NAS auf den Desktop PC (NVMe SSD empfohlen). Copy the full server folder (UUID) from NAS to Desktop PC (NVMe SSD recommended).

2. Rendern am PC2. Rendering on PC

Erstelle eine start.bat im Ordner. Du brauchst Java 21. Create a start.bat in the folder. You need Java 21.
Tipp: Java Portable nutzen und in den Ordner entpacken (z.B. als java21). Tip: Use Java Portable and extract into folder (e.g. as java21).
REM start.bat Inhalt / Content @echo off title Minecraft Renderer REM Pfad zum lokalen Java anpassen! ".\java21\bin\java.exe" -Xms4G -Xmx12G -jar server.jar --nogui pause

Die Befehle in der Konsole (CMD):Commands in the Server Console (CMD):

# Erst Generierung beenden (CPU) chunky continue world # Map Rendern (Dauert!) bluemap start bluemap force-update world # Nur beim ersten Mal nötig / Only needed first time bluemap update world # Für Updates danach / For updates later

3. Rücktransport (Upload)3. Return Trip (Upload)

Kopiere nicht alles zurück! Das dauert zu lange. Do not copy everything back! Takes too long.

Option A: Normaler Upload (Langsam)Option A: Normal Upload (Slow)

Option B: Entpacken auf dem NAS (SSH) - Kein Netzwerk-Overhead!Option B: Extract on NAS (SSH) - No Network Overhead!

Vermeide es, Dateien über Windows Explorer zu entpacken (Traffic geht: NAS -> PC -> NAS). Mache es direkt per SSH! Avoid extracting via Windows Explorer (Traffic goes: NAS -> PC -> NAS). Do it directly via SSH!
# 1. Auf PC: "bluemap" Ordner zippen (z.B. bluemap-neu.zip oder .7z) # 2. Zip auf NAS hochladen in den Server-Ordner # 3. Per SSH verbinden & Ordner öffnen: cd /share/Container/minecraft/data/7eec13af-e601-4e33-b427-ab39818cdcea # 4. Alten Ordner löschen (Vorsicht!) rm -rf bluemap # 5a. Wenn es eine .zip Datei ist: unzip bluemap-neu.zip # 5b. Wenn es eine .7z Datei ist (falls 7z installiert ist): 7z x bluemap-neu.7z # 6. Zip löschen & Rechte korrigieren (WICHTIG für Docker!) rm bluemap-neu.zip chown -R 1000:1000 bluemap

📚 Allgemeine BlueMap Befehle

Freeze vs. Purge: Wenn du eine Welt neu rendern willst, nutze purge (Löschen). BlueMap fängt danach automatisch wieder an. Freeze stoppt das Rendering dauerhaft (auch nach Neustarts), bis du unfreeze nutzt. Freeze vs. Purge: Use purge to delete map data (starts re-rendering automatically). Use freeze to stop updates permanently until you use unfreeze.
Command Permission Description
/bluemapbluemap.statusDisplays render status.
/bluemap reload [light]bluemap.reloadReloads config/resources. light is faster (skips resource pack).
/bluemap stopbluemap.stopPauses all rendering (persists over restart).
/bluemap startbluemap.startResumes rendering.
/bluemap freeze <map>bluemap.freezePauses updates for a specific map (persists).
/bluemap unfreeze <map>bluemap.unfreezeResumes updates for a specific map.
/bluemap purge <map>bluemap.purgeDeletes map data. Starts re-rendering immediately unless frozen!
/bluemap update <map>bluemap.updateUpdates changed chunks. (Auto-update usually handles this).
/bluemap force-update <map>bluemap.updateRenders everything again (slow!). Use only for testing.
/bluemap fix-edges <map>bluemap.updateRe-renders map edges (useful after changing map borders).

BedWars Arena Setup: "Castles"

🧩 Relevant BedWars Plugins

File / Plugin Version InfoInfo
BedWars 0.2.42.1 Core Plugin (Screaming Sandals)Core Plugin (Screaming Sandals)
SBA (Addon) 1.5.17 Hypixel-Features AddonHypixel-Features Addon
VoidGen 2.2.1 Welt-Generator (Leere Maps)World Generator (Empty Maps)

1. Arena definieren & Warte-Lobby bauen 1. Define Arena & Build Waiting Lobby

Stell dich für die Warte-Lobby an eine Position hoch über der Map (z.B. Y=100 über der Mitte). Stand high above the map for the waiting lobby (e.g., Y=100 above center).
# Setzt einen Glasblock direkt unter deine Füße (Sicherung) /setblock ~ ~-1 ~ glass # Erstellt eine runde Glas-Plattform (Radius 25) //cyl glass 25 1 # Zieht eine Glaswand außenrum (Höhe 2) //hcyl glass_pane 25 2 # Erstellt die Arena "castles" in der Datenbank /bw admin castles add # Definiert deine aktuelle Position als Wartelobby /bw admin castles lobby

2. Spielfeld-Grenzen setzen 2. Set Arena Boundaries

Flieg jetzt runter zur Map. Definiere den gesamten Spielbereich (Würfel) von der tiefsten Ecke links bis zur höchsten Ecke rechts. Fly down to the map. Define the entire play area (cube) from the lowest corner left to highest corner right.
# Setzt die erste Ecke des Spielbereichs (unten links) /bw admin castles pos1 # Setzt die zweite Ecke des Spielbereichs (oben rechts) /bw admin castles pos2

3. Teams, Spawns & BettenBeds

# Registriert Teams: /bw admin [map] team add [Name] [Farbe] [MaxSpieler] /bw admin castles team add Red RED 5 /bw admin castles team add Blue BLUE 5 /bw admin castles team add Green GREEN 5 /bw admin castles team add Cyan CYAN 5 /bw admin castles team add Pink PINK 5 /bw admin castles team add Yellow YELLOW 5 # Setzt das Bett, das du gerade anschaust, für das angegebene Team /bw admin castles team bed [Color] # Setzt den Spawn-Punkt für das Team an deine aktuelle Position /bw admin castles team spawn [Color]

4. Ressourcen & Shops 4. Resources & Shops

# Fügt einen Item-Spawner an deiner aktuellen Position hinzu /bw admin castles spawner add iron /bw admin castles spawner add gold /bw admin castles spawner add diamond /bw admin castles spawner add emerald # Verknüpft die Item-Shop Konfiguration (shop.yml) mit der Map /bw admin castles store add Store shop.yml false # Verknüpft die Upgrade-Shop Konfiguration (upgradeShop.yml) mit der Map /bw admin castles store add TeamUpgrades upgradeShop.yml false

5. Abschluss & Speichern (WICHTIG!) 5. Finish & Save (IMPORTANT!)

Ohne Spectator-Spawn lässt sich die Arena nicht speichern! The arena cannot be saved without a spectator spawn!
# Setzt den Spawn-Punkt für Zuschauer (Spectators) an deine Position /bw admin castles spec # Speichert alle Änderungen und lädt die Welt neu /bw admin castles save

6. Spielen & Testen 6. Play & Test

# Tritt der Arena "castles" als Spieler bei /bw join castles # Erzwingt den sofortigen Spielstart (verkürzt Countdown auf 5s) /bw start castles # Verlässt die laufende Runde /bw leave



SBA Addon: Offizielle DokuOfficial Docs

Zusätzliche Funktionen durch das "Screaming Bedwars Addon" (Hypixel-Style Features). Additional features via "Screaming Bedwars Addon" (Hypixel-style features).
🔗 Original Tutorial (GitHub)

Setup & Shops

Wichtig für Updates:Important for Updates: Wenn du das Plugin aktualisierst, führe immer /sba upgrade aus. If you update the plugin, always run /sba upgrade.
Falls du eine alte Map hast, resette die Spawner vorher: If you have an old map, reset spawners first: /bw admin (mapname) spawner reset
# Fügt den Team-Upgrade Shop (Schmiede) hinzu /bw admin mapname store add TeamUpgrades upgradeShop.yml false # Fügt den Item-Shop (Händler) hinzu /bw admin mapname store add Store shop.yml false

Lobby Features (NPCs & Scoreboard)

# Erstellt einen Join-NPC für den Solo-Modus /sba gamesinv spawnnpc solo # Erstellt einen Join-NPC für den Doubles-Modus /sba gamesinv spawnnpc double # Erstellt einen Join-NPC für den Triples-Modus /sba gamesinv spawnnpc triple # Erstellt einen Join-NPC für den Squad-Modus /sba gamesinv spawnnpc squad # Setzt die Position für das Lobby-Scoreboard/Stats an deine Stelle /sba setlobby

Party System

Ermöglicht es, als Gruppe gemeinsam Spielen beizutreten. Allows joining games together as a group.
# Lädt einen Spieler in die Party ein /party invite player # Nimmt eine offene Einladung an /party accept # Lehnt eine Einladung ab /party decline # Verlässt die aktuelle Party /party leave # Wirft einen Spieler aus der Party (nur Leader) /party kick player # Löst die gesamte Party auf /party disband # Öffnet die Party, sodass jeder ohne Einladung beitreten kann /party open # Erstellt ein privates Spiel nur für Party-Mitglieder /party private

Server Wartung & Updates Server Maintenance & Updates

Wichtig: SSH ZugangImportant: SSH Access

Updates via Terminal (SSH) auf QNAP. Updates via Terminal (SSH) on QNAP.

1. Minecraft Server Update (Paper)

cd /share/Container/minecraft/data/7eec13af-e601-4e33-b427-ab39818cdcea rm server.jar ln -s paper-NEU.jar server.jar

2. Crafty Controller Update (Docker)

Schritt A: Konfiguration prüfen (Optional)Step A: Check Config (Optional)

Falls Ports oder Pfade angepasst werden müssen: If ports or paths need adjustment:

# Datei öffnen / bearbeiten nano /share/Container/container-station-data/application/minecraft-stack/docker-compose.yml # Inhalt (Referenz): services: crafty: image: registry.gitlab.com/crafty-controller/crafty-4:latest container_name: crafty-web dns: - 192.168.42.242 # Dein lokaler DNS (Router/PiHole) - 8.8.8.8 # Google Backup - 1.1.1.1 # Cloudflare Backup ports: - "8443:8443" # Webseite - "25565:25565" # Java Port - "19132:19132/udp"# Bedrock Port - "8444:8444" # Squaremap - "8100:8100" # Bluemap environment: TZ: "Europe/Berlin" volumes: - /share/Container/minecraft/data:/crafty/servers - /share/Container/minecraft/backups:/crafty/backups - /share/Container/minecraft/logs:/crafty/logs - /share/Container/minecraft/config:/crafty/app/config - /share/Container/minecraft/import:/crafty/import restart: unless-stopped

Schritt B: Update durchführenStep B: Perform Update

# 1. In den App-Ordner wechseln cd /share/Container/container-station-data/application/minecraft-stack # 2. Neues Update herunterladen (Pull) docker compose pull # 3. Container neu erstellen (Update anwenden) docker compose up -d