I have a simple game with three scenes. Movement through the scenes is via Application.LoadLevel(…). I have all three scenes added to my build settings. I want to create a package so that others can open my game and see how it works (for a tutorial). However when I export the entire game as a package and then import it into a new Project it doesn’t work because none of the scenes are in the Build Settings (in the new project). Rather than explaining to someone who uses my package how they need to set it up, is there any way to actually export the Build Settings as part of the package so that explanation is not required, ie so they can use it ‘as is’?
You can use this Unity - Scripting API: ExportPackageOptions.IncludeLibraryAssets to export Build Settings together with your assets.
How do I execute that statement? Do I put it into a script, attach to a GO and play the game? Or is there some other way to execute a script without playing the game? Or command line? Just a bit confused at this point
For anyone interested I received a different solution in Unity Answers. Don’t export as Unity package, rather enable visible meta files in the Editor settings, delete the Library and save as a zip file. Then Extract at the destination. Worked well when I tested it.
1 Like
Not really a useful answer.