Implement a masterlist

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on

#158 Change "out of date" icon to an up arrow

bitsquid_dt/dtmt

Reference: bitsquid_dt/dtmt#135

lucas commented

2023-11-15 01:17:39 +01:00

Owner

Certain features require (or at least would work better off of) a master list that can be edited out of sync of application releases. This includes

known issues
- split into warnings (has issues, but usable) and errors (unusable and/or will CTD)
  - broken after a patch
  - obsolete
- include a "critical" level, reserved for things like "actively malicious"
  - this is the only level that DTMM should actively block from being enabled for deployment
- accumulated indicators in the top bar for issues and warnings (similar to code editors)
- entries needs to be tied to a specific mod version
  - we could also fall back to import time when a mod doesn't have a version number. But that's prone to produce false positives, so for those it's probably better to rely on the masterlist being updated in a timely manner
  - we don't need to check game version, as Steam more or less guarantees the update
mod dependencies that the author fails to define
- or aren't defined with a dtmt.cfg
mod order by a priority value (e.g. LogMeIn at the very top) that can't easily be defined by a mod itself
Message Of The Day
notification about application updates

Other details:

Make sure to properly utilize HTTP cache headers
Are any of the above sections expected to grow substantially? If so, they should be split into a separate file. Mod order + dependencies would be a natural candidate to keep separate
Where to store the list? GitHub would be a candidate
- Should be accessible by multiple people -> permission system
- History tracking
Settings to turn off individual features? Maybe temporarily?
A way to manually update the list(s)

Certain features require (or at least would work better off of) a master list that can be edited out of sync of application releases. This includes - [ ] known issues - [ ] split into warnings (has issues, but usable) and errors (unusable and/or will CTD) - [ ] broken after a patch - [ ] obsolete - [ ] include a "critical" level, reserved for things like "actively malicious" - this is the only level that DTMM should actively block from being enabled for deployment - [ ] accumulated indicators in the top bar for issues and warnings (similar to code editors) - [ ] entries needs to be tied to a specific mod version - we could also fall back to import time when a mod doesn't have a version number. But that's prone to produce false positives, so for those it's probably better to rely on the masterlist being updated in a timely manner - we don't need to check game version, as Steam more or less guarantees the update - [ ] mod dependencies that the author fails to define - or aren't defined with a `dtmt.cfg` - [ ] mod order by a priority value (e.g. `LogMeIn` at the very top) that can't easily be defined by a mod itself - [ ] Message Of The Day - [ ] notification about application updates Other details: - [ ] Make sure to properly utilize HTTP cache headers - [ ] Are any of the above sections expected to grow substantially? If so, they should be split into a separate file. Mod order + dependencies would be a natural candidate to keep separate - [ ] Where to store the list? GitHub would be a candidate - Should be accessible by multiple people -> permission system - History tracking - [ ] Settings to turn off individual features? Maybe temporarily? - [ ] A way to manually update the list(s)

lucas added the

labels 2023-11-15 01:17:39 +01:00

lucas added this to the Mod Manager project 2023-11-15 01:17:39 +01:00

lucas pinned this 2023-11-24 14:19:47 +01:00

lucas added a new dependency 2023-12-04 13:29:09 +01:00

lucas referenced this issue

2023-12-04 13:30:18 +01:00

Message Of The Day #84

Rows
Columns

Implement a masterlist #135