Skip to content

Commit ee4c3f4

Browse files
ryanbarlow97claude
andcommitted
docs(coreprotect): document skill logging and a:skill lookups
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
1 parent 3ed13f2 commit ee4c3f4

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

‎projects/CoreProtect/docs/commands.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -199,8 +199,15 @@ ___
199199
| `a:+session` | player logins |
200200
| `a:-session` | player logouts |
201201
| `a:sign` | messages written on signs |
202+
| `a:skill` | skills used, and where they teleported the player |
202203
| `a:username` | username changes |
203204

205+
#### Skills
206+
207+
With MythicLib installed, CoreProtect logs each skill a player activates, such as MMOCore class skills and MMOItems abilities, at the player's position. If the skill teleports the player within 5 seconds, a second entry records where they went, at the destination, for example `[skill] Arcane Blink (ARCANE_BLINK) teleported from 0 -60 1 to 0 -59 6`. Automatic skills, such as timers and on-hit effects, are not logged.
208+
209+
Skill entries are stored with commands, so `a:command` also lists them and both need the `coreprotect.lookup.command` permission. Use `a:skill` to see only skills, and add `f:<name>` to narrow them to one skill, for example `/co lookup u:Steve t:1d a:skill f:arcane`. A radius lookup such as `/co lookup r:20 a:skill` finds players who teleported into an area. Set `player-skills: false` in `config.yml` to stop logging skills.
210+
204211
---
205212

206213
### `i:<include>`

0 commit comments

Comments
 (0)