LotsOfPixelsStudios / LotsOfPixelsStudios/Monstera
Monstera creates a broken addon when the resSounds path is changed
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If the resSounds path is changed in the monestera.json all sound files are moved correctly to the given directory. However, the sounds definition file also moves there, which isn't allowed in the addon structure.
Also the paths in the sound definitions do not include the new paths and instead use the old paths as if there was no change.
Contributor 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.
Research direction
Start by tracing how the resSounds path from monestera.json is handled during addon generation. Check where the sound files and sound definition file are placed, and how paths in the sound definitions are built. Done means the definition file remains in the valid addon location and its paths use the changed resSounds directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100