Forum rules - please read before posting.
Transferring Logic
In a blunder of version control, I've realised I've been mistakenly working on an old version of my project. What is the best way to transfer AC game logic (including actionlists, triggers etc) from one project to another, without losing references and action list data?
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
Welcome to the official forum for Adventure Creator.
Comments
Not easily. How many lists are we talking about?
If copying over scenes completely isn't an option, I'd say you'd want to look into converting your scene-based ActionLists into asset files (via the cog menu in their components). You can then move these asset files into the other project, and then (optionally) convert them back into Cutscenes.
First, though, you'll need to make sure that Manager data matches up - e.g. Variables, Inventory etc. Actions refer to these via ID values - so a Variable: Check Action, for example, will break if the new project doesn't have the same variable with the same ID.
When converting ActionLists to asset files, references to scene objects will also then be made via Constant ID number. The conversion process assigns such IDs to objects if missing, but you'd need to ensure the same IDs are assigned in the new scenes. This aspect may be more trouble than its worth - it may be better in the long run to just convert to asset, transfer to the new project, convert back to Cutscene, and then manually re-assign objects one-by-one.