lasersenigma

V9.0.0

Fixes

• #557: when a puzzle does not let you modify a component — a laser sender you may not turn, a mirror you may not take — the game now tells you so instead of silently ignoring your click. Until now that explanation only ever appeared for a mirror support locked on its own, and never when the puzzle forbade the action for the whole area. Server owners who prefer silence can still switch it off with the component_blocked_message option.
• #557: setting up a brand-new server on a MySQL database no longer fails at the very first startup — a stray character in the components table definition prevented that table from being created. Servers already running, and all SQLite servers, were never affected.
• #782: iron bars now block laser beams by default instead of letting them pass through — admins who still want them transparent can add IRON_BARS to the crossable_materials config option. A typo in that option also no longer turns every block transparent to lasers: the invalid entry is simply ignored.

Features

• #557: you can now control, at three levels, what players are allowed to do to a component — turn it horizontally or vertically, take and place its mirror, resize it. A server-wide default in config.yml seeds each area when it is created; the area configuration menu, now a clear grid of every permission by component type, sets the area's default; and each individual component can override its area — in either direction, so a single mirror support can stay turnable in an area where rotation is otherwise off. In a component's menu every permission shows at a glance whether it is the component's own choice or inherited from the area, and one click cycles it between allowed, denied, and following the area again. When you change an area default that already has components in place, you choose whether it reaches them too (losing any hand-set values, with the counts shown first) or only applies to components built from then on. Taking and placing a mirror support's mirror is a brand-new permission; the shipped defaults reproduce exactly what a new area got before, so a server that changes nothing sees no change. (The mirror of a reflecting or of a filtering sphere stays free for anyone to handle, as it always has.)
• #801: the damage a burnable block deals when it melts down next to you is now server-configurable through the new burnable_block_damage_multiplier option — set it to 0 for areas where the explosion should knock you back without hurting you. Existing servers keep exactly the same damage as before.
• #557: a mirror support and a gravitational sphere now show what players may do to them — the support's head reflects its allowed rotations and mirror handling, the sphere's head whether it can be resized. Some supports in existing puzzles change appearance: a support that could never be turned used to wear a free-looking head, and now tells the truth. Their behaviour is unchanged — this only corrects what you see.

Technical changes

• #717: the server-pack build again downloads the correct Paper server jar after PaperMC retired its old download API, and the website's schematic list is now protected against a rare filename-encoding case that could blank it. No visible change in-game.
• #557: the mirror support's old internal "free / blocked" mode is gone — its lock now lives entirely in the component permissions, worked out in one single place shared by the game logic, the menus and the in-world textures (which had begun to disagree). Copy/paste and schematics carry the permissions along, and older schematics still load. For plugin developers: the eighteen old per-setting area events become two generic ones, plus two for the per-component permissions. Downgrade note: rolling a server back to a version before 9.0.0 after this release loses the lock of any mirror support you locked on 9.0.0+; published schematics are unaffected.