Event system for Unity based upon Ryan Hipple's implementation presented at Unite 2017
Scriptable Events is used through Unity's Package Manager. In order to use it you'll need to add the following lines to your Packages/manifest.json file. After that you'll be able to visually control what specific version of Scriptable Events you're using from the package manager window in Unity. This has to be done so your Unity editor can connect to NPM's package registry.
{
"scopedRegistries": [
{
"name": "NPM",
"url": "https://registry.npmjs.org",
"scopes": [
"com.bang"
]
}
],
"dependencies": {
"com.bang.scriptable-events": "1.0.0"
}
}Archives of specific versions and release notes are available on the releases page.
To access nightly builds of the develop branch that are package manager friendly, you'll need to manually edit your Packages/manifest.json as so.
{
"dependencies": {
"com.bang.scriptable-events": "https://github.com/TNThomas/bang-scriptable-events.git#nightly"
}
}Note that to get a newer nightly build you must delete this line and any related lock data in the manifest, let Unity rebuild, then add it back. As Unity locks the commit hash for Git urls as packages.
If you wish to run the development environment you'll need to install the Node.js version in the .nvmrc file. The easiest way to do this is install NVM and run nvm use.
Once you've installed Node.js, run the following from the root once.
npm install
If you wish to create a build run npm run build from the root and it will populate the dist folder.
All commits should be made using Commitizen (which is automatically installed when running npm install). Commits are automatically compiled to version numbers on release so this is very important. PRs that don't have Commitizen based commits will be rejected.
To make a commit type the following into a terminal from the root.
npm run commitPlease see the CONTRIBUTIONS.md file for full details on how to contribute to this project.
This project was generated with Oyster Package Generator.