Links
Tags
Creators
Details
1.7.10
Compatibility
Changes
What's Changed
- 26.1 and 26.2 support
- Added the new FollowPresetPath Action!
- This action allows an NPC to follow a pre-recorded path. It has an option to enable "looping", which will make it teleport to the beginning of the path and start again automatically. It is planned to have the action start on NPC load, as to not need a player interaction to start it.
- Upgrade adventure to version 5
- Reworked the commands to use vanilla Brig
- Removed support for 1.20-1.20.4
- This is due to obfuscation changes which make maintaining these versions more burdensome than they are worth. Very few users use this version, so I felt it was the correct decision for the long term longevity of the project.
- Fixed a couple of misc bugs
- NPCs can have now empty hologram lines with
%empty% - Added a tip to inform players they can Sneak + Click NPCs to open the edit dialog
- NPCs can no longer have 0 hologram lines.
- Added a config fixer to recover NPCs who have 0 config lines, as that prevented the NPC from loading. (/npc fixconfig lines)
- Fixed the NPC skin not being updated when changed on versions 1.21.9-26.2
Full Changelog: https://github.com/Foxikle/CustomNPCs/compare/v1.7.9...v1.7.10
If you have experience speaking a language other than English and are willing to donate your time to improve the plugin, please consider becoming a translator. You can reach out to @foxikle on Discord for more details. In exchange for helping me with the project, you get access to preview builds and exclusive development content.
Cheers <3
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:ptXUpAzg:4KfRWthp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ptXUpAzg:4KfRWthp"
}

