3D Tunnel Lines Demonstration

[bplus]

Hi Ken,

MOD is the remainder part of a division of two integers:
1/3 = 0 R 1 so 1 MOD 3 = 1
2/3 = 0 R 2 so 2 MOD 3 = 2
3/3 = 1 R 0 so 3 MOD 3 = 0  another way of saying 3 divides 3 exactly, like 3 divides 6, 3 divides 9, 3 divides 12...
4/3 = 1 R 1 so 4 MOD 3 = 1
5/3 = 1 R 2 so 5 MOD 3 = 2, the remainder of m/n is always between 0 and n-1, you can never have a remainder >= n which comes in really handy for allot things in computer programming.

n MOD m
+ it always keeps numbers between 0 and m-1
+ you can test if something divides evenly, if  a mod b = 0,  b divides a as 6 mod 3 = 0 because 3 divides 6
+ toggle = (toggle + 1) MOD 2 always keeps toggle at 0 or 1

offset is just an add on, say you want a box every 10 pixels, but you want to start with a margin of 5 from edge the the x offset is 5:  boxX(i) = i * 10 + xOffset

[SierraKen]

Very cool, thanks B+. I've also been wondering about how I used to use XOR with PUT to make graphics put on top of other graphics and the rest remains, without having to draw it again. Might be something for me to look into if it's still online somewhere.

[bplus]

Very cool, thanks B+. I've also been wondering about how I used to use XOR with PUT to make graphics put on top of other graphics and the rest remains, without having to draw it again. Might be something for me to look into if it's still online somewhere.

I don't know if XOR is used that much unless manipulating bits, you're talking numbers in binary format.

Let's stick to elements this thread brings up. I would spend my time learning _PUTIMAGE over the old way of PUT.

We could practice with the monster image. Can you set up an area to draw the monster using _NEWIMAGE, draw the monster there with the data statements (then you don't need an array to store the colors nor have to redraw from array, just use _PUTIMAGE). This is when you learn _SOURCE and _DEST, specially _DEST for telling QB where images are coming from (_SOURCE) and are to go (_DEST) that's what _PUTIMAGE needs the most.

'set up Monster area to draw it and store image under the handle monster&  << notice type long

Code: QB64: [Select]

1. monster& = _NEWIMAGE(12, 12, 32) 'the monster is 13 x 13 which is 0 to 12 X 0 to 12
2. _DEST monster&  '<<< drawing commands will now go to monster& area
3. FOR my = 0 TO 12 'draw monster in monster& image area
4.     FOR mx = 0 TO 12
5.         READ cl
6.         pset (mx, my), _RGB32(cl * 60, 0, 0)
7.     NEXT mx
8. NEXT my
9. 'we now have a monster image stored under the handle monster&
10. _DEST 0 ' back to the screen

Use _PUTIMAGE to show monster. Here is the "monster" Swiss army knife of _PUTIMAGE command:
' _PUTIMAGE [STEP] [(dx1, dy1)-[STEP][(dx2, dy2)]][, sourceHandle&][, destHandle&][, ][STEP][(sx1, sy1)[-STEP][(sx2, sy2)]]

 dx, dy controls where on screen for top, left corner, bottom right corner, the monster image will stretch or shrink to fit there dx, dy coordinates you specify. d stand for destination which is main screen for our monster&
(dx1, dy1) is top left corner
(dx2, dy2) is bottom left corner
with these you can control how big or small to show the monster on main screen.

Source handle is monster&
Destination handle is 0 for default screen

sx, sy controls what parts to show from source image, we are using whole image so those options remain blank

This code replace load array colors of monster and _PUTIMAGE replaces the GOSUB showMonster:

Still need:
monsterdata:
DATA 0,0,0,4,4,4,4,4,4,4,0,0,0
DATA 0,0,4,4,4,4,4,4,4,4,4,0,0
DATA 0,4,4,4,4,4,4,4,4,4,4,0,0
DATA 0,4,4,4,4,4,4,4,4,4,4,0,0
DATA 4,4,4,1,1,4,4,1,1,4,4,4,0
DATA 4,4,4,4,4,4,4,4,4,4,4,4,0
DATA 4,4,4,4,4,4,1,4,4,4,4,4,0
DATA 4,4,4,4,4,1,1,4,4,4,4,4,0
DATA 0,4,4,4,4,4,4,4,4,4,0,0,0
DATA 0,0,4,4,1,1,1,1,4,4,0,0,0
DATA 0,0,4,4,4,4,4,4,4,4,0,0,0
DATA 0,0,4,4,4,4,4,4,4,4,0,0,0
DATA 0,0,4,4,4,4,4,4,4,0,0,0,0

[bplus]

And this is what I worked out for ShowMonster

Code: QB64: [Select]

1. showMonster:
2. 'PUTIMAGE [STEP] [(dx1, dy1)-[STEP][(dx2, dy2)]][, sourceHandle&][, destHandle&]
3. _PUTIMAGE (300 - ms * 10, 300 - ms * 10)-(300 + ms * 10, 300 + ms * 10), monsterh&, 0
4. RETURN
5.  

[SMcNeill]

Bplus:  PUT (as the graphical command), was the old school way to store images in an array buffer and place them onto the screen, and XOR was one of the options available to draw (and remove) those images.  The wiki has a description of the PUT options here:  https://www.qb64.org/wiki/PUT_(graphics_statement)

[bplus]

Bplus:  PUT (as the graphical command), was the old school way to store images in an array buffer and place them onto the screen, and XOR was one of the options available to draw (and remove) those images.  The wiki has a description of the PUT options here:  https://www.qb64.org/wiki/PUT_(graphics_statement)

Yes, I did call PUT the "old way", but Steve wouldn't you advise learning new way with _PUTIMAGE, it's so much better!

This works great for resizing demon image:

Code: QB64: [Select]

1. OPTION _EXPLICIT
2. 'Made by Ken G. on July 11, 2019
3. 'Thank you to B+ for his example on QB64.org forum!
4. '2019-07-13 Bplus update with using image techniques
5. _TITLE "Ken's Tunnel - Use Up and Down Arrow Keys" 'mod B+ 2019-07-12
6. SCREEN _NEWIMAGE(600, 600, 32)
7. DIM offset, my, mx, cl, s, sz, a$, monster, ms, monsterh&
8.  
9. 'get monster image stored under monsterh&
10. monsterh& = _NEWIMAGE(12, 12, 32) 'the monster is 13 x 13 which is 0 to 12 X 0 to 12
11. _DEST monsterh& '<<< drawing commands will now go to monster& area
12. FOR my = 0 TO 12 'draw monster in monster& image area
13.     FOR mx = 0 TO 12
14.         READ cl
15.         PSET (mx, my), _RGB32(cl * 60, cl * 60, cl * 60)
16.     NEXT mx
17. NEXT my
18. 'we now have a monster image stored under the handle monster&
19. _DEST 0 ' back to the screen
20.  
21. offset = 600000 'track if we are coming or going
22.  
23. DO 'go:  DO... LOOP indents main loop and makes it easier to read
24.     CLS
25.  
26.     'handle tunnel
27.     offset = offset + s
28.     IF offset = 0 THEN offset = 300000
29.     IF offset = 600001 THEN offset = 300000
30.     FOR sz = 0 TO 300
31.         IF (sz + offset) MOD 40 THEN
32.             LINE (300 - sz, 300 - sz)-(300 + sz, 300 + sz), _RGB32(0, sz / 2, 0), B
33.         ELSE
34.             LINE (300 - sz, 300 - sz)-(300 + sz, 300 + sz), _RGB32(255 * sz / 300, 255 * sz / 300, 255 * sz / 300), B
35.         END IF
36.     NEXT sz
37.  
38.     'handle keys
39.     a$ = INKEY$
40.     IF a$ = CHR$(27) THEN END
41.     IF a$ = CHR$(0) + CHR$(72) THEN s = s - 1: IF s < -5 THEN s = -5
42.     IF a$ = CHR$(0) + CHR$(80) THEN s = s + 1: IF s > 5 THEN s = 5
43.  
44.     'handle monster
45.     monster = monster - 1
46.     IF s > 0 THEN ms = ms - .05
47.     IF s < 0 THEN ms = ms + .05
48.     IF ms > 5 THEN ms = 5
49.     IF ms < 0 THEN ms = 0
50.     IF monster <= 0 THEN monster = RND * 500 ELSE GOSUB showMonster
51.  
52.     _DISPLAY
53.     _LIMIT 60
54. LOOP 'goto go
55.  
56. showMonster:
57. 'PUTIMAGE [STEP] [(dx1, dy1)-[STEP][(dx2, dy2)]][, sourceHandle&][, destHandle&]
58. _PUTIMAGE (300 - ms * 10, 300 - ms * 10)-(300 + ms * 10, 300 + ms * 10), monsterh&, 0
59. RETURN
60.  
61. monsterdata:
62. DATA 0,0,0,4,4,4,4,4,4,4,0,0,0
63. DATA 0,0,4,4,4,4,4,4,4,4,4,0,0
64. DATA 0,0,4,4,4,4,4,4,4,4,4,4,0
65. DATA 0,4,4,4,4,4,4,4,4,4,4,4,0
66. DATA 0,4,4,1,1,1,4,4,1,1,1,4,4
67. DATA 0,4,4,1,1,1,4,4,1,1,1,4,4
68. DATA 0,4,4,2,2,2,4,4,2,2,2,4,4
69. DATA 0,4,4,4,4,4,1,1,4,4,4,4,4
70. DATA 0,0,4,4,4,4,4,4,4,4,4,4,0
71. DATA 0,0,4,4,4,1,1,1,1,4,4,0,0
72. DATA 0,0,0,4,4,4,4,4,4,4,4,0,0
73. DATA 0,0,0,4,4,4,4,4,4,4,0,0,0
74. DATA 0,0,0,4,4,4,4,4,4,4,0,0,0
75.  

PS I was screwing around with image data...

[SMcNeill]

Aye.  I’d definitely promote _PUTIMAGE over PUT.  I was mainly just responding to your statement here:

I don't know if XOR is used that much unless manipulating bits, you're talking numbers in binary format.

It’s not used much nowadays, but you’ll see it in old QBasic programs to do as Ken suggested — drawing on top of various backgrounds.  ;)

[SierraKen]

Thanks guys, but B+ you are doing too much. I pretty much took off on my original code, but I am using your monster. I tried to put your code in mine but it didn't work for some reason and I couldn't figure it out. Here is where I am so far, but unless I ask for certain help on something, there's no need to try to help me with it. I use the Wiki pages a lot and today I learned how to use JPG pictures for doors on the side. For a few days I've just been using boxes for doors on the side but my own JPG pictures look much better. :) I will also do that for monsters too, etc. I'm not certain yet if I will keep that sprite monster, it was pretty much only for testing. Also, I really don't have a plan yet on my game, I just add something when I come up with something. But if you are curious, here is my code so far, but as of right now I don't need anything. I appreciate all the help you have given though. I just don't want you to take off in one direction and me the other. Also, personally, it feels best when I know exactly what all my code does. Back in the 90's I used to toss other people's code in my programs and most of the time I had no idea what it did. I'm a slow learner. lol But of course, feel free to always have suggestions, thanks. Oh, and right now the doors are just for looks, you can't enter them yet, but soon I hope to be able to. The door pictures are attached to this post. Oh also, I removed the way to back up so people just use the up arrow key now to go forward. There wouldn't be much of a need to back up. If I get really good and want people to turn around, they can use the arrow keys. I'm thinking to open the doors, people can just press the O or D keys, but that will be in the _TITLE so people know first.

(Note: There is a much better version below on this forum page.)

Code: QB64: [Select]

1. OPTION _EXPLICIT
2. 'Made by Ken G.
3. 'Thank you to B+ for his example on QB64.org forum!
4. 'Other files needed for this game: doorl.jpg, doorr.jpg
5.  
6. _TITLE "Ken's Tunnel - Use Up Arrow Key To Move"
7.  
8. begin:
9. DIM segment(100)
10. DIM my, mx, cl, s, sz, a$, monster, ms, x, y, t, sz2, seg2, length, rt, tu, doorr, doorl, os, m, mon
11.  
12. SCREEN _NEWIMAGE(600, 600, 32)
13. x = 300: y = 300: t = 50
14. s = 10
15. sz2 = 10
16. seg2 = 1
17. 'Load tunnel into memory.
18. RANDOMIZE TIMER
19. length = INT(RND * 60) + 30
20. tunnel:
21. RANDOMIZE TIMER
22. rt = INT(RND * 100) + 1
23. tu = tu + 1
24. IF rt < 25 THEN
25.     segment(tu) = 1 'Right Door
26. END IF
27. IF rt >= 25 AND rt < 50 THEN
28.     segment(tu) = 2 'Left Door
29. END IF
30. IF rt >= 50 THEN
31.     segment(tu) = 3 'No Door
32. END IF
33. IF tu = length THEN GOTO starttunnel:
34. GOTO tunnel:
35.  
36. starttunnel:
37. FOR sz = s TO 300
38.     LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 2, sz / 2, sz / 2), B
39. NEXT sz
40.  
41.  
42.  
43. doorl = _LOADIMAGE("doorl.jpg", 32)
44. doorr = _LOADIMAGE("doorr.jpg", 32)
45.  
46. go:
47.  
48. a$ = INKEY$
49. IF a$ = CHR$(27) THEN END
50. IF a$ = CHR$(0) + CHR$(72) THEN
51.     os = s
52.     s = s + 5
53.     IF s < 10 THEN s = 300: seg2 = seg2 - 1
54.     IF s > 300 THEN s = 10: seg2 = seg2 + 1
55.     t = t + 10
56.     IF t > 255 THEN t = 20
57.  
58.     sz2 = sz2 + 1
59.     IF sz2 < 10 THEN sz2 = 300
60.     IF sz2 > 300 THEN sz2 = 10
61.     IF m = 0 THEN
62.         RANDOMIZE TIMER
63.         monster = INT(RND * 500) + 1
64.         IF monster > 498 THEN
65.             m = 1
66.             GOSUB monster:
67.         END IF
68.     END IF
69.     IF m = 1 THEN
70.         mon = mon + 1
71.         IF mon > 50 THEN
72.             LINE (290, 284)-(316, 316), _RGB32(0, 0, 0), BF
73.             m = 0
74.             mon = 0
75.         END IF
76.     END IF
77. END IF
78. IF segment(seg2) = 1 THEN 'Right Door
79.  
80.     _PUTIMAGE (x + 50 + s, y - s - 50)-(x + 70 + s * 1.5, y + s + 50), doorr
81.     FOR sz = s + 50 TO 10 STEP -1
82.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 2, sz / 2, sz / 2), B
83.     NEXT sz
84. END IF
85.  
86. IF segment(seg2) = 2 THEN 'Left Door
87.     _PUTIMAGE (x - 70 - s * 1.5, y - s - 50)-(x - 50 - s, y + s + 50), doorl
88.  
89.     FOR sz = s + 50 TO 10 STEP -1
90.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 2, sz / 2, sz / 2), B
91.     NEXT sz
92. END IF
93.  
94. IF segment(seg2) = 3 THEN 'No Door
95.     LINE (x - s, y - s)-(x + s, y + s), _RGB32(127, 255, 127), B
96.     FOR sz = s - 1 TO 10 STEP -1
97.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 2, sz / 2, sz / 2), B
98.     NEXT sz
99. END IF
100.  
101. IF segment(seg2) = 0 THEN
102.     LOCATE 30, 30: PRINT "You Beat The Tunnel!"
103.     LOCATE 35, 30: INPUT "Press enter to end.", a$
104.     END
105. END IF
106.  
107.  
108.  
109. GOTO go:
110.  
111. monster:
112. RESTORE monsterdata:
113. FOR my = 1 TO 13
114.     FOR mx = 1 TO 13
115.         READ cl
116.         PSET (mx + 290, my + 290), _RGB32(0, cl * 100, 0)
117.     NEXT mx
118. NEXT my
119. RETURN
120.  
121. RETURN
122.  
123.  
124.  
125. monsterdata:
126. DATA 0,0,0,4,4,4,4,4,4,4,0,0,0
127. DATA 0,0,4,4,4,4,4,4,4,4,4,0,0
128. DATA 0,4,4,4,4,4,4,4,4,4,4,0,0
129. DATA 0,4,4,4,4,4,4,4,4,4,4,0,0
130. DATA 4,4,4,1,1,4,4,1,1,4,4,4,0
131. DATA 4,4,4,4,4,4,4,4,4,4,4,4,0
132. DATA 4,4,4,4,4,4,1,4,4,4,4,4,0
133. DATA 4,4,4,4,4,1,1,4,4,4,4,4,0
134. DATA 0,4,4,4,4,4,4,4,4,4,0,0,0
135. DATA 0,0,4,4,1,1,1,1,4,4,0,0,0
136. DATA 0,0,4,4,4,4,4,4,4,4,0,0,0
137. DATA 0,0,4,4,4,4,4,4,4,4,0,0,0
138. DATA 0,0,4,4,4,4,4,4,4,0,0,0,0
139.  
140.  

[SierraKen]

I'm back at working with this game. This morning I was able to add the ability to go through the doors :). It doesn't show the doors opening or anything but you use the left and right arrow keys to go to a different tunnel by going through them when you see them. The tunnels also change colors as you go through the doors so you know you are in a different tunnel. I think I'm going to make this into a little 3d shooter game of some kind. Maybe have the monster shoot at you or something. Or shooter / RPG dungeon game. Now that I got the doors out of the way, I can add pretty much anything! :))

[SierraKen]

I finished the game! It's self explanatory on the front page. Tell me what you think everyone :).
You also have to use the 2 door picture files I will put again as attachments to this post. So I suggest putting the game and 2 door pictures in its own folder. I did decide to make a different monster to make him larger and easier to see.
It's mostly another random game, except you have to shoot the monster before he shoots you. You also can run from the monster by entering any of the doors to another tunnel.
Have fun!

Code: QB64: [Select]

1. 'Ken's Tunnels
2. 'Made by Ken G.
3. 'Thank you to B+ for his example on QB64.org forum!
4. 'Other files needed for this game: doorl.jpg, doorr.jpg
5. '
6. 'This game makes a rnadom dungeon before you start, so every game will be different.
7. 'Use the up arrow key and the left and right arrow key to move forward and through the doors on the sides.
8.  
9. _TITLE "Ken's Tunnel - Use Up and Left and Right Arrow Keys To Move and Space Bar."
10.  
11. begin:
12. DIM segment(500)
13. SCREEN _NEWIMAGE(600, 600, 32)
14. CLS
15. PRINT "                           K e n ' s   T u n n e l s"
16. PRINT: PRINT: PRINT
17. PRINT "                                 By Ken G."
18. PRINT: PRINT: PRINT
19. PRINT "Use the arrow keys up, left, and right to move forward and into the next"
20. PRINT "tunnels on the left or right doors."
21. PRINT "Use the Space Bar to fire at the monster ahead of you."
22. PRINT "You can dodge the monster by going into any of the doors."
23. PRINT "If you see a door anywhere on your screen, you can use it."
24. PRINT "The object of the game is to finish the tunnels without losing the game."
25. PRINT "To end anytime, press the Esc key."
26. PRINT "Every game is different!"
27. PRINT
28. PRINT "Be ready as soon as it starts!"
29. PRINT
30. INPUT "Press Enter to start game.", a$
31. CLS
32.  
33. x = 300: y = 300: t = 50
34. s = 20
35. sz2 = 10
36. seg2 = 1
37. lives = 10
38. m = 0
39. mon = 0
40. points = 0
41. tu = 0
42. 'Load tunnel into memory.
43. RANDOMIZE TIMER
44. length = INT(RND * 15) + 25
45. tunnel:
46. RANDOMIZE TIMER
47. rt = INT(RND * 100) + 1
48. tu = tu + 1
49. IF rt < 25 THEN
50.     segment(tu) = 1 'Right Door
51. END IF
52. IF rt >= 25 AND rt < 50 THEN
53.     segment(tu) = 2 'Left Door
54. END IF
55. IF rt >= 50 THEN
56.     segment(tu) = 3 'No Door
57. END IF
58. IF tu = length THEN GOTO starttunnel:
59. GOTO tunnel:
60.  
61. starttunnel:
62. GOSUB drawtunnel:
63.  
64.  
65. doorl = _LOADIMAGE("doorl.jpg", 32)
66. doorr = _LOADIMAGE("doorr.jpg", 32)
67.  
68. go:
69. _LIMIT 400
70. a$ = INKEY$
71. IF a$ = CHR$(27) THEN END
72. IF a$ = CHR$(0) + CHR$(72) THEN
73.     os = s
74.     s = s + 5
75.     IF s < 10 THEN s = 300: seg2 = seg2 - 1
76.     IF s > 300 THEN s = 20: seg2 = seg2 + 1
77.     t = t + 10
78.     IF t > 255 THEN t = 20
79.  
80.     sz2 = sz2 + 1
81.     IF sz2 < 10 THEN sz2 = 300
82.     IF sz2 > 300 THEN sz2 = 10
83.     IF m = 0 THEN
84.         RANDOMIZE TIMER
85.         monster = INT(RND * 500) + 1
86.         IF monster > 495 THEN
87.             m = 1
88.             GOSUB monster:
89.         END IF
90.     END IF
91.     IF m = 1 THEN
92.         mon = mon + 1
93.         IF mon > 50 THEN
94.             LINE (285, 284)-(316, 316), _RGB32(0, 0, 0), BF
95.             m = 0
96.             mon = 0
97.         END IF
98.     END IF
99. END IF
100.  
101. IF m = 1 THEN
102.     RANDOMIZE TIMER
103.     monstershoot = INT(RND * 1000) + 1
104.     IF monstershoot > 998 THEN
105.         SOUND 800, 1
106.         FOR blast = 3 TO 26 STEP 1
107.             CIRCLE (300, 300), blast, _RGB32(127, 255, 127)
108.             _DELAY .01
109.             CIRCLE (300, 300), blast, _RGB32(0, 0, 0)
110.         NEXT blast
111.         lives = lives - 1
112.         GOSUB monster:
113.         SOUND 400, 1
114.         SOUND 300, 2
115.         SOUND 200, 2
116.         SOUND 100, 3
117.         points$ = STR$(points)
118.         lives$ = STR$(lives)
119.         _TITLE "Ken's Tunnels            Score:" + points$ + "             Lives: " + lives$
120.         IF lives < 1 THEN
121.             LOCATE 20, 30: PRINT "G A M E     O V E R"
122.             LOCATE 23, 30: PRINT "Score:"; points
123.             LOCATE 25, 30: INPUT "Play Again (Yes/No)?", ag$
124.             IF ag$ = "y" OR ag$ = "Y" OR ag$ = "YES" OR ag$ = "yes" OR ag$ = "yes" OR ag$ = "yES" OR ag$ = "yeS" OR ag$ = "yes" THEN GOTO begin:
125.             END
126.         END IF
127.     END IF
128.     points$ = STR$(points)
129.     lives$ = STR$(lives)
130.     _TITLE "Ken's Tunnels            Score:" + points$ + "             Lives: " + lives$
131. END IF
132.  
133.  
134. IF a$ = CHR$(0) + CHR$(77) AND segment(seg2) = 1 THEN
135.     RANDOMIZE TIMER
136.     cl = INT(RND * 200) + 1
137.     RANDOMIZE TIMER
138.     cl2 = INT(RND * 200) + 1
139.     RANDOMIZE TIMER
140.     cl3 = INT(RND * 200) + 1
141.     LINE (285, 284)-(316, 316), _RGB32(0, 0, 0), BF
142.     m = 0
143.     mon = 0
144.     GOSUB drawtunnel:
145.  
146. END IF
147. IF a$ = CHR$(0) + CHR$(75) AND segment(seg2) = 2 THEN
148.     RANDOMIZE TIMER
149.     cl = INT(RND * 200) + 1
150.     RANDOMIZE TIMER
151.     cl2 = INT(RND * 200) + 1
152.     RANDOMIZE TIMER
153.     cl3 = INT(RND * 200) + 1
154.     LINE (285, 284)-(316, 316), _RGB32(0, 0, 0), BF
155.     m = 0
156.     mon = 0
157.     GOSUB drawtunnel:
158. END IF
159.  
160. IF a$ = " " THEN
161.     SOUND 100, 1
162.     FOR blast = 25 TO 3 STEP -1
163.         CIRCLE (300, 300), blast, _RGB32(255, 6, 0)
164.         _DELAY .01
165.         CIRCLE (300, 300), blast, _RGB32(0, 0, 0)
166.     NEXT blast
167.     IF m = 1 THEN
168.         SOUND 100, 1
169.         SOUND 200, 2
170.         SOUND 300, 2
171.         SOUND 400, 3
172.         LINE (285, 284)-(316, 316), _RGB32(0, 0, 0), BF
173.         m = 0
174.         mon = 0
175.         points = points + 100
176.         points$ = STR$(points)
177.         lives$ = STR$(lives)
178.         _TITLE "Ken's Tunnels            Score:" + points$ + "             Lives: " + lives$
179.     END IF
180. END IF
181.  
182. nex:
183.  
184. IF segment(seg2) = 1 THEN 'Right Door
185.  
186.     _PUTIMAGE (x + 50 + s, y - s - 50)-(x + 70 + s * 1.5, y + s + 50), doorr
187.     FOR sz = s + 50 TO 20 STEP -1
188.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 5 + cl, sz / 6 + cl2, sz / 7 + cl3), B
189.     NEXT sz
190. END IF
191.  
192. IF segment(seg2) = 2 THEN 'Left Door
193.     _PUTIMAGE (x - 70 - s * 1.5, y - s - 50)-(x - 50 - s, y + s + 50), doorl
194.  
195.     FOR sz = s + 50 TO 20 STEP -1
196.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 5 + cl, sz / 6 + cl2, sz / 7 + cl3), B
197.     NEXT sz
198. END IF
199.  
200. IF segment(seg2) = 3 THEN 'No Door
201.     LINE (x - s, y - s)-(x + s, y + s), _RGB32(127, 255, 127), B
202.     FOR sz = s - 1 TO 20 STEP -1
203.         LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 5 + cl, sz / 6 + cl2, sz / 7 + cl3), B
204.     NEXT sz
205. END IF
206.  
207. IF segment(seg2) = 0 THEN
208.     LOCATE 21, 30: PRINT "You Beat The Tunnels!"
209.     LOCATE 23, 30: PRINT "Score:"; points
210.     LOCATE 25, 30: INPUT "Play Again (Yes/No)?", ag$
211.     IF ag$ = "y" OR ag$ = "Y" OR ag$ = "YES" OR ag$ = "yes" OR ag$ = "yes" OR ag$ = "yES" OR ag$ = "yeS" OR ag$ = "yes" THEN GOTO begin:
212.     END
213. END IF
214.  
215.  
216.  
217. GOTO go:
218.  
219. monster:
220. RESTORE monsterdata:
221. FOR my = 1 TO 16
222.     FOR mx = 1 TO 30
223.         READ cll
224.         PSET (mx + 285, my + 290), _RGB32(0, cll * 250, 0)
225.     NEXT mx
226. NEXT my
227. RETURN
228.  
229. RETURN
230.  
231. drawtunnel:
232. FOR sz = s TO 300
233.     LINE (x - sz, y - sz)-(x + sz, y + sz), _RGB32(sz / 5 + cl, sz / 6 + cl2, sz / 7 + cl3), B
234. NEXT sz
235. segment(seg2) = 3
236. RETURN
237.  
238.  
239.  
240.  
241. monsterdata:
242. DATA 0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0
243. DATA 0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0
244. DATA 0,0,0,0,0,0,1,1,1,0,0,0,0,1,1,1,1,0,0,0,0,1,1,1,0,0,0,0,0,0
245. DATA 0,0,0,1,1,1,1,1,1,0,0,0,0,1,1,1,1,0,0,0,0,1,1,1,1,1,1,0,0,0
246. DATA 0,0,0,1,1,1,1,1,1,0,0,0,0,1,1,1,1,0,0,0,0,1,1,1,1,1,1,0,0,0
247. DATA 0,0,0,1,1,1,1,1,1,0,0,0,0,1,1,1,1,0,0,0,0,1,1,1,1,1,1,0,0,0
248. DATA 0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0
249. DATA 0,0,0,0,0,0,1,1,1,1,1,1,1,1,0,0,1,1,1,1,1,1,1,1,0,0,0,0,0,0
250. DATA 0,0,0,0,0,0,0,0,1,1,1,1,1,0,0,0,0,1,1,1,1,1,0,0,0,0,0,0,0,0
251. DATA 0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0
252. DATA 0,0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,0
253. DATA 0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0
254. DATA 0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0
255. DATA 0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0
256. DATA 0,0,0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,0,0
257. DATA 0,0,0,0,0,0,0,0,0,0,0,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,0,0,0,0
258.  
259.  
260.  

[SierraKen]

It's been a little over 1 month now since I started using QB64. June 20 was when I completed Ping Pong 2 which was my first game on QB64. So I want to thank you all for encouraging me to keep programming and making apps and games with this language. It has been a wild ride and has kept me busy. Thank you!

[bplus]

It's been a little over 1 month now since I started using QB64. June 20 was when I completed Ping Pong 2 which was my first game on QB64. So I want to thank you all for encouraging me to keep programming and making apps and games with this language. It has been a wild ride and has kept me busy. Thank you!

I like your enthusiasm and your ability to turn even this little bit of tunnel code into a game, excellent start!

[SierraKen]

Thanks B+! Maybe soon I'll think of something else to make. lol

[OldMoses]

It's been a little over 1 month now since I started using QB64. June 20 was when I completed Ping Pong 2 which was my first game on QB64. So I want to thank you all for encouraging me to keep programming and making apps and games with this language. It has been a wild ride and has kept me busy. Thank you!

Just like you, I joined (relatively) recently; last year about this time, and have been like a kid in a candy store with QB64. There's so much more power at your fingertips than QuickBasic 4.5 could muster, and no more DOS emulators, as fine as they were. It's cool to see someone else discovering it.

I note that you mentioned MOD earlier. That's one that I never paid attention to before, but recently discovered wields a lot of utility once you get to know it, it greatly simplified several display tools in my space vector plotter. A 20+ year old program which was DOA until QB64 brought some bigger variable ranges to the table.

Great job on the game, keep 'em comin'.

PS... I was thinking that you could _PUTIMAGE the monsters face and have it grow in perspective size as it comes down the tunnel...just a thought to challenge you with. ;)

PPS  You know, you never really "finish" a game. You just put out there and let it roll until you can come back with new and better tools to upgrade it.

[SierraKen]

LOL That's true about games or programs, you never really finish them. I haven't used this version of MOD yet, but it's funny you bring that up because right now I'm working on a VERY simple Space Invaders like game, which I am converting from an ASIC 5.0 language one I did back in the 90's and I used MOD in a different way back then, with RND, but I still don't know exactly why, I can't remember why I used it. Had something to do with the range of random numbers to pick from. Maybe ASIC's MOD was different than QBasic, or maybe not, I can't tell, but it's not important. Actually, the more I think about it, I think it used RND with MOD by picking a random number between 0 and 1 and then getting the MOD of that and then I timed that by the number I wanted the range to be in. I think that's what I did.