Unfortunately, I did not complete my 1 week challenge to make a game, though I still believe it is within my abilities to do so. It was more so the timing I chose, which turned out to be pretty bad, something that the post title clearly suggests.
There is a lot that has happened in the last 2 weeks. I’ll go ahead and rewind back to week 1, which was the week following my last post, and when I was originally supposed to have completed the game creation challenge. I actually managed to squeeze in 3 or 4 days of work on the game that week, though I was majorly hindered by the need to purchase sound affects from a source I’d never used, and thus didn’t trust yet. Furthermore, this mistrust was enhanced when my friend spent $85 on their sound affects, and didn’t receive his sounds for several days. As a result, I didn’t get the necessary sounds until Thursday of that week, so I decided to give myself an extra few days to work on it, and thus decided to delay the blog post a few days as well.
Well guess what? After getting a few more consecutive days of work done on the game challenge, I found out I had a summer reading assignment to complete for school, and that my family vacation to Maine would indeed be happening, — on Friday! of that week. And while I only considered the former to be a bad thing, both meant that coding a game would be quite hard, if not impossible for a little bit.
That said, vacation was great. There’s not too much to say about it, except for that it was relaxing, I didn’t have to put up with 110 degree Texas heat, and I did not work on my summer reading assignment or coding games or anything that required the use of my intelligence. But even though I got home on Wednesday of last week, I had a camping trip with my church youth group in Oklahoma on Friday and Saturday, then spent all of Sunday at church.
Today has been a day of rest for me. I didn’t really do anything productive, as I’ve basically been non stop the past several days. But for those wondering about the status of the game challenge, I’ve decided not to finish it, because honestly my timing was bad, it was meant to be only a week thing, and once I get back to coding I really need to start porting my main projects over to Python. That will have to wait a bit though, so that I can get this school reading assignment done before it’s too late. And believe me, I want to code games this week, but I’ve already had 2 dreams that involved me walking in on the first day of school and realizing that I didn’t complete the summer reading assignment because it totally slipped my mind, and that I’d be starting off the school year by failing English. I’d much rather leave that in my dreams.
Still, in the free time I did have during that time, I managed to create a little recording, that I would like to share with followers of this blog. I hardly ever post audio on the blog itself, so you know this is going to be good.
I had one of the text-to-speech voices from my computer commentate a recording I made of myself playing Red Spot, an audio first person shooter. This voice is named Microsoft Sam, and has been used to create funny skits and recordings all over YouTube. Anyway, though I didn’t think it would, this recording received quite a bit of approval from those I showed it to. It’s about 10 minutes long, and is bound to make you chuckle at some point.
In case the comments seemed untimely or out of place at certain points, this was basically my process for creating this recording, literally:
1. I recorded a segment of myself playing and owning on Red Spot.
2. I played it back, paying attention to key events in the game.
3. Once I came upon a turning point, major event, or just felt like Sam should say something, I paused the playback, recorded a piece of Sam’s speech, and inserted it into the recording. This was kind of hard because I had to focus on timing.
4. I listened to it, made sure there were no errors, and saved it.
I should note that none of Sam’s speech was scripted. These were all responses I thought appropriate to the occasion.
Thanks for reading,
type you later,
P.S. that file received quite a bit of positive reaction, and I hope to create more. But like Sam’s speech in that recording, the decision will likely be made two seconds before its execution, so don’t count on counting on or not counting on it.