Hey guys,
Steve here.
So, it’s been nearly two months since I last posted here? Seriously? There’s no way I can believe that. Time has flown by these last couple of months. And when I said it would be one or two weeks, instead of four, before I posted again, only the last part of that statement was true. Unless, of course, I meant one or two months, not weeks.
Over the last month and a half, I did some work on S Quad Racing, though not as much as, perhaps, I should have. Nonetheless, I completed a few things, such as adding proper menu sounds, improving the artificial intelligence’s, well… intelligence, Creating an achievements system complete with the possibility to earn experience points, and completely fixing all bugs that could be found in the game thus far, but that’s about it. I sat down and wrote an outline for Arcade Mode, and will try to compose a sort of to-do list, so I can at least try to structure my coding into priorities, something I have failed at doing in the past. This is not to say I’ll end up sticking to that, but it’s worth trying.
On a loosely related note, the very basics of Matt the Terrorist have been established, in the form of a primitive, and I mean extremely primitive, game where all you can do is walk around. There’s a platform that spawns, but you can’t even interact with that, yet. But I guess every game has it’s starting point. To my credit, even though you can only walk around, tiles have a property called thickness. And for platforms, depending on the thickness, a different footstep sound will play. For example, if the thickness is 10.0, it will play the sound of walking on stable wooden boards. However, by the time it gets to 2.0 or lower, you will hear yourself walking on very unstable wood. So even though the game seems primitive, I’m still a bit proud of myself for what I did manage to code in under an hour.
In other news, part of the reason I haven’t been coding and writing as much, is my recent spike in gaming. Recently, Danny and I have been playing a two player pong game, created by Dragon Apps. I must say, I kind of feel bad for Danny. Because out of all the matches we’ve played, and I’d say that’s about four or five, he hasn’t won a single one. We’ve played one “long” game, where the winner was the one to reach a score of 21, and the rest were “short” games, in which 11 was the winning score. The closest he came to winning was the long game, where he managed to achieve a score of 16 give or take, due to a streak of complete failures on my part. That’s okay. Because even after several months of frequently playing, he still owns me on Audio Quake most of the time, so I think we’re even.
That wraps up this post. I’m not necessarily done catching up, but I’ll save the rest for a later post. Do not worry, this is not, my last post of 2015. I’m not sure what happened that got me out of blogging in October, causing that lengthy silence (besides that poem), but it won’t happen. I’ll blog again next week, I mean it this time.
Thanks for reading,
type you later,
Steve.
Tag: blind geek
Racing Game Updates and a Programming Venture
Hey guys,
Steve here.
Nearly a month it has been, without one single word from me on this blog. Good lord! I can’t believe it! So much has been going on in that time frame, and recently it feels as though my creativity is spiking again, which may or may not be a good thing. You decide. As a result, I completed S Quad Racing’s Race Mode, and did away with the few bugs that have been so stubbornly plaguing this game and hindering its further advancement. That burden being lifted has allowed me to expound more on the opponent AI, building auto gear shifting in for them as well. However, that’s not what matters so much, or in fact what puts me in such a jovial state of mind at having completed Race Mode. It turns out, that another goal was accomplished that day. I actually managed to do it on the last day of the first six weeks of school, which was the deadline my Digital Interactive Media teacher and I had set. So not only did my game achieve a great milestone on its path to the metaphorical finish line, I managed not to let my teacher down in the process.
After completing Race Mode, I took a small break from S Quad Racing, and decided to experiment with linked lists in Pure Basic. One of my main reasons for wanting to use BGT for the complex adventure platformer I’ve been realizing was Pure Basic’s rather flawed array system, which does not allow programmers to directly interface with elements, (I.E. removing, inserting, swapping), which is a necessity that, although can be worked around if not available, is not at all worth the pain since most languages have that ability. But I came across Linked lists, and have recently been experimenting with them. Here’s what I can gather so far. (Non-geeks, just bear with me a moment, this is about to get over your heads)
One cannot access an element directly. In order to get to a certain element of a list, a programmer must first tell the program to go to the first or last element, and sycle to the next or previous element respectively, until they reach the particular element. This has the potential to make apps that use linked-lists run slower, because they have to move element by element until they reach the desired one, whereas elements of an array can be accessed on the fly.
Nonetheless, I’ve begun incorporating these into S Quad Racing, and unsurprisingly they have made things a lot less painful. Remember the problems I’ve had with obstacles? How their affects would loop and loop and loop unrealistically? That ended because I am now directly able to… in non programmer turns, make that obstacle disappear from the track, or more realistically become ineffective because it was driven upon. This also means that turns will now be able to be taken out of tracks by builders, with no unnecessary headache for me as the developer.
Bottom line, I think these linked lists provide an advantage over arrays, even though they may make things a bit slower and accessing elements can be difficult at times.
That wraps up tonight’s post. I have more to talk about, but this is getting quite lengthy as it is, so I’ll save the rest of it for later posts. See you all in a week, not four.
Thanks for reading,
type you later,
Steve.