VelorSTUDIO
EN
BuiltByBit
HomePluginsPlaygroundDocumentationChangelogSupportDiscordBuiltByBit

Upgrading from 1.6.0

Upgrading #

  1. Stop the server and replace the jar with CrossMenu-1.6.1.jar.
  2. Start the server. config.yml moves to config-version: 3, gains the audit section and is copied first to config.yml.backup-v2. Menus, edited language values and stored cooldown data are kept.
  3. A 1.6.0 jar refuses a version-3 config. To go back, restore config.yml.backup-v2 as config.yml.

Language files you already have keep the old wording of the reload message. Delete the line config-invalid from your copy, or the whole file, to get the new text. New package-import messages are merged into existing language files after a backup copy is made; your translations and custom values are kept.

What is new since 1.6.0 #

  • Languages. Six more bundled languages (Japanese, Italian, Dutch, Indonesian, Ukrainian and Vietnamese), 16 in total. They are machine-assisted translations; edit lang/<code>.yml if a line reads wrong on your server.
  • Yes/no prompts. The word a chat prompt names is accepted in every bundled language.
  • Open triggers. A menu can open when a player joins or clicks an item.
  • Export and package import. /crossmenu export and /crossmenu import package.
  • Material warnings. validate, reload and doctor flag a material: that is not a real item.
  • Audit log. Optional, off by default.
  • HeadDB. Optional hook for material: headdb-<id>.
  • Clearer messages. A refused reload names the file, YAML errors give line and column, and tab completion lists only the subcommands a player may use.

Known limitations #

  • A [player] command that no plugin registers does nothing and the player sees no message.
  • Bedrock forms are static once open. Decorative items without an action are left out of Bedrock forms unless you configure them to show.
  • A headdb- slot can briefly show its fallback barrier while HeadDB finishes its first asynchronous lookup; the slot then refreshes by itself.
  • Open triggers match the main hand only.
  • Material validation uses the running server's item registry, so an item introduced only by another Minecraft version may be reported as unknown.
  • Package import checks syntax and menu structure, not integrations or placeholders that exist only on the server where the package was made.