Explain why a HuskHomes teleport has no warmup

An immediate teleport is not always a broken timer. HuskHomes supports both a permission-based warmup duration and a separate bypass. Staff accounts commonly differ from regular players, so compare like-for-like access before changing the delay for everyone.

Before you change settings

Choose one home in a safe location and record the configured warmup, affected player, server and permission context. Keep the same destination for each attempt so a different command or plugin cannot change the test halfway through.

Follow the request through the plugin

  1. Check whether the affected player inherits huskhomes.bypass_teleport_warmup. A deliberate staff bypass should not be copied into a public rank just to make a test pass.
  2. Inspect numeric huskhomes.teleport_warmup. permissions. HuskHomes documents that the highest applicable numeric value wins, even when stacking is enabled for other limits.
  3. Compare a non-operator account with the affected account. Trigger the same HuskHomes home command, stand still and record the message and elapsed delay rather than estimating from the animation.
  4. Adjust only the incorrect permission or documented warmup setting. Retest a member and a staff account, checking that intended staff access and member delays both match your policy.

Confirm the intended result

Your member account should wait the expected interval before arriving. The staff account should follow whichever exception you deliberately retain. Test again after reconnecting, because an old session can make a group change harder to interpret.

If the test fails

If neither account follows the configured duration, confirm that HuskHomes owns the command. Another homes plugin can register the same label. A non-positive configured delay also needs checking; permission changes cannot prove which command handler actually ran.

Restore the earlier warmup and permission entries if the change affects unrelated players. Keep the timing notes and command ownership evidence; do not grant operator status as a workaround for a teleport delay.


Revision #1
Created 2026-11-09 16:36:27 UTC by CloudExa Hosting Admin
Updated 2026-11-09 16:36:27 UTC by CloudExa Hosting Admin