Skip to main content
Version: 1.4

FAQ

Does this support Paper only, or Spigot too?​

It targets the Bukkit/Paper API level for 1.21+ and is intended for Paper/Spigot server environments.

Does it work with Folia?​

Yes. The plugin declares folia-supported: true and uses region-aware scheduling via reflection. Delayed block updates and shared-state access use Folia-aware scheduling automatically.

Can players opt out individually?​

Yes. Players can toggle all behavior or specific block families with /doubledoors toggle subcommands.

Can I disable all behavior quickly during an incident?​

Yes. Use /doubledoors server-toggle to flip the global runtime switch.

Can players change their language?​

Yes, if perPlayerLocaleEnabled is enabled in config.yml. Players can use /doubledoors locale <code> to set their locale, /doubledoors locale credits to list translation credits, and /doubledoors locale credit <code> to inspect one language file.

Why are there delayed sync tasks?​

Delays ensure the plugin reads final post-vanilla block state rather than pre-update state when running at MONITOR priority.

Is GriefPrevention required?​

No. It is optional. If present, linked partner checks are attempted through reflection. Per-claim villager blocking is available via /doubledoors grief villagers.

Does WorldGuard work with this?​

Yes. WorldGuard is an optional soft dependency. When present, linked door actions can be restricted by build permission, USE flag, and a custom state-flag (double-doors-allow). Region blacklists/whitelists are also supported.

Can I restrict linking to specific regions or locations?​

Yes. Two filter systems are available:

  • Location filters (locationFilter.mode): Whitelist or blacklist exact world:x:y:z coordinates.
  • WorldGuard region filters (worldGuardRegionFilter.mode): Whitelist or blacklist WorldGuard region IDs.

Is recursive opening only for gates and trapdoors?​

Recursive BFS grouping is used for non-door openables. Under current implementation, the recursive feature flag also gates linked state application in all paths.

Where are player preferences stored?​

In plugins/DoubleDoors/players.yml by default. When SQL storage is enabled (sql.enabled: true), preferences are stored in the configured database.

Can I edit players.yml while server is running?​

You can, but best practice is to use in-game commands and then /doubledoors reload for consistency.

Can players manually open iron doors?​

Yes, if they have the doubledoors.iron.manual permission (default: op). This allows right-click toggling of iron doors, which is not possible in vanilla Minecraft.

What is anonymous tracking?​

DoubleDoors can optionally send anonymous usage metrics via FastStats (e.g., which features are enabled, server language, detected plugins). All data is public at https://faststats.dev/project/double-doors-server. Disable with enableAnonymousTracking: false. See Telemetry for the full details.

Can I use the plugin API from other plugins?​

Yes. DoubleDoors exposes a DoubleDoorsAPI interface for third-party integration. See API for details.

How do I troubleshoot linked doors not syncing?​

See Troubleshooting. The /doubledoors debug command shows diagnostic messages about partner matching, location filter blocks, and protection-plugin denials.

Can I preview which block is the linked partner?​

Yes. Use /doubledoors preview while targeting a door-like block within 8 blocks. It spawns particles at the partner block and prints its location and facing direction.