Team-HomeGUI Plugin

[1.3.3] — Real Root Cause of "Homes Lost on Every Restart" (confirmed via server log)

Critical Bug Fix

• BUG-09: load: STARTUP in plugin.yml caused every home/team-home to be silently dropped on every single server start, which is the actual cause behind the "restart wipes all home data" report (BUG-08's corruption-safety fix in 1.3.2 was good defensive practice, but was not the real trigger — confirmed by a live server log showing no corruption warnings, but repeated Location.deserialize / IllegalArgumentException: unknown world errors at plugin-enable time).

  What was happening:

  1. load: STARTUP enabled this plugin before any Minecraft world was created (log showed Enabling Team-HomeGUI-Plugin at 23:19:58, then Preparing level "world" only at 23:20:00 — two seconds later).
  2. HomeManager.load() / TeamManager.load() run during onEnable(), deserializing stored Location objects. Location.deserialize() must resolve the world by name; with no worlds registered yet, it throws IllegalArgumentException: unknown world.
  3. Bukkit logs that as an error and returns null for the location; this plugin's loaders skip null locations, so the home/team-home never enters memory.
  4. On the next graceful /stop, save() faithfully writes the now-incomplete in-memory state back to disk — permanently erasing the data, every time.

  Fix: removed load: STARTUP from plugin.yml so the plugin enables in the default POSTWORLD phase (after worlds are ready), which is required for any plugin that deserializes Locations at startup. Relative load order versus DiscordSRV / PlaceholderAPI / Essentials remains handled correctly by the existing softdepend.