devilpepper/ggj-template

https://drive.google.com/file/d/1KY0DeRcLiFhUxAdW_TOSkyTHmHRnuxSH/view

Unity Template for Global Game Jam

This project template follows the tutorials from GameCI using the simple example (one platform) and a Personal License. The releases are in the format required to make GGJ submissions. Namely, the zip contains:

• Source files moved from PROJECTNAME/ to src/
• Build in release/
• press/ & other/ directories
• License is CC0

How to use

1. Fork this repo
2. Rename GGJ-Game/ to the name of your game (no spaces)
3. Change PROJECT_NAME from "GGJ-Game" to the same name you gave the folder
4. Optionally, edit the target branch if you use anything other than master as your default branch (I guess main)

TODO: Explore OpenUPM

Activate License

You also need to activate a Unity license once to use the build/release job. Go to Github > <Your repository> > Actions > Acquire activation file (One time per repo) and run this workflow. Once it's done, follow these steps:

Copied from https://game.ci/docs/github/activation

• Download the manual activation file that now appeared as an artifact.
• Visit license.unity3d.com and upload it.
• You should now receive your license file (Unity_v20XX.x.ulf) as a download.
• Open Github > <Your repository> > Settings > Secrets.
• Create a secret called UNITY_LICENSE and copy the contents your license file into it.

press directory

You'll want to push at least 1 screenshot to the press/ directory. Use press/Videos.md to link to videos uploaded somewhere.

other directory

Push other required licenses to the other/ directory and use other/Credits.md to list team members and optionally contact info.

Limitations

1. To use GameCI for Unity version > 2019.2, this template uses GameCI actions that are still in alpha. This is probably why Test and Build steps build a new Docker image every time...
2. Test step takes forever even with 0 tests! So it's commented out. This is probably due to it downloading assets, which should probably be done in a previous step.
3. Due to the long duration of the main workflow you probably don't want to run this in PR, so it only runs on push/merge to master.