You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The v. 2.5.2 (and potentially other versions) doesn't inform users to update their third party plugins, like v. 2.5.0 did. This is even more important on other release platforms, like Nexus. V. 2.5.2 required additional updates, compared to v. 2.5.0. This results in many questions from technically inexperienced users (and some experienced ones as well), because they're not aware that they need an update and think they did something wrong on their end, which isn't the case at all.
To Reproduce:
Create a basic game plugin in v. 2.4.4, as instructed, copying code from native basic game plugins in v. 2.4.4.
Add the plugin and create an instance for that game.
Close MO2.
Update the basic game plugin to Qt 6 (only change, as this is the only thing that one can figure out with trial and error in v. 2.5.0).
Update MO2 to v. 2.5.2.
Run MO 2.5.2.
Environment:
Mod Organizer Version that exhibits the issue: v. 2.5.2
Last Mod Organizer Version that did not exhibit the issue (if applicable): v. 2.5.0
Desktop OS/version used to run Mod Organizer: Windows 11 64bit
Details:
Here are the messages for the plugin, written in v. 2.4.4, updated in v. 2.5.0, attempted to use in v. 2.5.2:
The first message is targeted at plugin creators, but users don't understand anything. The second message isn't applicable.
The result: Users aren't aware that they need an update. They think they did something wrong on their end.
Additionally, basic_game went through changes that required updating game plugins, but didn't inform plugin creators or users about the change, they had to read that through the error message.
Notes:
I asked for guidance on Discord, without proper response (to this day). (As a normal message that was responded to, it is bound to get lost, so I decided to open this issue.)
Please don't handle this issue as a don't know how to update basic_game plugins. Read the issue carefully, please, and kindly respond here or on Discord, how you plan to resolve that issue (or not).
The problem:
The v. 2.5.2 (and potentially other versions) doesn't inform users to update their third party plugins, like v. 2.5.0 did. This is even more important on other release platforms, like Nexus. V. 2.5.2 required additional updates, compared to v. 2.5.0. This results in many questions from technically inexperienced users (and some experienced ones as well), because they're not aware that they need an update and think they did something wrong on their end, which isn't the case at all.
To Reproduce:
Environment:
Details:
Here are the messages for the plugin, written in v. 2.4.4, updated in v. 2.5.0, attempted to use in v. 2.5.2:
The first message is targeted at plugin creators, but users don't understand anything. The second message isn't applicable.
The result: Users aren't aware that they need an update. They think they did something wrong on their end.
Additionally, basic_game went through changes that required updating game plugins, but didn't inform plugin creators or users about the change, they had to read that through the error message.
Notes:
Link to Mod Organizer logs:
USVFS:
https://gist.github.com/ak2yny/331635acb4259b60e24729a26f94378a#file-usvfs-2024-08-16_05-43-49-log
MO Interface:
https://gist.github.com/ak2yny/331635acb4259b60e24729a26f94378a#file-mo_interface-log
The text was updated successfully, but these errors were encountered: