Turn into package and delete playmaker integration #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi. Not sure if anyone still cares about this project, but I want to use it and I am making some changes in my fork. This PR restructures the files to conform to Unity's package conventions and adds assembly definitions and a
package.jsonto allow the code to be installed straight from GitHub using Unity's built-in package manager. I had to delete the Playmaker integration because that is a paid asset store package that cannot be installed using Unity's package manager. I think Visual Scripting (formerly Bolt) would be a better alternative these days, since that is now a free, official part of the Unity Engine.