Tags
Creators
Details
5.6.9
Compatibility
Changes
Importance Notice: due to a permission issue in 5.6.8 where the console occasionally did not have permission to perform admin commands (e.g. /at reload), at.member.core.* no longer gives permission to administrative commands - whilst at.member.core.reload still works, it is not inherited through the aforementioned wildcard permission. Instead, at.admin.core.* is the new permission to grant. Permissions like at.admin.core.reload will grant permission to /at reload too.
I couldn't find why attempted workarounds did not work to prevent this change, but I do think this is a better change in the long run. Please do let me know if anything doesn't seem right permission-wise.
There are also some extra changes that will give the plugin higher priority in handling respawns, but this can be changed and disabled - this is only to overrule plugins like Multiverse if they are being a pain and it's not immediately clear what is causing the plugin issues.
f925d18 fix: Info section not being lenient - Thatsmusic99
04c799e feat: allow blank messages to be replaced with actionbar messages in the console - Thatsmusic99
4ab5a83 feat: add teleportation to the nearest spawnpoint - Thatsmusic99
e926936 fix!: change admin core permissions to at.admin.core.command - Thatsmusic99
3b221aa feat: add /atp and /adtp as aliases - Thatsmusic99
5caad3c fix: set respawn priority to HIGHEST, *hopefully beating down other plugins - Thatsmusic99
74c715f fix: use current location rather than previous location when respawning - Thatsmusic99
caa66ef fix: admin commands not showing up in tabcomplete when user has permission - Thatsmusic99
28f78e6 fix: at.member.core not considered a default member permission - Thatsmusic99
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:BQFzmxKU:r901m14z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BQFzmxKU:r901m14z"
}
