Release 26.1 - PREMIUM
Structory Premium 26.1 is a big maintenance and usability release. The main goal was simple: keep the power of Premium, but make it feel less like editing a pile of YAML blindfolded.
If you are updating from 1.5.0, this release is the point where Structory Premium becomes a separate private project built on top of the shared Free/core code.
New project layout
Premium is now separated from the public Free repository.
The shared code lives in structory-core; Premium depends on that core and keeps Premium-only systems in the private Premium repository.
This makes the project cleaner and safer:
- less duplicated code;
- fewer painful branch merges;
- less risk of shipping Premium code in the Free build;
- clearer difference between Free features and Premium features.
New editor dashboard
The Premium admin/editor GUI has been expanded into a proper dashboard.
You can open it with:
/structory editor
or:
/structory admin editor
From there you can reach the main Structory admin tools:
- structures;
- placed instances;
- recipes;
- config files;
- loaded options;
- loaded addons;
- GUI definitions;
- health/validation checks.
The idea is that you should be able to inspect and fix most Structory setup problems in-game before jumping into files.
Better structure, recipe and option editing
The editor is now more modular.
Each option can describe how it wants to be edited. When an option provides its own editor fields, the GUI uses those. Generic/reflection-style editing is still there as a fallback, but it is not the main design anymore.
This matters because Premium options are not all the same. A crate, a privacy rule, a block display and a particle decoration do not deserve the same generic editor.
Config editing from GUI
The admin editor now has safer editing flows for files like:
config.yml;messages.yml;gui.yml;- recipes;
- structures.
Edits are draft-based where possible, and saves create backups for sensitive files. It is still YAML underneath, but the GUI should make small fixes much less painful.
Particle and animation cleanup
Particles, sounds and reusable decorations now belong to the particle option.
Crafting animations remain part of crafting behavior.
That split is important:
particleowns reusable effects such asconsume,result,insert,place,take, sounds and decorations;- crafting animation decides how the crafting process behaves or plays over time.
The editor now avoids showing particle/decoration editors on structures that do not have a particle option configured. In that case it points you to add the particle option first instead of opening a confusing empty editor.
Old configs that still put consume or result effects directly under crafting should be migrated to:
options:
particle:
consume:
type: particle
particle: FLAME
Crate editor cleanup
The crate editor received a usability pass.
Crate settings are now easier to understand from the GUI, including placement behavior, actionbar messages, item data, sound settings and build settings.
The goal is not to hide every YAML detail, but to make common edits possible without guessing what each random item in the inventory means.
Folia work
Premium now declares:
folia-supported: true
The plugin was moved onto the updated DadaPlatform scheduling layer, with Folia-aware scheduling paths where possible.
Important note: this means Structory itself has been moved in the right direction. Optional dependencies still matter. If an external plugin or addon is not Folia-safe, that plugin can still cause problems in a Folia setup.
ActionBar fix
DadaPlatform was updated so sendActionbar/sendActionBar sends a real action bar instead of falling back into chat.
This fixes cases where messages such as:
Now you can craft serious items
were appearing as normal chat messages.
Update notes
Back up your full plugins/Structory/ folder before updating.
Make sure the generated or existing config.yml contains:
version: 26.1
If Structory detects an older config version, it may create a backup and regenerate the default config. That is normal, but you should compare your old file before copying custom settings back.