Step by step: getting an IP or hardware binding reset through a Discord ticket, what to include, and fair use.
When your server's IP or hardware changes, the binding recorded on the license server has to be updated — and that update is performed by the staff, personally. Resets are ordinary operations (hosts migrate, hardware gets upgraded), and the process is a single Discord ticket. This page walks through it.
/force ip-reset or /force hw-reset on your license.Order ID: (paste from Dashboard → Order history)
Product: BedWars
Change: Moved from the old host to a new VPS —
old IP 203.0.113.10 → new IP 198.51.100.42
Timing: Migration tonight ~22:00 UTC, old server is up until then.That is everything a staff member needs to act in one pass: no back-and-forth, no waiting for clarifications. The example above uses documentation IP addresses — yours are the real ones from your host's panel.
Resets exist for legitimate infrastructure changes: migrations, hardware upgrades, host moves. They are performed personally by staff, which is also why abusive repeat resetting can be refused — a pattern of constantly rotating servers is what license sharing looks like, and the reset flow will not become a loophole for it.
Normal use never comes close to that line. A handful of resets over the life of a license — the honest footprint of real infrastructure work — is exactly what the feature is for, and it is handled without friction.
Tip:Open the reset ticket before you shut down the old server. A reset timed with your migration window means no downtime waiting on staff.