CurseForge · Minecraft mod
ChunkPurge
Systematically check for and unload chunks that shouldn't be loaded
Quick answer
Which ChunkPurge release should I use?
Chunkpurge 1.7.10-2.1 targets 1.7.10. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.
Where it goes
Is ChunkPurge required on the client, server, or both?
The project page does not say whether this file belongs on the client, dedicated server, or both.
The source does not explicitly classify this release as client-only or server-only.
What else does Chunkpurge 1.7.10-2.1 need?
Chunkpurge 1.7.10-2.1. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add ChunkPurge without breaking your instance.
Built for Chunkpurge 1.7.10-2.1. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use Chunkpurge 1.7.10-2.1. It targets 1.7.10; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
The project page does not say whether this file belongs on the client, dedicated server, or both.
- 04
Pick the file you checked
Use the “Get this file” button beside Chunkpurge 1.7.10-2.1. It opens that exact file at the source.
About this project
What does ChunkPurge add?
This project is a forked and now heavily modified version of ChunkPurge for 1.6.4.
It is intended to work with Minecraft v1.7.10 Infitech 2 v3.1.14
While the project had already been forked and updated to 1.7.10, it was both uncompiled, and didn't work with infitech 2.
GitHub: https://github.com/Android25/ChunkPurge
Description
This mod works by periodically scanning the loaded chunks in each dimension that are configured to be scanned, and identifying those which are isolated from any valid chunk watchers. Those chunks are then scheduled for unloading. Valid chunk watchers are players, chunkloading tickets (force loaded chunks), and the spawn areas of certain dimensions.
By only unloading isolated chunks, we avoid breaking energy nets and other multi-chunk objects. Partially unloading these would cause significant lag spikes. A flood fill algorithm is used to identify which chunks are still linked to chunk watchers, and the remaining chunks are unloaded.
Commands
These configuration options can also be edited in ChunkPurge.cfg. For all commands omit the parameter to view the current setting.
/chunkpurge delay [ticks]
The number of ticks to wait between chunk unloading attempts. Default: 600
/chunkpurge debug [true|false]
Logs to console the number of chunks unloaded from each dimension, and how long is spent calculating which chunks to unload. Default: false
/chunkpurge enable [true|false]
Setting to false will prevent any attempts to unload chunks. Default: true
/chunkpurge pradius [# of chunks]
Sets the ignore radius around each player. Ignore radius for the player is the sum of server set player view distance and pradius. Chunks outside the ignore radius will be forced to unload regardless of whether or not those chunks are connected to player loaded chunks. Default: 4
/chunkpurge tradius [# of chunks]
Sets the ignore radius around each force loaded chunk (chunk loading ticket). Chunks outside the ignore radius will be forced to unload regardless of whether or not those chunks are connected to force loaded chunks. Default: 5
/chunkpurge sradius [# of chunks]
Sets the ignore radius around spawn loaded chunks. Ignore radius for spawn is the sum of spawn loaded chunks (8) and sradius Chunks outside the ignore radius will be forced to unload regardless of whether or not those chunks are connected to spawn loaded chunks. Default: 3
/chunkpurge dimlist
Lists the current dimension ID's being checked by ChunkPurge for unload. The default is set to only check the Overworld (dim 0) for unload. Default: 0
/chunkpurge dimlist add [DimID,DimID,ect.]
Adds dimension ID's to be checked by ChunkPurge for unload. The default is set to only unload chunks in the overworld (dim 0). However, using /chunkpurge dimlist add -1,1 would set the Nether and End to be checked as well. Any number of dimID's can be added at one time in a comma seperated list with NO spaces.
/chunkpurge dimlist remove [DimID,DimID,ect.]
Removes dimension ID's to be checked by ChunkPurge for unload. If the the config is set to check Overworld, Nether, and End, using /chunkpurge dimlist remove -1,1 would set the Nether and End to no longer be checked. Any number of dimID's can be removed at one time in a comma seperated list with NO spaces.
Project description from CurseForge.
Pick your setup
ChunkPurge by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
Check the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
ChunkPurge versions and loaders
Chunkpurge 1.7.10-2.1
ChunkPurge-1.7.10-2.1.jar
19 Oct 2015
ChunkPurge 1.7.10 2.0 Release
ChunkPurge-1.7.10-2.0.jar
15 Oct 2015
Looking for an older file? The official CurseForge project page is in Resources.