# JourneyMap Land Registry A client-side Fabric add-on for JourneyMap that records parcels, owners, designated land uses, colors, tags, and claimed chunks in a local SQLite database. Registered parcels appear as colored overlays on JourneyMap. > [!IMPORTANT] > This mod is informational and local to one Minecraft client. It does not enforce claims on a server, synchronize data with other players, or verify ownership. ## Requirements - Minecraft 26.1.2 - Fabric Loader 0.19.3 or newer - Fabric API 0.155.2+26.1.2 or compatible - JourneyMap 26.1.2-6.0.2 for Fabric or newer compatible release - Java 25 ## Installation 1. Install Fabric Loader for Minecraft 26.1.2. 2. Download Fabric API and JourneyMap for Minecraft 26.1.2. 3. Download the JourneyMap Land Registry release JAR. 4. Place all three mod JARs in the Minecraft `mods` directory. 5. Start Minecraft with the Fabric profile. JourneyMap Land Registry is client-side only. A server does not need to install it. ## Basic Usage Open a world or join a server and ensure JourneyMap has started mapping it. Parcel data is stored separately for each mapped world. Create a parcel and add the chunk where your player is standing: ```text /parcel create Spawn /parcel chunk add Spawn ``` Running `/parcel` by itself shows information for the parcel at your current chunk. Use `/parcel info ` to inspect a parcel by name. New parcels receive a random unique color selected to contrast with existing parcel colors. Colors can be changed manually or kept distinct from touching parcels with auto-color. ## Commands | Command | Description | | --- | --- | | `/parcel` | Show parcel information for your current chunk. | | `/parcel list` | List all parcels and their chunk counts. | | `/parcel info ` | Show a parcel's owner, use, color, chunks, and tags. | | `/parcel create ` | Create a parcel. | | `/parcel rename ` | Rename a parcel. | | `/parcel delete ` | Delete a parcel. | | `/parcel export ` | Export a consistent copy of the complete land registry database. | | `/parcel import ` | Replace the current registry from an exported database after creating a backup. | | `/parcel chunk add ` | Add your current chunk to a parcel. | | `/parcel chunk add ` | Add specified chunk coordinates in your current dimension. | | `/parcel chunk remove ` | Remove your current chunk from a parcel. | | `/parcel owner list` | List registered owners. | | `/parcel owner create ` | Create an owner. | | `/parcel owner set ` | Assign an owner to a parcel. | | `/parcel owner reset ` | Reset a parcel to unowned. | | `/parcel use set ` | Set a parcel's designated use. | | `/parcel use reset ` | Reset designated use to `Custom`. | | `/parcel description set ` | Set a parcel description. | | `/parcel description reset ` | Clear a parcel description. | | `/parcel color set ` | Set RGB color and optionally an alpha transparency override. | | `/parcel color auto enable ` | Automatically contrast the parcel with parcels that share a chunk edge. | | `/parcel color auto disable ` | Keep the parcel's current color and stop automatic updates. | | `/parcel color reset ` | Reset color to cyan and use the global parcel opacity. | | `/parcel tag add ` | Add a tag to a parcel. | | `/parcel tag remove ` | Remove a tag from a parcel. | | `/parcel tag reset ` | Clear all tags from a parcel. | | `/parcel reset ` | Reset owner, use, description, color, and tags. | ### Parcel Groups Parcel groups let the same management action be applied transactionally to several parcels. A parcel may belong to multiple groups. Deleting a group only removes the group and its memberships; the parcels remain registered. | Command | Description | | --- | --- | | `/parcel group list` | List parcel groups and their member counts. | | `/parcel group info ` | List the parcels in a group. | | `/parcel group create ` | Create a parcel group. | | `/parcel group rename ` | Rename a parcel group. | | `/parcel group delete ` | Delete a group without deleting its parcels. | | `/parcel group add ` | Add a parcel to a group. | | `/parcel group remove ` | Remove a parcel from a group. | | `/parcel group owner set ` | Assign an owner to every parcel in a group. | | `/parcel group owner reset ` | Reset every parcel in a group to unowned. | | `/parcel group use set ` | Set the designated use for every parcel in a group. | | `/parcel group use reset ` | Reset designated use for every parcel in a group. | | `/parcel group description set ` | Set every parcel description in a group. | | `/parcel group description reset ` | Clear every parcel description in a group. | | `/parcel group color set ` | Set RGB color and optional alpha for every parcel in a group. | | `/parcel group color auto enable ` | Enable auto-color for every parcel in a group. | | `/parcel group color auto disable ` | Disable auto-color for every parcel in a group. | | `/parcel group color reset ` | Reset every parcel color in a group. | | `/parcel group tag add ` | Add a tag to every parcel in a group. | | `/parcel group tag remove ` | Remove a tag from every parcel in a group. | | `/parcel group tag reset ` | Clear tags from every parcel in a group. | | `/parcel group reset ` | Reset metadata for every parcel in a group. | Command completion suggests existing parcel and owner names. Quote parcel names containing spaces when another argument follows them, for example: ```text /parcel owner set "Town Square" Builder /parcel color set "Town Square" 00FFFF /parcel color set "Town Square" 00FFFF80 /parcel chunk add "Town Square" -4 12 ``` Eight-digit colors use `RRGGBBAA`; for example, `00FFFF80` is cyan at approximately 50% opacity. Six-digit RGB colors continue to use the Mod Menu parcel opacity setting. Auto-color updates whenever registry data changes, including when chunks are added or removed. Only parcels sharing a cardinal chunk edge in the same dimension affect the automatic color; diagonal chunks do not. Automatic updates change RGB while preserving a parcel's alpha override. Setting or resetting a color manually disables auto-color. A chunk can belong to only one parcel. ## JourneyMap Integration - Parcel boundaries use each parcel's configured color. - Each parcel displays its name once, in its largest connected region. - With Mod Menu installed, use the **Parcel opacity** and **Border thickness** sliders to customize parcel displays. - Use the **Parcels On/Parcels Off** button in JourneyMap's add-on controls to toggle all parcel overlays and labels. - Toggle **Select Chunks** in JourneyMap's add-on controls, then left-click chunks to add or remove them from the highlighted selection. - Use **Land Registry > Chunks** to add or remove all selected chunks, or create a parcel to claim the full selection. Successful actions clear the selection. - Right-click a chunk on the fullscreen map and open **Land Registry** to access parcel, chunk, owner, use, description, color, tag, and reset actions. - Use **Land Registry > Color > Toggle auto-color...** to enable or disable automatic contrast for a parcel. - Use **Land Registry > Groups** to create and inspect groups, manage membership, or apply owner, use, description, color, auto-color, tag, and reset actions to all members. - Use **Land Registry > Database** to export the complete registry or import one after confirmation. - Map actions that select a parcel open a searchable parcel list. ## Database Transfer Exports are complete SQLite snapshots containing parcels, owners, groups, memberships, tags, chunks, and settings. Relative command and map-menu paths are resolved from the Minecraft game directory; absolute paths are also accepted. Imports replace the current registry data. Before replacement, the mod writes a timestamped `land-registry.backup-*.sqlite` snapshot beside the active database. Imported databases are copied, migrated if necessary, and integrity-checked before any active data is changed. The active world's identity is retained, and invalid or unsupported databases are rejected without changing the current registry. ## Building From Source The Gradle wrapper provisions the required Java 25 toolchain automatically. On Linux or macOS: ```bash ./build.sh ``` Alternatively, on any supported platform: ```bash ./gradlew clean build ``` Built JARs are written to `build/libs/`. Use the regular mod JAR, not the sources JAR. To launch a development client: ```bash ./gradlew runClient ``` ## Data and Backups Parcel records are held in a world-scoped `land-registry.sqlite` database inside JourneyMap's add-on data directory. Back up the relevant JourneyMap world data before deleting or replacing Minecraft instances. Removing the mod does not transfer its records to another client. ## License JourneyMap Land Registry is available under the [MIT License](LICENSE).

JourneyMap Land Registry

Compatibility

Minecraft: Java Edition

Platforms

Supported environments

Links

Tags

Creators

Details