-
awesome-unity-open-source-on-github
A categorized collection of awesome Unity open source on GitHub (800+)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Unity-Style-Guide
This article contains ideas for setting up a projects structure and naming convention for scripts and assets in Unity
-
FizzBuzz Enterprise Edition
FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
https://github.com/baba-s/awesome-unity-open-source-on-github#Trello
Well, the "classes are kind of everywhere" statement was directed toward the project structure. It seems like the files are all just scattered around in the _Scripts folder. Could be hard to work with when you start working at a larger scale. Check out this styleguide to get an impression on how a good structure would look like.
So I would tidy up and make your variable names consistent, add line breaks, comments, remove the init methods and use Awake, Start properly. Remove the build files from the repo and add to the gitignore - if you are unsure use gitignore/Unity.gitignore at master ยท github/gitignore
Lol, reminds me of Enterprise FizzBuzz.