Release New unitypackage #795
Merged
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
RoyalCoder88
approved these changes
Apr 6, 2023
There was a problem hiding this comment.
Good job from @timbotimbo, covered every essential aspect for new users to know!
RoyalCoder88
approved these changes
Apr 11, 2023
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.
Description
As we've had a couple of bug fixes merged in to master recently, I think it is time for a new unitypackage.
This will prevent getting questions about issues that have already been fixed.
I propose the name
fuw-2022.2.0to match the current plugin version.Current changes:
/legacyto prevent any confusion.Personally I would like to merge #794 first and then create the unitypackage.
That will reduce the amount of newtonsoft issues in up-to-date unity versions.
Type of Change