Dig Up

So, strangely enough, I cannot figure out how to get the screen which worked almost perfectly to finally be finished. The other event which I am having problems with is  the bullets.

HOWEVER!

You can play an incredibly laggy game of SpaceWars now, up until the upgrade screen. Also, you can't shoot.

In other great news, it seems my proctoring will be accepting and I will be able to take the final. Now I just need to print out everything. Good thing tomorrow is a holiday.

Does Compute

So, while the program was daunting and confusing at first, once I knew what it was supposed to do, it was very easy. We have used similar things many times before. We use this style for queuing up events in our game, except they were read from a Lua file. Needless to say, I find this very fun.
I probably should have broke everything up into separate files, but I just kept adding, thinking it would be the last thing until it got massive. It all works though and I guess they sort of belong together anyway. I have similar set ups in my other project where I am doing this very similar set up as I mentioned.
I am sad I did not use the as -- reference, method, keyword? -- but casting worked with me having to do less work and less editing the test. I wanted to avoid editing the test, but I had to, there was no way around it. Everything works though and it looks pretty so I am happy.
I am still very confused about the dump function. I have an idea of what it is supposed to do, but the method signature provided would make it useless and I don't feel like editing it so I just had every method do its own printing. I hope Keenan doesn't mind. Plus the way the test is set up, it has to be public, and yet it - I don't know, it's just a mess so I didn't use it.
I'm excited to get this final project underway! :D