You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Justin Wiblin dab527bb13
Registry Registration (#32)
1 year ago
DependencyGraph Level Music (#8) 1 year ago
InfernalGameFramework Registry Registration (#32) 1 year ago
InfernalGameFramework.Library Registry Registration (#32) 1 year ago
InfernalGameFramework.Library.Tests General Cleanup and Improvements (#31) 1 year ago
PocoWithID Registry Registration (#32) 1 year ago
.gitignore Update .gitignore (#12) 1 year ago
InfernalGameFramework.sln Rename GameTest to Infernal-Game-Framework (#11) 1 year ago
Jenkinsfile Rename GameTest to Infernal-Game-Framework (#11) 1 year ago
LICENSE.md Initial commit 2 years ago
README.md Rename GameTest to Infernal-Game-Framework (#11) 1 year ago
publish.ps1 Append branch name on non-main builds (#25) 1 year ago
publish.sh Append branch name on non-main builds (#25) 1 year ago

README.md

Infernal Game Framework

Jenkins

Downloads

Bleeding Edge

You can download the latest build of the main branch from our build server

Releases

The latest full release is found at on the release page

Building from Source

Requires the .net 6 SDK to build

Once installed you can build and run.

To build run either the publish.ps1 or publish.sh script depending the platform you are building on. You can specify which platforms you wish to build for by passing one or more of: win-x64, osx-x64, linux-x64, or portable as arguments to the script, if you dont sepcify any platforms it will build for all. This will createa Zip file for each platform as well as a publish folder, with a sub-folder for each platform.

Contributing

We use and encourages Early Pull Requests. Please don't wait until you're done to open a PR!

  1. Fork
  2. Add an empty commit to a new branch to start your work off: git commit --allow-empty -m "start of [thing you're working on]"
  3. Once you've pushed a commit, open a WIP: pull request. Do this before you actually start working.
  4. Make your commits in small, incremental steps with clear descriptions.
  5. Tag a maintainer when you're done and ask for a review!