Smed

Any suggestion on the color change? We agree its a good idea, but we disagree on the color schemes, lol! Will probably make it user configurable later. The high score superimposition was my idea, I wanted it to look like the old stand-up arcade games. If you can tell us WHY the high scores aren't working for you we'd love to know, they work for us. Single script instance is definitely a great idea, one line fix, np, thanks. Nitpick? Not at all, we're glad to have all the feedback we can get, so when we call it "Finished", it truly will be.

another vote for zips

The maze was ultimately your inspiration, if you hadn't sent the images they probably wouldn't have happened. Thats why you got the extra 'thanks' line. Two more mazes are already in the code, but unused yet. Uncomment line 581 if you don't like the snake length not resetting between levels. That will be a start-up option next release. Need some feedback on how score is calculated.

That looks really nice, I can't wait to see it in action. As previously discussed, w0uter's point is simply insurmountable, however if a scripter knows they're going to do that then use an #include-all directive in the include file. my first concern would be: include file A requires function X from include file C include file B requires function Y from include file C does it catch that? I can't imagine that anybody is going to be using nested includes more than 10 levels deep, but then at one point in history someone assumed that a computer would never have more than a meg of ram. And here we are now. Slightly off topic, but since you're half-way there anyway... Back in the day (on VAX/VMS anyway, other platforms also I'm sure) there was a program called XREF that took source code and returned a reference of all function and variable usage information. Line numbers for declarations, calls, assignments, references. Extreemely useful for debugging large programs.

Playing? Never.. I spend more time Playing.. ups, I mean Testing, yeah, that it, Testing, than I spend coding, LOL. New release with gameplay options, levels, mazes available now! Thanks to Burrup for the maze images Thanks to everyone on the forum for general participation. Check it out, bug reports, enthusiastic praise, and other comments are welcome. snake_1.2.Au3

gafrost corrected for it, but he didn't point out that yours will return each possible value with a linear probability rather than the nice bell curve you expect from rolling multiple dice. I.e. if you roll 2, 6-sided dice, you are more likely to get a 7 than a 2 or a 12.

quick_sliver007 and I have been discussing how the next version of this should behave and we're not certain what the end user will want. We've agreed that starting game options are a good idea, and if things work out, there will be plenty. I like the snake speeding up every time it eats (thats in my copy, not the public release). I think you should level-up around the time you eat 50 food. But thats just me. So, we were wondering.. what would you want? There are so many choices.. more food per level, starting snake length based on level, starting speed based on level. Number of poisons placed per level (yes, thats definitely coming). Any other brilliant ideas? If anybody likes the game enough to have an opinion, we'd like to hear it.

I'm shocked that this topic hasn't had more replies. I read it, and thought, "I don't need it, but its cool." more than twice. I guess there aren't that many people used to programming in Perl here. I think its a great idea, but by the time I need it, I'll probably have already done it in another language.

You die whenever the snake tries to move over a position where it already is. If the cell phone version handles this differently, its that version thats wrong. Glad you're enjoying it, thanks for the feedback. EDIT: P.S. @Ejoc: I never played the DOS version, I remember this game from waaay back in the era of Black&White monitors, so I'd have to differ with your opinion on the "Classic" color scheme. I think last time I helped implement this game we used a '&' to represent the food, and I can't even remember what language it was in. I do remember that it was a 4 terminal 'Mini', but even the brand escapes me. Misspent youth, and all that...

Yeh.. all 5632 is pretty over the top. I've got 938. And I'm certain I haven't even played all of them. If anything though, this thread has brought to my attention it was time to upgrade... was running 0.55!

Congrats Layer, I noticed the (By Layer) tag in Dev thread earlier. Best I've done so far is point out a few Doc typos. Thats okay though, I still like seeing the (Thanks Smed) tags. They make me feel all warm and fuzzy inside.

Breakout..... Pong &#% it. I posted a paddle version in the old thread. Don't make me beg! LOL!

Pong. Pong. Pong. Looking forward to this too though.

That sucks... sounds like a job for... Opt("GUIOnEventMode", 1) Seriously.. set a Global flag for can/can't do this right now, OnEvent functions for the buttons that simply ignore the event and dump back when the flag tells them to.

Can't just disble the controls? I wanna move my mouse around and point at them while they're blinking... dammit. Helps me remember.

Very nice... I suppose the flying saucer skin would be too much to ask for! Running W2K here. Doesn't like the spaces in the path and in the file name. Not your problem, I'll have to narrow it down before I ask if its a bug. The "beeps" aren't distinctive enough. Its been too many years ago for me to remember what the old "hand-held" sounded like, but I was expecting more of a "bleep", "bloop", sorta noise rather than barely differentiable "bzzzt"s. But then it may sound differently here than it does there... dunno. Also, my mouse totally freezes while its doing its thing. May be unavoidable, but it is mildly annoying. Still, very nice. EDIT: The space issue was a problem with file type association, it may have been my own monkeying with it. fixed.

I'm all for, "I made a pot of tea and if you don't want any, you can go F*** yourself." But I have to agree that over usage of "Web Lingo" is just retarded. Quoting yourself as a good example doesn't help much. 1337 argument.

MsgBox will fire when $x is exactly 80, but I think you have the right idea now.

nope... test value is always the same as present value. If you need to know that its changed you must preserve the old value. The test you presented will always fail.

$num = 345 $pct = 80 $oldnum = $num ; Do some stuff that changes the value of $num If $num < $oldnum*$pct/100 Then ; Do something else EndIf Something like that? EDIT: added the phrase "that changes the value of $num"

nice...

It might be worth making a note of the maximum string length in the Remarks section in the Docs. Just a thought.

@Ejoc: If you could post your cell phone number and the 'restart instructions' for your computer this could be tested more thoroughly. I'm sure you'll post these in public for the greater good.

I swear, I tried really really hard to make only minimal code changes to what you had already written, and I failed misserably. Here's a version with a paddle. #Include<GUIConstants.au3> HotKeySet("^e", "myexit") $w = 9 $h = 9 $ph = 8 ;$bggui = GUICreate("ball", $w, $h, $w, $h, $WS_POPUP, $WS_EX_TOPMOST + $WS_EX_TOOLWINDOW + $WS_EX_CLIENTEDGE ) $bggui = GUICreate("ball", $w, $h, $w, $h, $WS_POPUP, $WS_EX_TOPMOST + $WS_EX_TOOLWINDOW) GuiSetState () GuiSetBKColor (0xFF0000, $bggui) ;$pg1gui = GUICreate("paddle", $w, $ph*$h, $w, @desktopheight - $ph*$h/2, $WS_POPUP, $WS_EX_TOPMOST + $WS_EX_TOOLWINDOW + $WS_EX_CLIENTEDGE ) $pg1gui = GUICreate("paddle", $w, $ph*$h, $w, @desktopheight - $ph*$h/2, $WS_POPUP, $WS_EX_TOPMOST + $WS_EX_TOOLWINDOW) GuiSetState () GuiSetBKColor (0x00FF00, $pg1gui) $width = @desktopwidth $height = @desktopheight - 30; taskbar should be sacrosanct $bDeltaX = 1 $bDeltaY = 1 While 1 $bpos = WinGetPos ("ball") $bX = $bpos[0] + $w/2 $bY = $bpos[1] + $h/2 $p1pos = MouseGetPos () $p1X = $p1pos[0] $p1Y = $p1pos[1] If $p1pos[1] > ($height - $ph*$h/2) Then $p1Y = $height - $ph*$h/2 ElseIf $p1pos[1] < $ph*$h/2 Then $p1Y = $ph*$h/2 EndIf WinMove ("paddle", "", $p1X - $w/2, $p1Y - $ph*$h/2) $bX = $bX + $bDeltaX $bY = $bY + $bDeltaY Select Case ($bX - $w/2) < 0 ; Ball hits Left Edge of Desktop MsgBox (0, "Point Scored!", "Right side scores a point") $bx = $width - $w $bDeltaX = -1 Case ($bX + $w/2) > $width ; Ball hits Right Edge of Desktop MsgBox (0, "Point Scored!", "Left Side scores a point") $bx = $w $bDeltaX = 1 Case (($bY - $h/2) < 0) Or (($bY + $h/2) > $height) ; Ball hits Top or Bottom $bDeltaY = -$bDeltaY Case (Abs ($bX - $p1X) < $w) And (Abs ($bY - $p1Y) < $h*$ph/2) ; Ball is too near paddle $bDeltaX = -$bDeltaX EndSelect WinMove ("ball", "", $bx - $w/2, $by - $h/2 ) Sleep(10) WEnd func myexit() Exit endfunc EDIT: new and improved paddle code now doesn't interfere with taskbar.

OMG! Pong! Or at least its evil twin Squash. How soon 'till we can start organizing the International NetPong Tournament? No sarcasm there... I wanna play!