Abort process when running mismatched official plugins
JustArchi opened this issue · comments
Checklist
- I read and understood ASF's Contributing guidelines
- I also read Setting-up and FAQ, I don't need help, this is an enhancement idea
- This is not a duplicate of an existing issue
- My idea doesn't duplicate existing ASF functionality described on the wiki
- I believe that my idea falls into ASF's scope and should be offered as part of ASF built-in functionality
- My idea doesn't violate the Steam Subscriber Agreement
- My idea doesn't violate the Steam Online Conduct
- This is not ASF-ui suggestion
Enhancement purpose
After my discussion with @xPaw - we should abort the process if plugins from mismatched ASF version are loaded into the process. People doing that usually have no clue what they're doing, and since we always distribute official plugins in matched versions, this should be regarded as unsupported practice.
I might make it configurable behind --ignore-unsupported-environment just in case.
Will not apply to unofficial plugins, although I'm considering a warning if ASF loads plugin X that targets ASF version older than current.
Solution
Why currently available solutions are not sufficient?
Can you help us with this enhancement idea?
Yes, I can code the solution myself and send a pull request
Additional info
No response