Opened 11 years ago
Closed 11 years ago
#19 closed enhancement (wontfix)
Update Info
| Reported by: | Samer | Owned by: | Alloc |
|---|---|---|---|
| Priority: | minor | Component: | AEI2 |
| Keywords: | Cc: |
Description
If possible when an update for a mod is available to display a short message for what the update does .. example :
Dashing AI update available : fixes an important bug
Casey update : adds a new outfit for more info go here: with a link.
so users can asses the importance of the update as they might ignore something important even if the pack is non core like the dashing AI recent issue.
Change History (3)
comment:1 follow-up: ↓ 2 Changed 11 years ago by Iritscen
comment:2 in reply to: ↑ 1 Changed 11 years ago by Samer
Replying to Iritscen:
mm yes that could work however .. not all changes on the depot concern the file uploaded .. you may just be changing a word or adding a link to the description or something which will also mandate a revision, thus having something simple like that displayed to the user would be annoying .. if possible to only make it displayed when the actual file is changed then that would work. I also suggest simple sentences not entire changelogs to be displayed to the user, I think the forum should hold the detailed changelog for the mod itself .. another idea would be for it to only display a rating of the update available example : optional, adds new features, fixes a bug, crucial, highly recommended or the likes .. and that could be stored on the depot and displayed somehow.
like for example the dashing blur fix was crucial to avoid a crash however an update to some textures of a mod is optional .. just a way to make sure user knows if the update is important or not because some may just ignore it.
comment:3 Changed 11 years ago by Alloc
- Resolution set to wontfix
- Status changed from new to closed
People ignoring updates: Their own fault if something is not working then. That's what updates are for ;)
In general about this topic: As long as there's no way to store and fetch such information it can't be implemented. (E.g. Depot revisions can't be read out)
This sounds annoying to implement :-) Where would the changelog be stored? Although there is a simple solution -- make the revision comment field mandatory on the Depot (since nobody seems to be using it when it's optional, I'm thinking of doing this anyway), and (if possible) pull the text from there for the update message that we display to the user. Then we just have to train the modders to write proper, full sentences with the end user in mind.