After trying the evaluation version for a couple weeks, I just purchased the full version of Quest Machine! Unfortunately though, all my code that was referencing it is showing "are you missing a using directive or an assembly reference?" error messages.
Specifically, the way I upgraded was:
1. Deleted all Quest Machine files (everything in "Assets/Editor Default Resources", "Assets/Gizmos", and "Assets/Plugins/Pixel Crushers").
2. Imported Quest Machine via Window > Package Manager > My Assets
I'm guessing this is related to us using assembly definitions. We have three: one at Assets/Scripts/Scripts.asmdef, one at Assets/Tests/EditTests/EditTests.asmdef, and one at Assets/Tests/PlayTests/PlayTests.asmdef.
I tried going to one of these assembly definitions and adding an entry in the "Assembly Definition References" section, but it doesn't look like there are any Quest-Machine-related references available to add. Is there something I need to do to generate one, or am I going about this all wrong?
Missing assembly reference after upgrading from evaluation version
Re: Missing assembly reference after upgrading from evaluation version
Hi,
Thanks for buying Quest Machine!
Import this unitypackage, which should already be in your project:
Plugins / Pixel Crushers / Quest Machine / Scripts / QuestMachineAssemblyDefinitions.unitypackage
(Since not every dev uses asmdefs, they're tucked away in a package.)
In your asmdefs, add references to the PixelCrushers and QuestMachine asmdefs.
Thanks for buying Quest Machine!
Import this unitypackage, which should already be in your project:
Plugins / Pixel Crushers / Quest Machine / Scripts / QuestMachineAssemblyDefinitions.unitypackage
(Since not every dev uses asmdefs, they're tucked away in a package.)
In your asmdefs, add references to the PixelCrushers and QuestMachine asmdefs.
Re: Missing assembly reference after upgrading from evaluation version
Thanks Tony, that did the trick! Appreciate you pointing it out