I found my old remote collimator, which focused the signal from an infrared remote. In the Arduino sketch, I grouped all the remote button codes into an array and scanned them each time the tagger received a code. I used that code to reassign the tagger's team designation the same way I could do it over serial.
I created a framework for the overall gaming programs. The remote can assign a value to a game status variable, and the START button will increment that variable to a value corresponding to an active game. The rules for each game were not coded, but the framework was started.
My serial monitor and screen were getting cluttered, so I added a couple of bits to control the diagnostic messages. I could toggle the bits through the USB connection. I started coding the Golden Gun game mode, where players have one hit point and unlimited ammo, since it seemed the easiest mode.
In my list of tasks for the Golden Gun game, I wanted to begin by receiving an infrared START signal and entering a 60-second countdown timer so players could scatter and prepare to start. I had a few issues with errant messages appearing on the screen, but I was happy with the yellow characters announcing when the game would begin.
I made a colorful welcome screen for the power-up sequence so I knew when the system was finished loading. I made a screen for the Golden Gun game with a live counter that tracked how many shots the player had fired. I decided the most logical approach was to permanently assign a location on the screen so that every game would put it in the same place. I did something similar with the remaining hit points, but this one was not live because there was only one HP per player and they got booted after taking a hit.
I finished the Golden Gun game mode, so I have a playable tagger now! I updated the elimination screen to include the player who delivered the final shot. I also tidied up the playing screen to show how many shots the player took. Lastly, I fixed the bug that let players shoot as fast as they could pull the trigger.
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
 |
| Remote in a range extender shell |
I created a framework for the overall gaming programs. The remote can assign a value to a game status variable, and the START button will increment that variable to a value corresponding to an active game. The rules for each game were not coded, but the framework was started.
 |
| Game selection and start notifications |
My serial monitor and screen were getting cluttered, so I added a couple of bits to control the diagnostic messages. I could toggle the bits through the USB connection. I started coding the Golden Gun game mode, where players have one hit point and unlimited ammo, since it seemed the easiest mode.
 |
| Code start and outline |
In my list of tasks for the Golden Gun game, I wanted to begin by receiving an infrared START signal and entering a 60-second countdown timer so players could scatter and prepare to start. I had a few issues with errant messages appearing on the screen, but I was happy with the yellow characters announcing when the game would begin.
 |
| Starting a one-minute countdown |
I made a colorful welcome screen for the power-up sequence so I knew when the system was finished loading. I made a screen for the Golden Gun game with a live counter that tracked how many shots the player had fired. I decided the most logical approach was to permanently assign a location on the screen so that every game would put it in the same place. I did something similar with the remaining hit points, but this one was not live because there was only one HP per player and they got booted after taking a hit.
 |
| Golden Gun playing screen |
I finished the Golden Gun game mode, so I have a playable tagger now! I updated the elimination screen to include the player who delivered the final shot. I also tidied up the playing screen to show how many shots the player took. Lastly, I fixed the bug that let players shoot as fast as they could pull the trigger.
 |
| Each tagger has a serial number and associated name |
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
Comments
Post a Comment