1.1
Compatibility
Changes
RU
-
Добавлена проверка LuckPerms. Теперь если у игрока будет группа у которой есть пермишен op, то его так же забанит.
-
Добавлена команда /ado reload, которая перезагружает конфиг. Нужна для того, чтобы перезагрузить конфиг, если Вы его меняли в ручную, а не через команду.
В последующих версиях может быть будет реализована блокировка по списку определённых групп
EN
-
Added a LuckPerms check. Now, if a player is in a group with the op permission, they will also be banned.
-
Added the /ado reload command, which reloads the config. This is needed to reload the config if you changed it manually, rather than using the command.
In future versions, banning based on a list of specific groups may be implemented
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:uFIF4Ilk:dXhdLsmt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uFIF4Ilk:dXhdLsmt"
}

