Links
Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 hours ago
All versions
1.8.0
Release
CustomNPCs 1.8.0last month 1,294
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.5โ1.20.6
Platform
Paper
Changes
What's Changed
- New storage options:
- Local Storage (Default): Stores data in a file on the server.
- MySQL: Stores data in a SQL Database (Good if you already have one)
- MongoDB: Stores data in a MongoDB document (Ideal)
- Conditional Injection (Api only for now): Ensure certain conditions are met prior to spawning the NPC
- Support for PluginUpdater
- Removed support for very old NPC file versions (<1.6- no known users of the plugin this old)
- new command to import data into a storage provider: `/npc movedata <conflict-resolution>
- new config fixer to fix NPCs with 0 hologram lines
- added support for empty hologram lines with
%empty% - the update checker now runs once per hour instead of only on startup
Fixes
- Fixed being able to make NPCs have 0 config lines
Api Changes
- Removed deprecated methods
NPCApi#initialize,NPC#setPostion,NPC#setLegacyActionsSettings#direction,LegacyAction - Reworked action serialization, read the wiki for details.
- Moved some action condition classes around, most notably
Condition#SelectionModeis nowSelector - Settings now has a builder
- Equipment now uses
nullfor empty slots, notAIR. Setting a slot to air will now set it to null. - CustomNPCs is now in maven central! You no longer need to (and shouldn't) https://repo.foxikle.dev. It will be taken down soon.
IMPORTANT NOTE: Any preset walking paths created before this release are sadly incompatible, and need to be re-recorded. This was because of some glaring issues with storage efficiency that I needed to address. I am sorry for the inconvenience if that effected you. According to my analytics, there are no current uses of the action, though.
Cheers! Foxikle <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:5RkhOGwn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ptXUpAzg:5RkhOGwn"
}

