Command /i dont work with all Items
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the /i command with the item names fire and portal, and compare them with item IDs 51 and 90. Trace the item lookup used by /i after the switch from IDs to names; done means the command works for these examples and the other affected items.
Written by the indexing model from the issue text.
Description
CMDBOOK-2430 - Reported by seema
Since the switch from Item ID's to Item Names the Command /i dont work with all Items.
Example: fire and portal / 51 and 90 (but there are more)
- Dominant language
- Java
- Stars
- 152
- Forks
- 104
- 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/CommandBook
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
EngineHub/CommandBook#294 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
EngineHub/CommandBook#285 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
EngineHub/CommandBook#283 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
EngineHub/CommandBook#282 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
EngineHub/CommandBook#280 ·
All issues in EngineHub/CommandBook
Similar issues
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100