Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
PermaClicker 2.0.0 moves to TurtleLib 2.0.0 and the MIT license, makes Mining mode safer around mobs and players, and fixes the toggle key and the update notice.
Compatibility
- TurtleLib 2.0.0: PermaClicker now requires TurtleLib 2.0.0 or newer; update both mods together.
- NeoForge: Requires NeoForge 26.3.0.76 or newer, the first stable NeoForge release for Minecraft 26.3.
Improvements
- Translated status: The action-bar status now appears in your game language.
- Settings file: A damaged settings file is kept as
permaclicker.json.brokeninstead of being overwritten, and saving can no longer leave an empty file.
Fixes
- Mining mode: Mobs, animals and players that step in front of the block are no longer hit, and mining stops as soon as you look away from the block.
- Toggle key:
F7no longer ignores a press after a menu was open, and the misleading "toggle key was reset" message is gone. - Attack key: PermaClicker now uses your own attack key binding instead of the default one.
- Dedicated servers: PermaClicker no longer stops a NeoForge server from starting when it is installed there by mistake; the server now skips it.
- Update notice: The update check works again, only reports versions for your loader and Minecraft version, and its links open the release directly.
- NeoForge warning: The "deprecated logoFile" warning no longer appears in the NeoForge log.
Other
- Update privacy: The README and wiki now list which services the update check asks and what they receive.
- Mod details: Updated description, icon and links in Mod Menu and the NeoForge mod list.
- MIT license: PermaClicker is now licensed under MIT (previously Apache-2.0).
- Build from source: The repository now builds on its own, without the development workspace.
Full Changelog: https://github.com/hrobasti/permaclicker-mod/compare/1.4.0...2.0.0
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| PermaClicker_2.0.0_MC-26-3_NEOFORGE_26-3-0-76-source.jar | Sources jar | 66.24 KiB |
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:nVaFHGVe:m91WjNXJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nVaFHGVe:m91WjNXJ"
}

