MCSkylines-Property

Configuration defaults: Values shown for operator-configurable settings are the bundled defaults, and can be changed in the module’s configuration or definitions. The server’s active settings take precedence, so costs, speeds, ranges, durations, chances, effects, recipes, limits and enabled features may differ. Command examples illustrate syntax; fixed mechanics and validation bounds are not configuration defaults.

Property maps WorldGuard regions to owned parent parcels, child plots, sale listings and guarded leases. Use Suite installation; retain the existing Property data and legacy migration backups.

Recommended property setup workflow

Create and verify the WorldGuard parent region before registering it. Register that region to the owning player, then let the landlord create child rental plots with the Property wand. Left-click sets corner one and right-click sets corner two; the selection is rejected and cleared immediately if it leaves the parent parcel, crosses someone else's managed property, or overlaps an existing plot.

For a rental listing, set both price and duration before advertising it. Give tenants the full guarded command including expected price and expected duration so a changed listing cannot charge them silently. Purchased listings become ordinary parent properties and can hold new child rentals.

Rental lifecycle

Rent payment uses Economy when its compatible API is active, otherwise the registered Vault provider. On a successful lease, the tenant is synchronized into the child WorldGuard region as a member. Renewal repeats the expected-terms check and extends the lease according to the configured behavior. Expiry removes membership but never resets blocks, empties containers, or teleports the former tenant.

Active leases protect both the Property record and its WorldGuard region from removal. A landlord or administrator must wait for or otherwise resolve the lease. Quick deletion additionally refuses collateral, parent parcels with children, and other unsafe states.

Sales, ownership, and nested plots

/prop buy <name> [expected-price] transfers the listing to the buyer after payment. The result is a parent-capable owned property, not a lease. Property synchronizes landlord ownership to WorldGuard and preserves active child lease behavior. Staff teleport is an administrative convenience only; the plugin has no automatic home or landlord teleport system.

Economy integration

When Economy is active, Property registers the property collateral type and property-tax provider. Parent parcels count by default; ALL_PROPERTIES includes child plots. Collateral locking prevents unsafe transfer or deletion. Seizure transfers landlord ownership while preserving active tenants rather than evicting them or resetting their builds.

Utilities and industrial ownership

Utilities uses the Property landlord UUID as each machine's owner. Tenancy or WorldGuard membership alone does not grant machine operation. Owners explicitly add operators with /utilities access add <player-or-UUID>. Ownership changes clear delegated operators and remove links touching affected machines.

One Utilities meter serves each registered plot. Infrastructure staff connect that meter to a named grid. Staff separately approve machinery with /utilities industrial on; this is plot authorization, not chunk loading. All machinery except meters requires approval. Registered street lamps and meters may serve ordinary properties.

Entry notices while driving

Property entry is checked for moving passengers as well as walking players. The three-second property action-bar notice has priority over vehicle telemetry, so the region name remains visible to a driver until the notice expires. Ordinary telemetry then resumes. Entry messages still use the configurable property-enter-actionbar message with {property} and {region} placeholders.

Current boundaries

Property manages records, payment, ownership/member synchronization, and safety rules. It does not restore terrain, clear inventories, reset rented builds, create homes, or migrate money between incompatible Economy providers. The legacy command aliases exist for compatibility, but new instructions should use /prop and property.*.

Selection, listing, and pricing workflow

Register a pre-existing parent region with /prop admin register <region> <player>. The landlord obtains /prop wand: left-click selects corner one, right-click corner two. Feet-position pos1/pos2 are fallbacks. The whole cuboid must stay within the landlord's parent, avoid another owner's managed property and avoid plot overlaps; invalid selections clear both points. Complete WorldEdit/FAWE cuboids are accepted only when a complete Property selection is absent.

Create child rental with /prop plot create <name> <price> <duration>. Staff can register existing sale/rental regions or use quick commands to create one from a selection. Set complete terms before advertising. Rent and renew accept guarded expected terms or open a menu to confirm the current offer. Price changes cannot silently charge stale terms. Sale optionally accepts expected price.

Configuration and persistence

Review limits, durations, taxation scope, collateral and entry notices in Property configuration/messages. Current canonical command is /prop, permissions are property.*; legacy areashop.* permission checks remain accepted. Public APIs provide ownership/collateral rather than restoring terrain. Entry notices identify the innermost plot and retain action-bar priority for three seconds while driving. Database and matching WorldGuard region state must be backed up together.

SQLite and MySQL storage

SQLite remains the default, including for existing config files without database.type. Set database.type: MYSQL and configure database.mysql.host, port, database, username, and password to use a pre-created MySQL database. MySQL 8+ and MariaDB use InnoDB transactions and the bundled Connector/J driver. Core tables have a core_ prefix and Property tables have a property_ prefix, so both can share the Economy database without overlapping its tables.

database.mysql.use-ssl: true requires encrypted transport. For a local database without TLS, explicitly set it to false. allow-public-key-retrieval defaults to false; enable it only when the configured MySQL authentication needs it. Connection/backend changes require a server restart. Switching backends does not copy or delete existing records: a fresh remote database starts empty. Keep the existing SQLite files if you might switch back. SQLite file, busy-timeout, startup backup and integrity-check settings apply only to SQLite; arrange server-side backups for MySQL. The configuration schema remains config-version: 1.

Property menus, trading signs, and optional targets

Use /prop to browse your properties, then select Available listings to shop. /prop gui [property] (alias /prop menu) opens the named property, or the innermost managed property you stand in. Outside managed land it opens the browser. The browser is paginated; staff with property.list can also browse all properties. property.gui grants menu access and defaults to true. Individual action permissions, ownership, lease, collateral, and child-plot checks still apply when a button is used. Menus show owner, tenant, current price/duration, and lease expiry in UTC.

The menu supports buying, renting, renewing, ending your lease, changing listing price/duration, listing your property for resale, cancelling its sale, and removing eligible registrations. Purchases and leases display a confirmation button with the offered price and duration; a changed offer fails instead of charging a new amount. Vacating and removing also require a confirmation click. Vacating has no refund. Price/duration buttons accept one chat value within 60 seconds; cancel aborts. Starting another menu cancels any earlier pending input. The selected property remains the target; moving to another world aborts the action.

To link a trading sign, write [Property] on its first line and the managed region ID on the second. Leave the second line blank to use the property you stand in. [AreaShop] and [as] are accepted link tags. [asbuy] and [asrent] link an existing sale/rental listing of the matching type; they do not create regions or take prices from the sign. Register and price the listing first. Multiple signs can link to one property, including signs outside its boundary in the same world. The owner needs property.sign (true by default); staff can link/remove any sign with property.admin.sign (included in property.admin). Normal WorldGuard build permissions still apply to placement and breaking.

Both sides show sale/rent/leased/owned status and current terms. Right-click opens the management menu without taking money. The confirmation button performs the guarded transaction. Signs are waxed against edits; owners or authorized staff can break them. Links live in the sign block's persistent data and survive restarts. Loaded signs refresh every five seconds; unloaded chunks are never forced to load. A sign for an unregistered property shows unavailable and cannot trade. Signs do not replace or migrate old AreaShop sign blocks automatically. All menu labels, prompts, sign lines and feedback are configurable MiniMessage values in messages.yml; missing new keys are added on startup/reload without replacing custom wording.

/prop sell <price> [property] (alias resell) lists your owned parent property for a future buyer. /prop stopresell [property] cancels the listing. Both require property.sell (true by default). Listing pays nothing immediately: you retain ownership until another player buys it and pays through the existing economy gateway. Child plots, active leases and collateral block resale. Remove child plots before listing a parent. While listed, the parcel cannot receive new child plots. This suite has no automatic server buyback/refund for selling property.

For existing-property commands, an omitted target means the smallest containing managed region in your current world; ties use the region ID consistently. An explicit name always overrides your location. Outside managed land, specify a name. New-region names for plot create, quickbuy and quickrent remain required. create and admin register can omit the region and use the smallest containing WorldGuard region, even before it is managed.

Examples while standing inside a property:

• /prop info, /prop buy, /prop vacate (alias unrent), /prop stopresell.
• /prop rent or /prop renew opens its menu for offered-term confirmation.
• /prop rent 250 7d and /prop renew 250 7d immediately submit those guarded

terms. Existing /prop rent apartment_1 250 7d syntax continues to work.

• /prop buy 250 buys the current property only if the price is still 250;

an existing numeric region named 250 takes precedence as an explicit target.

• /prop sell 50000, /prop setprice 250, /prop setduration 7d.
• /prop plot terms 250 7d, /prop plot remove.
• /prop delete, /prop quickdelete, /prop admin unregister, /prop admin tp.
• /prop admin landlord Alex, /prop admin register Alex, /prop create buy.

Owners with property.plot.terms can change their own listing price/duration; staff use property.admin.terms to edit other owners' listings. Price must be positive and within configured limits. Active leases and collateral remain protected. property.info and property.list retain their existing restricted defaults; property.gui separately grants public listing discovery and own-property management. Legacy areashop.* equivalents of the checked permissions remain accepted.

Reading command syntax

Configuration defaults: Values shown for operator-configurable settings are the bundled defaults, and can be changed in the module’s configuration or definitions. The server’s active settings take precedence, so costs, speeds, ranges, durations, chances, effects, recipes, limits and enabled features may differ. Command examples illustrate syntax; fixed mechanics and validation bounds are not configuration defaults.

<argument> is required; [argument] is optional. Replace the placeholder, including its brackets, with your value. Choices separated by a vertical bar mean choose one. ... accepts the remaining words. Do not type quotation marks around multiword names unless the command specifically requires them. A bare command has no required arguments. Examples use sample players/IDs: substitute entries from your server and use Tab for configured IDs.

player means a username; operational actions usually require that player online. amount and price are currency values such as 25.00, unless the row specifies items, levels, or units. reason, memo, message, name, and statement accept text where supported. duration uses the module's duration format (for example 10m, 2h, or 7d); it is not a bare number of minutes unless stated. id is the exact identifier displayed by that system, not its friendly name. Permissions and ownership/state/location checks both apply.

Property commands

Operations use your current world and require an in-game player for selections/listings. A name/region is a region/property ID in that world. Prices are positive currency; durations such as 7d are parsed lease times. Canonical permission prefix is property; legacy areashop equivalents remain accepted.

Example: /prop info apartment_1, then /prop rent apartment_1 250.00 7d using exactly its displayed terms. Renew accepts the same forms; omitting both expected terms opens the confirmation menu. An omitted target uses the innermost containing property. Explicit names override location. New-region names remain required. The shorthand /rent is a root alias, so use its full subcommand syntax; prefer /prop rent to avoid ambiguity.

Root commands and aliases

These are the registered command entry points. The subcommand tables above describe their complete operations. Alias names use the same arguments as their root.

Menus, resale, and signs

Link signs with [Property], [AreaShop], or [as] on line one and the region ID on line two (blank uses the current property). [asbuy]/[asrent] require an existing matching listing. Sign creation/removal requires property.sign and ownership, or property.admin.sign for staff, plus normal build access. Right-click opens the menu; the confirmation button submits the displayed price/duration. See the Property guide for lifecycle, persistence, resale restrictions and chat-input behavior.