I just tested this out in MV for simple run (as my base turn rect to
x,y,w,h) as it seems to work in MV.
however, I do find that the popup window is larger and the text
is cut off on the 3rd line, not a smaller window (each parameter
is kept default).
but its a nice plugin to find the issue, so pressing F8/F12 can give
the list (2 errors made, throw 7 warnings, each missing ">".
so can confirm it works in MV if they use my SDJB_Base without issue ^^
at least on my end though =)
[Free Plugin] CT_NotetagGuardian - Notetag Validator & Warning Helper (RPG Maker MZ Plugin) » Comments
Thank you so much for testing it in MV and sharing the info! Really appreciate it. 🙏
NotetagGuardian was originally made for RPG Maker MZ only, mainly because I don’t currently have MV, so I don’t have a proper way to test and support it there. 😂
But this is very useful to know — especially that it seems to work on your end with SDJB_Base, and also the note about the popup window being too large / text getting cut off on the 3rd line.
For now, I’ll still list it as an MZ plugin officially, but your testing helps a lot for MV users who may want to try it carefully on their own setup.
Thanks again for taking the time to test and report this!
it needs my full MV SDJB_Base version.
I don't mind the 3rd line as its more targetting the plugin commands
to use which does not work in MV.
without my base, no pop is going up => but console log still shows
the error logs as well + error on pluginCommands not defined.
but that that doesn't bother.
so you can put in the helpfile it does work in MV when opening
the console log (for MV users that use my full SDJB_Base => pop shows).
but only the last line is irrelevant for MV users anyway :)
so its still useful without my base, but have to open the console.log.
and it works as smoothly as well without the popup.
I may use it or run it just in case I made an oversight, but also a small feedback.
while "<blabla: 44" throw an error or <<blabla> because of 1 <.
how does it handle if notetags has <<something>> to allow <= and =>
operators?
or use <something\> as closing tag?
unless you can define something that in the parameter to the white list.
Thank you again for the extra testing and explanation! This is really useful. 🙏
That makes sense — since it depends on your full SDJB_Base setup, I’ll add a note in the help file that in MV the plugin can still be useful through the console log, and that the popup behavior may depend on the user’s setup.
I’ll still keep NotetagGuardian officially listed as an MZ plugin for now, since MZ is the version I can properly test and support, but your MV testing is very helpful for anyone who wants to try it there.
Good catch on the < / > edge cases too. Since the plugin checks for malformed angle-bracket style notetags, cases like <=, =>, or custom tag formats can create false positives. I’ll look into adding an ignore/whitelist option so users can allow valid custom syntax from their own plugins.
For something like <something!> as a closing/custom tag, I think it’s safer not to assume it is valid by default unless the user defines it as allowed syntax, because different plugins may use different notetag formats.
Really appreciate you testing this so deeply — this is exactly the kind of edge case feedback that helps improve the tool. 😄