Tags
Creators
Details
3.0.0
Compatibility
Required content
Changes
-
Architectury dependency removed. DeepIn now uses each loader's native APIs directly (Fabric, NeoForge, Forge).
fabric-apiis now a required dependency instead of optional. -
Folia support
-
Forge support
-
/deepin reloadreloads the config file. -
LuckPerms support (Optional) The mod will work as normal without it.
deepin.use— allows using the instamine featuredeepin.reload— allows/deepin reloaddeepin.bypass.tool— instamine with any tooldeepin.bypass.enchants— skip the efficiency requirementdeepin.bypass.beacon— skip the beacon requirementdeepin.bypass— bypasses all requirements
-
Haste is now granted purely from server-tick logic instead of directly from block-break/damage events, fixing the desync warning below and making chain-mining much cheaper on busy servers.
-
Failed beacon searches are throttled to once every 2 seconds per player, instead of scanning every tick.
New tuning options (config, all defaults)
| Key | Default | What it does |
|---|---|---|
graceDurationTicks |
120 (6s) | How long grace haste lasts after leaving a beacon/stopping mining |
renewSkipTicks |
5 | How often the haste effect packet is refreshed while mining |
miningTargetTtlTicks |
40 (2s) | How long a mining target stays "active" after your last hit |
beaconScanRange |
50 | Radius (blocks) searched for beacons |
permissionNodePrefix |
deepin |
Prefix for all permission nodes |
geometryCacheTtlTicks |
4 | How often beacon geometry is recomputed |
geometryCacheEvictTicks |
400 | Idle geometry cache eviction time |
searchCooldownTicks |
40 (2s) | Cooldown between failed beacon searches |
cacheSweepIntervalTicks |
6000 (5min) | Interval of the periodic cache cleanup |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:6aUxvoDr:AL2xsQAW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6aUxvoDr:AL2xsQAW"
}

