Folia and Compatibility
Structory 26.1 declares Folia support in plugin.yml.
That means the plugin has been moved away from the old direct Bukkit scheduler paths where Structory controls the scheduling. It now uses the DadaPlatform scheduling layer, which can choose the correct scheduler for Paper, Spigot or Folia.
Recommended Java version
Use the Java version recommended by your server software.
For modern Paper/Folia servers, Java 21 LTS is the safest recommendation unless your server build explicitly asks for something else.
If you are testing with a much newer Java version and you see strange watchdog or classloading problems, try reproducing the issue on Java 21 before blaming Structory or another plugin.
What Folia support does and does not mean
Folia support means Structory tries to schedule its own work correctly.
It does not mean every plugin in your server stack is automatically safe.
This especially matters for optional integrations:
| Dependency | Notes |
|---|---|
| CraftEngine | Optional. Needed only if you use CraftEngine items/blocks. |
| Oraxen | Optional. Needed only for Oraxen recipes/results. |
| Nexo | Optional. Needed only for Nexo recipes/results. |
| MMOItems | Optional. Needed only for MMOItems recipes/results. |
| ItemsAdder | Optional. Needed only for ItemsAdder recipes/results. |
| Vault | Optional. Needed for Vault economy ingredients/results. |
| CoinsEngine | Optional. Needed for CoinsEngine currency ingredients/results. |
| EcoItems | Optional. Needed only for EcoItems recipes/results. |
| ExecutableItems | Optional. Needed only for ExecutableItems recipes/results. |
| SCore/nightcore | Optional dependencies used by some external plugin integrations. |
If you do not use a specific integration in your recipes, the missing plugin should not break Structory by itself.
Custom materials and custom block keys
Structory can validate normal Bukkit materials directly.
Keys such as:
default:palm_wood
are not Bukkit materials. They belong to a custom block/item plugin such as CraftEngine.
If the matching plugin is not installed, not loaded, or the key is used in a field that expects a Bukkit material, Structory will report it as invalid.
Use normal Bukkit materials for fields that explicitly ask for a Bukkit material. Use the dedicated CraftEngine/Oraxen/Nexo/etc. ingredient or checker types when you want custom plugin items or blocks.
ActionBar messages
Structory 26.1 uses the newer DadaPlatform release that sends real action bars.
If an actionbar message appears in chat, check that your jar was built with the updated DadaPlatform version and that there is no old Structory jar still loaded on the server.
Watchdog logs
If Folia prints a watchdog stack trace, check the stack before assuming it is Structory.
If the stack contains Structory classes, open the relevant page or report the stack trace.
If the stack is inside vanilla autosave, map saving, region ticking, disk I/O or another plugin, the cause may be outside Structory.