Competition

[bplus]

Great! Thanks @Steve  ha, ha @SMcNeill

[TempodiBasic]

@bplus
ok man, so ANY kind of game is welcome, text adventure, dugeon, puzzle, card game, platform, shooter, fighting and so on... all in ASCII with 16 color plus blinking! (0-31 = 32 colors to use), yes sound and music.
Let's go!

[bplus]

@bplus
ok man, so ANY kind of game is welcome, text adventure, dugeon, puzzle, card game, platform, shooter, fighting and so on... all in ASCII with 16 color plus blinking! (0-31 = 32 colors to use), yes sound and music.
Let's go!

Great, and the most important thing, One Key only (except maybe an esc to quit).

[bplus]

You know, I was saying Screen 0 (Text) for Competition for this forum challenge but I am having 2nd thoughts.

It really should be Halloween Themed and for that graphic freedom is essential.

I was saying Screen 0 (Text) to maybe get @Pete involved but he was kidding and my program needs some graphics distractions :-)) (In fact the one key requirement makes it a bit of a pig that probably won't be fixed by graphics lipstick. I need to find some idea made for one key control like Flappy Bird.)

So if OK with you guys forget Screen 0 Text only requirement unless you've already started on something. Let's say extra points if you do pull off a Screen 0 Text only Game and that wouldn't need to be so Halloween themed.

So either one key control text game or one key control Halloween theme game and extra credit for doing both text and Halloween.

(Yeah, I want to get @Dav latest game qualified.)

[johnno56]

I have created 62 audio files.
Complete alphabet - includes 1-4 in wav and ogg (2 files)
30 individual letters - including 1-2 in wav and ogg (60 files)

They total to just over 6mb. Voice is female. No special effects.

  [ You are not allowed to view this attachment ]  
(sample - alphabet + 1 to 4)

If this is ok, let me know, and I will post the rest.

J

[bplus]

Thanks @johnno56  I'll get to work on it today.

[bplus]

Hi @johnno56

Oh! It's just one sample ogg.

I thought you said 60 files, well what can I say didn't have my coffee yet.

Is it possible to get a deep, dark, Moo ha ha kind of voice saying or implying:
"So, you've selected B, (Moo ha ha, well let's just see how that works out for you, Moo ha ha)."

Or we could do good voice (female computer like when the guess is correct), bad voice (Moo ha ha devil may care like when the guess is wrong!) routine.

[bplus]

Hi @johnno56

Oh! It's just one sample ogg.

I thought you said 60 files, well what can I say didn't have my coffee yet.

Is it possible to get a deep, dark, Moo ha ha kind of voice saying or implying:
"So, you've selected B, (Moo ha ha, well let's just see how that works out for you, Moo ha ha)."

Or we could do good voice (female computer like when the guess is correct), bad voice (Moo ha ha devil may care like when the guess is wrong!) routine.

Oh man, I've been watching to much TV, too much Me Too political correctness???
ie female = good, masculine deep voiced male = bad

Please reverse good and bad characterization stereotypes, please, let's buck this trend!

[SMcNeill]

@bplus So here's a quick question: Would something like this work as a valid entry for the One Input challenge?

Code: QB64: [Select]

1. $Color:32
2. $Console
3. _Console On
4. Screen _NewImage(640, 480, 32)
5.  
6. Do
7.     x = OneInput
8.     Print x; Chr$(x)
9.     _Limit 30
10. Loop Until _KeyDown(27)
11.  
12. Function OneInput
13.     Static InputScreen
14.     If StaticScreen = 0 Then
15.         StaticScreen = _NewImage(400, 400, 32)
16.         D = _Dest
17.         _Dest StaticScreen
18.         For i = 1 To 26
19.             x = 200 + 150 * Sin(_D2R(13.85 * i))
20.             y = 200 + 150 * Cos(_D2R(13.85 * i))
21.             CircleFill x, y, 16, &HFFFFFF00
22.             Color &HFFFF0000, 0
23.             _PrintString (x - 8, y - 4), Chr$(64 + i)
24.         Next
25.         temp$ = "Move mouse to choice"
26.         l = _PrintWidth(temp$)
27.         _Dest StaticScreen
28.         _PrintString ((400 - l) / 2, 196), temp$
29.         _Dest D
30.     End If
31.  
32.  
33.     PCopy 0, 1
34.     _PutImage ((_Width - 400) / 2, (_Height - 400) / 2), StaticScreen
35.     _MouseMove _Width / 2, _Height / 2
36.     _Delay .2
37.     While _MouseInput: Wend 'clear mousebuffer after move
38.     Do
39.         While _MouseInput: Wend
40.         mx = _MouseX: my = _MouseY
41.         For i = 1 To 26
42.             x = _Width / 2 + 150 * Sin(_D2R(13.85 * i))
43.             y = _Height / 2 + 150 * Cos(_D2R(13.85 * i))
44.             If InCircle(mx, my, x, y, 16) Then Exit Do
45.         Next
46.     Loop
47.     OneInput = 64 + i
48.     PCopy 1, 0
49. End Function
50.  
51. Sub CircleFill (CX As Integer, CY As Integer, R As Integer, C As _Unsigned Long)
52.     ' CX = center x coordinate
53.     ' CY = center y coordinate
54.     '  R = radius
55.     '  C = fill color
56.     Dim Radius As Integer, RadiusError As Integer
57.     Dim X As Integer, Y As Integer
58.     Radius = Abs(R)
59.     RadiusError = -Radius
60.     X = Radius
61.     Y = 0
62.     If Radius = 0 Then PSet (CX, CY), C: Exit Sub
63.     Line (CX - X, CY)-(CX + X, CY), C, BF
64.     While X > Y
65.         RadiusError = RadiusError + Y * 2 + 1
66.         If RadiusError >= 0 Then
67.             If X <> Y + 1 Then
68.                 Line (CX - Y, CY - X)-(CX + Y, CY - X), C, BF
69.                 Line (CX - Y, CY + X)-(CX + Y, CY + X), C, BF
70.             End If
71.             X = X - 1
72.             RadiusError = RadiusError - X * 2
73.         End If
74.         Y = Y + 1
75.         Line (CX - X, CY - Y)-(CX + X, CY - Y), C, BF
76.         Line (CX - X, CY + Y)-(CX + X, CY + Y), C, BF
77.     Wend
78. End Sub
79.  
80. Function InCircle (px, py, cx, cy, r)
81.     distX = px - cx
82.     distY = py - cy
83.     distance = Sqr((distX * distX) + (distY * distY))
84.     If (distance <= r) Then temp = -1
85.     InCircle = temp
86. End Function
87.  

I'm only using one input feed for my program here -- the mouse position itself.  It doesn't care about mouseclicks, or up or down positions, or anything of that sort...  Just how you move the trackball itself.

Is there any reason why a trackball wouldn't count as "One Input", since it's only that one input segment of a mouse, much like the "Spacebar" is only that single segment of our keyboard??

Personally, I find this to be perhaps the most intuitive of input methods that I can come up with that only involves a single input feed.

[bplus]

Hi Steve,

I had something like that in mind too, when I first read of this competition at Syntax.

I ruled it out for myself because I was sure that this part:

Code: QB64: [Select]

1.     DO
2.         WHILE _MOUSEINPUT: WEND
3.         mx = _MOUSEX: my = _MOUSEY
4.         FOR i = 1 TO 26
5.             x = _WIDTH / 2 + 150 * SIN(_D2R(13.85 * i))
6.             y = _HEIGHT / 2 + 150 * COS(_D2R(13.85 * i))
7.             IF InCircle(mx, my, x, y, 16) THEN EXIT DO
8.         NEXT
9.     LOOP
10.  

Decides in an analog manner by position instead of a simple On/Off signal from a button eg you can use the fact the mouse was clicked, On/Off, but you can't use the place where it was clicked, that would be analog position control.

If you want to appeal my ruling I can take your case to the Syntax Bomb forum for the Supreme Court judge to rule ie, just link Qube to this discussion. I am pretty sure he would agree with me, but again I could be wrong, it wouldn't be the first time.

[bplus]

@SMcNeill

BTW that is a nice realization in code of what I was thinking and I know you want to stress that you didn't click anything!

You could alternately use Atan2 after the mouse is a certain distance away to pick up the general direction of choice so that it's not forced to remain in a the circle.

[SMcNeill]

@SMcNeill

BTW that is a nice realization in code of what I was thinking and I know you want to stress that you didn't click anything!

You could alternately use Atan2 after the mouse is a certain distance away to pick up the general direction of choice so that it's not forced to remain in a the circle.

Quote from: MikeHart on August 14, 2021, 06:56:10
Question: does one feature of a controlling device include an axxis of a Mouse or a Stick on a gamepad, an analog button on a gamepad? Or are we bound to Buttons with 2 states, on and off?

Answer:
Single on / off state be it a key on a keyboard, click on a mouse, button on a joystick / joypad ( X Y etc ). No analog input for main gameplay.

[SMcNeill]

So I guess the timed spacebar method is my best input idea so far. 

Or morse code.  LOL!

[bplus]

So I guess the timed spacebar method is my best input idea so far. 

Or morse code.  LOL!

Yes! Morse code I think is OK because timers are OK. Even though something in time is a position, whether it's past a certain point or not is On/Off or Yes/No or True/False = Digital. So Morse code would be acceptable but who wants to learn it. The game would have to teach it in fun way to be a winner. It's a possibility.

[johnno56]

Oh, a neural interface is looking better all the time... Moo Ha Ha...  "Igor!  Throw the switch!"  "Yes, master."