This is the central rules and operations document for LIFE SMP. It is intentionally detailed so players, staff, business owners, police, and judges can use the same standards. The server owner may revise a rule, but changes should be written down and announced before enforcement whenever possible.

Contents

1. Server Identity and Technical Snapshot

2. The LIFE SMP Charter

3. Player Code of Conduct

4. Gameplay, PvP, Raiding, and Safety

5. Theft, Griefing, and Crime Levels

6. Jail, Court, Evidence, and Appeals

7. Land, Spawn, and Building Permits

8. Economy and Item Values

9. Taxes and Government Revenue

10. Banking and Player Transactions

11. Businesses, Shops, and Trading

12. Government, Police, and Courts

13. Ranks, Quests, and Playtime

14. Staff Structure and Admin Permissions

15. Moderation Procedure and Penalty Matrix

16. Server Security, Logs, Backups, and Fair Play

17. Events and Rewards

18. Crossplay and Technical Operations

19. Player Quick-Start Guide

20. Official Forms and Templates

21. Daily / Weekly Operations Checklists

22. Quick Reference: Fines and Jail Time

Current server snapshot

Server address and plugin details can change. Keep this snapshot updated if the host, port, software, or crossplay setup changes.

1.1 What LIFE SMP is

LIFE SMP is a community survival server built around player-created towns, trade, ownership, government, business, and fair competition. Players should be able to build a home, make money, open a business, join events, take part in public decisions, and enjoy the world without worrying that their work will be destroyed or stolen without consequences.

1.2 Main goals

A fair survival experience where effort matters.

An economy where players can earn money through gameplay, jobs, mining, farming, crafting, quests, trading, and businesses.

A town and government system with public buildings, a bank, courts, police, shops, and useful public spaces.

Rules that are serious and consistent without being needlessly harsh or embarrassing.

Staff who solve problems using evidence rather than favoritism.

Crossplay where supported, with clear communication when updates temporarily affect Bedrock access.

1.3 Approved world areas

1.4 Server values

Respect: disagree without harassment.

Fairness: no cheating, exploits, or special treatment.

Ownership: ask before taking or changing another player’s property.

Accountability: penalties depend on evidence, value, damage, and prior offenses.

Transparency: publish prices, taxes, permits, and rule changes.

2.1 Player rights

The right to have a complaint heard by staff.

The right to know which rule was allegedly broken.

The right to see the evidence that can reasonably be shared.

The right to appeal a major penalty to a different staff member when possible.

The right to keep legitimately earned items and money unless a fair ruling says they must be returned or confiscated.

The right to participate without being targeted because of friendships, status, rank, or personal disagreements.

2.2 Player responsibilities

Follow published server rules and event-specific rules.

Protect login details and never pretend to be another player or staff member.

Report serious bugs, theft, scams, or abuse honestly.

Do not use lag, duplication, or plugin exploits to gain an unfair advantage.

Cooperate with reasonable staff investigations.

Respect approved public spaces and the property of other players.

2.3 How new rules are adopted

1. A proposed rule is written clearly, with a reason and an example of how it will be used.

2. The owner or delegated government/staff group reviews it for fairness and technical feasibility.

3. The rule is announced in-game before enforcement, unless an emergency temporary restriction is needed to stop active damage.

4. The rule is added to this handbook and dated. Staff should not punish players for breaking a new rule before it was announced.

2.4 No rule is a blank cheque

Staff may stop active harm, secure evidence, or temporarily separate players while an incident is reviewed. Staff may not invent a fine, jail term, or confiscation amount just because they are annoyed. If an incident is not covered, use the closest existing rule, explain the decision, record it, and review whether the handbook needs a new rule.

3.1 Chat penalty ladder

Mute commands require a suitable moderation plugin or a manual staff process. If no mute plugin exists, staff should use the available chat controls and record the decision rather than claiming an unavailable command worked.

3.2 Language and disagreements

Players do not need to agree with each other. They do need to keep arguments from taking over the server. Staff should stop a conflict from escalating, ask players to move to private messages or a moderated hearing, and judge rule-breaking separately from personal dislike.

4.1 PvP baseline

Unless the owner announces a different rule for a specific event, PvP is allowed only when it is consensual, in an announced arena/event, or in an explicitly designated PvP zone. Spawn, the bank, court, jail, government buildings, and protected event staging areas are safe zones. Attacking a player who is using a safe zone to disengage is not allowed.

4.2 Combat rules

No spawn killing, combat logging to avoid a fair ruling, or repeatedly targeting a player who has asked for the fight to stop.

No trapping players at spawn, at the bank, or in a public service building.

Do not use bugged items, duplication glitches, or unintended mechanics to make combat unfair.

Maces and other weapons may be used under normal server rules, but a weapon does not create permission to attack a player outside allowed PvP.

Event organizers must announce whether items are kept, dropped, or returned after an event.

4.3 Raiding

LIFE SMP uses a property-respect model, not an open-raiding model. Taking items from another player’s chest, barrel, shulker, furnace, hopper, shop stock, or storage without permission is theft, even if the container is not locked. Entering an open building does not mean the owner consented to taking items. If a player advertises a public free chest or public exchange, only the items clearly offered are available.

4.4 Fires, explosions, and damage

Do not start fire or trigger explosions on another player’s property without permission.

Do not use TNT, lava, water, pistons, mobs, or block updates to damage protected builds, roads, shops, farms, or public facilities.

If accidental damage happens, tell staff promptly, stop making changes, and help repair it. Prompt honest reporting may reduce the penalty.

Staff should restore damaged builds from backups or logs when possible, but restoration does not replace a fair investigation.

4.5 Deaths and dropped items

Normal survival deaths are part of the game. A player may retrieve their own drops unless another player has collected them. If another player collects the drops, they should return them or arrange an agreed handoff. Refusing to return identifiable drops is treated as theft, assessed at the server’s item values.

4.6 Public works and protected builds

Roads, spawn paths, bridges, government buildings, public farms, and event builds are community assets. Do not alter them unless the relevant builder or staff member approves. Staff should clearly mark public projects and, where practical, place signs naming the project owner or government department.

5.1 What counts as theft

Taking items, currency, shop stock, or resources from another player without consent.

Taking items from a public-looking container that is not clearly marked as free or public.

Keeping another player’s dropped items after being asked to return them.

Moving, hiding, selling, or giving away stolen items to prevent their return.

Taking payment without delivering the agreed item/service and refusing to fix the deal.

Using access to a shop, farm, storage room, bank, or staff role to take property beyond the permission granted.

5.2 Valuing stolen property

Staff should calculate the value using the current posted shop price or the approved LIFE SMP Item Value List. If no posted value exists, use the median of three recent fair trades when possible. If that is not possible, staff choose a reasonable value, explain it in the incident log, and allow an appeal. Do not use a one-time inflated listing to claim an unreasonable value.

All items taken in one incident are added together to determine the tier. Hiding items, splitting them between friends, or selling them before the report does not lower the total value. Separate incidents may be treated separately, but a pattern of coordinated theft can increase the penalty.

5.3 Theft penalty schedule

Examples: if the approved value stolen is $80, the player returns the items (or pays $80) and owes a $25 minimum fine, then receives 5 minutes in jail for a first offense. If the value is $1,000, the player returns/pays $1,000, owes a $350 fine, and receives 30 minutes in jail for a first offense.

5.4 Repeat offenses and aggravating factors

Second theft within 30 days: increase jail by one penalty step, up to twice the first-offense time; add 25 percentage points to the fine rate.

Third theft within 60 days: treat as at least Level 4, require senior staff review, and consider a temporary ban.

Organized theft, hiding items, or selling stolen property: increase one level and recover identifiable stolen goods for return.

Theft from a bank, government office, or public-service storage: increase one level because public trust was affected.

Immediate confession and full return before a report: a first-time offender may receive one step less jail time; this reduction does not apply to repeated or organized theft.

Knowingly false accusations or fabricated evidence: open a separate conduct case and set a penalty based on intent and harm caused.

5.5 Fines are separate from restitution

Restitution pays the victim back. A fine is the separate consequence paid to the government bank, if that feature is active. A player should not be charged twice for the same purpose without the decision explaining why. If the player cannot pay immediately, use the payment-plan rule in Section 9.4 rather than taking every item they own or forcing a negative balance.

5.6 Griefing penalties

6.1 Jail is an in-game consequence

“Jail” means an in-game jail cell or an equivalent staff-controlled confinement system. It is not a real-world threat. If no jail plugin is installed, staff may use a designated cell and manual supervision only if it is safe and practical. If the feature cannot be enforced reliably, use a logged warning, fine, mute, or temporary ban instead—never pretend a timer is running when it is not.

6.2 How jail time is counted

Jail time starts when staff confirm the player is in the jail area and the incident is logged.

If a plugin supports reliable countdowns, use the plugin timer. Otherwise, staff record the start and release time.

Do not add extra jail time without recording the reason.

Jail escape attempts count only if the player breaks a clearly explained jail rule or exploits a plugin; do not punish ordinary disconnections as escape.

Staff may not jail someone indefinitely. All jail terms must use the schedule or a written senior-staff decision.

6.3 Evidence standard

Before imposing a serious penalty, staff should have at least one reliable piece of evidence and, when feasible, two independent pieces. Examples include inventory/container logs, transaction records, screenshots, video, witness statements, server logs, plugin logs, or the player’s admission. A rumor or personal dislike is not enough by itself.

6.4 Case process

1. Receive the report and record the reporting player, accused player, date/time, location, claimed value, and summary.

2. Prevent ongoing harm if necessary, using the least disruptive temporary measure that works.

3. Collect and check evidence before publicly accusing anyone; use logs, witnesses, screenshots, transactions, or admissions where available.

4. Calculate the value, check relevant prior offenses, and apply the published penalty schedule.

5. Tell the player the rule, evidence summary, restitution, fine, jail/ban duration, and appeal process. Log the decision and return recovered property to the owner; staff must never keep evidence items as personal loot.

6.5 Court and disputes

The court is for disputes that staff cannot settle quickly, major theft/griefing, business disagreements, land conflicts, and appeals of serious decisions.

A judge or hearing officer should not decide a case in which they are a victim, witness, or close friend involved in the dispute.

Both sides should be allowed to explain their version and submit evidence.

The judge should decide the rule broken, the value involved, the remedy, and any penalty.

The written decision should be brief but specific. “Because staff said so” is not a sufficient reason for a major penalty.

6.6 Appeals

Appeal within seven days, stating the disputed decision and any new evidence. Where possible, another staff member should review it; filing an appeal does not pause safety restrictions or justify extra penalties.

7.1 The 500-block government reservation

7.2 Required permits

7.3 Suggested permit fees

7.4 Application requirements

Player name and contact method in-game.

Requested coordinates or a marked map screenshot.

Build type, footprint, and approximate height.

Whether it is private, commercial, or public.

Expected redstone/mob-farm impact, if relevant.

Agreement not to expand into another player’s land or the protected zone without approval.

7.5 Permit process

1. Player submits the building permit form.

2. A staff member checks ownership, protected zones, and the requested footprint.

3. Approval, denial, or requested changes are recorded in writing.

4. Player places a sign at the site showing owner, project name, and permit status, where practical.

5. Staff should give a reasonable deadline to correct a boundary issue before removing a build, unless it is causing immediate harm.

7.6 Land disputes

Do not resolve a land dispute by breaking the other player’s build. Staff should compare permit records, claim markers, dates, and evidence. If two players were given overlapping permissions by mistake, staff should prioritize fair compensation or relocation over blame.

8.1 Basic money rules

Proposed new-player starting balance: $1,000 when the economy is activated.

The website/dashboard showing $0 is only a placeholder unless connected to the real economy. A website display does not create or change in-game money.

Money should be earned through gameplay, jobs, quests, approved sales, events, and business activity.

Players may negotiate a price freely unless a specific shop price or event rule states otherwise.

Do not duplicate money, exploit plugins, or create fake transaction screenshots.

When a trade uses both items and money, both sides should confirm the exact deal before exchanging.

8.2 Suggested item value guide

These are starting reference ranges to help police, banks, shops, and courts value property consistently. They are not automatic shop prices. The owner/economy manager should update them when supply, demand, or the server economy changes.

8.3 Jobs and rewards

8.4 Inflation prevention

Do not award huge balances just for logging in.

Make rare resources valuable but avoid easy repeatable methods that create unlimited money.

Use money sinks such as permits, shop rent, event registration, and reasonable repairs—not surprise fines.

Review the richest-player leaderboard weekly for suspicious jumps.

If money duplication occurs, stop the exploit, preserve logs, and remove only clearly duplicated funds after review.

9.1 Purpose of taxes

Taxes should support public buildings, road improvements, events, prizes, and approved community services. They must be announced, predictable, and recorded. A tax cannot be created retroactively for money players already earned unless the community explicitly adopts an exceptional transition rule.

9.2 Suggested progressive business-income tax

Recommended model: tax net business profit per week, not a player’s entire bank balance. Apply the brackets progressively so only the portion in each bracket is charged at that bracket’s rate.

9.3 Tax example

If a business has $30,000 in weekly taxable net profit: first $5,000 at 0% = $0; next $20,000 at 2% = $400; final $5,000 at 4% = $200; total proposed tax = $600. Staff should use a calculator or a checked ledger and give the business a receipt.

9.4 Payment plans and tax disputes

Give the player a written amount, calculation period, due date, and appeal route.

If the player cannot pay, agree on a payment plan instead of making the balance negative by default.

Do not seize a player’s private items without a published law and a documented ruling.

A player may challenge arithmetic, bracket placement, or whether the amount was taxable.

Government revenue must be recorded; staff may not keep tax payments personally.

9.5 Government spending

10.1 Banking principles

The bank holds and records player money; it should not secretly change balances.

Every deposit, withdrawal, payment, fine, tax, refund, or government transfer should have a reason and a record.

Never ask another player for their password. Staff should not need anyone’s account password to help with a bank issue.

Bank staff should not handle a case in which they are accused of stealing or changing money.

When an economy plugin is installed, test it on a non-critical account before using it as the only record.

10.2 Transaction confirmation

Before a player-to-player payment, both players should agree on recipient and amount. Use the official payment command if a tested economy plugin supports it. For trades, confirm item, quantity, amount, and delivery order before proceeding. Staff cannot guarantee a trade if players ignore the published process, but clear scam evidence must still be investigated.

10.3 Recommended transaction record

10.4 Loans and debt

Private loans are agreements between players. The lender and borrower should record principal, due date, repayment plan, and whether interest is allowed. Keep interest reasonable and agreed before money changes hands. Staff should not enforce a vague verbal “you owe me” claim without evidence. A player must not use threats, harassment, or property damage to collect a debt.

10.5 Refunds and mistaken transfers

If money goes to the wrong player, preserve the transaction record and ask the recipient to return it. Staff may assist with a documented reversal if the economy plugin supports it and the error is clear. Do not reverse a payment simply because the buyer regrets a fair completed trade.

11.1 Starting a business

1. Choose a business name and type: shop, farm, crafting service, building service, transport, or another approved activity.

2. Choose a location outside the 500-block government reservation unless a written exception is granted.

3. Submit the Business Registration form and a building permit if a structure is needed.

4. Publish shop prices clearly. Prices should say whether they are per item, stack, service, or job.

5. Keep enough stock or explain that the item is preorder-only. Do not advertise stock that does not exist as though it were available immediately.

11.2 Business rules

Do not use a shop name, sign, or skin to impersonate another shop.

Do not hide prices until after a player commits to a purchase.

Do not claim an item is enchanted, rare, or fully repaired unless that is true.

Do not use fake sale signs, fake bank confirmations, or fake staff approvals.

Keep customer property separate from shop stock where practical.

Clean up abandoned stalls when the government gives a reasonable notice and deadline.

11.3 Business dispute resolution

For a missed delivery or disputed sale, the first remedy should usually be delivery, refund, or an agreed replacement. If the seller refuses, staff assess whether it was a mistake, a failure to perform, or deliberate fraud. A business dispute is not automatically theft; intent, communication, evidence, and the value involved matter.

11.4 Store maintenance

Post owner name, opening status, and a way to contact the owner in-game.

Check prices at least weekly while the economy is active.

Remove signs that quote expired promotions or unavailable stock.

Do not build over a road or another shop’s entrance to gain an advantage.

A shop may be closed for inactivity only under a published inactivity rule and after reasonable notice.

11.5 Marketplace agreement

Every registered business agrees to respect neighboring claims, use honest prices, comply with published taxes, clean up its area, and settle disputes through the normal process rather than retaliation.

12.1 Government jobs

12.2 Police procedure

Respond to reports calmly and gather evidence.

Separate people involved if a dispute is escalating.

Record what was observed and what was reported as separate facts.

Use a warning or temporary measure only when appropriate; do not declare someone guilty before review.

For theft or damage, calculate value with the current item value list.

Return recovered items to the rightful owner when ownership is confirmed.

Refer high-value cases, repeat offenses, and staff-related allegations to a senior reviewer or judge.

12.3 Conflict of interest

A staff member must step aside if they are the victim, accused person, a key witness, or personally involved in the dispute. A different staff member should review the case. If the entire active staff team is involved, postpone a final ruling until the owner or neutral reviewer can examine it.

12.4 Government transparency

Publish the current fees, taxes, item values, permit process, and penalties. Maintain a public summary of government spending without exposing private player information. Record exceptions to standard rules and explain why they were necessary.

13.1 Earned player ranks

Ranks should reward long-term activity and achievements. Requirements below are suggested starting rules. If a rank depends on playtime or money, staff should verify the relevant data and avoid granting ranks solely because of friendship.

These thresholds are a proposed progression and should be balanced after the server has real playtime and money data. “Net worth” must be defined before being used: a simple option is bank balance plus verified business assets, minus recorded debts.

13.2 Supporter status

Supporter is separate from earned ranks. If a supporter role is ever offered, it should provide recognition and cosmetic benefits only—not stronger weapons, extra combat damage, special access to other players’ property, or unfair economic power. Any real-money store must follow applicable platform and Minecraft rules and be managed with appropriate adult oversight.

13.3 Quest design

Quest integrity: publish the objective, proof, deadline, and reward before a quest begins. One-time rewards cannot be claimed repeatedly, and staff should not approve their own submissions. If a bug or outage blocks completion, offer a fair extension or replacement.

14.1 Rank design

14.2 LuckPerms safety

Keep yourself as the owner account until the replacement permissions have been tested.

Do not grant wildcard permission (*) to every administrator unless you intentionally want near-total access.

Give moderators only the commands needed for their work.

After changing permissions, test with a non-owner account or a trusted test account.

Keep a record of who belongs to each group and why.

Remove access when a staff member leaves the team.

14.3 Example command concepts

15.1 Standard response ladder

15.2 Offense-specific matrix

16.1 Protecting the world

Make a backup before changing server software, installing major plugins, editing core configuration, or performing a major world operation.

Keep at least one backup separate from the active server where the host supports it.

Never delete world, world_nether, or world_the_end folders as part of routine plugin troubleshooting.

Update one plugin at a time where practical and test after restarting.

Keep a list of installed plugins, their versions, and what each one does.

If an update breaks the server, stop changes and restore the last known-good backup.

16.2 Logs and evidence

Enable and retain the logs needed to investigate theft, griefing, economy exploits, staff abuse, and crashes. Logs should be used for legitimate server moderation—not public humiliation or personal snooping. Do not promise that a block, chest, item, or transaction can be traced unless the relevant plugin was installed and logging it at the time.

16.3 Anti-cheat and exploits

Use an anti-cheat that explicitly supports the server version and expected Bedrock/Geyser behavior.

Test new anti-cheat settings with both Java and Bedrock players before enforcing strict actions.

A suspicious alert is a lead, not automatic proof. Staff should review logs and context.

If players discover a duplication or economy exploit, ask them to stop and report it. Do not reward people for abusing it repeatedly.

Fixing an exploit should come before deciding penalties for everyone affected.

16.4 Account and permission safety

Use strong passwords for the hosting panel and any database or website.

Limit panel access to people who genuinely need it.

Do not share hosting credentials in public chat.

Use two-step verification when the host supports it.

Do not let multiple staff share one account; individual accounts make logs meaningful.

Review permissions after staff role changes.

17.1 Suggested event calendar

17.2 Event notice checklist

Name, date/time, location, and organizer.

How players enter and whether entry is free.

Allowed gear, PvP rules, and whether drops are kept.

Prize amounts and how winners are judged.

What happens if a player disconnects or a bug interrupts the event.

How results and prizes are recorded.

17.3 Prize guidance

For a small server, avoid prizes so large that one event changes the entire economy. Suggested range: $250–$5,000 for most events, with higher rewards reserved for rare major events and funded through a recorded event budget. Non-money prizes—trophies, titles, decorative items, or a place in a hall of fame—can make events meaningful without creating inflation.

17.4 Weekly playtime prizes

If using the weekly top-three playtime idea, publish the reset time and prize amounts. Count legitimate playtime only; use anti-AFK rules if necessary and announce them beforehand. If too few players participate, staff can still award the prizes but should not claim a large competition happened when it did not.

18.1 Platform summary

LIFE SMP is based on Paper, a Java server platform. Bedrock players such as Xbox and PlayStation users require a compatible bridge such as Geyser, and Floodgate is commonly used to allow Bedrock authentication without a Java account. Console platforms may also require a method to select a custom server, such as BedrockTogether, because they do not always expose arbitrary server entry the same way PC Bedrock does.

18.2 Important crossplay note

18.3 Troubleshooting order

1. Check whether the server is online in the host panel and whether Java players can join.

2. Check the console for Geyser and Floodgate startup errors.

3. Check the official supported versions for the current Bedrock and Java versions.

4. Confirm the Bedrock port in Geyser configuration and ensure that the host allows UDP traffic on that port.

5. Test the connection with one Bedrock device before changing other settings.

6. Change one thing at a time. Keep a note of the old setting so it can be restored.

18.4 Safe plugin update procedure

Stop the server before replacing a plugin JAR.

Download from the plugin’s official site or its official release page.

Check that the file is the correct platform build (for Paper, normally Bukkit/Spigot/Paper-compatible).

Keep only one active copy of each plugin JAR in the plugins folder.

Do not delete plugin data folders unless you are intentionally resetting configuration and understand the effect.

Restart the server, read startup messages, and test commands before inviting everyone back.

18.5 Current plugin-status note

LuckPerms is installed and the “admin” group has been created. That group still needs its membership and permissions configured and tested. Geyser/Floodgate should be checked after each relevant Minecraft update. Do not assume a stats GUI, sidebar, /invsee, /tempban, /mute, economy, or banking command exists until the plugin that supplies it is installed, loaded, configured, and tested.

19.1 First time on LIFE SMP

1. Read the server rules and ask staff if a rule is unclear.

2. Choose a base location outside the protected government reservation; apply for a permit if required.

3. Register a shop before opening a public business.

4. Protect your own items and respect other players’ storage and builds.

5. Earn money through survival, trading, jobs, quests, and events once those systems are active.

6. Report theft, griefing, scams, and serious bugs with as much evidence as possible.

Initial named player roster (update as the community changes)

19.2 How to avoid trade problems

Agree on the exact item, quantity, and price before trading.

Check item names, enchantments, and durability where relevant.

Do not click unknown links or share accounts/passwords.

Keep screenshots or written messages for large trades.

Use the bank/payment system only after confirming recipient and amount.

If a trade goes wrong, stop the argument and report the evidence instead of retaliating.

19.3 Safe community play

You can compete, fight in allowed areas, build ambitious structures, run a business, and negotiate tough deals. You may not use those activities as cover for harassment, theft, cheating, or destructive retaliation. A strong LIFE SMP player helps make the world more interesting for everyone else.

Copy these templates into a message, document, or in-game form. Staff should keep submissions consistent so approvals and rulings are easy to review.

20.1 Building permit application

Player name: ______________________________________________

Project name / type: ________________________________________

Requested coordinates / map location: ________________________

Approximate footprint and height: _____________________________

Private / commercial / public: ________________________________

Planned redstone, farms, or mob systems: _______________________

Nearby claims / roads / structures: ____________________________

Applicant agrees to follow land rules: Yes / No

Decision: Approved / Denied / Changes requested

Reviewer, date, and notes: ____________________________________

20.2 Business registration

Owner: _____________________________________________________

Business name: _____________________________________________

Business type: ______________________________________________

Location / permit number: ____________________________________

Items or services offered: ___________________________________

Posted prices / pricing unit: _________________________________

Opening hours / availability: _________________________________

Tax / fee status: ____________________________________________

Approved by / date: _________________________________________

20.3 Theft or griefing report

Reporting player: __________________________________________

Accused player (if known): ___________________________________

Date/time and location: ______________________________________

Items / blocks / money involved: ______________________________

Estimated total value: $_______________________________________

What happened (facts only): ___________________________________

Evidence available (logs/screenshots/witnesses): ________________

Was the property marked/private? ______________________________

Staff assigned: ______________________________________________

Outcome / restitution / fine / jail / appeal: ____________________

20.4 Court hearing / dispute form

Case number: _______________________________________________

Players involved: ___________________________________________

Issue being decided: _________________________________________

Rules involved: ______________________________________________

Evidence from each side: _____________________________________

Value / damage calculation: __________________________________

Conflict-of-interest check completed: Yes / No

Decision and reasoning: ______________________________________

Restitution / penalty / due date: ______________________________

Appeal deadline and reviewer: _________________________________

20.5 Staff application and agreement

Player name: ______________________________________________

Requested role: _____________________________________________

Usual availability: __________________________________________

Relevant experience / strengths: ______________________________

I will not misuse commands or punish personal enemies: Yes / No

I will record serious actions and follow published rules: Yes / No

I will protect player privacy and account security: Yes / No

Applicant signature / date: __________________________________

Approver / date: ____________________________________________

20.6 Jail / punishment record

Incident ID: ________________________________________________

Player: ____________________________________________________

Rule and offense level: ______________________________________

Evidence summary: ___________________________________________

Value involved: $____________________________________________

Restitution due / paid: _______________________________________

Fine due / paid: _____________________________________________

Jail start / end: ____________________________________________

Decision-maker: _____________________________________________

Appeal requested / outcome: __________________________________

20.7 Government spending request

Department / requester: ______________________________________

Purpose / project: ___________________________________________

Estimated amount and items: __________________________________

Funding source: _____________________________________________

Expected benefit to players: __________________________________

Approved / denied by: ________________________________________

Final cost and proof of completion: ____________________________

20.8 Event plan

Event name: ________________________________________________

Date/time/location: __________________________________________

Organizer: __________________________________________________

Rules / allowed items / PvP status: ____________________________

Entry requirements: __________________________________________

Prizes and funding: __________________________________________

Judging / tie-breaking process: _______________________________

Backup plan for bugs or disconnections: ________________________

Winners and actual rewards paid: ______________________________

20.9 Economy adjustment log

Date: ______________________________________________________

Change (price, reward, tax, or balance correction): ______________

Reason: ____________________________________________________

Players/businesses affected: __________________________________

Evidence / calculation: _______________________________________

Approved by: ________________________________________________

Announcement made before enforcement: Yes / No

21.1 Before opening / restart

☐ Confirm the server started and Java joining works.

☐ Check console for severe errors and plugin load failures.

☐ Check that key plugins (LuckPerms, Geyser, Floodgate, economy/moderation plugins if installed) loaded successfully.

☐ Confirm the correct world is active and the latest backup is available.

☐ Check that admin access still works and regular players do not have unwanted permissions.

☐ If Bedrock is affected by an update, confirm supported versions before announcing that access is fixed.

21.2 Daily staff tasks

☐ Review new player reports and support requests.

☐ Check for unresolved theft, griefing, or transaction disputes.

☐ Confirm that jailed players have release times recorded.

☐ Check that shops and public paths are not badly obstructed.

☐ Write down significant staff actions and any economy adjustments.

21.3 Weekly economy review

☐ Review total currency and the richest-player changes.

☐ Check for suspicious large payouts or repeated rewards.

☐ Update market values only after recording the reason.

☐ Review taxes and government spending for accuracy.

☐ Confirm the next event’s date, rules, and prize budget.

☐ Announce material rule/economy changes before they take effect.

21.4 Monthly governance review

☐ Review whether theft and griefing penalties are proportionate.

☐ Check if the 500-block government district is marked clearly enough.

☐ Review staff permissions and remove access that is no longer needed.

☐ Review open court cases, appeals, and payment plans.

☐ Update this handbook version date after approved policy changes.

Other common responses

Final rule for staff

Handbook version 1.0. Suggested policy draft for LIFE SMP. The owner should review the penalties, officially adopt them, announce them in-game, and keep this document updated as plugins and server features change.