Skip to content

Feature Request: Enhanced mod details, loader detection, orphan/duplicate warnings, and AI-assisted contribution #2

Description

@TeaClearInkII

I've been using ModpackGraph and find it very helpful. However, I noticed a few areas where additional information and warnings could significantly improve the modpack troubleshooting experience. I'd like to propose several enhancements and, if the maintainer agrees, I'm willing to implement them with AI assistance – and I will carefully review and test all code before submitting a PR.

Proposed Features

  1. External link to mod homepages
  • Add clickable links (or a button) that redirect to the mod's official page on CurseForge, Modrinth, or GitHub, so users can quickly access detailed descriptions, changelogs, and support channels.
  1. Display mod loader (Forge/Fabric/NeoForge/etc.)
  • Clearly indicate which loader each mod supports, and optionally show the loader version compatibility.
  1. Warnings for incompatible version/loader combinations
  • Detect and highlight mods that are packaged for a different Minecraft version or a different loader than the current environment, to help users avoid common launch errors.
  1. Orphaned / no-longer-required dependencies
  • Identify dependencies that are no longer referenced by any active mod, suggesting they might be safely removed to declutter the modpack.
  1. Duplicate or overlapping functionality detection
  • Highlight cases where multiple mods provide similar features (e.g., two minimap mods), which may cause conflicts or performance issues.

Practicality Note
I understand that some of these features may be difficult to implement or not always feasible (e.g., duplicate detection requires heuristic rules). I'm open to discussing priorities and technical trade‑offs.

Commitment to AI‑assisted development
If you are open to external contributions, I would like to fork this repository and use AI tools to accelerate the development process. I assure you that I will:

  • Thoroughly review every piece of generated code for correctness and style.
  • Write appropriate tests and verify the changes in a local environment.
  • Keep the PR focused and documented.
  • Respond to any feedback promptly.

Please let me know your thoughts. I'm happy to adjust the scope or implementation approach based on your direction.

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