ZFGC
Projects => Other Projects => Topic started by: mit on April 01, 2006, 07:16:24 pm
-
I made my own version of Minesweeper in PHP! Now you can play minesweeper in the comfort of your own browser and with less features than the Windows one! Ontop of that, my algorithm for the cascading effect is unbelieveably memory consuming for the server, and may or may not run out of memory. Wanna play?
(http://www.kousougames.co.uk/Spritezors/thumb/features/t_minesweeper.jpg)
http://www.kousougames.co.uk/Minesweeper (http://www.kousougames.co.uk/Minesweeper)
If I ever have the effort, I may make an online highscore thingy so that this actually has an advantage over the windows one. But for now, it really doesn't.
-
Pretty neat. Cool job!
-
Cool, maybe you should limit the max size :P that might help with how much memory it uses?
-
I don't get it.
I clicked on the squares, and nothing happened. I right clicked on them...and nothing happened. How does this work?
-
Hmm, should work. What browser do you have? The buttons are only form thingies.
-
I'm using IE 6.0.
-
Hmm... interesting... what size board did you set it to? Test it at 10, with 10 mines, and if that doesn't work I don't know. My algorythm sucks, and so very large boards crash it...
-
Okay, it works now, it just takes like 2 seconds to load after each click XD
-
Sorry to bump, but I wanted everyone to know that now I've added that highscore table I promised: http://www.kousougames.co.uk/Minesweeper/?act=highscore
See if you can beat me ;D
-
You should write it in JS, cause then your server won't crash and you'll learn JS, lol. That's what I did >_>.
-
The only reason this crashes is because my method of clearing many blank squares is terrible. In the windows one, it adds each ajacent blank square into a queue, and then goes through each one doing the same thing again. Mine has a funciton that sets the squares around it to visible if they're empty and calls itself on them if they have no value (the value of the number of close mines, precalucalted at the start). This method is very lazy and slow, causing the sever not to crash, but to exceed the amount of memory allowed for this script to use. You can change this limit, but I'm not going to.