Code Rewrites (August 01 2025)
- Thomas Tang
- Aug 2
- 2 min read
I kept working on the tower level, and I'm a bit stuck at the ending right now. For the ending I wanted you to unlock a way to make it easier (but still with a few restrictions) to get boxes past the tower. I tried several things, but decided on having bounce blocks that will send the box to the top of the tower (where it will get bounced away again). Now the question is, what unlocks those new bounce blocks, and then what to do with all the boxes you get access too.
Another thing I did was change how switches work. The tower level really wanted it where multiple switches had to be activated at the same time in order to deactivate/activate a platform. The problem is this was basically impossible to do with the switches as is. I instead rewrote the game where the player object would first find every switch in the level, and keep a list of what objects those switches interact with. Then for each object, it checks whether any switches that interact with that object are on or off.
Anyways, I've been working on this one level for a while now, and I think maybe it'd be better if I take a bit of time away from it. Instead maybe I can try to make a level based around the bullets I programmed earlier. It's possible I have to change the way the player holds boxes in order to more effectively use boxes as a shield against the bullets.
Finally I discovered a new innovation. Originally when you're given text buttons in my digital card games, that's that, they were just text. When you click one of those buttons, the player receives a number and then figures out what to do from there. It mostly worked, except there were some tricky cases that could happen when some buttons need a condition in order to show up. I now changed that system where when a button is created, it gets sent both text and also what will happen when the button is clicked. It's more direct and accurate this way.
Comments