1.0.5
Compatibility
Changes
Added timer support for script hosts.
Script hosts can now use timer methods similar to NPC timers. This allows smoother particle animation weapons, advanced tick-based weapon effects, looping skills, and other complex scripted behaviors.
One important reason for adding this system is to avoid putting everything inside player scripts.
Using only player scripts makes special weapons difficult to manage:
It is inconvenient for maps with many custom weapons. Different weapons may conflict with each other. It is not practical to create one player script page for every weapon.
Now, scripted items can manage their own timer logic independently.
Added global CNPC API support for script hosts.
**You no longer need to manually use:
Java.type("noppes.npcs.api.NpcAPI").Instance()
Now you can directly use:
API**
inside script host environments.
This update is mainly focused on improving development experience for RPG maps, animated weapons, and advanced scripted combat systems.
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:LyKJm6uV:52YESygX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LyKJm6uV:52YESygX"
}

