I completely redid the controller code. This should work better.

you could allow controllers with various button counts by using this to select what button to use for what:

Code: QB64: [Select]

1.    
2. FOR i%% = 1 TO _LASTBUTTON(C.Control_Pad)
3.  IF _BUTTON(i%%) THEN Bselect%% = i%%: i%% = _LASTBUTTON(C.Control_Pad) + 1
4. NEXT i%%
5.  

then you assign that button to the control, and it wont matter if they have 4 buttons or 24 buttons.
say you picked the controller button to be used for 'A' assign:Controller.A = Bselect%%

and I'm not sure if STRIG() will pull it off anyway looking at the WIKI page. based on the following line from the WIKI
"Odd devices use 0, 1, 4, 5, 8 and 9 and Even devices use 2, 3, 6, 7, 10 and 11 as first parameters with device number following."
(you were using 0,4,8; all inline with an Odd device number)

So I don't know if my button 2 or 10 would even work with STRIG() as my controller is an odd device number(reported as 3)
I would have recommended using _BUTTON() instead.
And I don't think you can assign the Dpad buttons correctly for the same reason.
Even though my Dpad returns as 2 axis, it only returns 3 values for each axis -1,0,1 that is it.

And custom keyboard controls could be done in a similar manor, you have a menu where the player selects what button they want to customize then you get what they pressed and assign it for that button.

Looking at the code it doesn't appear that it would be too terribly hard to swap out STRIG for _BUTTON, and probably STICK for _AXIS, but then I haven't looked through that much.

Now I know the keyboard controls I will see about giving it a run though!

how my computer registers the 4 buttons on the controller.

Gotcha. Good luck. The game is crazy hard using the keyboard. ill see if i can pick up a cheap controller at the store and play with it.

Cobalt

Battle Theme 1 was supposed to be removed. That track is not used which is why I never took down the 320k encoding.

Keyboard is the normal W,A,S,D with Q=B and E=A, TAB=Select, Enter=Start on the NES controller..
As far as the screen, everything is built around that specific resolution. I can put in a _FULLSCREEN if that will help maybe?

I would love to support more that a PS4 controller but that is all i had available to me to test and play with. Not sure how the others work but I can def add support for them
if i can get an idea how the D-Pad is translated. On the PS4 controller the DPad is not picked up at all so I ignored it.

Has some bug fixes and the open source version now has access to the score sever for you speed runners.

Just as a note, this was built in QB64 v1.5 as this was the current version when development started. v2.0 does not seem to work right with this game.

EDIT:
Based on the comments I redid the controller code. This should work better now.

If i am understanding the question correctly, the starfield only does that during certain parts of the song.
The asses are from Stereospace 2. Still unsure what will be reused.

 This is a concept demo for background and effects. Those of you who loved Stereospace 2 can see where this is going :).

 

Port 23 is the most scanned port in existence. Every port scanner will ping it. So if you for example are running a server at the front of your network you can use this to gather the IP address of people either scanning your network or straight attempting to telnet in. Naturally you would want to block these address with your firewall.

This program simply automates this process. This is how most honeypot type programs work.
Is this useful for the average user, absolutely not. It is only useful to those who run a windows machine at the edge of their network.

It has been some time since this was released. Any gripes or anything i should have done differently on this before i start on the next game? I know it is pretty heavy code wise.