I created a webpage that shows you maps what areas of a gamepad you use the most! You can find it here: here!

If you connect a controller, you can run it in the background while you play a game to analyze what inputs you're using the most.

Lua Visualizer is one of the projects that I've had around for a while, but I didn't really get around to actually making any progress on. Now that I'm done with school for the summer, I can actually get around to completing.

The idea of the project is to print out the state of the Lua Virtual Machine so that you can see what exactly it's doing to make your script run. The way I'm doing this right now is by printing out instructions and memory in the command prompt.

The way that the virtual machine works is that instead of having registers or caches like a normal CPU, it works entirely off of these "registers", which are really stack indices. understanding this concept has caused me a lot of trouble, but this resource has helped me a lot in understanding it, along with whatever other documentation I can get my hands on.

I also want to do more projects related to programming languages and human languages. This sort of stuff is really interesting me and I want to delve more deeply into it!

Multiplayer snake is like normal snake, but you split up the direction controls by player. So one player will control left and right, and another player will control up and down. This means you can have anywhere from 2-4 players.

I've done some networking projects before, but they haven't been easily presentable. There are some things that I want to do differently for this project:

• WebSocket based - I want to be able to run this game entirely out of the web. This means that I'll have to use some technologies I haven't used before.
• Visualization - There will be options to look at what is happening on the networking side of things. If you want to, you should be able to look at each individual packet, see what data is being transmitted, and when connections are established/terminated.
• Testing - This app should have complete unit testing, which is quite different for networking apps. This requires setting up fake clients and thinking ahead of time about the architecture of the app. For example, I want to split up the code for receiving packets and the code for interpreting the packets' data. That way, I can write tests for checking whether both work individually, and if they work together. The server will also have to be developed to handle plenty of error handling, as in theory the client could send any packet it wants to at any point in time.

For the client side, these are some hand-drawn UI layouts:

The top left is used as a big screen mode, the top right square is a small screen mode, and the two screens on the bottom are special screens used for state outside of being in a lobby playing a game.

Below that is the packet debug interface, which will appear either on top or on the side of the screen. This will display a list of all the recent packets sent and allow you to access all of their information and see information like latency, timestamps, server information, etc. The goal for that screen is to give as much debug information as possible.

After spending most of the day today trying to get this website published, it's finally here! The database is connected, the app is running, and so far everything is working perfectly!