Spigot Heights

A Purpur 26.2 plugin adding craftable player-scaling potions and dispenser launch tubes for tiny players.

Approved behavior is specified in the SoMC OKF wiki.

Requirements

• Purpur 26.2 build 2618
• Java 25 or newer

Potions

Potion of Shifting Stature

Amethyst Shard | Chorus Fruit   | Amethyst Shard
Amethyst Shard | Awkward Potion | Amethyst Shard
Amethyst Shard | Chorus Fruit   | Amethyst Shard

Drinking it chooses a random configured scale in 0.1 increments.

Potion of Growth

Gold Ingot | Amethyst Shard             | Gold Ingot
Amethyst   | Potion of Shifting Stature | Amethyst
Gold Ingot | Rabbit's Foot              | Gold Ingot

Potion of Diminution

Use the Growth recipe with a Fermented Spider Eye instead of the Rabbit's Foot. Growth and Diminution adjust scale by one configured step and clamp at the limits.

Potion of Restoration

Gold Ingot     | Amethyst Shard             | Gold Ingot
Amethyst Shard | Potion of Shifting Stature | Amethyst Shard
Gold Ingot     | Sugar                      | Gold Ingot

Produces one Potion of Restoration. Drinking it restores scale to exactly 1.0 (normal size), even outside configured limits. This size is saved across reconnects, respawns, and server restarts. Other permanent saved scales are still clamped to the configured range.

Temporary splash and lingering variants

Brew any of the four authenticated stature potions with gunpowder to make its splash variant; brew that with dragon's breath to make its lingering variant. Brewing preserves the stature kind, not arbitrary cosmetic renames/lore. Ordinary potions and cancelled brewing/application events are not overridden. Renaming an ordinary item cannot turn it into a stature potion.

Each splash/cloud applies once per player, without recipient opt-in. The first application saves the player's original base scale. Further applications operate on the temporary scale and reset expiry to five minutes after the latest application, including a valid application already at a stature bound. Growth/shrinking respect the current limits; throwable Restoration sets temporary scale to exactly 1.0.

Example: 1.0 → 0.8, then 0.8 → 0.6 four minutes later, returns to 1.0 five minutes after the second application. Expiry restores the exact original baseline, even if administrator limits changed meanwhile. Offline time counts. Baseline, expiry, and application receipts are persisted; a pending restoration survives disconnect during persistence and is acknowledged only after live application. After that sequence is cleared, ordinary later joins/respawns use the usual limit policy.

Drinking a permanent stature potion ends the temporary sequence, using the current temporary scale (or restored baseline if already expired). Administrator height changes also end the sequence. File writes are serialized off the server tick thread; failed saves do not apply an unsaved change. Disable waits for the active writer and drains its result before returning. Do not forcibly kill the server while it is saving.

Heights tracks only its loaded clouds and checks them every five ticks, dispatching AreaEffectCloudApplyEvent and honoring cancellation and recipient filtering. This supports effectless stature clouds without adding a vanilla status effect. Online expiry is checked every second. Durable receipts survive cloud unload and are retired on observed permanent entity removal; abrupt process termination can leave harmless orphan receipts.

Verification: automated domain and Bukkit-boundary tests cover this implementation. Actual brewing, cloud delivery, client appearance, and logout/restart gameplay on Purpur 26.2 build 2618 still require manual acceptance checks.

Consensual carrying (US-010; live acceptance pending)

Sneak-right-click another player with your main hand to request a ride or pickup. The larger player is always the carrier, regardless of who asks. The other player has 30 seconds to explicitly accept:

/heights carry accept
/heights carry decline
/heights carry stop

These commands require no administrator permission; settings and player-height commands still require spigotheights.admin. Console cannot carry players. One outstanding request per participant prevents replacement/ambiguous consent. Either participant can withdraw a pending request with stop; decline rejects an incoming request. Requests and carry tracking are not persisted.

Both players must be available and within 4 blocks, in the same world, when requesting and accepting. Their effective scale difference must be at least three current adjustment steps (normally 0.3), including other plugins' attribute modifiers. Neither may already have a vehicle or passengers. Heights permits only one rider per carrier, and blocks additional/nested mounts involving an active pair.

Either player can stop with normal Minecraft dismounting. Heights calls the rider's native leaveVehicle() and allows ordinary sneak-dismounts, leaving placement, falling, damage, and environmental hazards to Minecraft. There is no safe-ground requirement or search, rescue teleport, saved-position/spawn fallback, motion/fall-distance reset, invulnerability, or recovery system. Getting off above a drop is a gameplay risk.

Eligibility is rechecked every five ticks, including temporary potion application/expiry, administrator edits and external scale modifiers. Death, disconnect, plugin disable and loss of eligibility attempt native cleanup. For observed teleport events, Heights detaches the pair and lets the original teleport continue, without replaying or redirecting it. Native carrier teleports that refuse passengers before emitting an event may still require /heights carry stop first.

Server/plugin cancellation remains authoritative: a refused dismount leaves accurate tracking and is reported, not bypassed or called successful. A cancelled voluntary stop can be retried by either player; automatic eligibility cleanup continues checking and reports refusal once per ride rather than spamming. Lifecycle/disable refusals are logged. Native dismount events are reconciled after dispatch so a later cancellation is honored. An unrelated vehicle is never ejected during stale-pair cleanup.

Verification: automated domain and constructed Bukkit-event tests are not live-server evidence. Purpur 26.2 build 2618 still needs checks for scaled rider positioning and movement, ordinary dismount placement/falling, cancellation interoperability, both-role death/disconnect, portal/cross-world teleports, plugin disable and eligibility changes. No throwing or added launch force, player items, storage, or changes to throwable-potion opt-in behavior are included.

Tiny-player launchers

A player below the configured scale threshold can walk onto a hopper whose output points into a dispenser. If the block in front of that dispenser is passable, the player is moved there and launched in the direction the dispenser faces. The launcher does not require redstone.

Configuration

Defaults are in src/main/resources/config.yml:

height:
  minimum: 0.4
  maximum: 2.0
  adjustment-step: 0.1
launcher:
  maximum-player-scale-exclusive: 0.5
  speed: 1.5
  cooldown-ticks: 20

Player scales are stored by UUID in plugins/SpigotHeights/state.yml.

Commands

Operators (or senders granted spigotheights.admin) can use:

/heights settings
/heights set min 0.2
/heights set max 3.0
/heights player Steve
/heights player Steve 0.5

Console is supported. Tab completion suggests subcommands, bound names, and valid example values; other valid numbers may also be entered.

Changes are saved to plugins/SpigotHeights/config.yml and take effect without a restart. Minimum must be at least 0.0625, maximum at most 16.0, minimum cannot exceed maximum, and the launcher threshold must remain within the range. Invalid changes or save failures leave active settings unchanged.

Players are not immediately resized. Subsequent potion use, joins, and respawns use the new limits; Restoration still returns and preserves exact scale 1.0. Processing an expired temporary sequence is another exception: its exact baseline is restored before ordinary later joins/respawns follow the new limits. The settings commands only change min/max; edit other settings in the configuration file and restart the server.

Player height

/heights player <name> reports an online player's scale (1.0 = normal size). If another plugin adds scale modifiers, both the base scale and effective scale are shown.

/heights player <name> <scale> sets that player's base scale by UUID after an asynchronous durable save and ends any temporary sequence. Values must be finite and within current min/max limits, except 1.0 is always allowed. Saved scales follow the usual limits on reconnect and respawn if configuration changes later. A failed save leaves the player's height unchanged.

Player names must match an online player exactly (case-insensitive); partial names and offline players are rejected. Tab completion suggests online names and valid example sizes. Operators, console, and senders with spigotheights.admin may view or set heights, including their own.

Build

./gradlew clean check jar

The plugin JAR is written to build/libs/.

Releases

Gitea Actions checks pushes and pull requests and stores a development JAR. Pull requests validate conventional commits. Main-branch conventional commits drive semantic releases when the repository defines a RELEASE_TOKEN with contents-write permission.