Tags
Creators
Details
1.4
Compatibility
Changes
Added:
- Support for the FancyHolograms plugin.
- Support for the HolographicDisplays plugin for versions 1.7 and below.
- Now on 1.7.10, the gift cannot be broken with a piston (Never change a new block to a regular head on this version).
- New loot system.
- Check for updates.
- Lots of new actions.
- A single configuration file with a single English language, so that there is no confusion.
- Now you can change the gift block.
- Now you can put a nickname instead of a texture in the head of the gift.
- Added restrictions on the world/biome.
- Added new ways to find a location for a gift.
- Now the hologram can adjust the location in more detail.
- Messages when starting/shutting down the plugin with a link to get help on the plugin.
- New plugin structure (perfectly compatible with the old one).
- The command to get the player's locale is no longer hidden.
Fixed:
- Version compatibility errors.
- The gift could have been broken.
- Some settings were not updated after /gifts reload
- Errors with placeholders in holograms.
- Removed annoying/buggy messages.
- The authorship has been returned.
- The team was put in the right shape.
- The colorization could be buggy.
- The methods did not meet the standards.
- Incorrect plugin structure.
- The code has been optimized.
Deleted:
- Old loot systems and extra code.
- Some old settings.
- Garbage in configurations based on the type of studio advertising or beautiful texts.
- Message mode.
- Other trash...
Thank you all for this long wait. I apologize for posting this resource so early. I don't want people to use bad plugins, so I try to improve it every time. This time, I believe it's the perfect example.
I hope that you will download this correct version. Download my plugins only from trusted forums that I point to GitHub. Be careful!
Optional dependencies
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:PNJfgBM4:UVGPMmqS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PNJfgBM4:UVGPMmqS"
}

