[SPIGOT-7180] Player-Owned Cats Not Sitting Created: 06/Nov/22 Updated: 25/Dec/24 |
|
Status: | Open |
Project: | Spigot |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Minor |
Reporter: | Tyler Digiacomo | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 0 |
Labels: | bug, redstone, spigot | ||
Environment: |
Apex Hosting 6GB -MC966131 server. |
Attachments: |
![]() |
Version: | 1.19.2 |
Plugin: | Floodgate, Geyser (These are confirmed to not be the cause of the issue, see description) |
Guidelines Read: | Yes |
Description |
When disconnecting from the server, any cats owned by a player have a chance to not sit down/lock chests. This has been extensively tested in spawn chunks: If another player is present near the cat when the player logs out, the cat will sit normally, locking a chest and triggering a redstone signal. However, if this is done in the absence of another nearby player, it fails to trigger 50% of the time for seemingly no reason. This issue is only affecting Spigot - testing this in vanilla and Paper server versions causes the cat to sit and lock the chest 100% of the time, regardless of the presence of other players. Modifying spigot yml settings did not affect this in any noticeable way. Attached is a screenshot of the redstone device used for testing. This is normally used for wireless redstone to trigger an ender pearl stasis chamber. The only loaded plugins are Floodgate and Geyser, which cause no issues when loaded on a Paper server. |
Comments |
Comment by md_5 [ 07/Nov/22 ] |
Thanks. We might need to whitelist owned animals. |
Comment by Tyler Digiacomo [ 07/Nov/22 ] |
Just tested this now and can confirm that this resolved the issue. Thanks heaps for the fix! |
Comment by md_5 [ 07/Nov/22 ] |
Setting activation range to 0 should disable it. Does that fix the issue? |
Comment by Tyler Digiacomo [ 06/Nov/22 ] |
Disabling entity activation allows the 2nd spectating player to witness this issue. As expected, the cat completely fails to sit approximately 50% of the time. Based on the above, this issue is likely tied to entity-activation range. Since this setting cannot be disabled, the values only increased or decreased, this issue/bug cannot be circumvented. |