What Is Dynmap-Residence and Why Your Server Needs It
If you run a Minecraft server with protected residential areas, you already know how important it is to let players see where they can build. The dynmap-residence plugin bridges the gap between two essential tools: Dynmap, the live web-based map, and Residence, the powerful land protection system. It automatically draws the outlines of every claimed residence directly onto your Dynmap, making boundaries crystal clear for everyone without any manual work.
Instead of guessing where a neighbor’s plot ends or constantly typing commands to check region info, players can simply glance at the map. This plugin listens to Residence zone updates and refreshes the display on a configurable timer, so the map always stays up to date. It’s a lightweight layer that sits between Dynmap and Residence, using the Residence API to fetch data and Dynmap’s rendering engine to draw it.
How It Works Under the Hood
Dynmap-residence depends on both Dynmap (version 1.7.1 or later) and Residence (version 2.6.6.5 or later). Once installed, it automatically detects all existing zones and subzones and begins plotting them on your web maps. Updates happen in two ways: by a periodic full refresh (default every 300 seconds) or by listening for custom update events fired by Residence itself. This dual approach ensures that changes appear quickly without hammering your server’s performance.
One of the clever design choices is the ability to restrict outline visibility based on zoom level. With the minzoom setting, you can make region borders disappear when a player is zoomed out too far, keeping the map clean at world scale and only revealing details when someone zooms in. This is especially handy on large servers where hundreds of small plots would otherwise clutter the global view.
Installation and First Steps
Getting dynmap-residence running is straightforward. Download the distribution zip, extract it into your server’s plugins/ folder, and restart. The plugin will generate a default configuration file and immediately start displaying all Residence zones. If you were previously using the built-in region component for Residence inside Dynmap, remember to disable that support to avoid double-rendering or conflicts.
Many server owners appreciate how easy it is to manage plugin setups these days. While the manual method works perfectly, you can also install this mod effortlessly through the foxygame.net launcher, a flexible and modern Minecraft launcher that lets you download plugins directly from its menu, saving time and reducing the chance of version mismatches.
After the first load, you’ll find a config.yml inside plugins/dynmap-residence. The default settings are sensible, but customizing them unlocks the full potential. The configuration revolves around a few core parameters:
- visibleregions – A list of region names to explicitly show. Use
world:<worldname>to make all regions in a world visible. - hiddenregions – A list of region names to hide, again supporting the world-level wildcard.
- minzoom – The minimum zoom level at which outlines appear. Set to 0 to always show them.
- updateperiod – The interval (in seconds) for automatic full refreshes. Default 300.
These lists give you fine-grained control. For example, you might hide all regions in a creative world while showing only specific admin zones, or reveal everything in a survival world but only when players zoom in past level 2.
Fine-Tuning Visibility and Performance
The visibleregions and hiddenregions settings accept both individual region names and world-based patterns. If you list world:survival under visible regions, every residence in that world gets drawn. Conversely, placing world:creative under hidden regions blanks the entire world. You can mix and match—hide a few sensitive regions while leaving the rest of the world visible, or show only a handful of important plots on an otherwise empty map.
Because the plugin uses the Residence API directly, it respects all permission and ownership rules. Players will only see zones they have access to, and the map never leaks private boundaries. The automatic update system means you never have to reload or run a command when someone claims new land; the map catches up within a few minutes at most.
Metrics and Transparency
Dynmap-residence uses Hidendra’s plugin metrics system to collect anonymous usage data. This helps the developer understand how many servers rely on the plugin, what Java versions are common, and how many players are online. The collected information includes a unique identifier, server version, Java version, online mode status, plugin version, OS details, CPU core count, and player count. No personal or world data is ever transmitted. You can opt out by editing the metrics configuration if your server policy requires it.
Why This Plugin Is a Must-Have
Combining Dynmap and Residence without dynmap-residence means your map is blind to land claims. Players must constantly run /res info or rely on signs and fences. With this plugin, every plot becomes a clearly outlined shape on the live map, reducing disputes and making server navigation intuitive. The automatic sync and low performance footprint mean you can set it and forget it.
Whether you run a small community server or a large network, dynmap-residence adds a layer of polish that players immediately notice. It turns a static map into an interactive land registry, all without requiring any extra work from your staff. Just install, tweak the config to your liking, and let the outlines draw themselves.