1.8.3
Compatibility
Changes
Feature creep being a very real thing, I've added in a Ranger Points system for interacting with Gigaremo. It should be noted that right now these points serve no function.
Players gain points for the following interactions:
- Activating a Gigaremo: -500
- Destroying a Gigaremo with a Move Skill: 100
- Destroying a Gigaremo with a special interaction (enabled through config): 25
- Destroying a Gigaremo manually: 15
There are also commands allowing points to be checked, added, or set to a specific value. Points are tracked in two ways - total points earned, and available points. Total points can be negative, while available points cannot. Available points cannot be higher than total points, if you have a negative total you will need to get this into a positive before you will be able to gain available points.
The eventual intention is that Ranger NPCs will trade items to players. Total Points will determine the players reputation/rank with the Rangers (and the range of items available) while Available Points will act as the currency players can spend to get the items. Total Points is able to go into a negative value as I intend of having unique dialogue (and possibly combat interactions) if players with bad standing try to talk to Ranger NPCs, and to allow similar positive interactions with villain teams (although this isn't a major focus to me so I'm unlikely to flesh it out myself, I recognize the potential here for other people to eventually expand the concept with the Pixelmon quest system).
I also intend on granting players points for defeating enraged Pixelmon in battle, however I haven't figured out how to do this reliably yet.
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:YuN7khZs:mYjOjAaE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YuN7khZs:mYjOjAaE"
}

