I have suggestion to add an Outdated icon in the Network Library.
Why?
User scenario: I created a mod. After some time, the game updates to a new version, my mod runs with errors or even leads to a game crash. I don’t have time to fix it, but I can inform everyone about the mod's status by editing the repository file.
When a user opens the Network Library, he will see the new Outdated icon, which will be displayed based on certain conditions:
If the Outdated field in the Repository editor is empty, the user will only see "Outdated" on the icon.
If the field contains "After patch 6.01 the mod does not work properly" the user will see: "Outdated: After patch 6.01 the mod does not work properly."
As you can see i added few variants to Outdated icon
Here is look in Repository Editor
The character limit for the Outdated string is 100.
There is also a second part to the suggestion (not necessary)
In the Repository Editor, there can be an additional two fields (besides Outdated): "Game version from" and "Game version to"
If only the "Game version from" field is filled, it means the mod is not outdated (or the mod author has not yet realized that it is outdated). If the "Game version to" field is also filled, it means the mod will definitely work within those versions, but there are no guarantees it will work beyond that. So, if this version matches the current version, everything is fine. However, when it gets updated, there is no guarantee that it will work properly. Therefore, the second field should only be filled if the mod is truly outdated.
These game version fields can only be displayed in the Network Library tab.
At first, I thought it would be better if these fields "Game version from" and "Game version to" were in the Mod Editor, because the mod author tests versions and should specify them. But the thing is, he can only accurately specify the version for which he is currently developing the mod, and he cannot guarantee which version will work in the future since updates may come later, and the effects on the mod are unknown. Thus, the "Game version to" field should only be filled when the Outdated case has occurred and we know for certain that it no longer works later on. Therefore, when editing the repository, we can specify the versions from and to or just the Outdated status.
Why did I separate the logic of Outdated from the two fields?
Because there are game versions where previous versions simply cannot technically be played, as the game only progresses forward, and older versions cannot even connect to the servers. For example, games from Steam. Therefore, for such scenarios, it is better to inform the repository users that the mod is Outdated and briefly state what is wrong with the mod (whether it is a major or minor issue does not matter, the main point is to notify that the mod is not satisfactory for the latest version).
On the other hand, the feature with the fields "Game version from" and "Game version to" pertains to games that allow play in different versions. In most cases, these are single-player games, with patches that do not always satisfy the audience. The presence of such fields is almost unrelated to Outdated, except for instances where some parts of the game are updated again, and the mod indeed does not start.
I hope the translator managed well, and I was able to convey my thoughts. In my daily scenario, I only need the Outdated feature
I have suggestion to add an Outdated icon in the Network Library.
Why?
User scenario: I created a mod. After some time, the game updates to a new version, my mod runs with errors or even leads to a game crash. I don’t have time to fix it, but I can inform everyone about the mod's status by editing the repository file.
When a user opens the Network Library, he will see the new Outdated icon, which will be displayed based on certain conditions:
If the Outdated field in the Repository editor is empty, the user will only see "Outdated" on the icon.
If the field contains "After patch 6.01 the mod does not work properly" the user will see: "Outdated: After patch 6.01 the mod does not work properly."
As you can see i added few variants to Outdated icon
Here is look in Repository Editor
The character limit for the Outdated string is 100.
There is also a second part to the suggestion (not necessary)
In the Repository Editor, there can be an additional two fields (besides Outdated): "Game version from" and "Game version to"
If only the "Game version from" field is filled, it means the mod is not outdated (or the mod author has not yet realized that it is outdated). If the "Game version to" field is also filled, it means the mod will definitely work within those versions, but there are no guarantees it will work beyond that. So, if this version matches the current version, everything is fine. However, when it gets updated, there is no guarantee that it will work properly. Therefore, the second field should only be filled if the mod is truly outdated.
These game version fields can only be displayed in the Network Library tab.
At first, I thought it would be better if these fields "Game version from" and "Game version to" were in the Mod Editor, because the mod author tests versions and should specify them. But the thing is, he can only accurately specify the version for which he is currently developing the mod, and he cannot guarantee which version will work in the future since updates may come later, and the effects on the mod are unknown. Thus, the "Game version to" field should only be filled when the Outdated case has occurred and we know for certain that it no longer works later on. Therefore, when editing the repository, we can specify the versions from and to or just the Outdated status.
Why did I separate the logic of Outdated from the two fields?
Because there are game versions where previous versions simply cannot technically be played, as the game only progresses forward, and older versions cannot even connect to the servers. For example, games from Steam. Therefore, for such scenarios, it is better to inform the repository users that the mod is Outdated and briefly state what is wrong with the mod (whether it is a major or minor issue does not matter, the main point is to notify that the mod is not satisfactory for the latest version).
On the other hand, the feature with the fields "Game version from" and "Game version to" pertains to games that allow play in different versions. In most cases, these are single-player games, with patches that do not always satisfy the audience. The presence of such fields is almost unrelated to Outdated, except for instances where some parts of the game are updated again, and the mod indeed does not start.
I hope the translator managed well, and I was able to convey my thoughts.
In my daily scenario, I only need the Outdated feature