Event-Based Block Tracking Issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by examining the current handling of BlockBreakEvent, EntityExplodeEvent, and similar events. Investigate whether a ChunkListener can detect block changes caused through alternative mechanisms without those events. Done means establishing a more reliable block-tracking approach, with its behavior verified against the stated limitations.
Written by the indexing model from the issue text.
Description
Using BlockBreakEvent, EntityExplodeEvent, and similar events may not be reliable, as some plugins can modify or break blocks through alternative mechanisms without triggering events like BlockBreakEvent.
It might be worth considering the use of a ChunkListener as a more robust solution :)
- Dominant language
- PHP
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RSS-Bridge/rss-bridge#5098 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
phingofficial/phing#2025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
silverstripe/developer-docs#911 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100