plugin load block after vam update

[cmramlow]

After finally updating to the latest version of vam I keep running into this block with plugins where, as an example, using everlaster's UX+ plugin I can't load plugins that aren't in vars and I have 100's of pre-var legacy plugins.

example error: .

Plugin inside a package everlaster.UXPlus.17:/Custom/Scripts/everlaster/UXPlus/UXPlus.cslist tried to load another plugin from outside of a package at path Custom\Scripts\-ALL-SCRIPTS-\BODY\AppearanceLoadeR\CharacterFusioner\src\MacGruber_Utils.cs which is no longer allowed

How to work around this please?

 

[hazmhox]

Contact the author of the plugin to fix it : )
There is no workaround a security fix sadly.

 

[cmramlow]

Hey hazmhox! Its impacting not just this plugin but every one that tries to load a plugin outside a var even via plugin presets and it sounds like by your response either you've not encountered this or I've got a unique/abnormal problem that no one else is experiencing? Thanks!

 

[hazmhox]

I work with both local and "packaged" version of scenes, none of them have ever triggered that since the update.

The thing is, old plugins might try to do things that are not allowed anymore. Do you have other examples than this one?

 

[cmramlow]

You were right @hazmhox this only occurs with everlaster's UX+ plugin and another one I frequently use. The only workaround is moving loose scripts into a var.