UnofficialCrusaderPatch / UnofficialCrusaderPatch3

Development for the dll Injection approach
GNU General Public License v3.0
11 stars 2 forks source link

[AI_SWAPPER] Offer AI version update handling #68

Closed TheRedDaemon closed 8 months ago

TheRedDaemon commented 10 months ago

The way depends on how the version handling develops.

Krarilotus commented 9 months ago

The way to make version compatibility excessible woudl be to allow path-names with astericses in the versions. So it should probably support these in some form or another for changing file path names: Original-Pluginname- Original-Pluginname-X. Original-Pluginname-X.X.*

TheRedDaemon commented 9 months ago

@gynt I have actually no idea how to solve this:

Any ideas?

TheRedDaemon commented 9 months ago

There can only be one version of a plugin/module loaded at any time, right? If yes, if I could get the version of the currently active plugin in the backend, I might be able to construct the folder. The same counts for the GUI: If only one plugin version can be active, I do not need to care for the version of the plugin in the swapper, since it can only be one AI of the same name per plugin.

gynt commented 8 months ago

There can only be one version of a plugin/module loaded at any time, right? If yes, if I could get the version of the currently active plugin in the backend, I might be able to construct the folder. The same counts for the GUI: If only one plugin version can be active, I do not need to care for the version of the plugin in the swapper, since it can only be one AI of the same name per plugin.

Correct