Closed ScrapMetalGolem closed 7 months ago
Using the binary method, the offending plugin was PurpurExtras. Reviewing the config, someone had set mobs to require a nametag to ride. When using a nametag, the feature functions as expected.
Closing issue, thank you for the assistance.
Spark link
https://spark.lucko.me/lGqW0BM2VP
Expected behavior
When a player with proper permissions, or an OP, shift-right-clicks a mob which is configured to be ridable, the player will mount the mob.
Observed/Actual behavior
When a player does not have the proper permissions, an error is printed in chat as expected: However, when a player with permission allow.ride.mobname tries to mount a mob configured with ridable: true, there is no response at all, no message in chat, no message in console.
Steps/models to reproduce
Purpur 2143 (same result with other 1.20.4 versions) enable ridable: true (and optionally controllable: true) in purpur.yml for a mob (e.g. sheep) set permission allow.ride.sheep true for a player or rank right click, and shift right click the relevant mob - no response test again as OP or with * perm - no response
Purpur version
[09:04:50] [Render thread/INFO]: [System] [CHAT] Checking version, please wait... [09:04:50] [Render thread/INFO]: [System] [CHAT] Current: git-Purpur-2143 (MC: 1.20.4)\nPrevious: git-Purpur-2127 (MC: 1.20.4)\n You are running the latest version
Agreements
Other
Horses, donkeys, etc still function as in vanilla.