Skip to main content
Announcements

๐Ÿงญ Phase 1: Lands Claim Reorganization ๐Ÿก

A seven-day plan to reconnect, merge, and reorganize claims safely on the Valeriano Minecraft Server.

Phase 1 is a live claim-reorganization window for the Valeriano Minecraft Server. It is designed to help families and neighbors reconnect split claims, combine Lands when that makes sense, and recover the money spent on chunks while moving them.

๐ŸŸข The migration window is open

The server update is live and verified. Temporary 100% chunk cashback is active now. Read the paid extra-Land refund steps below before merging or deleting a second or third Land.

โฐ Migration deadline: Wednesday, August 12 at 11:59 PM Eastern Time

Finish any refund-approved deletion, chunk reorganization, and intended merge by Wednesday, August 12, 2026 at 11:59 PM Eastern Timeโ€”Thursday, August 13 at 11:59 AM Philippine Time. After the window, chunk cashback is scheduled to become 75%.

๐Ÿ’ฐ Temporary 100% chunk cashback

During the migration window, paid chunk unclaims return 100% of the chunk purchase price instead of the usual 50%.

  • The current paid-chunk price is $50.
  • Only money actually paid for a chunk can be returned; free chunks do not create free money.
  • Check the confirmation shown in game before completing an unclaim.
  • After the migration window, cashback is scheduled to become 75%. The 75% closing rate is staged but is not live during the reorganization period.

๐Ÿงฎ Reorganizeโ€”do not profit

The temporary cashback is for moving existing claims into a cleaner layout. It does not increase claim limits or turn free starter chunks into a payout.

๐Ÿงพ One-time refund for a paid second or third Land

Verified paid Land #2 and Land #3 cost $750 each. If one is merged away or deleted specifically to consolidate claims during the migration period, it can qualify for a one-time $750 staff refund.

Before merging or deleting anything

  1. Write down or screenshot the exact Land name.
  2. Contact Jethro or another server administrator before the merge or deletion.
  3. Explain which paid Land you want to merge away or delete and which Land you are keeping.
  4. Wait for staff to verify the purchase and approve the migration refund.
  5. Only then merge or delete the approved extra Land.

๐Ÿ›ก๏ธ Staff captured a private baseline

Staff recorded the eligible paid extra Lands before the update. A normal merge or deletion does not automatically refund the $750 creation cost, so record the name and contact staff before the extra Land disappears. You do not need to post receipts or private account information.

The refund applies only once to an eligible, verified paid second or third Land that disappears through a consolidation merge or approved deletion during this window. If you only move the chunks but keep the paid extra Land, there is no $750 refund yet because that Land slot still exists and can be reused. The refund is not for a free first Land, a duplicate payment, or an ordinary deletion unrelated to migration.

๐Ÿงฉ Land merging is live

The merge command is:

/land <destination> claim merge <source>

The merge command is enabled and permission-verified live. Read the confirmation carefully before accepting it.

What a merge does

  • The destination Land survives.
  • The source Land is absorbed into the destination.
  • The combined claims must be connected.
  • The merged result must contain 25 chunks or fewer.
  • If the source and destination have different owners, the source owner must accept the merge request.

๐Ÿ‘ฅ Ownership changes when you merge

Different owners should not merge if they want to keep separate ownership. Two Lands may touch safely without becoming one Land; use Claim at Border consent instead.

Claim at Border (LAND_CLAIM_BORDER) lets a specific person claim a chunk beside someone else's Land. Consent goes in only one direction.

Imagine Player A wants to claim beside Land B:

  • The owner of Land B must place Player A into a role in Land B with Claim at Border enabled.
  • Player A adding Land B's owner to Player A's own Land does not grant Player A permission beside Land B.
  • If both players need the same freedom, each Land owner must grant the other player consent separately.

A custom Family or Neighbor role is recommended so the permission is clear and easy to remove later.

๐Ÿ“ฑ Java and Bedrock-friendly menu flow

  1. Open the target Land directly:

    /land <land>

    Or open the general menu and select the Land:

    /lands menu
  2. Open Roles.

  3. Create or select a Family or Neighbor role.

  4. Enable Claim at Border for that role.

  5. Assign the player to the role:

    /land <land> member setrole <player> <role>

This owner role-management flow is enabled for both menu users and players who prefer commands. Bedrock and mobile players can use the Lands forms; Java players can use the same menu path or the command.

๐ŸŒ‰ Joining claims step by step

If two claims have a one-chunk gap and the owners want to connect them:

  1. The neighboring Land owner grants the claiming player one-way Claim at Border consent.

  2. The claiming player claims the gap chunk for the appropriate Land, creating a connected claim.

  3. Stop here if the Lands should keep separate ownersโ€”touching claims are enough.

  4. If consolidation into one owner and one surviving Land is truly wanted, run the merge command:

    /land <destination> claim merge <source>
  5. If the Lands have different owners, the source owner reviews and accepts the request.

Before claiming the bridge or requesting the merge, count carefully: the surviving Land must stay at 25 chunks or fewer.

๐ŸŽ›๏ธ What Land owners can customize

Land owners now have role-menu and member-role controls so they can configure lower roles for family, neighbors, builders, farmers, and visitors.

Only these role flags are part of Phase 1:

๐Ÿงฑ Build and interact

  • BLOCK_PLACE
  • BLOCK_BREAK
  • INTERACT_GENERAL
  • INTERACT_CONTAINER
  • INTERACT_DOOR
  • INTERACT_TRAPDOOR
  • INTERACT_MECHANISM
  • INTERACT_VILLAGER

๐ŸŒพ Farm, collect, and travel

  • PLANT
  • HARVEST
  • SHEAR
  • ITEM_PICKUP
  • VEHICLE_USE
  • LAND_ENTER

๐Ÿ‘ค Membership and claiming

  • PLAYER_TRUST
  • PLAYER_UNTRUST
  • PLAYER_SETROLE
  • LAND_CLAIM
  • LAND_CLAIM_BORDER

๐Ÿ” These are Land permissions, not admin powers

Role flags only control ordinary actions inside that Land or at its border. They do not grant server administration, bypass protection, or override the owner and server limits.

๐Ÿšซ What Phase 1 does not enable

This update does not enable owner-editable controls for:

  • Mobs or natural behavior
  • PvP
  • Spawn teleportation
  • Flight
  • Land banks
  • Rent or rental areas
  • Taxes or upkeep
  • Wars
  • Nations

If a menu appears to expose something outside the Phase 1 list, do not rely on it. Capture a screenshot and report it to staff.

๐Ÿ“ Current Lands limits and prices

SettingCurrent policy
Lands you may own3
Lands where you may be trusted12
Chunks per Land25
Total contributed chunks55
First LandFree
First contributed chunks per player9 free chunks
Extra Land$750
Paid chunk$50

The migration does not raise these limits. The in-game menu or confirmation screen remains the final authority before any charge or destructive action.

โœ… Quick migration checklist

  • ๐Ÿ—บ๏ธ Decide which claims should touch and which should remain separate.
  • ๐Ÿ“ธ Record the exact name of any paid second or third Land you may merge away or delete.
  • ๐Ÿ’ฌ Contact Jethro or another administrator before an eligible merge or deletion.
  • ๐Ÿค Use a Family or Neighbor role for one-way Claim at Border consent.
  • ๐ŸŒ‰ Claim a one-chunk bridge only after the neighboring owner grants consent.
  • ๐Ÿงฉ Merge only if one destination Land should survive.
  • ๐Ÿ“ Keep the merged total at 25 chunks or fewer.
  • ๐Ÿ’ฐ Confirm the shown cashback before unclaiming paid chunks.
  • โฐ Finish by Wednesday, August 12 at 11:59 PM Eastern Timeโ€”Thursday, August 13 at 11:59 AM Philippine Time.

๐Ÿก Cleaner claims, safer neighbors

Take screenshots, coordinate with the other owners, and pause whenever a confirmation does not match this guide. Staff would rather answer a question before a deletion than repair a preventable mistake afterward.