Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ProjectSettings not needed? #1

Open
AvinZarlez opened this issue Mar 10, 2016 · 1 comment
Open

ProjectSettings not needed? #1

AvinZarlez opened this issue Mar 10, 2016 · 1 comment

Comments

@AvinZarlez
Copy link
Contributor

Since the point is to just copy the Captain's Mess files into your own Unity project, shouldn't the files in ProjectSettings not be tracked/included as part of the Git repo?
@hengineer
Copy link
Owner

Yes you're right. I'll remove it in the next update. If you know any best practices for organizing Unity extensions please let me know. When development is further along I'll make an official Unity asset package for the Asset Store.

hengineer pushed a commit that referenced this issue May 28, 2016
Merge pull request #1 from hengineer/master
418c7eb 
Pulling latest changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hengineer @AvinZarlez