Skip to content

Roadmap/backlog triage: priority & difficulty of open PRs, issues and roadmap items #16

Closed as not planned

Description

@Berkayprof

Sharing a triage pass over the current open PRs, issues, and the README roadmap, so we have a shared view of what to tackle next.

Item Type Priority Difficulty Notes
Crash at startup — Resource not found: lang\en_US.yml (#5) Bug Critical Easy Plugin fails to enable entirely on affected builds. Root cause looks like a Windows-style backslash path slipping into ResourceUtil when listing jar entries.
Internal Exception w/ DecoderException (#3) Bug High Hard Breaks opening/creating changelogs on Purpur, likely Geyser/Bedrock-related. Blocked on missing logs.
Store player first-seen timestamps (#13) PR / Roadmap High Easy Implements the roadmap's "Player first-join storage". Code + tests already written.
Add read-all button to changelog dialog (#12) PR Medium Easy Small, self-contained, ready to merge.
Public API for other plugins (#9) Feature request Medium–High Hard High ecosystem value, needs real API design/versioning/docs.
Legacy color code support &1-&9, &f, &r, &l (#1) Feature request Medium Easy–Medium Adventure ships a legacy serializer; mostly wiring work.
Add a title to changelogs (#2) Feature request Medium Medium Needs data-model + storage migration + UI changes.
Paged changelogs (Roadmap) Roadmap Medium Medium Not urgent yet, but needed as history grows.
JDBC/relational DB support (Roadmap) Roadmap Medium Hard New storage abstraction + YAML migration.
Customizable dialog layout (Roadmap) Roadmap Low–Medium Medium New config + rendering logic.
"pre kotlin fixies :3" (#11) PR / Infra Low Medium Build/version-catalog cleanup, no direct user-facing value, risk of conflicts with other PRs.
Pre-defined authors (Roadmap) Roadmap Low Easy Just a config-driven list plus a selection step in the editor dialog.
Other UI types (Roadmap) Roadmap Low Medium–Hard Separate rendering path per UI type.
Poll/voting system (Roadmap) Roadmap Low Hard New data model, UI, vote aggregation.

Methodology: priority = user impact (crashes > core UX > nice-to-haves); difficulty = how much is already built vs. how much new design/architecture is needed.


Activity

  1. codingcat2468 commented on Sep 27, 2026

    @codingcat2468
    Owner

    I see the idea, but I am very much aware of what needs to be done next regarding the project.
    I'd also appreciate not receiving fully AI-generated issues/PRs on this project, or at least with them being marked as such in the future.

  2. Berkayprof commented on Sep 27, 2026

    @Berkayprof
    Author

    Hi Codingcat, Human here (trust me bro, lol), Im very sorry for not mentioning the use of AI in my issue, and will take this as feedback for the future, I do know that you are probably aware, but for other users wanting to contribute to the project, I thought it'd be an good idea to summerise stuff a bit, tho as much as I wanna help, Im also lazy, so sorry for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions