summaryrefslogtreecommitdiff
path: root/apps/settings_list.c
diff options
context:
space:
mode:
authorFrank Gevaerts <frank@gevaerts.be>2011-11-15 23:44:56 +0000
committerFrank Gevaerts <frank@gevaerts.be>2011-11-15 23:44:56 +0000
commitb7508a766df991539bec5e10fd7739001c1fdb99 (patch)
tree31f77d4f20dec11934cce165c9340cc03367b2a2 /apps/settings_list.c
parent3607d88aa0371b047464b98690fead9c9b88b1e3 (diff)
downloadrockbox-b7508a766df991539bec5e10fd7739001c1fdb99.tar.gz
rockbox-b7508a766df991539bec5e10fd7739001c1fdb99.zip
Don't put mines adjacent to the starting position instead of just not *on* the
starting position. (FS#12387 by Ophir Lojkine) Since in minesweeper one needs information about at least two positions to deduce anything (unless the first position has no adjacent mines at all), having mines adjacent to the starting position means the player has to guess without any information, which is no different than having a chance that the first position already has a mine. I don't think minesweeper is meant to be a game of pure luck. git-svn-id: svn://svn.rockbox.org/rockbox/trunk@30994 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'apps/settings_list.c')
0 files changed, 0 insertions, 0 deletions