With the 'no turning back' policy of releasing skill games, it's often hard to get everything perfect on the first try. Some things only come to light when you watch enough of other people's replays to see what you did wrong. Opportunities missed, sections that are less challenging than they should be, etc.
Obviously releasing a new version of your game every change you make will annoy everyone. What is the unofficial on re-releasing skill games?
Is there a naming convention?
Is there really no way to delete your older versions from the community?
Mark your own track as Offensive?
Just put a 'Revision #' in the title.
Marking your track as offensive won't do anything for you. A TC mod will have to view the track, see no offensive material, and restore the track to TC.
Testing a lot is the only way to ensure you don't end up with "FireBike - v2.4 alpha turbo".
The policy is to not do it. Test a lot before hand and make sure you get it perfect the first time. If you make a small mistake, just get over it and do not release a new version.
Originally Posted by ShiftySamurai![]()
This is the way to do it. With people busting out multi weapon dual stick shooters it's usually down to excitement over releasing a Skill Game as to why it was put out with issues.Originally Posted by buttcheekofdeth
Take your time and test. And test. Test.
Test.
Thats not true at all and I wouldn't even tolerate a small mistake. I test the **** out of all my games and stuff and I release....theres still mistakes. Its nearly impossible to not release a skill game with a mistake. All of mine I needed a second version, it sucks, but I'm not leaving a broken game up there.Originally Posted by buttcheekofdeth
Examples:
Record High - Broken medal times (because I didn't give 30 mins for each set and when plat was reached then going for more jumps in longer time, they got a gold instead) <- couldn't be known through hours of testing
Code Cracker - Didn't stop the randomize with 'A' so someone could hit 'A' first THEN 'y' to stop and would receive a different code. <- Didn't think about that until after was released
Half Pint - Reversed the primary and secondary scoring <- couldn't be known through hours of testing
So **** happens....not like you can think of everything in testing and see. This is also because of the problem we can't remove games. We don't know if something is broken until its released sometimes even with copious amounts of testing.
I don't think I've even touched a track that has V whatever at the end of it.
Make of that what you will![]()
Thats a shame if its one of my tracks because if theres a V2 theres a dam well good reason for it.Originally Posted by EuphoricFusion
Seeing a version number just makes me not want to download it for fear of there being successive versions after that.