New update this week, broke Proximity Compass. Broke it last week too, but I was too busy to work on it, so I waited. Here's the output from the console:
Code:js/rmmz_managers.js:2030 TypeError: Cannot read property 'note' of null
at Game_Event.<computed> [as setupProximityCompassNotetags] (js/plugins/VisuMZ_4_ProximityCompass.js:584)
at Game_Event.<computed>.setupProximityCompassEffects (js/plugins/VisuMZ_4_ProximityCompass.js:584)
at Game_Event.refresh (js/plugins/VisuMZ_4_ProximityCompass.js:584)
at Game_Map.<computed>.<computed> [as isSpawnHitboxCollisionOk] (js/plugins/VisuMZ_1_EventsMoveCore.js:6254)
at Game_Map.<computed> [as prepareSpawnedEventAtRegion] (js/plugins/VisuMZ_1_EventsMoveCore.js:6254)
at Game_Interpreter.<anonymous> (js/plugins/VisuMZ_1_EventsMoveCore.js:6254)
at Function.PluginManager.callCommand (js/rmmz_managers.js:3105)
at Game_Interpreter.command357 (js/rmmz_objects.js:11274)
at Game_Interpreter.<computed> (js/plugins/VisuMZ_0_CoreEngine.js:6363)
at Game_Interpreter.<computed>.<computed> (js/plugins/VisuMZ_1_EventsMoveCore.js:6254)
If I turn off proximity compass, the problem goes away. I was going to submit a proper bug report, but I am using so many different Visustella plugins, that recreating the issue in a blank project could take a significant amount of work. I'll try to do that when I have a chance.
Here are my thoughts on the matter:
I have lots of different kinds of events.
Some use COMMENT tags to specify compass icons and range.
Most do not.
Some Events are created by Events Move Core when the map loads.
My suspicion is that it has to do with events created by events move core.
If I startup on a map where events ARE created, I get the error above.
If I startup on a map where events ARE NOT created, I do not get the error and things seem to work as they should.
It looks like spawned events are not being handle properly in the notetag parsing code. Just a guess.