Skip to content
This repository has been archived by the owner on Dec 10, 2020. It is now read-only.

Latest commit

 

History

History
58 lines (49 loc) · 2.55 KB

ROADMAP.md

File metadata and controls

58 lines (49 loc) · 2.55 KB

Roadmap/Planned

Should probably use a project board. Don't actually have a roadmap here.

UI

  • Menu Bar (94%)

    • Quick Tools(83%)
      • Open Minecraft Launcher(66%)
      • Open MultiMC Launcher(100%)
    • Language Selection (100%)
    • Check for Updates (100%)

  • Mod Library Manager (50%)

    • Drag and Drop Fabric Mods (100%)
    • Enable/Disable Fabric Mods (100%)
    • Eliminate Fabric Mods (100%)
      • Can Eliminate (100%)
      • Confirmation Menu(100%)
    • Open Mods Folder (100%)
    • Refresh Directory Mods (100%)
    • Mod Info redirect to Mod Repository Browser via specific title/author or minecraft version
    • Single Mod Updater (5%)
      • Use ModUpdater(10%)
      • Use Existing Repository(0%)
    • Mod Pack Manager (0%)
      • Custom Modpacks Profiles (0%)
      • Mod Pack Updater (0%)
    • Search Bar (0%)

  • Mod Repository Browser (60%)

    • Search by title/author or minecraft version (100%)
    • Minecraft and Mod Versions Selection (100%)
    • Download/Install to specific profile or Downloads Manager (25%)
    • Build via GitHub Repository (no promises and bandwidth intensive)

  • Downloads Manager (0%)

    • Install to specific profile or keep in the cache (0%)
    • Asynchronous downloader (100%) using jddl

  • Settings (0%)

    • Change Custom Minecraft Directory (0%)
    • Change MultiMC Directory(100%)
    • Add/Remove Custom Repositories (0%)
      • Direct JSON DB (5%)
      • API (75%) using CurseForge API

API (Future, missing resources to provide this. This is necessary for huge repositories)

This will be most likely written in NodeJS.

  • Mod Repository API (5%)

    • Schematics (75%)
    • Query via GraphQL (no promises)

  • Mod Repository Local API (10%) meant for Fabric Mod Repository.

Database

This will be most likely split into 2. Using GitHub as repository which will make the application memory intensive. Using MongoDB as an actual database and query using the API. How do I plan to populate these? Well no idea.

  • Mod Repository using Fabric Mod Repository. I will be keeping this for testing might keep it as an update strategy.
  • Curse Forge API. NOTE: This will only allow projects that are opted in.