AAC Issue Tracker.
Please make sure to take a quick search in existing issues before posting your issue.
When creating an issue, please include lots and lots of detail. Videos are preferred, screenshots and full console logs at the very minimum. The following will also be nessecary:
If your explanation is too vague, or the issue can't be reproduced, then your issue will be closed. We might require buyer verification before handling issue reports on individual basis.
The AAC Test Server is at test.kons.co
A public discord server is available at https://discord.gg/uc9w2nx
Some links
The ConditionalCommands plugin (written by konsolas) allows you to check certain conditions before another command is issued. Possible conditions: ping, tps, time online, server uptime, player count, permission, aacvl (not aac5), chance More information: https://www.spigotmc.org/resources/conditionalcommands.14295/
The JsonMessageMaker plugin (written by Janmm14) allows you to simply add hover and click effects to chat messages. This might be a useful replacement to /aacstaffnotify. Check it out here: https://www.spigotmc.org/resources/jsonmessagemaker.7938/
The API of AAC is documented in the SpigotMC resource description.
Plugins built against older versions of the AAC API usually work with newer versions of AAC, but not the other way round.
In case a plugin developer has not bought AAC, he can code against a dummy AAC API which is available in this repository, just scroll up to the file list.
Alternatively the dummy AAC API is also available in a maven repository:
<repository>
<id>janmm14-public</id>
<url>https://repo.janmm14.de/repository/public/</url>
</repository>
<dependency>
<groupId>de.janmm14</groupId>
<artifactId>aac-api</artifactId>
<version>5.0.0</version>
<scope>provided</scope>
</dependency>The API and its version is only updated when the API changes. The available versions are in the file names of the api jars (scroll up).
Debug logging can greatly help fixing false positives and bypasses. Consider adding a debug log to your issue, especially when it is about movement.
Debug logging can be toggled for all with /aac debug. Debug will be printed where you executed the command (your chat or the console).
Per-player debugging can be toggled with /aac debug playername, prefer this over general debug logging. Both are spammy.
If enabled, AAC will log check specific data and many player actions from all online players into a debug log file inside plugins/AAC/.
WARNING: AAC debug logging can generate really huge files.
You can toggle the debugging state with /aacdebug, everytime debug is disabled a new debug file will be generated.
A debug log is especially useful for movement related issues.
A debug log shows extended information on what AAC is doing. AAC is capable of debugging one player at a time.
Start debbuging: /aacdebug <player>, <player> needs to be replaced with the name of the player to debug.
Stop debugging: /aacdebug
Saves the debug log to plugins/AAC/.