Frequently asked questions

Still stuck? Open a ticket on Discord.

What server version do I need?

Paper 26.1+. DexHomes v2 is built against it directly.

A player says they should have more homes. How do I check?

/dexhomes check <player> — it tells you exactly which rule decided their slot count, whether that's a tier permission, OP status, admin, or the default.

Do slot tiers stack?

No. A player holding vip and mvp gets the highest value, not the sum. That's deliberate — stacking is how most homes plugins end up giving someone 40 slots by accident.

Can I add my own tiers?

Yes — add, rename or delete entries under limits: freely. The permission nodes follow automatically; there's no separate list to maintain. Just keep values under settings.max-slots.

Can I raise the cap past 56?

56 is the hard cap — four pages of 14. settings.max-slots is the network limit and tier values are capped by it.

Does it conflict with EssentialsX homes?

Run one homes system, not both. Disable Essentials' /home and /delhome via its command overrides so DexHomes takes them.

Can staff be limited like normal players?

Set op-unlocks-all: false and admin-unlocks-all: false. Staff then get whatever their rank tier grants.

A particle name doesn't exist on my version. Will it crash?

No. Names are alias-resolved so modern and pre-1.20.5 names both work, and anything genuinely unavailable just drops that layer and logs it. The teleport still fires.

What happens to my config after an update?

An outdated config.yml is detected and backed up automatically — and your license key is carried across to the new one for you.

What if LuckPerms isn't installed?

Everything still works; %rank% falls back to settings.rank-fallback ("Default"). You just lose tier-based slots, since there's nothing to read permissions from.

Are homes safe from combat logging?

Yes — a 15 second combat tag blocks teleports by default, and the 5 second warmup cancels on move or damage. Both are configurable.