#032 - Scaling up
Something one shouldn't do without a structure
Hey there,
this week's delay was actually an active decision, a decision to sleep. Anyway, let's take a look at my priorities from last week.
The workout worked out.
The exams were prepared.
The programming did happen. Although I had felt over the past few weeks that I got stuck with the project, my difficult tetris-like with polyhexes, so I had to make a drastic decision. I changed the goal from a fully-featured Multiplayer game to just a mini-game, as was the original plan. So, I scraped the Multiplayer for now and stepped down with the amount of customization.
For this week, I implemented a pause menu. I implemented the fix for row clearing I mentioned last time. Lastly, I implemented a score, as of last week's plan.
Further, I thought about what else there is to do, before I can call the project not finished, but publishable. It's not much, actually. I'll need to just reimplement the ability to see the next piece, implement a High score page that saves. Furthermore, I need an end screen for when the player finishes a game.
Really, there was a fourth unforeseen priority this week. I was working on a Minecraft Datapack to craft and throw paper planes with a friend.
The crafting, throwing, and picking up do all work already, just the in-between, the flying, is still a bit weird.
For a lightning round:
I tutored some people this week.
I thought about the importance of systems.
I thought about the existence of true randomness, and whether it matters, if it exists.
I also signed up for something which will take a lot of time from me over the next few months.
My priorities for this week will be:
Participating in a Datapack Jam (it starts today)
Preparing for upcoming exams. They're the last ones before exams season ends.
Reading. I don't read as much as I'd like.
Ole370’s Weekly Report will return next week…