Tags
Creators
Details
Licensed ARR
Published last year
Updated 5 months ago
All versions
2.3.0
Release
AntiGrifer 2.3.09 months ago 51
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Paper
Changes
Changelog
[2.3.0] - 2026-01-16
✨ Новые возможности (Features)
- Система слежки и Алертов (Alerts & Spectator):
- 🎨 Premium Design: Новые красивые градиенты для уведомлений.
- 👁️ Click-to-Spectate: Кнопка [СЛЕЖКА] в чате для мгновенного перехода в режим наблюдения за подозреваемым.
- 📡 Discord Integration: Улучшенные вебхуки с указанием ника игрока и действия.
- Команда
/ags internal spectate <player>(внутренняя).
- Стабильность и Исправления:
- ✅ Исправлено отключение плагина при первом запуске (авто-создание
messages.yml). - ✅
DatabaseManager: Добавлен авто-реконнект к базе данных (fixconnection closed). - ✅
LocaleManager: Исправлена ошибка "Message not found" для ключей в корне файла. - ✅
Dependency Loading: Автоматическая загрузка драйверов SQLite черезlibraries(Paper 1.21+).
- ✅ Исправлено отключение плагина при первом запуске (авто-создание
🇬🇧 Added (EN)
- Alerts & Spectator System:
- 🎨 Premium Design: New gradient colors for in-game notifications.
- 👁️ Click-to-Spectate: Clickable [SPECTATE] button to instantly teleport to potential griefers.
- 📡 Discord Integration: Enhanced webhooks with player names.
- Stability & Fixes:
- ✅ Fixed plugin disabling on first launch (auto-create
messages.yml). - ✅
DatabaseManager: Added auto-reconnect logic to preventconnection closederrors. - ✅
LocaleManager: Fixed "Message not found" error for root keys. - ✅
Dependency Loading: Native support forlibrariesloading (SQLite/HikariCP) on Paper 1.21+.
- ✅ Fixed plugin disabling on first launch (auto-create
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:ZcDANgmk:pYRzozqc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZcDANgmk:pYRzozqc"
}

