[Kde-games-devel] Behavior of game applications after being started.

Richard Hartmann richih.mailinglist at gmail.com
Mon Aug 11 14:31:00 CEST 2008


On Sat, Aug 9, 2008 at 16:02, Karl Ove Hufthammer
<Karl.Hufthammer at math.uib.no> wrote:

>> With other games, however, it is fine.  Is it fair for some timed games to
>> have a pre-start observation period?
>
> I think that could be considered cheating. And I guess KShisen hides the
> tiles when you press the 'Pause' button because of this.

I can not think of any game where this would not be cheating.And yes, that
is why those games hide the screen when you press pause.

I would even go as far as saying that all highscrores for timed games should
note if a game has been paused and how many times. Even if you don't
abuse ksnapshot, pausing gives you certain advantages, depending on
game type


> I guess in card games and similar games you could lay out the cards (so that
> the user could see the current layout) but not turn them over and start the
> timer before the user cliks on the 'Start game' button. But then again,
> KPat doesn't *use* a timer (and should not, either). :-)

Having a populated, but void, board would indeed be a nice idea.
I hate to 'waste' a game when I, for example, start a game, it creates a game,
I change a setting and it recreates said game. I feel morally obliged to solve
the game. Silly, I know :)
This is why I dislike all auto-starting of games, no matter if timed
or not. Your
suggestion is obvious in hindsight (most great ideas are), I love it! :)
Does not work for all game types, but with the ones it _does_ work with..


Richard


More information about the kde-games-devel mailing list