[SPIGOT-5712] Guardian laser only display bubble Created: 01/May/20  Updated: 28/Apr/21  Resolved: 01/May/20

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: cocoraid Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: 1.15.2, PaperSpigot, bubble, bug, guardian, laser, spigot

Version: 1.15.2 and 1 version behind
Plugin: ProdigyNightclub
Guidelines Read: Yes

 Description   

I don't know if it is linked:

https://bugs.mojang.com/browse/MC-165595

But with spigot, all my lasers are only bubbles in the world.

Some of my customers reported me that in some worlds that's fine.

So I decided to switch to paper spigot, and this is working, lasers are always displayed.

 

My code:

https://paste.md-5.net/huremodohe.java

 

 Comments   
Comment by cocoraid [ 28/Apr/21 ]

I fixed this bug by setting the world time elapsed to 0 when the plugin loads

WorldData worldData = ((CraftWorld)p1.getWorld()).getHandle().getWorldData(); Reflection.getField(worldData.getClass(),long.class,0).set(worldData,0);

This guy was right:

When I tried to use NBTExplorer to modify the "Time" metadata in 'level.dat', I found out that when this value reaches ~2800000 or above , this issue occurs. Pasting this value or anything higher on a brand new world will have an 100% chance to cause this issue.
Comment by cocoraid [ 23/Apr/21 ]

For the latest spigot version (1.16.5 latest build), this bug still occurs.

I have more info now:

  • During my test the world was fine, and after a few restart during 1 week, the guardian beam shows only bubble via packets
  • So I decided to spawn a vanilla guardian with a simple egg and the behavior is the same, only bubble. This is not a packet issue.
  • When I load a new world that's fine
  • The bug does not exist with paperspigot
  • and someone posted an issue about that for mojang:
I found the bug cause: After creating backups upon backups, deleting files in those backups... When I tried to use NBTExplorer to modify the "Time" metadata in 'level.dat', I found out that when this value reaches ~2800000 or above , this issue occurs. Pasting this value or anything higher on a brand new world will have an 100% chance to cause this issue.
Comment by cocoraid [ 01/May/20 ]

I can't test with vanilla as the guardian only use player or squid for targeting. And I use armorstand's target.

 

I have probably an idea of what's happening. This is occuring in specific worlds, maybe old worlds. I will test with spigot API and come back to you.

Comment by md_5 [ 01/May/20 ]

Packets are not API; how can this bug be reproduced through the API or vanilla gameplay?

Generated at Sat Dec 13 15:19:29 UTC 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.