A question about rating
Hello, people!This is my first pyweek and I have a doubt about rating:
I have python 2.4 , what will be the sensible thing to do for games that I cant run due to python 2.5 dependencies ?
1. Not rate
2. Rate as DNW, telling in the comment 'python 2.4 compatilibity problem'
I know it is not required 2.4 compatilibity.
Having an entry in this pyweek, I can feel a litle down seing the DNW count going up, but on the other side I prefer to know how much people have problems with my game, esp. if they can point out some concrete info.
comments ?
[ edited spelling only]
(log in to comment)
Comments
If so, then I vote for option #2.
HanClinto: That's true. However, I'd still like to see DNW reserved for those cases where the game actually doesn't work, as opposed to the rater simply not bothering to install dependencies. After all, there's no requirement that you rate every game.
I'm curious to know if people were frustrated by my game's install process, or if they merely didn't get time to play my game, since the two of those are very different things that have impact on me when I choose my development platform.
I'm interested in that feedback -- how would you like to see such feedback given? If someone said:
"The game has too many dependencies"Then that's valuable feedback that I really want to know. But then how would they rate it? If they gave me a 1 1 1, I'd be pissed if they didn't check the DNW box.
I'm fine with reserving the DNW box for errors with the game itself, but if so, then I want a viable alternative mechanism for getting dependency issues sent back to me.
--clint
I'm going to try again if I have time to get some of those things installed on Saturday.
I know the pain of seeing high% DNW all too well, but usually in my games it's because of weird OpenGL stuff.
I don't think I'll play your game because it uses pygame. Where do you draw the line?
More usually it is because the game uses a GL feature not all people have available, or do something funky, or just plain wrong.
Personally - if a game doesn't work for dependency issues - I just don't rate it. Simple.
Personally I think it is somewhat silly to spend time doing fancy OpenGL stuff for a one week contest - especially when you risk it not running on others' systems. But then again if it really looks good and you enjoy doing it :) Maybe try to provide settings for disabling it for those ppl whos hardware doesn't support it.
Yeah, my problems in previous contests have been largely self-inflicted :-(
Martin on 2008/09/16 12:34:
If you can't install Python 2.5 for some reason, I would say that your best bet is simply to not rate the game in question at all. Personally, I see DNW as being there to alert developers that their game doesn't work due to bugs, etc. Using it because you haven't installed the dependencies seems a little silly.
That said, it is always useful to know when dependencies are difficult to install, don't work on various systems, etc. I just don't see this as being the case with Python 2.5.