CustomKits | SwiftCore - Duel,Party,FFA

1. Preset system​

What it does

  • Staff can save a full snapshot of a player’s inventory and armor as a named preset.
  • Presets are listed in a preset browser GUI with paging.
  • Choosing a preset loads that kit into the player, then opens the kit editor so they can finish tuning and assign it to a custom kit slot.
Staff command

  • /ck preset add <presetname> <slot>
    • Saves current inventory + armor for the executing player under that preset name.
    • <slot> is a non‑negative GUI index where the preset appears in the preset menu (supports layout across pages via slot math).
Configuration

  • All presets live in preset.yml under the plugin data folder (editable offline).
  • Typical fields include: display name, icon material, GUI slot, default arena type, serialized contents and armor.
  • Presets are cached in memory; /ck reload reloads them.
GUI entry points

  • Create kit screen: option to open preset selection.
  • Main custom kits GUI: right‑click empty slot can open presets directly (as implemented in your flow).

2. Kit settings: SwiftCore rules and rounds​

Kit flags (rules)

  • Settings include a Kit flags / rules area tied to SwiftCore KitRule values.
  • The UI is intentionally limited to the rules that are supported and meaningful for custom kits, so admins are not overloaded with unrelated toggles.
Configurable rules (by behavior name)

These map to SwiftCore concepts such as:

  • Fall damage behavior
  • Saturation‑based healing behavior
  • Whether “normal” melee/other damage applies in the intended way for that kit rule set
  • “Stick spawn” / restricted movement‑teleport behavior during countdown (as your core implements it)
  • Hunger drain behavior
  • Auto‑TNT, bed‑explosion behavior
  • Golden head effects
  • Only arrow damage
  • Visual enchanted golden apple cooldown
  • Arrows despawning instantly on hit
Top