Tags
Creators
Details
2.1.0
Compatibility
Changes
Grave lists, Grave fixes, Grave performance, Grave limits
After releasing version 0.5.0, I got to work on version 0.6.0 next. I got really close to finally releasing a stable version of HyperGrave after more than a year of development, and I expected to do a few more bug fixes before releasing 2.0.0.
However, on 28th of February, the Iran war started (I'm an Iranian by the way, if you didn't know that). Now the war itself wasn't the main problem, actually, it was Iran's government completely shutting down internet. I could only use government-approved websites. I couldn't use Github, Modrinth, Planet Minecraft, Discord, etc.
I wanted HyperGrave 2.0.0 to release a few weeks after Minecraft 26.1's release, but because of the internet shutdown, I couldn't make it release on time.
Eventually, I got a VPN from the black market. It was 1 GB and around 6,000,000 Iranian Rials (around 4 US Dollars), and I could only use it on my phone. I then rushed to just release HyperGrave 2.0.0, skipping 0.6.0 entirely.
This is why HyperGrave 2.0.0 was buggy. I thought it supported Minecraft 26.1, but then I realized it didn't fully support Minecraft 26.1. I realized that not only was the Creation Time field in Grave Info Display broken, but so was like all text messages were also broken. There were these little double quotes (") everywhere and some text were not colored correctly. Not only that, but it was also slow and made Minecraft laggy, especially when there were multiple graves (This one issue happened on all versions by the way).
This version fixed all of those bugs and several other issues with HyperGrave. It also adds grave lists (keep reading) and a new operation for Item Distribution / Grave Generation Fail!
Additions
- Added Grave List Display.
- This shows a list of GIDs of all graves. It is used to navigate through the Grave Info Display feature easier and quickly view the info of all active and broken graves.
- All of those GIDs are separated into 4 groups to easily tell which graves are broken or active and also tell which graves belong to you or other players.
- Added operation "drop" to Graves / Item Distribution / Grave Generation Fail config.
- If this operation is selected, the player's items will be dropped if grave generation fails.
- There is also a new config: Graves / Item Distribution / Grave Generation Fail / Naturalize Drop Acceleration, which gives dropped items random motion to seem natural and match vanilla behavior.
- Added list of commands to help menu.
- This should make it easier for players to quickly learn about how HyperGrave's commands work in-game, without having to go to the documentation at Modrinth.
- Added a link to Planet Minecraft on the info menu.
- Added proper support for Minecraft 26.1.x and 26.2.x.
Changes
- Improved item tooltips in Grave Info Display.
- They should now show the components of the item (i.e. enchantments, custom names, custom models, etc).
- Limited the number of loaded active graves to 16.
- More than 16 active graves in loaded chunks is considered too many and it significantly slows down Minecraft, so to prevent players from spamming graves everywhere, this limit has now been put in place.
- Limited the number of graves (active or broken) in database (keep reading) to 100.
- Okay, the very actual limit is 128. The 100 limit is only applied when the number of graves reaches 129.
- This is done to prevent HyperGrave from slowing down overtime
- Rename the Documentation link to Modrinth in the info menu.
- Changed pack.png
- Significantly improved performance of HyperGrave.
Removals
- Removed the warning message for failed /time commands.
- Removed success messages for changing some configs.
- Removed the command
/function hygrave:run/graves/admin/generate.- This command always had some sort of issue and I don't really see why anyone would use it, so I removed it.
Technical
- Added Annoying Mode.
- Renamed the term "map" to "database".
- Renamed the function directory "macro" to "helper".
- Renamed operation "insert" on databases to "append".
- Localized function macro arguments (i.e. they are now stored in
temp.mcargs.'FUNCTION'instead oftemp.args). - Removed the unused
players[].gravesdatabase.
Fixes
- Creation Time field in Grave Info Displays and Backup Info Displays not working properly (#20)
- Unexpected pretty-printing (#21)
- Remotely looting graves not giving you the items in some rare cases (#22)
- Requirements for generating graves not being applied as if items were already distributed (#23)
- The Grave Info Display sometimes showing the despawn time of another grave (#24)
- The Grave Mini-Info Display field separator being inconsistent (#25)
- Graves / Drop Contents On Despawn config not working properly (#26)
- Grave Mini-Info Display not being shown to other dead players
- Many Issues with uninstalling and reinstalling
- GID showing as white in error message when trying to view the info of a non-existent grave
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:zwO28AXh:FEJR3gff"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zwO28AXh:FEJR3gff"
}

