This entry collects useful information for packaging projects, that were created using the Study Framework Plugin.
# Should I package my project?
Generally - in the video game industry - packaging a UE-project is useful to protect assets and code, as well as making it more straightforward to launch the game for the end user. For most applications of the Study Framework Plugin this will probably be superfluous. When it comes to running projects locally for use with HMD, from our limited testing, we have not found a significant performance improvement from running a packaged project vs. from the UE editor. Also, even though everything _should_ work like in the editor, there usually are some issues one encounters in the packaged projects, that did not occur when running from the editor, and to test code changes, re-packaging is required... So unless you are planning to use the cave, it is probably not worth the extra effort to go through the packaging process. However:
**For using the cave, packaging is required**.
# Recommended Settings for Packaging
- In the project settings, make sure you set the **Game Default Map** to the map that contains the StudySetupActor.
-**Deselect "Use Pak File"**, that way the content directory is not converted to a .pak file. That way the game can still easily use separate files for config and data (like face-tracking .csv-files or .json-files for configs)
