You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
enable_homes and enable_warps config switches to turn the home and warp systems on or off
independently (the back system already had enable_back). Disabled systems hide all of
their commands and respond to /fiwwarp reload.
Player-created warps: warps_players_can_create lets non-admins use /setwarp up to max_warps_per_player each (admins stay unlimited). Each warp remembers its creator —
non-admins can only /delwarp//editwarp their own; admins can manage any warp.
Warp confirmation: /warp <name> now prompts a clickable [Accept]/[Deny] message
before the warmup starts (like a teleport request), controlled by warp_confirmation_enabled
and warp_confirmation_seconds. New /warp accept and /warp deny commands. Set warp_confirmation_enabled to false for the old instant behavior.
Separate cooldowns per command: home_cooldown_seconds, warp_cooldown_seconds, and back_cooldown_seconds replace the single cooldown_seconds, each ticking independently.
Visual polish for teleports: vanish_particles_enabled adds an extra "poof" burst at the
spot a player teleports away from, and instant_teleport_blindness_enabled gives a short,
purely cosmetic Blindness effect (instant_teleport_blindness_seconds, default 2s) on any
instant teleport (no warmup), so instant hops feel less jarring.
Every player-facing message is now customizable via a messages object in config.json —
reword any text the mod sends, with {placeholder} tokens for dynamic values.
Changed
cooldown_seconds was replaced by home_cooldown_seconds / warp_cooldown_seconds / back_cooldown_seconds. If you had a custom cooldown set, re-apply it under the matching key.
Built jar files are now named fiw-warp-fabric-*.jar / fiw-warp-neoforge-*.jar
(the loader mod id stays fiwwarp).
License changed to MIT.
Notes
warps.json from 1.0.0 loads and migrates automatically — existing warps keep working with
no owner (admin-managed), same as before.
Don't name a warp accept or deny; those are reserved /warp subcommands. /setwarp and /editwarp now reject those names, and the server logs a warning on startup if a warp with
a reserved name already exists from before the upgrade.