Hey there! Welcome to the Olympus guide—your chill companion for keeping your server smooth. This plugin’s got tools to optimize and manage stuff, so let’s dive in nice and easy. Grab a tea, and let’s vibe!

---

What’s Olympus All About?
Olympus is like your server’s low-key assistant. It cleans up clutter, tames redstone, stacks items, and watches performance. Perfect for big servers or epic builds that need a little love to stay lag-free. Here’s the scoop on what it does and how to use it.

---

Features & How to Use ‘Em

1. Entity Cleanup
What it does: Stops mobs, items, and entities from piling up and bogging down your server. Too many in a chunk? It’ll block new spawns or clean ‘em out after a heads-up.

• How it works: Scans chunks around a spawn point. If the entity count hits the limit (set in cleanup.yml), it either blocks more or sets up a cleanup with a warning to ops.
• Setup: Check cleanup.yml. Adjust
  Code (Text):

  default-max-entities-per-type
  (default: 50) or set custom limits like
  Code (Text):

  entity-spawn-limits.ZOMBIE: 30
  . Tweak
  Code (Text):

  cleanup-countdown
  (default: 60s) for warning time.
• Pro Tip: Protected entities (boats, players, etc.) are safe—peek at the code to add more if you want!

2. Item Stacking
What it does: Gathers dropped items into neat stacks to lighten entity lag.

• How it works: When an item drops, it checks a radius (default: 2 blocks) for matches, stacks ‘em, and adds a hover name (e.g., “Iron Ingot x64”).
• Setup: In optimization.yml, tweak
  Code (Text):

  item-stacking.radius
  and
  Code (Text):

  item-stacking.format
  (like "&e%item% x%amount%"). Add a language file in lang/ (e.g., en_us.yml) for custom names.
• Pro Tip: Disable it with
  Code (Text):

  item-stacking.enabled: false
  if you’re into the messy vibe.

3. Chunk Optimization
What it does: Unloads idle chunks and caps entities per chunk to keep things light.

• How it works: Looks at loaded chunks. If no players are nearby and it’s been quiet, it unloads after a delay. Triggers cleanups if entities get out of hand.
• Setup: In optimization.yml, set
  Code (Text):

  chunk-limits.max-entities
  (default: 100) and
  Code (Text):

  chunk-unload-delay
  (default: 600 ticks, ~30s). Toggle
  Code (Text):

  unload-inactive-chunks
  .
• Pro Tip: Bump up
  Code (Text):

  chunk-optimization-interval
  (default: 1200 ticks, ~1 min) if you don’t need constant checks.

4. TPS Monitoring
What it does: Keeps tabs on your server’s TPS (ticks per second). If it drops too low, it pings ops and starts a cleanup.

• How it works: Checks TPS every 30s. Below the threshold (default: 16)? It notifies ops and runs chunk/entity cleanup.
• Setup: In optimization.yml, tweak
  Code (Text):

  tps.threshold
  . Customize the alert in messages.yml (e.g., “TPS low at %tps%!”).
• Pro Tip: Raise it to 18 for tighter lag control.

⚡ 5. Redstone Management
What it does: Monitors redstone in chunks and pauses it when no players are around, saving resources.

• How it works: Tracks pistons, repeaters, wires, etc. If activity’s low and no one’s nearby, it shuts ‘em off. Turns back on when players roll up.
• Setup: In optimization.yml, adjust
  Code (Text):

  redstone.check-interval
  (default: 200 ticks, ~10s),
  Code (Text):

  redstone.activity-threshold
  (default: 5), and
  Code (Text):

  redstone.player-detection-range
  (default: 2 chunks).
• Pro Tip: Flip
  Code (Text):

  redstone.debug: true
  to peek at what’s happening in the console.

---

Deep Dive: The Redstone Scanner
What it does: Scans for active redstone in a wide area—perfect for hunting laggy machines or troubleshooting builds.

• How it works: Use
  Code (Text):

  /olympus scanredstoner
  as a player. It scans a 180-block radius (~11 chunks) around you, finding powered redstone (wires, pistons, etc.). Shows active chunks, component counts, and exact block coords.
• Details: Scans all online players (60s cooldown per player), so it’s easy on the server. Results hit the requester with a clean summary.
• Setup: No config needed, but edit messages.yml for custom scan messages (e.g., “Found %active% active spots!”). Disable with
  Code (Text):

  features.redstone-scanner: false
  in config.yml.
• Example Output: “Redstone Scan: 50 components total, 3 active in chunks at (x,z). Locations: (100, 64, 200).”
• Pro Tip: Run it near big farms or clocks to spot lag culprits quick.

---

Config Files - Your Chill Toolkit
Olympus drops these in your plugins folder. Here’s the lowdown:

• config.yml: Main switches for features (e.g.,
  Code (Text):

  features.cleanup: true
  ).
• cleanup.yml: Entity limits, cleanup timing, countdowns.
• optimization.yml: Redstone, chunks, item stacking, TPS settings.
• messages.yml: Chat/console messages—add colors with &codes!
• lang/: Drop a .yml file (e.g., en_us.yml) for item names in stacking, You can only have 1 language file inside the folder, in case there is one already created you delete that language and put yours and restart the server!

Heads Up: Only one lang file allowed, or it’ll grumble. Defaults to en_us.yml if you skip it.

---

️ Commands

• /olympus scanredstoner - Players scan redstone nearby. No perms, just be in-game.
• /olympus chunk - Ops (or console) check loaded/unloaded chunk stats per world.

---

Final Chill Tips
Start with defaults, then tweak as you vibe. Console logs are color-free, so keep an eye there. If cleanup’s too eager, stretch out intervals or raise limits in the configs. You’re running this chill show!