It is now maintained at InfectedBytes/gj-unity-api.
Game Jolt Game API wrapper for Unity.
Check out the documentation.
Released under MIT.
Keeping /CHANGELOG.md
up to date as new features are added make the release of new versions much simpler.
In addition, it gives a clear indication on what has been added/fixed/etc but not released yet.
The documentation is generated with Doxygen and can be used via the GUI or the CLI.
The configuration file can be found at /Documentation/Doxyfile
. Unfortunately the paths are absolute and will depend on the developer machine.
To update the documentation, run make doc_generate
. To preview it, run make doc_serve
and visit http://localhost:8000/
. Finally, to publish the documentation, commit
the changes to master
and push
to origin
, then run make doc_publish
to copy the Documentation/Output/html
subdirectory to the gh-pages
branch so the documentation will be available at loicteixeira.github.io/gj-unity-api/.
- Update the version number following Semantic Versioning.
VERSION
in/Assets/Plugins/GameJolt/Scripts/API/Constants.cs
.PROJECT_NUMBER
in/Documentation/Doxyfile
.
- Update
CHANGELOG.md
.- Convert the
Unreleased
section to the new version number, following the formatting of the previous versions. - Make sure to create the corresponding link at the bottom of the file
- Make sure to update the
unreleased
link as well to it compare from the new version.
- Convert the
- Commit the changes with the message
Release vX.Y.Z
. - Push the changes to the remote. See the 2.2.0 release as an example.
- Create the corresponding tag with
git tag vX.Y.Z
. - Push the tag to the remote with
git push --tags
- In the
Project
view, select thePlugins
folder. - Right-click and choose
Assets > Export Package...
. - Uncheck
include dependencies
. - Click
Export
. - Save as
GameJoltUnityAPI_X.Y.Z.unitypackage
in a folder which isn't tracked by git.
- GitHub
- Go to
Code > Releases
. - Click
Draft a new Release
. - In
tag
andversion
, use the name of the tag created earlier. It should bevX.Y.Z
. - Copy the changes from the changelog in the body (formatting can stay the same)
- Attach the newly created package.
- Click
Publish release
- Go to
- GameJolt
- Go to
Dashboard > Your Games > Unity API > Manage
. - Select
Packages
. - Find
Unity API v2
and clickManage
. - Click
New Release
. - Set the version number.
- Attach the build as a
Downloadable Build
. - Select
Other
for theplatform
. - Publish.
- Create a news in the
Devlog
so the developers following the project are notified.
- Go to
- Unity Asset Store