Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 51 additions & 0 deletions packages/kb/content/minecraft/diagnosing-lag.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
title: Diagnosing Modded Servers
description: A comprehensive guide to diagnose modded server lag and performance issues.
tags: [minecraft, mods, server, lag]
author: NodeByte Team
lastUpdated: 2026-06-16
order: 9
---

# How to Diagnose and Fix Modded Server Lag (Forge/Fabric)

Modded Minecraft servers (like ATM, Pixelmon, or custom Forge/Fabric packs) demand significantly more resources than plugin-based environments. While a standard server lag issue is usually related to entities or chunk generation, modded servers add a completely new bottleneck: **Tile Entities and Automation Networks**.

This guide covers how to track down mod-specific lag and optimize your modded environment.

---

## 1. The Enemy of Modded Performance: Tile Entities
A **Tile Entity** is a block that has extra data attached to it and performs calculations every single tick. Examples include:
* Automated pipes and item cables
* Power generators and reactors
* Auto-sorting digital storage networks (Applied Energistics, Refined Storage)
* Auto-quarries and chunk loaders

When hundreds of machines are running across multiple bases, they will cause severe tick lag (high MSPT), resulting in rubber-banding and ghost inputs.

---

## 2. Best Practices for Modded Machinery
To keep your modded server running smoothly, enforce these rules on your community:
* **Isolate High-Frequency Pipes:** Avoid massive loops of item transport cables. Use pipes that transfer items instantly or in large stacks, rather than hundreds of single items flying down a pipe visible to the world.
* **Chunk Loader Limits:** Modded packs often allow players to keep their bases loaded 24/7. Cap the number of chunk loaders allowed per player or team. If too many automation setups are running when players are offline, the server will choke.
* **Limit Digital Storage Fluid/Item Excess:** Avoid loop systems where items are constantly being exported and imported endlessly into storage systems.

---

## 3. Using Mod-Specific Diagnostic Tools
You can't always rely on traditional metrics to find mod lag. Use these modern modded tools to find the exact block coordinates causing problems:

### Option A: Observable (Fabric / Forge)
If your pack includes the **Observable** mod (or you can add it to the server), it is the ultimate tool for finding lagging blocks visually.
1. Run the command: `/observable profile`
2. Wait 30 seconds for it to calculate.
3. It will generate a web link showing you a list of every single block in the world sorted by how many microseconds it takes to tick.
4. It will give you the exact X, Y, Z coordinates so you can teleport to the base and fix or remove the offending machine.

### Option B: Spark Profile
Just like on plugin servers, **Spark** works perfectly on Forge and Fabric.
1. Run `/spark profiler start` during a lag spike.
2. Stop it after 3 minutes with `/spark profiler stop`.
3. Look at the call tree under `world.tick` -> `tileEntities` to see exactly which mod's machinery is burning your CPU cycles.
47 changes: 47 additions & 0 deletions packages/kb/content/minecraft/server-backups.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
title: Server Backups
description: A comprehensive guide for backing up your server files.
tags: [minecraft, mods, server, backups]
author: NodeByte Team
lastUpdated: 2026-06-16
order: 14
---

# Managing and Backing Up Your Server Files Securely

Data integrity is the foundation of a great server. Whether you are adding a new modpack, editing plugin configuration files, or ensuring your players don't lose progress if something breaks, understanding how to manage your files securely is essential.

---

## 1. Web File Manager vs. SFTP
Our web panel includes a built-in file manager, but it is designed for quick tasks. Knowing when to use SFTP will save you time and prevent corrupted transfers.

* **Use the Web File Manager for:** Quick configuration text changes, deleting a single file, or uploading small plugins under 50MB.
* **Use SFTP (Secure File Transfer Protocol) for:** Uploading entire world folders, downloading backups, transferring modpacks, or managing directories with thousands of files.

### How to Connect via SFTP:
1. Download an SFTP client like **FileZilla** or **Cyberduck**.
2. On your server panel, navigate to the **Settings** or **SFTP Details** tab to find your connection details (Host, Port, and Username).
3. Open your SFTP client, enter those details, and use your **panel password** to connect.

---

## 2. Upgrading Server Versions Safely
When a major new Minecraft version drops, rushing to update without a plan can permanently corrupt your world files. Always use this exact order of operations:

1. **Take a Manual Backup:** Never rely on luck. Create a full backup of your server before changing anything.
2. **Update the Server Jar:** Change your server software version in the panel settings.
3. **Update Dependencies First:** Before booting up, make sure core layout plugins like *ProtocolLib*, *LuckPerms*, or *Geyser* are updated to support the new version.
4. **Boot and Monitor:** Start the server and watch the console closely for errors or severe missing block warnings.

---

## 3. Automating Your Backups
Do not rely on remembering to click "Backup" every day. Set up an automated schedule through the panel:

1. Navigate to the **Schedules** tab in your control panel.
2. Create a new schedule called "Daily Backup".
3. Configure the cron expression for your preferred time (e.g., every night at 3:00 AM).
4. Add a new task to that schedule and set the action to **Create Backup**.
5. Set it to lock older vital backups so they don't get automatically rotated out or overwritten.

4 changes: 2 additions & 2 deletions packages/kb/content/minecraft/server-optimizations.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
title: Server Optimizations
description: Learn how to optimize your Minecraft server for peak performance.
tags: [minecraft, perfromance, optimization, tps-lag]
author: Tyler. H
author: NodeByte Team
lastUpdated: 2026-06-16
order: 10
order: 15
---

# Optimizing Your Minecraft Server: A Complete Performance Guide
Expand Down
65 changes: 65 additions & 0 deletions packages/kb/content/minecraft/troubleshooting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
---
title: Troubleshooting
description: Learn how to troubleshoot common Minecraft Server issues.
tags: [minecraft, server, troubleshooting, errors]
author: Tyler. H
lastUpdated: 2026-06-16
order: 20
---

# Troubleshooting Common Minecraft Server Crashes

When a Minecraft server crashes, it can feel overwhelming to look at a wall of text in the console. However, crash reports are highly structured and usually point directly to the exact file, plugin, or world coordinate causing the issue.

This guide will show you how to find your crash reports, read them, and fix the most common issues.

---

## 1. Where to Find Your Crash Logs
When a server shuts down due to an error, it will attempt to write a dedicated log.
* **Dedicated Crash Reports:** Check the `/crash-reports/` folder in your server’s root directory. The files are named by date (e.g., `crash-2026-06-16_14.30.00-server.txt`).
* **Console Logs:** If the server crashed so hard it couldn't generate a report, check the `/logs/` folder and open `latest.log`.

---

## 2. The "Watchdog" Crash (The Server Lagged Out)
### The Error String:
`Description: Watching Server` or `A single server tick took 60.00 seconds (Should be max 0.05)`

### What it means:
Minecraft has a built-in safety system called the **Watchdog**. If the main server thread freezes completely for a set amount of time (usually 60 seconds by default), the Watchdog assumes the server is deadlocked and kills the process to prevent world corruption.
* **This is not a network crash.** It means the CPU got stuck trying to process a massive task.

### Common Culprits & Fixes:
* **Massive WorldEdit Commands:** If a player tries to paste a schematic with millions of blocks, the main thread will freeze.
* **Large Redstone Loops:** High-frequency redstone clocks or item sorting loops stuck in an infinite cycle.
* **Massive Entity Cramming:** Hundreds of mobs crammed into a 1x1 hole on a farm.
* **Fix:** You can increase the threshold or disable it entirely in `server.properties` by setting `max-tick-time=-1`. *Note: Disabling this means a frozen server will hang indefinitely instead of restarting automatically.*

---

## 3. Out of Memory (OOM) Errors
### The Error String:
`java.lang.OutOfMemoryError: Java heap space` or `Container killed by OOM Killer`

### What it means:
The server ran completely out of allocated RAM. This happens when the amount of data the server needs to store in memory (loaded chunks, players, entities, plugin data) exceeds the maximum limit (`-Xmx`) set in your startup flags.

### Common Culprits & Fixes:
* **Too many plugins/mods:** Every plugin or mod increases the baseline RAM requirement.
* **High view distance:** Loading too many chunks per player simultaneously.
* **Fix:** Optimize your chunk configurations (see our Optimization Guide), reduce your view distance, or upgrade your server plan to allocate more RAM.

---

## 4. Mod or Plugin Mismatch
### The Error String:
`java.lang.NoClassDefFoundError` or `java.lang.NoSuchMethodError`

### What it means:
A plugin or mod is trying to communicate with code that doesn't exist. This happens when you install a plugin built for an entirely different version of Minecraft, or when two mods conflict with each other.

### Common Culprits & Fixes:
* **Outdated Plugins:** Running a 1.16 plugin on a 1.20+ server.
* **Missing Dependencies:** Many plugins require a core library (like *ProtocolLib*) to function. Check the console right before the crash; it will usually say exactly which plugin failed to load.
* **Fix:** Temporarily remove the most recently added plugin or mod, restart the server, and check if the crash persists.