config file instead of resourcepack
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
It's very annoying to be required to create a whole resource pack just to change some widgets
I think it would be preferable to simply have a config file
the only pro I see for having it as a resource pack is the fact that you can quickly change between configs
This could also be done via a Config screen where you see all created widgets and be able to activate and deactivate them. This would be even more flexible than a resource pack
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.
Research direction
No files, tests, or entry points are named. Start by locating the resource-pack and widget configuration handling, then compare the proposed config file and Config screen approaches; done means users can change widgets without creating a resource pack and can switch configurations as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100