Rules of the world.

Bindspire is built on a simple principle.

Don't make the world worse for the people sharing it with you.

Everything in this document exists to protect the people, the builds, and the history that make this server worth calling home. The rules that follow are that principle, made specific.

If you read four lines, read these

Progress is earned in survival, the same way for everyone. BS-001 · Survival integrity
Everything a player creates stays theirs. BS-002 · Respect builds and players
The server has one tick budget, and everyone shares it. BS-004 · Performance matters
Large-scale projects start with a conversation, not a rollback. BS-005 · Big projects get a heads up

Everything below is the full document. It is long because it is precise, not because it is strict.

Document: BS-RULE-001
Revision: 1.1
Effective: August 30, 2026

Part one BS

Server rules

Conduct, integrity, and care for the world

These apply everywhere on Bindspire SMP, to everyone, all the time. They are deliberately short — the intent behind each one matters more than the letter of it.

Issuing authority: Bindspire Server Administration
Sections: 8 — BS-001 to BS-008

BS-001

Survival integrity

Progress is earned in survival, the same way for everyone.

Why this exists

The world only means something if what you have took effort to get. Every shortcut quietly devalues the hours someone else spent earning the same thing honestly.

Allowed

Farms, automation, and efficiency built in survival
Trading, gifts, and shared infrastructure between players
Pushing the modpack's intended mechanics as far as they go

Not allowed

Cheats, xray, spawned items, or client-side advantages
Exploit and dupe abuse, including "it was already in the pack"
Importing items from creative or another world

Examples

Good: Working out the mob-cap mechanics and building a farm that genuinely earns its output.
Not good: Xraying to a stronghold and calling it a lucky tunnel.

BS-002

Respect builds and players

Everything a player creates stays theirs.

Why this exists

Players put hundreds of hours into what they build here. Respecting that is the entire reason the world stays worth investing in — nobody builds big on a server where things go missing.

Allowed

Leaving gifts, repairing public roads, maintaining shared infrastructure
Using designated public farms and community facilities
Asking first — before you take, borrow, or build up against someone

Not allowed

Opening private storage, inventories, or machines
Editing, extending, or "improving" someone's build uninvited
Borrowing materials you intend to put back later

Examples

Good: Helping repair a bridge on a public road after a creeper takes out a span.
Not good: Taking a stack of iron from an unlocked chest "just for now."

Operator note

Claims are a convenience, not the rule. An unclaimed build is still someone's build, and "it wasn't protected" has never been a defence.

BS-003

Community standards — 18+

An adult server that stays somewhere people want to be.

Why this exists

The age floor exists so conversation can be relaxed and unfiltered, not so it can be cruel. Adult means we trust you to read the room, not that anything goes.

Allowed

Blunt disagreement, settled and dropped
Dark humour between people who actually know each other

Not allowed

Harassment, hate speech, slurs, or stalking
Fixating on a player, in-game or in Discord
Importing drama from other servers or communities

Operator note

If someone asks you to stop, that is the end of it. Whether you meant it the way it landed is not the test.

BS-004

Performance matters

The server has one tick budget, and everyone shares it.

Why this exists

TPS is a shared resource. A single runaway build is paid for by every player online, including you — lag is not something that happens only to the person who caused it.

Allowed

A Create iron farm sized to serve you and your town
Chunkloaders on things you actively use
Asking staff to profile a build you are unsure about

Not allowed

Massive idle passive-mob farms nobody is harvesting
Chunkloading whole regions you are not using
Thousands of idle entities left running because "it still works"

Examples

Good: A Create contraption that runs while you are there and stops when you are not.
Not good: Four thousand cows loaded around the clock for a farm you visit twice a month.

Best practice

Planning something heavy? Ask for a spark profile before you scale it up. Fixing a design at ten percent built costs nothing; fixing it at full size costs a weekend.

Builds hurting TPS may be adjusted, disabled, or removed.

BS-005

Big projects get a heads up

Large-scale projects start with a conversation, not a rollback.

Why this exists

Ambitious builds are some of the best things on this server, and none of this is meant to discourage them. Staff review protects the server and gives affected nearby players a voice before a major footprint becomes difficult to change.

Allowed

Large projects once you have generally reached Elder and completed staff review
Earlier large projects when staff approves a reasonable exception
Mega-factories, world-eaters, quarries, huge claims, and heavy automation — after review
Staged builds, scaled up as they prove out

Not allowed

Starting major construction or reserving a huge area before staff review
Treating project approval as permission to claim unlimited land
Ignoring nearby players who would be meaningfully affected
Quietly scaling a prototype into production

Examples

Good: Posting your quarry plan, hearing from nearby players, agreeing a reasonable footprint, then digging.
Not good: Claiming an unlimited buffer around an approved build and calling the whole area part of the project.

Operator note

Large projects generally require Elder, but staff may approve exceptions. Approval covers a reviewed project and reasonable footprint—not unlimited land.

BS-006

Lootr chests

Structure loot stays available to every player.

Why this exists

Lootr gives each player their own instance of a structure chest, so everyone gets the same first run at a monument. Tampering with the structure itself takes that away from everyone who arrives after you.

Allowed

Looting your own instance of any Lootr chest
Clearing hostile mobs and lighting a structure

Not allowed

Breaking, moving, or replacing structure chests
Stripping a monument so nobody else can run it

Examples

Good: Running an ocean monument, taking your instance, leaving the chests in place.
Not good: Mining out the chests "since I already looted them."

BS-007

Spawn

Communal ground, held to a higher standard.

Why this exists

Spawn is the first thing a new player sees and the one place every single player shares. It only stays good if the people using it leave it the way they found it.

Allowed

Using the public workshops and facilities
Repairing damage you come across
Contributing builds, with staff approval

Not allowed

Leaving a workshop reconfigured, drained, or emptied
Claiming personal space at spawn without approval
Leaving damage unreported

Examples

Good: Refilling the smelter you drained and putting the tools back where they were.
Not good: Rewiring a public workshop for your own recipe and walking away.

Reminder

If you break something at spawn, tell the player who built it. Owning it is always cheaper than being found out.

BS-008

Land claims & settlement

Claim what you are building, leave room for the people building beside you.

Why this exists

Claims protect real work and give settlements room to grow. They stop serving that purpose when huge unused areas become land banks that keep newer neighbours from finding a home.

Allowed

Claiming a real build and reasonable surrounding space
Elder and Ancient players reserving reasonable expansion around an established or clearly planned project
Talking with established nearby players before choosing a close settlement site
Future-player progression: Fresh 10, Settler 50, Pioneer 150, Elder 500, Ancient 500 chunks

Not allowed

Land-banking huge unused areas, especially as a newer player
Meaningful encroachment on an established player or settlement without communicating first
Using a rank allowance as automatic justification for an unreasonable footprint

Examples

Good: Claiming your town, its working space, and a practical expansion edge after checking in with the settlement next door.
Not good: Claiming hundreds of empty chunks with no build plan so nobody else can settle there.

Operator note

Existing players and claims are grandfathered. The claim ladder applies to future players. Established nearby players may object to meaningful encroachment, and staff makes the final call in disputes.

BS-ENF

Enforcement

Warning → rollback / removal → ban.

Enforcement is severity-based and proportionate. Most issues end at the first step, and a good-faith mistake handled honestly rarely goes further than a conversation.

Inactive, abandoned, or excessive claims may be reduced or removed after staff review. Unapproved or problematic projects may be rolled back, and unrelated player belongings will be preserved whenever reasonably possible during that work.

Bad-faith behaviour can skip straight to removal. Operators have final say on what is reasonable when protecting the world, the players, and the server.

Crashes, bugs, whitelist issues, and weird mod behaviour all go to the help channel. Include:

Your Minecraft username
What happened, and roughly when
Screenshots or logs, if you have them

Part two BRA

Bindspire Rail Authority

Railway standards and regulations

The Bindspire Rail Authority oversees the planning, maintenance, and operation of the public railway network across Bindspire Homestead. These standards exist to keep the railway safe, organized, and enjoyable for everyone.

Issuing authority: Bindspire Rail Authority (BRA) Established 2026
Responsible for: Public railway standards
Safety and signalling
Infrastructure and right-of-way
Maintenance and yards
Rolling stock approval
Sections: 6 — BRA-001 to BRA-006

Railway standards sit under the server rules. Where the two overlap, the server rules win.

BRA-001

Rolling stock

Trains on the public network fit the gauge and look like they belong.

Why this exists

Shared clearances are the whole reason anyone's train can run anyone's line. Stock built past them fouls tunnels and bridges that were surveyed for everybody.

Allowed

Trains within 5 blocks wide × 7 blocks tall
Any length, within reason and within common sense
Named or numbered locomotives — encouraged, not required

Not allowed

Oversized stock that fouls tunnels, bridges, or platforms
Unfinished, non-functional, or half-decorated trains on public track

Examples

Good: A four-car freight consist that clears every tunnel on the mainline.
Not good: An eight-wide locomotive that only fits the one line you built yourself.

BRA-002

Storage

The public railway moves trains. It does not store them.

Why this exists

Occupied track is track nobody else can run. Yards exist so that storage has a proper home instead of costing the network its capacity.

Allowed

Storage at your own base, on your own track
Leased space in an approved rail yard

Not allowed

Long-term parking anywhere on the public network
Occupying yard track without a lease

Operator note

Yard lease fees scale with occupied track, and every spur goes back into construction, maintenance, and expansion. The railway pays for itself.

BRA-003

Public network

Connections to the mainline are approved, never assumed.

Why this exists

Every junction is a place two trains can meet badly. Approval keeps the network coherent, and keeps new lines from cutting through ground somebody already claimed.

Allowed

Private branch lines — encouraged
Proposing a mainline connection for approval
Routing through claimed land with the owner's permission

Not allowed

Tying into the mainline without BRA approval
Building through another player's claim without asking

Examples

Good: Bringing a branch to the edge of the right-of-way and asking for a junction.
Not good: Cutting your own turnout into the mainline overnight.

BRA-004

Operations

Keep the mainline moving, and talk to each other on shared track.

Why this exists

Single-track routes only work when operators cooperate. One unattended train on an active line stops every service behind it, and nobody can see why.

Allowed

Sidings and stations for extended stops
Signals and passing sidings on shared lines, wherever practical

Not allowed

Unattended trains left standing on active track
Holding a mainline for a stop that should have used a siding

Reminder

Scheduled passenger services take priority over freight and private trains. If a service is due, clear the road.

BRA-005

Infrastructure

Public infrastructure changes only with approval, and is maintained by whoever owns it.

Why this exists

Track, junctions, and signalling are interdependent — an unannounced change in one place puts a train somewhere it shouldn't be, three chunks away.

Allowed

Maintaining and decorating your own station, yard, or branch
Proposing infrastructure changes to the BRA

Not allowed

Modifying public track, junctions, signals, stations, bridges, tunnels, or yards without approval
Letting a connected station or yard fall into disrepair

BRA-006

General conduct

Recover your own stock, and keep the line running for everyone.

Why this exists

The network is maintained by the same people who use it. Small courtesies scale into a railway that actually works.

Allowed

Asking for help recovering a disabled train
Flagging a blockage you cannot clear yourself

Not allowed

Leaving disabled stock blocking a running line
Abandoning rolling stock anywhere on the network

Abandoned rolling stock may be relocated by the BRA if it obstructs railway operations.

BRA-ADM

Administration

These regulations are subject to change as the Bindspire railway network continues to grow and evolve. The Bindspire Rail Authority reserves the right to amend, clarify, interpret, and enforce these standards at any time, in the interest of maintaining a safe, organized, and enjoyable public railway.

The BRA exists to support the community railway, not to restrict it. The goal is a network that grows with Bindspire Homestead while staying reliable, organized, and fun for everyone.

Failure to comply with these regulations may result in the removal or relocation of rolling stock or infrastructure from the public network, or other action deemed appropriate by BRA representatives or server administration.

Contact

For questions, clarification, approval requests, or to connect to the public railway, contact the railway team in Discord. Ping @Railroad .

Document control

Reference: BS-RULE-001
Issued by: Bindspire Server Administration
Revision: 1.1
Effective: August 30, 2026

Revision history

1.1 · August 30, 2026 Added BS-008 Land Claims & Settlement; clarified Elder expectations and staff review for large projects in BS-005; expanded BS-ENF for abandoned or excessive claims and project rollback.
1.0 · August 2026 First consolidated edition. Server rules and Bindspire Rail Authority standards published as one document.

Operators may amend this document as the server grows. Material changes are published here with a new revision number.

Questions about any of this?

Ask before you build, not after. Someone in Discord will know, and no one has ever been in trouble for asking first.

Join Discord Something is broken