[SPIGOT-5989] Modifying the respawn location in PlayerRespawnEvent still consumes respawn anchor charge Created: 12/Jul/20 Updated: 25/Aug/21 |
|
| Status: | Open |
| Project: | Spigot |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | JRoy | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | 1.16.1, api | ||
| Environment: |
N/A but Windows 10 & latest Java 8 |
||
| Version: | Built from b0c6dfe1ae6fd5907379ba180851f94f45a8a2da |
| Guidelines Read: | Yes |
| Description |
|
During the PlayerRespawnEvent, if the player was being respawned to a respawn anchor (PlayerRespawnEvent#isAnchorSpawn) and you modify the respawn location with PlayerRespawnEvent#setRespawnLocation (away from the respawn anchor) a charge on the respawn anchor will go down. |
| Comments |
| Comment by Martoph [ 02/May/21 ] |
|
I PRd a different solution. The respawn location is not the precursor to the respawn anchor, rather, it's the other way around. |