2. I strongly disagree with you on the other comment.
I write lots of plugins and changes to the game and unless I intend to, I should not break anything in the basic functionality of the game or engine - That's called a bug. Again, unless whoever wrote it explicitly stated that "X" will stop working when using the plugin. And I did actually check if it was written somewhere in the release notes.
I think you misunderstand what I said - there is nothing you can disagree
with :stickytongue:
Plugins cannot affect
anything in the editor, only in the running game - this is fact.
The various "test" buttons in the editor (for events and battle test) do
not do the full loading process of the plugin database - this is fact.
Therefore, some modifications via plugins will not work or be reflected properly when using the editor's test functionality. This is nothing to do with the plugin being written incorrectly, it's the way MV was built. It's unavoidable.
This is most commonly seen in the battle test, where effects loaded via plugin notetags may or may not work as expected, but it's true for any quick testing in the editor.
You're probably correct that it would be the most professional practice for the plugin authors to say "Using this may cause these buttons in the editor to not work as expected," but I think it's such a widespread issue that most of us are in the habit of not using those tests.