Links
Tags
Creators
Details
4.0.0
Compatibility
Changes
In this update the groupId is changed, the API is published in Maven Central instead of JitPack, MiniPlaceholders 2 is supported and the ignoreSignedPlayers option is removed.
How to update
Simply delete the libs folder in the AuthMeVelocity directory.
In addition, AuthMeVelocity is now distributed in 2 jars (as initially distributed), this allows to have a better modularity and to be able to implement more modules in the future (probably an exclusive version for Paper 1.19.3+). AuthMeVelocity-Proxy must be installed on your Velocity proxy and AuthMeVelocity-Paper must be installed on your servers that have AuthMeReloaded installed
Compatibility with Minecraft 1.19.1+
In this version the ignoreSignedPlayers option is removed. This is done because I developed a plugin that fixes this problem in Velocity, called UnSignedVelocity.
What's Changed
- AuthMeVelocity 4 in https://github.com/4drian3d/AuthMeVelocity/pull/76
- fix(deps): update dependency org.bstats:bstats-velocity to v3.0.1 in https://github.com/4drian3d/AuthMeVelocity/pull/77
- chore(deps): update dependency gradle to v8 in https://github.com/4drian3d/AuthMeVelocity/pull/78
- chore(deps): update dependency net.minecrell.plugin-yml.bukkit to v0.5.3 in https://github.com/4drian3d/AuthMeVelocity/pull/80
- chore(deps): update shadow to v8 (major) in https://github.com/4drian3d/AuthMeVelocity/pull/81
- chore(deps): update dependency gradle to v8.0.2 in https://github.com/4drian3d/AuthMeVelocity/pull/79
- refactor!: change package to io.github._4drian3d.authmevelocity
- feat: implement separate releases
- publish: Maven Central
- fix: removed ignore signed players option
- fix(deps): updated to MiniPlaceholders 2
- feat: implement injection
- feat: improved configuration handling
- test: implement tests
- fix: fixed legacy minecraft version plugin message sending
Full Changelog: https://github.com/4drian3d/AuthMeVelocity/compare/3.0.6...4.0.0
Optional dependencies
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:sG6SrXta:PP6Iflc5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sG6SrXta:PP6Iflc5"
}

