1. #11

    Re: Re-releasing skill games... what's the policy?

    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.
    I agree with this. If I see Version 2, I naturally assume it will be followed by a Version 3.

    If you want to fix issues, I would suggest making a full-on sequel with the fixes. Give us a better reason to download the game again -- new visuals, new obstacles, new experience. If the game logic you worked so hard on was worth the time to create and to fix, why not spend a little more time and offer some actual new content along with the fix?
    Share this post

  2. #12

    Re: Re-releasing skill games... what's the policy?

    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.

    Yea, this is a very valid point. I don't think I've downloaded any versioned tracks or games. For the record I spent probably 20 hours testing my skill game, even had people over to help me beta, but the bottom line is everyone plays differently and some of that just isn't apparent until you watch a hundred different people try it.

    Anyway, I guess I won't be releasing another version. Thanks for the tips, community!
    Share this post

  3. #13

    Re: Re-releasing skill games... what's the policy?

    As far as testing goes, you really need to go over the track many times AFTER you believe it is perfect. Go in with the intention of breaking the track. Do everything you can think of that is "wrong" to see if it makes a difference. The more you stray from the concept of a simple trials track, the more testing you need to do.

    I'm working on a track now that has a complicated twist that has added HOURS worth of extra testing. I've been testing bailing out at almost every conceivable point, multiple CP resets, reversing from different locations, multiple approaches to ramps, etc. And this isn't even a skill game.
    Share this post

  4. #14

    Re: Re-releasing skill games... what's the policy?

    I do wish there was a better way to test these in terms of releases such as sharing them with only your friends as a sort of beta. Community releases are just so final.
    Share this post

  5. #15

    Re: Re-releasing skill games... what's the policy?

    the simple answer would be for redlynx to add a remove option for builders.
    Share this post

  6. #16

    Re: Re-releasing skill games... what's the policy?

    I suspect they don't have this because that would destroy all the top times on that track... imagine how annoying it would be if you got the #1 spot and the creator deleted the track and re-released it...
    Share this post

  7. #17

    Re: Re-releasing skill games... what's the policy?

    Originally Posted by maxxrafen
    I do wish there was a better way to test these in terms of releases such as sharing them with only your friends as a sort of beta. Community releases are just so final.
    You can test unreleased tracks with your friends. That does help.
    Share this post

  8. #18

    Re: Re-releasing skill games... what's the policy?

    Online?
    Share this post

  9. #19

    Re: Re-releasing skill games... what's the policy?

    Originally Posted by maxxrafen
    Online?
    Yep, start a custom match and invite friends. When you're adding maps scroll to the right and there's a 'saved games' section. I think it's a problem this isn't more common knowledge, not that I blame anyone because it's not very obvious.
    Share this post

  10. #20

    Re: Re-releasing skill games... what's the policy?

    Online private testing is for tracks only and not skill games unfortunately.

    I think the best way to look at it is how annoyed people get when a game is released and things don't work properly and then you need to wait for a patch.
    As gamers this is one of the most annoying things so when it comes to bugs in tracks it is just as irritating.
    Moral is you can NEVER test too much. When you think it's done, it probably isn't.
    Share this post