Version 1.6.7 - End Portal Relighting Fix

Fixed

• Fixed a bug that could prevent a rebuilt End Portal from relighting. Mined End Portal Frames were preserving both their original orientation and their installed Eye of Ender state.
• When those preserved frames were placed in a new portal ring, they could keep the wrong internal orientation. Because the Eyes were already stored inside the preserved block state, players could not reinstall them to make Minecraft run its normal portal activation check. The completed portal could therefore remain inactive.
• Mining now always drops one fresh, empty vanilla End Portal Frame. If the mined frame contained an Eye of Ender, it also drops one Eye of Ender as a separate vanilla item.
• Fresh frames receive the correct orientation through normal placement. After all frames are placed, players reinstall the Eyes normally so Minecraft can run its vanilla portal activation process and open the portal.
• End Portal Frames no longer use the Vault saved-structure system, so old orientation and installed Eye state cannot be carried into a rebuilt portal.

Unchanged

• Monster Spawners still preserve their configured mob data.
• Trial Spawners still use Bedrock's native data-bearing item to preserve their configuration.
• Normal and Ominous Vaults still use saved one-block structures to preserve their Vault data and cycling behavior.
• Budding Amethyst, prices, unlocks, admin controls, and achievement-friendly pack metadata are unchanged.

Validation

• Added release checks requiring the fresh frame and separate Eye drop path.
• Added a guard that keeps saved-structure preservation limited to Vaults.

Version 1.6.6 - SilkyControlAdmin

This update replaces the pack gear/settings screen with a dedicated, operator-only in-game menu, and adds full Bedrock Dedicated Server support.

Versions 1.6.2 through 1.6.5 were internal testing builds. Everything below is new since the last public release.

Added

• /andy_stms:silkycontroladmin and a SilkyControlAdmin renamed stick. Both open the world settings menu: per-relic payment (cost) toggles, per-relic mining availability, unlock scope, all seven unlock prices, and reset.

• Both routes require Bedrock's Operator permission level, so the world owner, Realm operators, and server operators qualify. Permission is checked independently on the command, on the stick, and on every settings page.

• Bedrock Dedicated Server console support. Read and change every setting from the server console with no operator status and no in-game access:

  scriptevent andy_stms:help
  scriptevent andy_stms:list
  scriptevent andy_stms:status
  scriptevent andy_stms:get <setting>
  scriptevent andy_stms:set <setting> <value>
  scriptevent andy_stms:reset [setting|all]
  scriptevent andy_stms:debug
  

• Per-relic mining availability settings, so a category can be disabled entirely without erasing its paid unlock records.

• Every settings write is now verified after saving and logged to the Content Log with its exact setting name and value.

Changed

• Removed the pack gear/settings screen. On retail Bedrock 26.45 the game saved its toggles but never delivered them to the add-on, so the screen could not actually change anything. All configuration moved to SilkyControlAdmin and the server console, which verify their writes.
• /andy_stms:silkycontrol and the SilkyControl stick are now purely player-facing. World configuration is no longer reachable from them.
• Settings are stored in the world itself, so they travel with the world and survive add-on updates.
• Unlock prices moved to a dedicated form with strict validation.

Fixed

• Fixed the free-relic and disable-relic settings never taking effect, because the values the gear screen saved were never readable by the add-on.
• Fixed a settings form that could shift its values and trigger an unintended reset.
• Fixed a failed settings write being able to escape unreported. It now shows a clear message and saves nothing.
• Restricted world settings to operators. Earlier testing builds exposed some settings more broadly.

Notes

• No Cheats, Beta APIs, or Experiments are required. Both commands declare cheatsRequired: false, so achievement eligibility is preserved.
• Minecraft's own /scriptevent requires Cheats when a player types it in chat. In-game operators should use /andy_stms:silkycontroladmin; leave scriptevent for the server console.
• Existing paid unlock records, world-wide and per-player, are retained.