Commanditems+Playlist Glitches

Open
#946 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
game-dev

Research direction

Start by reproducing the command item consumption cases with duplicate item stacks, then create a second consuming command item and test playlist playback while checking the console error. Trace the command-item configuration and playlist loading paths. Done means stacked consumption works, existing quantities persist when new items are added, and playlists load without the duplicated .txt lookup.

Written by the indexing model from the issue text.

Description

CRAFTBOOK-3113 - Reported by BenButler77

Glitch #1: When an item is set to consume multiple of the same item, for example, Item A consumes 10 redstone. If you have 6 redstone in one stack and 64 in another, and try to use the command item, it will say "YOU MUST HAVE 10 REDSTONE TO USE THIS ITEM." Moving some of the redstone from the 64 stack to the stack that's closer to the left fixes this, but it's not easy to do in the middle of a fight.

Glitch #2: When a new command item is added, all other command items set to consume multiple of the same item revert to only consuming one. For example, Item A consumes REDSTONE*10. When I create Item B, Item A only consumes REDSTONE. So, every time I create a new item, I have to go through the config and fix every single item, which is becoming less and less plausible, since I have over 100 commanditems on my server.

Glitch #3: Playlists do not work, and instead play the first song specified then give a console error "Could not find [playlist].txt.txt

Dominant language
Java
Stars
320
Forks
165
Avg merge
6d 21h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EngineHub/CraftBook

All issues in EngineHub/CraftBook

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.