[SPIGOT-7076] End gateway age resets on cancelled break events Created: 21/Jun/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: Hjalmar Gunnarsson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: 1.19, BlockBreakEvent, end_gateway
Environment:

Repros on fresh install of the latest spigot 1.19 artefact, running on windows 10.
Attached dummy plugin used to repro.

Does not repro on fresh install of the final spigot 1.18 artefact running on windows 10 with attached dummy plugin.
The same attached dummy plugin was used in both repro attempts.
 

Attachments: File EndGatewayExample-1.jar    
Version: CraftBukkit version 3537-Spigot-56be6a8-622dbe6 (MC: 1.19) (Implementing API version 1.19-R0.1-SNAPSHOT)
Guidelines Read: Yes

 Description   

The age property can be used to prevent end gateways from producing their distinctive purple beam. It is a common practice to set the age of aesthetic end gateways to `-9223372036854775808L`

Such an age can be simulated with the vanilla command 

setblock ~ ~ ~ end_gateway{Age:-9223372036854775808L} replace

In previous versions of spigot, if a player's attempt to break an end gateway gets cancelled, the age persists. Unfortunately, in 1.19, that changed: cancelled player break attempts reset end gateway age, therefrom resulting in a purple beam.

 Comments   
Comment by Hjalmar Gunnarsson [ 21/Jun/22 ]

f3+I data of the block before breaking it: /setblock -65 145 304 minecraft:end_gateway{Age:-9223372036854771420L}
f3+l data of the block after breaking it: /setblock -65 145 304 minecraft:end_gateway{Age:-9223372036854767202L}

So I guess it's an client side issue

Comment by Black Hole [ 21/Jun/22 ]

Please check using F3+I (requires an opped player) that the internal data is really reset or just the data on the client.

Generated at Tue Apr 15 09:41:35 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.