search

xNVSE / NVSE

New Vegas Script Extender (NVSE)
https://git.io/JfSAo
702 stars 55 forks source link

Lot of incompatible plugins, yet still loads #174

Closed RedSnt closed 11 months ago

RedSnt commented 11 months ago

Just sharing my concerns, because I didn't used to get messages about incompatibilities in MO2 (v2.4.4) before, and now I am.
But everything still loads just fine, so just wanted to know what might've changed, because this happened as I upgraded from 6.2.7 to 6.3.4.

Should I be worried? I just updated all of these (even accidentally overwrote lSteveAl Tweaks INI sigh), and still getting notified about this, and I can see on the "last modified" date that NVSE.log is getting updated for each run, so it's not like MO2 is reading the wrong log.

image image nvse.log

WallSoGB commented 11 months ago

NVSE.log structure changed in 6.3.4 and MO2 doesn't know how to read it now, so it freaks out. Safe to ignore.

RedSnt commented 11 months ago

Thanks a bunch, was just worried for a second there. Now to keep going through lSteveAl Tweaks INI.. 😅

AnyOldName3 commented 10 months ago

It'll make it easier to change our parsing if you can link the relevant commit (or even make a PR yourselves if you're keen - the relevant plugin's pretty simple https://github.com/ModOrganizer2/modorganizer-script_extender_plugin_checker/blob/master/src/ScriptExtenderPluginChecker.py).

Either way, the attached log and screenshot don't seem to match as it has to pull the reported as incompatible during query string out of the relevant line to print it. If the regex didn't match after the change, it wouldn't recognise it as a line mentioning a plugin and would ignore it, and if it matched but incorrectly, it'd spit out most of what it matched more-or-less verbatim, but there's no path for it to make up a reason for a plugin to fail, and last I checked, nothing caching the message from a past run.