scorrp10 Posted July 14 Share Posted July 14 The problem is likely a reserved alias. If one quest loads a reference into alias as "reserved", no other quest can load same reference into uts alias unless alias has "allow reserved" property. And a quest can't start if it can't load all of its aliases. So the solution would be to find which quest is holding on to that alias... Link to comment Share on other sites More sharing options...
Recommended Posts