Tags
Creators
Details
0.2.1
Compatibility
Changes
This update internally changes a lot.
NQMItems now must be classified into a group. Added a fake creative menu for better testing and ease of access. Particles and Projectiles are now split into 3 different class types.
- No prefix means the object supports no entities being linked normally
- Simple means it supports one entity
- Complex supports multiple entities
Added an inbuilt yaw rotation for the entities visually in both.
Both Projectiles and Particles are now spawned by just making a new object instead of through their handlers. The Particle and Projectile ticker are now always running. Fixed issue with performance involving entities sometimes sticking around when they shouldn't.
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:9o48ewWA:hiwK3sAQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9o48ewWA:hiwK3sAQ"
}

