[MC1269] - does not detect items if they are worn or in offhand.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start at the player inventory sensor and trace how it checks inventory slots, using the ender pearl example to compare main-hand, offhand, worn, and regular inventory items. Done means the sensor detects qualifying items in offhand and worn slots as well as the existing inventory locations, with tests covering those cases if the project has applicable sensor tests.
Written by the indexing model from the issue text.
Description
CRAFTBOOK-3258 - Reported by Andy_S
any item that should be detected in inventory by player inventory sensor is ignored if it is worn (f.e. elytra) or held in offhand.
example with enderpearl, if kept in main hand or inventory, IC is triggered, if in offhand, IC is off
[MC1269]S
50
368
- Dominant language
- Java
- Stars
- 320
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from EngineHub/CraftBook
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
status:accepted type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in EngineHub/CraftBook
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days
-
area:cpan-port area:database bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fglock/PerlOnJava#1605 ·
Maintainers usually reply within 1 day
-
1.0.0-rc2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#377 ·
Maintainers usually reply within 1 day
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day