← The Frontier Suite

FrontierEndLock

v1.2.0World

Keeps the End closed until a scheduled unlock, or until an admin opens it.

What it does

Locks the End so a fresh survival server can reach the Dragon fight together instead of one player rushing it in week one. While locked, players without bypass cannot enter an End portal, place End portal frames, or push Eyes of Ender into frames.

The lock can open automatically on a schedule (unlock-at), with daily countdown broadcasts and final warnings before it fires; staff can still flip it by hand. Unlocking broadcasts a decorated "The End Has Been Unlocked!" banner. The lock state persists in config.yml and the End starts locked on a fresh install. On mc.pvpers.us the End is locked and opens on its own on Saturday, October 24 at 5 PM Arizona.

Requires & integrates with

Required
Paper 26.3+, Java 25+
Optional
FrontierAnnouncements (Gazette post when the End opens).
Used by
FrontierTab (optionally shows an End: 🔒 element in the header while locked).

Commands

CommandWhoWhat it does
/endlock onAdminLock the End; broadcasts "The End has been locked!"
/endlock offAdminUnlock the End; broadcasts a banner
/endlock statusAdminShow LOCKED / UNLOCKED (running /endlock with no argument also shows status and usage)
/endlock schedule <yyyy-MM-ddTHH:mm>AdminSchedule the automatic unlock (in the plugin’s timezone)
/endlock schedule clearAdminCancel the scheduled unlock
/endlock reloadAdminRe-read config.yml

Permissions

Player features default to true, staff features to op. Every node follows frontier.<plugin>.<action>, so a LuckPerms setup is e.g. lp group default permission set frontier.shop.use true. Wildcards work: frontier.reputation.*.

NodeDefaultGrants
frontier.endlock.adminop/endlock
frontier.endlock.bypassfalseIgnore the lock: enter portals, place frames, use eyes

Config reference

File

plugins/FrontierEndLock/config.yml

To apply changes

/endlock reload — for the lock itself, use /endlock on|off rather than editing

KeyDefaultWhat it controls
lockedtrueWhether the End is currently locked. Written by /endlock on|off and again on shutdown
unlock-at—Scheduled automatic unlock (yyyy-MM-ddTHH:mm, set with /endlock schedule). mc.pvpers.us: 2026-10-24 17:00
timezone—Zone unlock-at and the announcement times are read in (mc.pvpers.us runs America/Phoenix)
schedule-fired / last-daily-announce—Internal bookkeeping written by the plugin — don’t edit
KeyDefaultWhat it controls
announce.daily-time—Time of day for the daily countdown broadcast
announce.final-warnings-minutes—Minutes before the unlock at which final warnings go out
announce.on-join—Also show the countdown to players as they join
announce.{message, final-warning-message, date-format}—Countdown and final-warning text, and how the unlock date is printed

Good to know

  • +Don’t edit config.yml while the server runs: the plugin holds the state in memory and rewrites locked on shutdown, so hand edits get overwritten. Use the command, or edit with the server stopped.
  • +Only player portal travel is blocked. Entities, and teleports that aren’t End-portal travel (plugin /tp, End gateways, other portal plugins), are not.
  • +frontier.endlock.bypass defaults to false, but ops with a * wildcard grant will have it. Bypass is per-player, and turning the lock on does not kick players already in the End.
  • +Frame placement is cancelled at HIGH event priority; a plugin at a higher priority un-cancelling it, WorldEdit, or /setblock will get around it.

Looking for something specific? Search the whole suite.