To avoid a lot of confusion on new people it's a must to have Examples that are good up to date. It's very strange when you try and you see all kinds of warnings ,, that's not a good example. CannonGameExample.cs is a good example of that.
Date
Votes
1 comment
-
Aurrie Lynne I do agree, example scripts need to be retested and revised with each release. I have released no scripts publically, that I have been working on, since each release either breaks it, or renders the method I chose to use , less desirable.
This is BETA so I expect to keeping code working and improving will be a challenge. I am chasing a rabbit of new script features...keep on running Rabbit I want more.... I have yet to release any code publically I am working on until I feel it is likely (no code will ever be update proof) to be stable long enough. I DO think enough features have settled down that I am using , so I am close to making them available soon. But once done, I too will have a testing cycle with each release as well...
The code side of using a BETA where we have limited access or internal knowledge is a big effort , especially if you do not want to break someone 's experience all the time and you want write efficient and effective reusable code.
Please sign in to leave a comment.