Hello, the MyPet condition in LevelledMobs v4 is currently failing to detect pets if the server is running the new MyPet v4 (alpha for 26.1.2).
Since MyPet v4 now uses standard vanilla entities instead of custom NMS classes, LevelledMobs treats all pets as regular mobs and applies levels/nametags to them, ignoring the 'external-plugins: included-list: ["my-pet"]' condition. Could you update the MyPet hook to support the v4 API?
A clear and concise description of what the bug is.
Server software
Paper
Server version
Minecraft 26.1.2
LevelledMobs version
4.5.3.2 b159
Config files
- custom-rule: 'Mypet no nametag'
is-enabled: true
use-preset: challenge-vanilla, nametag-disabled
conditions:
external-plugins:
included-list: ['my-pet']
#excluded-list: ['*']
Hello, the MyPet condition in LevelledMobs v4 is currently failing to detect pets if the server is running the new MyPet v4 (alpha for 26.1.2).
Since MyPet v4 now uses standard vanilla entities instead of custom NMS classes, LevelledMobs treats all pets as regular mobs and applies levels/nametags to them, ignoring the 'external-plugins: included-list: ["my-pet"]' condition. Could you update the MyPet hook to support the v4 API?
A clear and concise description of what the bug is.
Server software
Paper
Server version
Minecraft 26.1.2
LevelledMobs version
4.5.3.2 b159
Config files
is-enabled: true
use-preset: challenge-vanilla, nametag-disabled
conditions:
external-plugins:
included-list: ['my-pet']
#excluded-list: ['*']