GlowstoneMC / GlowstoneMC/Glowstone
Ability to send block changes from chunks not in view
- Dominant language
- Java
- Stars
- 2k
- Forks
- 280
- PR merge metrics
- No merged PRs in 30d
Description
Currently when a `sendBlockChange` or a `send#Change` method in GlowPlayer is called, action will only occur if the chunk is visible to the client at that current time.
It would be nice if you could send a block change in a chunk the client doesn't know about, for it to optionally be stored in memory and when their known chunks update, for it to send the block change if it belongs to that chunk.
I could work on this when I have free time if this is an approved idea.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/46325033-ability-to-send-block-changes-from-chunks-not-in-view?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14691067&utm_medium=issues&utm_source=github).
Contributor guide
Research direction
Start by locating GlowPlayer and its sendBlockChange/send#Change methods, then trace how visible or known chunks are determined and updated. The issue is complete when an optionally retained block change for an unknown chunk is sent once that chunk becomes known; no file or test is named, so the relevant coverage will need to be found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100