Tags
Creators
Details
Licensed MIT
Published last year
Updated 2 weeks ago
All versions
1.0.8
Release
BlockRevive 1.0.82 weeks ago 70
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platform
Paper
Changes
Changelog
Stability Release and many Bug Fixes:
Version Update
- Have been tested all all latest 26.+ version, thanks for all the support and sorry for the long long delay.
Security
- Fixed: any player could run
/blockrevive rewards resetandreload— no permission was checked at all
Blocks stuck as bedrock
- Fixed:
/blockrevive group disableandrescanleft blocks permanently as bedrock, and rescan then saved that bedrock as the region's real content - Fixed: crops froze mid-growth after a cancel
- Fixed: a server crash lost every pending block — the save file was deleted right after being read
- Fixed: one error could stop regeneration server-wide until a restart
Rewards
- Fixed: item rewards were silently deleted when inventory space ran low (the space check counted entries, not stacks)
- Fixed: reward data could be wiped by a crash during the autosave, letting everyone re-claim every tier
- Fixed:
rewards reloaddiscarded unsaved progress and left Vault stale
Chests
- Fixed: ordinary chests randomly locked up and opened the rewards menu — any double chest with arrows or barriers in the bottom row was mistaken for the GUI
- Fixed:
blockrevive.rewardsis now actually enforced - Added:
rewards.enabledto switch the whole rewards module off
Nexo
- Fixed: Nexo custom blocks never counted toward rewards —
blocks-mined-requiredaccepted Nexo ids in the docs, but matching only used the vanilla block underneath, so those tiers never progressed - Fixed: Nexo blocks are now also counted in PlaceholderAPI mining statistics under their own id
Breaking & protection
- Fixed: breaks cancelled by protection plugins still paid rewards and still turned blocks to bedrock
- Fixed: installing WorldGuard blocked all non-OP mining, even with no WorldGuard regions
- Fixed: any block placed in a region after scanning became an infinite resource
Performance
- Fixed: region settings were re-read from disk every few ticks — now cached
- Fixed: scanning a region generated terrain just to look at it
Region data
- Fixed: saving a region could silently lose its block cache when the save collided with a block break
- Fixed:
/blockrevive resetscheduled one task per block, stalling the server on large regions
Other
- Fixed: break particles never rendered at all
- Fixed:
requiresPermissioninregions/<name>.ymlwas ignored - Fixed: crops dropped nothing when broken in a region
- Fixed: hologram entities leaked into the world permanently;
textScaleandlineSpacingdid nothing - Added:
config.ymlupdates automatically on new versions, keeping your settings and backing up the old file
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:SCRRvX5P:7HFITH1F"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SCRRvX5P:7HFITH1F"
}

