ResizePlayer

Resize

Smoothly change a player's size in-game, with donator classes, automatic timed resets, and per-world restrictions — built for servers that sell size perks and need it to expire cleanly.

Requirements

• Paper (or a Paper fork) 1.21.x

Installation

1. Drop the jar into your server's plugins/ folder and restart (or /reload, though a restart is safer).
2. A config.yml and a lang/ folder (with en.yml and ru.yml) will be generated in plugins/Resize/.
3. Set language: "en" or language: "ru" in config.yml, edit whatever you want, then run /resizereload.

Features

• Smooth, animated size changes (not an instant snap)
• Unlimited donator classes — define any number of permission-based size tiers (e.g. Iron, Diamond) with their own min/max range, fully configurable, no code editing needed
• Automatic timed resets — pair a temporary permission grant with /resizeschedule so a player's size reliably returns to normal when their donation period ends, even if they were offline when it expired or the server restarted in between
• Per-world restrictions — block resizing entirely in chosen worlds, or force a player's size back to normal the moment they enter one (e.g. the Nether)
• Configurable cooldown between uses
• Full permission set, so admins control exactly who can resize themselves, resize others, bypass the cooldown, bypass world restrictions, or manage timers
• Multi-language support (English and Russian included) with fully customizable message text, including the prefix — MiniMessage formatting throughout: named colors, <#RRGGBB> hex, and gradients all supported
• Master on/off switches for world restrictions, scheduling, and cooldown, so you only run what you need

Commands

Duration format for /resizeschedule: 30d, 12h, 45m, 20s, or combinations like 1d12h — the same tokens LuckPerms uses for settemp.

Permissions

Donator size classes (scale.tiers)

Instead of one fixed range, config.yml has an ordered list of size classes. Each has its own permission node and its own min/max range:

scale:
  tiers:
    - permission: ""
      min: 0.8
      max: 1.15
    - permission: "resizeplugin.resize.extended"
      min: 0.0625
      max: 16.0
    # - permission: "resizeplugin.tier.iron"
    #   min: 1.0
    #   max: 1.5
    # - permission: "resizeplugin.tier.diamond"
    #   min: 2.0
    #   max: 2.5

• Checked top to bottom; if a player qualifies for more than one, the last matching entry wins — list weaker/free tiers first, stronger/paid tiers last.
• permission: "" applies to everyone who can use /resize at all.
• Add, rename, reorder, or delete entries freely — no code changes needed, just /resizereload after editing.
• Uncomment or duplicate the example lines to create your own donator ranks (Iron, Diamond, VIP, whatever you sell), each gated by its own LuckPerms permission.

Making /resize itself free (or donator-only)

By default resizeplugin.resize is required to use /resize at all (recommended if size is a paid perk). If you'd rather let everyone use the base range and only gate the bigger ranges behind donator tiers, flip this in config.yml:

features:
  require-resize-permission: false

Solving the classic "temp permission expires, size doesn't" problem

Donation panels typically grant a size perk with something like:

lp user {player} permission settemp resizeplugin.resize.extended true 30d

That alone doesn't reset the player's size when the 30 days are up — LuckPerms and the plugin don't talk to each other. Pair it with a second command from your panel:

resizeschedule {player} 30d

The plugin stores this in scheduled-resets.yml inside its data folder, checks for due resets on an interval (configurable, see below), and applies it even if the player is offline when it fires — it catches up on their next login. It survives restarts and doesn't depend on the LuckPerms permission itself still existing; it just reliably sets the player back to scale.base-value at the scheduled time. Players can check their own remaining time with /resizetime.

Per-world restrictions

worlds:
  disabled-worlds:
  #  - "world_nether"
  force-reset-worlds:
  #  - "world_nether"
  #  - "world_the_end"

• disabled-worlds — /resize is blocked entirely while standing in one of these worlds.
• force-reset-worlds — blocked and the player's size is instantly reset back to scale.base-value the moment they enter (e.g. "enter the Nether → back to normal size, and can't resize again until they leave").
• Both lists are empty by default and only take effect once features.world-restrictions-enabled: true is set.
• resizeplugin.bypass.worldrestriction lets admins/staff ignore both lists.

Turning features on/off

config.yml has a features section so you can disable parts of the plugin without touching anything else:

features:
  world-restrictions-enabled: false   # the two world lists above
  scheduling-enabled: true            # /resizeschedule and /resizecancel
  cooldown-enabled: true              # the /resize cooldown
  require-resize-permission: true     # whether resizeplugin.resize is required at all

Performance / the "check every second" scheduler

scheduling.check-interval-seconds (default 1) controls how often the plugin scans for due scheduled resets. This is a cheap in-memory map scan — even at 1 second it's not something you'll notice on server performance — but you can raise it (e.g. 5) if you want to be extra conservative; resets will then fire up to that many seconds late.

Cooldown

cooldown:
  seconds: 30

Seconds a player must wait between uses of /resize on themselves. Ignored entirely if features.cooldown-enabled: false, and bypassable per-player with resizeplugin.bypass.cooldown.

Localization & colors

config.yml's language key points at a file in lang/ (en.yml and ru.yml are included — add your own by dropping a new <code>.yml in that folder and setting language to match). Every message, including the prefix shown before each line, lives in that file and is parsed with MiniMessage, so named colors, <#RRGGBB> hex codes, and <gradient:...> all work anywhere in it. Edit, save, /resizereload — no restart needed.

Troubleshooting

If a future Paper release removes Attribute.GENERIC_SCALE (it's currently deprecated in favor of a registry lookup, scheduled for removal no earlier than 1.22) and the plugin fails to load with an Attribute-related error on startup, check for a plugin update or report it on the issue tracker with your exact Paper version.

🐛 Support & Feedback

Found a bug? Have a suggestion? Feel free to:

• Contact me on Discord: igromania_