Botan626
Botan626
maybe updating logic from @Rudokhvist will help you to solve this https://github.com/CatPoweredPlugins/CommandAliasPlugin/blob/main/CommandAliasPlugin/CommandAliasPlugin.cs
> I have no clue why ASFE provides a zip asset per language though 🙂 So having only single ASFEnhance.zip archive in [ASFE releases](https://github.com/chr233/ASFEnhance/releases) would fix it?
> plugin can force itself to be updated to the same version at any time it wants I'm pretty sure @chr233 never intended this.
> since new ASF version could decide to use different asset And if the asset ASF decided to update to is the same as current one? In this case ASFE...
Now ASFE updates to v2.2.4.2. 2024-10-07 22:13:33|ArchiSteamFarm-1|INFO|ASF|GetTargetReleaseURL() Found ASFEnhance plugin update from version 2.2.4.0 to 2.2.4.2... 2024-10-07 22:18:17|ArchiSteamFarm-1|INFO|ASF|UpdatePlugin() Updating ASFEnhance plugin... but after restart it's v2.2.4.0 again 2024-10-07 22:18:30|ArchiSteamFarm-1|INFO|ASF|GetTargetReleaseURL() Found...
> just for testing github action, no need to upgrade this release I know it's was for testing, but still it had to update to v2.2.4.2 if I'm correct, since...
Another thing is `PV` command output.  this line `Current version: 2.2.5.0 New version: 2.2.4.0` could be like `Installed version: 2.2.5.0 Stable version: 2.2.4.0` in order to differentiate between pre-release...
> Do you know when this supposed change was made? no > I don't remember seeing a corresponding commit. most likely it wasn't made on purpose, and is a bug...
Not only config options are not sorted alphabetically, they shuffle after each ASF restart and subsequent ui page reload. Before restart:  After:  It makes it even harder to...