Upgrading to 1.7.7

Last updated Oct 28, 2026

Upgrading to 1.7.7

What you must do after installing the 1.7.7 jar. Jar updates do not overwrite live YAML.

Do this

  1. Full server restart with the new jar (not /reload).
  2. Confirm /sa version shows 1.7.7 and /sa modules list looks right.
  3. If you customized gui.yml or messages.yml, merge any missing keys from Config Reference defaults (or regenerate GUI from /sa guiconfig tools after backup).
  4. Optional: Discord punishment/report/ticket webhooks under config.yml → integrations.webhooks (new in 1.7.7).

What changed (owner-facing)

Change What it means
Module gating / enforce Ban, mute, IP ban, and jail still enforce when those modules are command-off
Custom commands Safer save/restore; wraps pass -force / -s; top-level wraps like /give when registered
MOTD on Spigot Ping fallback for list MOTD / player counts
Permission defaults Many player nodes in plugin.yml default false; grant what you want players to have
Performance Async moneylog, pay cache, trade debounce, tab caches

Soft new-install defaults are not forced onto existing configs. Full history: Changelog.

Coming from older 1.7.x

  • 1.7.5+ admin hub pages / Support Hub: regenerate or merge gui.yml if you still see a flat button wall.
  • 1.7.4+ GUI tertiary actions use F (f-action), not middle-click.
  • 1.7.2+ disabled modules release top-level aliases; staff lookup prompts stay out of public chat.

Verify

/sa version
/sa modules list
/sa admin
/sa help

See also: Getting Started · Troubleshooting · Config Reference

Still stuck? Ask about this page