-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add useful-only-in-out-of-spec-scenarios plugins to the plugin restrictions #28
Comments
We can/should probably include some of the other common cases (or come to formal conclusion on them) that are pinned in discord too, copied with some minor edits for tone below. https://discord.com/channels/581875019861328007/685275026156683280/929071629550645248 Common suggestions that won't happen:
|
It might be worth mentioning versions that are rule compliant, because people will always go "well XYZ does (something similar but not quite)". Such as "Select Next Loot Item Tweak", it's not auto loot but it achieves a similar thing. |
Might also mention re-coloring aoe's due to the can of worms that opens. |
Is this not already covered? The precise wording in the docs is: (emphasis mine)
Unless there's something more direct that you're thinking of? e.g. a plugin that would be allowed if it weren't useful only in circumstances that were out of spec? |
The plugin submission that prompted this did not strictly break anything but was only useful if the player had already done something to reach that point. This is to improve those cases, as modification to the local client won't result in -more- invalid data, but we can't endorse the steps/tools needed to get to that point. We also have several instances of plugins that don't directly go against guildeines, but would still be rejected. (Parsing, Modding, Posing, etc plugins). It would be better to have those "won't pass even if fine" concepts documented outside of discord or suggestion channels. |
The current plugin guidelines don't explicitly disallow plugins that are only useful in out-of-spec (e.g. OOB, etc) scenarios. We should mention this and the reason why they're not allowed - a plugin that only works in service of illegal behaviour tacitly encourages said behaviour, which we can't support or discuss within this community.
The text was updated successfully, but these errors were encountered: