Skip to content

Community funded. No paid power. Never pay-to-win.

Our promise
AshRun
SERVER POLICY GUIDE

Claims and chunk loading on AshRun

The current limits, what they protect, and why FTB Chunks is the supported route for keeping machinery active.

Last verified 2026-09-08 · ATMons 1.3.0 · Minecraft 1.21.1 · NeoForge 21.1.249

Claim protection is enabled

AshRun uses FTB Chunks with land protection enabled. New teams default block editing, block interaction, entity interaction, and entity attacks to allies. Claims remain visible publicly on the map unless a team changes its visibility setting.

Current claim and force-load limits

Claim ceiling
500 chunks per team before rank-based overrides
Force-load ceiling
10 baseline chunks plus up to 6 earned slots
Offline loading
Disabled; a team member must be online
Idle force-load expiry
14 real-world days without a team login
Resource world claims
Blocked by dimension policy

Earn extra force-loaded chunks through trainer progression

Everyone starts with the same 10-chunk team allowance. Playing through the installed Gym campaigns can raise your limit one step at a time; supporter ranks do not change it.

Team limitMilestone
11 chunksDefeat the first Gym Leader in any campaign
12 chunksDefeat the fourth Gym Leader in any campaign
13 chunksEarn eight badges in any campaign
14 chunksBecome Champion in any campaign
15 chunksBecome Champion in two campaigns
16 chunksDefeat Red or Blue, or become Champion in all three campaigns

For a party, the highest earned tier among its recently active members sets the team limit. Run /ashrunchunks in game to see your tier, current selection, active extra allocation, and next milestone.

The AshRun chunks command showing tier 1 of 6, an 11-chunk limit, one earned slot, a healthy shared pool, and the next Gym milestone
The allowance updates in game as milestones are completed. This example moved from the 10-chunk baseline to tier 1 and an 11-chunk limit after the first Gym Leader.

How load balancing affects extra chunks

The original 10 chunks are the protected baseline. Earned chunks above 10 share a server-wide pool distributed fairly across online teams, one round at a time. When the server is under sustained load, some extra chunks can pause temporarily and return automatically after performance recovers. The oldest selected chunks stay in the baseline, so select your most important machinery first.

Use FTB Chunks, not alternate loaders

Recipes and use are disabled for the dedicated chunk-loading paths covered by AshRun’s active server policy, including AE2 Spatial Anchors, Immersive Engineering Chunk Loaders, Mekanism Dimensional Stabilizers and Anchor Upgrades, Nature’s Aura Chunk Loaders, PneumaticCraft Chunkloader Upgrades, Steve’s Carts loader modules, and the Ars Additions chunk-loading ritual.

If an item tells you that it is prohibited, open your inventory and select FTB Chunks: Claim Manager. Left-click a map square to claim it, then Shift-click that claimed square to toggle force-loading. The counters along the bottom show both totals.

FTB Chunks Claim Manager with one claimed chunk marked as force-loaded and counters showing 1 of 500 claimed and 1 of 11 force-loaded
A striped claimed square is actively force-loaded. Hovering it shows the status, and the lower-right counter shows how many of the team’s available slots are in use.

The restriction keeps loading visible, bounded, and attributable to a team.

Protect only the area you actually use

Claim your base, storage, machines, farms, and access routes. Force-load only chunks that need active processing while you are online. Large idle areas add work without helping your build, and selecting all six earned extras is optional.

Related rules

Claims do not replace the server rules. Do not crowd another player, exploit claim borders, or build systems intended to lag the server. Start with the first-hour guide if you have not made your first camp yet.