[SPIGOT-1240] Setting max-bulk-chunks to 1 causes unusual lighting behavior in End Created: 18/Oct/15  Updated: 20/Dec/15  Resolved: 21/Oct/15

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

Type: Bug Priority: Minor
Reporter: VanDerProtofsky Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: 1.8, 1.8.8, spigot, world


 Description   

Summary

If max-bulk-chunks in Spigot.yml is set to 1, lighting updates seem not to be communicated between client and server if:

Reproduction

1. Setup a fresh Spigot 1.8.8 instance with creative gamemode
2. In `Spigot.yml`, set max-bulk-chunks to 1 under world-settings -> default: sections
3. Create an end portal to get to the end
4. Execute /tp 0 80 0 (within a seven chunk radius of End origin) and place a torch nearby. Observe that it lights up surrounding blocks as normal.
5. Fly out far enough to go beyond a seven chunk radius of the End's origin. Place torches nearby. Observe that it only lights up the block it is placed on.

Testing

The above reproduction was tested on:

  • Live server: git-Spigot-5f38d38-12698ea, 27 plugins - reproducable
  • Local server: git-Spigot-5f38d38-18fbb24, no plugins - reproducable

Workaround

Disconnect and reconnect, or unload the chunks by flying out of view distance or teleporting out of the world. Lighting will then correctly transmit upon loading the chunks.

Footnotes

  • This bug was discovered by a player on my server
  • We tried reducing our max-bulk-chunks value to 1 to try and alleviate teleport lag for some of our players with poor connections. It seemed to work, aside from this bug. We have since increased it to 2 which has introduced the teleport lag again but prevents this bug from happening.


 Comments   
Comment by Alecta [ 20/Dec/15 ]

Does anybody know where to find this setting? ;~; I don't own the server I keep getting kicked from so I'm wondering if I can actually do anything to fix this myself. Is it a problem with my setting or the server's setting? And where is the setting?

Comment by VanDerProtofsky [ 21/Oct/15 ]

Understood; thank you for responding

Comment by md_5 [ 21/Oct/15 ]

Don't set it to 1.
This feature is removed in 1.9 anyway.

Generated at Sat Dec 13 11:53:31 UTC 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.