Visual Scripting Errors
Solved
Hi guys,
Looks like the last update completely broke all visual scripts. Get this error upon loading even a blank script that does nothing.
MOD PARTIALLY SKIPPED, LOADED ONLY 1/6 PHASES, Following Error occured:
Object reference not set to an instance of an object.
Sandbox.Game
at Sandbox.Definitions.MyDefinitionManager.LoadDefinitions(List`1 contexts, List`1 definitionSets, Boolean failOnDebug, Boolean isPreload)
I have the same bug You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
After further testing doesn't appear to be affecting all scripts.
This VS mod though still causes the error: -
https://steamcommunity.com/sharedfiles/filedetails/?id=1431620589
So does a blank script with just the 4 nodes in it.
After further testing doesn't appear to be affecting all scripts.
This VS mod though still causes the error: -
https://steamcommunity.com/sharedfiles/filedetails/?id=1431620589
So does a blank script with just the 4 nodes in it.
Managed to track down why one works and the other doesn't.
Looks like the error happens if the mod doesn't have a 'Data' folder. Simple creation of the folder makes everything work fine even if the scripts arent in it and its completely empty *shrugs*
Managed to track down why one works and the other doesn't.
Looks like the error happens if the mod doesn't have a 'Data' folder. Simple creation of the folder makes everything work fine even if the scripts arent in it and its completely empty *shrugs*
So discovered it worked fine locally only to find workshop version didn't. I have to actually include cubeblocks.sbc, handitems.sbc etc etc. So yep, relative pathing must be broken again.
So discovered it worked fine locally only to find workshop version didn't. I have to actually include cubeblocks.sbc, handitems.sbc etc etc. So yep, relative pathing must be broken again.
I played around with this issue in dnSpy and found that the error occurs because one of the sub-lists is null and it can't be foreach'd.
Simply adding a nullcheck for `list[k]` before that foreach will prevent these errors and whatever hidden damage they might do to other mods.
I played around with this issue in dnSpy and found that the error occurs because one of the sub-lists is null and it can't be foreach'd.
Simply adding a nullcheck for `list[k]` before that foreach will prevent these errors and whatever hidden damage they might do to other mods.
it looks that Keen have re-introduced this bug again
sometimes i just wonder where the hell is their QA and testing
it looks that Keen have re-introduced this bug again
sometimes i just wonder where the hell is their QA and testing
Replies have been locked on this page!