Be more agressive with virtual components when compacting
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 887
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
Right now, compaction entirely ignores virtual components -- but this tends to produce overly bulky components when combined with MiniMessage's gradient/rainbow functionality. We can probably cull more layers of nesting in there, but that's too finnicky of a change to sneak in before release.
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
Start by tracing the compaction logic and its handling of virtual components, then examine how MiniMessage's gradient and rainbow functionality produces nested components. The work is done when compaction reduces the bulky nesting described in the issue without introducing unintended changes; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100