Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
AAAntylogout
AAAntylogout is a lightweight but fully featured anti-logout plugin for Paper PvP servers. It starts a combat timer when players hit each other, warns them with chat, bossbar and actionbar feedback, blocks common escape methods, and punishes combat logging with death and item drops.
Why use it?
- Clear 20-second combat timer after PvP hits
- Bossbar, actionbar and chat reminders while tagged
- Combat logout punishment with death, item drops and broadcast messages
- Command restrictions with blacklist or whitelist mode
- Blocked items such as ender pearls, chorus fruit, wind charges and rockets
- Teleport, item drop and elytra restrictions during combat
- Optional WorldGuard support for blocked regions
- Built-in local cuboid regions without any dependency
- Battle history for admins with duration, opponents and result
- Configurable death behavior: surviving opponents can stay tagged after a kill
Commands
/aaalo help/aaalo reload/aaalo status <player>/aaalo history <player> [page]/aaalo stats <player>/aaalo end <player>
Aliases: /antylogout, /al, /aaalog, /alo
Permissions
aaantylogout.admin- access to administration commandsaaantylogout.bypass- bypasses combat tagging and restrictionsaaantylogout.bypass.commands- allows blocked commands during combat
Requirements
- Paper 1.21+
- Java 21
- WorldGuard is optional
Configuration
Everything important is configurable in config.yml: combat duration, logout punishment, command mode, blocked items, teleport causes, region behavior, messages, bossbar, actionbar and chat reminders.
WorldGuard is optional. If it is installed, names from regions.blocked are matched against WorldGuard region IDs. Without WorldGuard, define matching cuboids in regions.local-regions.
First release
Version 1.0.0 is the first production release of AAAntylogout.
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:jD0hP9Rr:ZJauyv6P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jD0hP9Rr:ZJauyv6P"
}

