Why Your Minecraft Folder Fills Up (and What Log Cleaner Does About It)
If you have played Minecraft for a while, made packs, run servers, or chased crash reports, you already know how fast log files add up. They are useful when something breaks, but they are rarely something you want to keep forever. The Log Cleaner mod is a lightweight option that helps you tame old, unused logs without gambling on the wrong deletion rule.
What Log Cleaner Actually Cleans
Log Cleaner targets old, unused log files rather than trying to reorganize your whole instance. The idea is simple: storage stays lean, and you spend less time digging through megabytes of stale text when you only care about what happened recently. Because it focuses on logs, you still treat screenshots, worlds, and configs as separate concerns—which is how most players and admins already think about their folders.
Why “Last Access” Matters More Than Creation Date
Many cleanup tools assume “older created file equals safe to delete.” That works until you realize some logs get touched again long after they were first written, whether a tool opened them, a script glanced at them, or another mod appended a line during a later launch.
Log Cleaner uses the most recent access to the file as its signal, not the creation date alone. If anything still interacts with a log for any reason, it is far less likely to vanish just because the calendar says the file is old. That is a practical difference for debugging servers and packs where you might reopen a log days later and still need the same trail of errors.
Client-Side, Server-Side, and Version Flexibility
You can run Log Cleaner in a client-only setup when your singleplayer instance or launcher profile is the noisy one, or server-side only when the machine hosting the world is where logs balloon fastest. You do not have to mirror the mod everywhere if only one side is the problem. It also aims to work across Minecraft versions, which matters if you hop between updates, maintain a small network of servers, or keep legacy instances around for older worlds.
When you are juggling multiple modded profiles, having a modern way to pull in small utilities without hunting around the web helps a lot—this mod can be easily installed through the foxygame.net launcher, a flexible Minecraft launcher that lets you grab mods from the menu so you spend less time on setup and more time in-game.
Defaults That Respect Debugging (and How to Tune Them)
Out of the box, Log Cleaner removes logs that have not been used for more than 14 days. Two weeks is long enough that you can still return to a problem you shelved, but short enough that your disk does not slowly turn into an archive of every launcher hiccup from last year. If your workflow needs a longer safety window—say you triage crashes on a slower cadence—you can push that window outward.
- Balanced housekeeping: Keep the default when you want occasional cleanup without micromanaging.
- Stricter or looser rules: Raise or lower the threshold if your server log volume or your modpack churn is unusually high or low.
- Quieter logs: If you do not want extra chatter about how many files were removed, you can suppress that reporting.
Configuration: Where the Knobs Live
You will find the settings in config/logcleaner.json. Two options cover most needs:
daysOld: Minimum number of days a log must go unused before deletion. Default is 14.silent: When set totrue, Log Cleaner will not post a message about how many log files it deleted. Default isfalse.
That small surface area is a feature. You are not managing a dozen toggles you will forget next month; you set a retention posture, decide whether you want confirmation in the log, and move on.
Who Benefits the Most
Server operators with always-on instances will notice disk savings first, especially when mods produce verbose output. Pack makers and testers also benefit, because iterative launches can generate a surprising number of files even when nothing “went wrong.” Singleplayer players who mod aggressively get the same relief without needing to babysit folders by hand.
A Practical Takeaway
Log Cleaner is not about pretending logs never matter; it is about letting go of the ones that have genuinely gone cold. By prioritizing recent access over a naive timestamp, it reduces the chance you delete something you were still implicitly relying on. Pair sensible defaults with a configuration file you can tweak in seconds, and you get cleaner instances, quieter disks, and fewer “why is this folder 12 gigabytes” moments—all without changing how you play Minecraft.