Smart item deleter V2

Smart item deleter V2

Smart Item Deleter v2 is a server-side optimization mod designed to automatically clean up dropped item entities when the item count exceeds a defined threshold.

von
1.2K Downloads
neoforgemanagementoptimizationutility
Server mit dieser Mod mieten

Screenshots

Original-Artwork
ChatGPT-enhanced-artwork

Über diese Mod

How it should work, why and the idea are done by Human
Coded and implemented by AI

🧹 Smart Item Deleter v2

A lightweight, intelligent item cleanup system for NeoForge 1.21.1


📘 Overview

Smart Item Deleter v2 is a server-side optimization mod designed to automatically clean up dropped item entities when the item count exceeds a defined threshold.
It tracks items individually to ensure fair, efficient, and safe removal — deleting only excess, old, and unimportant drops without disrupting normal gameplay.

✅ Supports NeoForge 21.1.215, Youer 1.21.1, AsyncYouer-1.21.1
⚙️ Designed for Create-based and heavily modded survival servers
💾 Low overhead, deterministic cleanup cycles


⚙️ Configuration (for server owners)

Configuration file:

config/smart_item_deleter_v2-common.toml
Option Type Default Description
entityCountThreshold int 200 Number of dropped item entities required before cleanup activates.
minItemAgeMs long 15000 Minimum age (in milliseconds) before an item becomes eligible for deletion. Prevents immediate removal of new drops.
scanIntervalTicks int 20 How often (in ticks) the system scans the world for items (20 ticks = 1 second).
scanJitterEnabled boolean true Adds small random offset (±scanJitterTicks) to interval to reduce server tick spikes when multiple mods act simultaneously.
scanJitterTicks int 2 Maximum jitter added/subtracted from each cleanup cycle’s timing.
consoleDebugLogging boolean true When false, suppresses cleanup summary messages in the server console.
deletePercentage int 90 Percentage of eligible items to delete each cycle (0–100). Protects the newest items even when threshold is exceeded.
whitelistMode boolean false Toggles whitelist (true) or blacklist (false) filtering behavior.
filteredItems list [] Accepts exact item IDs (minecraft:stone), tag references (#forge:ingots), or wildcard globs with */? (e.g., minecraft:*, minecraft:oak*) that define which items are protected (blacklist) or targeted (whitelist).

Example:

entityCountThreshold = 250
minItemAgeMs = 15000
scanIntervalTicks = 20
deletePercentage = 80
whitelistMode = false
filteredItems = ["minecraft:nether_star", "minecraft:diamond"]

Wildcard example

filteredItems = ["minecraft:oak*"]

This configuration means:

  • Cleanup runs roughly every second.
  • Only starts when >250 dropped items exist.
  • Deletes 80% of all items older than 15 seconds (prioritizing the oldest).
  • Diamonds and Nether Stars will never be deleted.

🧠 Technical Details (for developers and maintainers)

Core Behavior

  • Items are tracked in TrackedItemsData, using persistent per-level storage.
  • Each item stores:
    • UUID
    • dimension
    • firstSeenMs (time first detected)
    • lastSeenMs (time last confirmed)
  • Cleanup only occurs when the total item count exceeds the configured threshold.
  • Items are eligible if:
    1. Their age ≥ minItemAgeMs
    2. They pass the current policy filter (blacklist/whitelist mode)
  • When protectNamedItems is enabled, items with custom names are ignored entirely — they do not count toward the threshold and
    are never deleted.

Deletion Logic

  • All eligible items are sorted oldest first (ascending by firstSeenMs).
  • The number of deletions per cycle is:
    deletions = min(excess_items, eligible_items * (deletePercentage / 100))
    
  • This ensures:
    • The server maintains stable tick times.
    • Recent player drops are preserved.
    • Automated machines that constantly spill items are kept clean.

Jitter (scan desynchronization)

  • The system uses a randomized interval of:
    nextInterval = scanIntervalTicks ± scanJitterTicks
    
    to avoid simultaneous heavy-tick bursts when multiple mods or systems run periodic updates.

Code Structure

Package Purpose
core/ Cleanup logic, ticking, filtering, and execution
persist/ Persistent tracking data (SavedData) for per-world storage
config/ Configuration spec and loading
command/ Optional /cleanup admin command for manual triggering

Commands

Command Description
/cleanup run Forces a cleanup cycle manually.
/cleanup status (Planned) Displays tracked item count, eligible items, and current thresholds.
/cleanup config Changes values in the config on the fly.

💡 Future Plans

  • Provide in-game feedback via action bar or server console only
  • Expose metrics to /cleanup status or a scoreboard-compatible data point

📜 License

MIT License — freely usable and modifiable.
Please credit Metl_Play if redistributed.
Would be appreciated if I am mentioned in modpacks, but it's not required.


🧩 Credits

  • Developer: Metl_Play
  • Minecraft: 1.21.1 (NeoForge)
  • Mappings: Parchment mappings
  • Libraries: NeoForge API, standard Java collections

“It’s not just a cleaner mod — it’s a smarter janitor.” 🧠🧹

Verfügbare Versionen

Smart item deleter V2 0.4.9-neoforgedrelease
MC 1.21.1neoforge
19. Januar 2026
Smart item deleter V2 0.4.5-neoforgedrelease
MC 1.21.1neoforge
18. Januar 2026
Smart item deleter V2 0.3.1-neoforgedrelease
MC 1.21.1neoforge
29. November 2025
Smart item deleter V2 0.2.3release
MC 1.21.1neoforge
9. November 2025
Smart item deleter V2 0.2.2release
MC 1.21.1neoforge
7. November 2025

Smart item deleter V2 auf dem Server installieren

1

Server bestellen

Bestelle einen Minecraft Java Server mit mindestens 3 GB RAM (4 GB empfohlen).

2

neoforge Loader setzen

Wähle im Panel unter "Egg" den neoforge-Loader und die passende Minecraft-Version (1.21.1).

3

Mod installieren

Öffne den Mod-Browser im Dashboard und suche nach "Smart item deleter V2". Klicke "Installieren" – fertig! Alternativ: Lade die .jar via SFTP in den /mods Ordner.

Kompatibilität

Mod-Loader

neoforge

Minecraft-Versionen

1.21.1

Server-seitig

Erforderlich

Empfohlener RAM

4 GB(min. 3 GB)

Häufige Fragen

Smart item deleter V2 Server crasht beim Start – was tun?

Häufigste Ursache: falsche neoforge-Version oder zu wenig RAM. Prüfe im Server-Log (latest.log), ob ein "OutOfMemoryError" oder "Mixin"-Fehler auftritt. Bei Mado Hosting: Stelle sicher, dass mindestens 3 GB RAM zugewiesen sind und der Loader zur Mod-Version passt (1.21.1). Über das Panel kannst du den Loader mit einem Klick wechseln.

Ist Smart item deleter V2 mit neoforge kompatibel?

Smart item deleter V2 unterstützt offiziell neoforge für Minecraft 1.21.1. Im Mado Dashboard werden inkompatible Loader-Kombinationen automatisch erkannt.

Server laggt mit Smart item deleter V2 – wie optimiere ich die Performance?

Empfohlener RAM: 4 GB (+1 GB pro 8 Spieler). Prüfe mit /spark profiler, ob Smart item deleter V2 den meisten Tick-Time verbraucht. Häufige Fixes: Server-View-Distance auf 8-10 reduzieren, bei Forge "performant" oder "starlight" als Zusatz-Mod installieren. Bei Mado Hosting läuft dein Server auf NVMe-SSDs mit dedizierten CPU-Kernen für minimale Latenz.

Modded Server mieten

Installiere Smart item deleter V2 mit nur einem Klick auf deinem Server.

Empfohlener RAM
4 GBab €5.2/Monat
Min. 3 GB | +1 GB pro 8 Spieler
Jetzt Server erstellen
1-Klick Mod Installation
NVMe SSD Speicher
DDoS-Schutz inklusive

Details

Lizenz
MIT License
Server-seitig
Erforderlich

Unterstützte Versionen

1.21.1