Getting Started
Installation
Section titled “Installation”- Stop the server.
- Put
KyuubiSoftLootbag-2.0.4.jarinto the server’smods/folder. When you update, remove the oldKyuubiSoftLootbag-*.jarfirst. - Make sure KyuubiSoft Core is installed as well (see Requirements); without it the server does not load Lootbags. DynamicTooltipsLib is optional.
- Start the server. The plugin creates its data folder
mods/kyuubisoft_lootbag/and writes the default files.
The UI textures (the shared KyuubiSoft UI kit) and all 150 bag items are inside the jar.
Files after the first start
Section titled “Files after the first start”mods/ KyuubiSoftLootbag-2.0.4.jar kyuubisoft_lootbag/ config.json main switches (see Configuration) configs/ lootbags.json the 150 shipped bags drop_tables.json creature and mining drop rules custom/ your bags and edits (custom_lootbags.json, written on the first save) localization/ en-US, de-DE, fr-FR, es-ES, pt-BR, ru-RU, pl-PL, tr-TR, it-IT (.json) data/ players/<uuid>.json per player: statistics, last 50 openings, opening window on/off latest_drops.json the server's latest finds (last 30) kslang/ language choices shared by all KyuubiSoft modsSome files only appear once they are first written: custom/custom_lootbags.json after the first save in the admin panel or with /lbadmin edit, data/players/ after the first player joins, latest_drops.json after the first opening. When the plugin saves drop_tables.json, custom_lootbags.json or a player file, it keeps the previous version as .bak next to it.
What an update changes
Section titled “What an update changes”config.jsonis never overwritten. Settings that are new in 2.0.0 (showDropSources,ignorePlacedBlocks) are on by default and are written into the file the next time the settings or drop rules are saved in the admin panel.configs/lootbags.jsonandconfigs/drop_tables.jsonare only written when they are missing. Delete them if you want the shipped versions back.- Four item IDs that do not exist in Hytale (
Food_Fruit,Food_Mushroom,Seed_Wheat,Seed_Pumpkin) are replaced in memory when the bags load. Drop rules that point to the bagCrystal_Lootbag_Epic(which does not exist) are mapped toCrystal_Lootbag, the epic Crystal bag. Your files are not rewritten for this. - Localization files older than version 11 are replaced. The old file is kept as
<lang>.json.backup-v<old version>. - Player files from 1.x keep their statistics; the History tab starts empty because 1.x did not store the items of each opening.
First test
Section titled “First test”You need the ks.lootbag.admin permission for the admin command (see Permissions).
- Get a bag. Run
/lbadmin give Default_Lootbag 3. Three common Default bags land in your inventory. - Open one. Hold a bag and right-click. The opening window shows what you received, split into Guaranteed and Drawn at random. Click Open another (2) to open the next one right there.
- Look into the catalog. Run
/kslootbags. Pick a style on the left and a tier above the contents to see every item with its chance and, under Where to find, where the bag drops. - Place a bag. Crouch and right-click with a bag in your hand. Press F on the placed bag: the catalog opens on that bag.
- Test a drop. Kill any creature: with the shipped rules every creature has a 2 % chance to drop a Default bag. Mining ore (
Ore_*) can drop Copper bags. - Open the admin panel. Run
/lbadmin panel. See Admin Panel.
Next steps
Section titled “Next steps”- Configuration: every field of
config.json, the bag file and the drop rules - Custom Lootbags: your own bags and changes to the shipped ones
- Admin Panel: editing bags and drop rules in game
- FAQ & Troubleshooting: when something does not work