BEEEG DEVLOG
Wowwee! I’ve gotta remember to make devlogs more often.
Seriously. Here’s a list of changes that I’ve made since my last devlog!
- The basics of the board are implemented! You can’t interact with it yet, but the template to do so is there, and it now exists on the server-side too and the client reads from that state.
- The board is also animated now. When someone selects a clue, it will highlight the category and the clue, you can hover clues, and, my favorite bit, the categories get revealed one by one when the game starts!
- That last part actually kind of sucked to implement lol. I prepared for this when making the lobby’s ready up system and made the state that it uses to work a bit dynamic because I knew that I would need it! The state stores
readyForNextState, which for some states (like when we’re in the lobby) allow unreadying, but for others, simply act as a marker of whether a specific client is ready to move on. This is probably actually really important because if we just ran a timer on the server, a NUMBER of things could go wrong, most importantly being that a laggy client could get desynced VERY quickly and have a bad time.
- That last part actually kind of sucked to implement lol. I prepared for this when making the lobby’s ready up system and made the state that it uses to work a bit dynamic because I knew that I would need it! The state stores
- Alongside this, there is an intro now! I spent a good bit of time in Aseprite and messing with FL Studio to make some art and an intro track, both for the logo and so I finally have some artwork to add in the Discord Developer Portal, so there aren’t anymore blank assets. It’s not perfect (i am NOT an artist lol) See pictures below!
- psst, I also made a “think” music track for if the final round is enabled! It’s not in the game yet, though.
- I made a number of styling fixes. The board in particular looks much better on different screen sizes now, even on my phone. Reminder to use relative sizes when able, not
px! - The server now registers the activity entry point command as having an
APP_HANDLERhandler, which means that the server must respond to interactions now, rather than Discord autolaunching the activity. The benefit of this is that we have control over whether a message gets sent to the channel it was started in (and when), or if we even launch the activity at all (disallow banned users? anything is possible…)! - The rich presence actually has meaningful details now lol, rather than placeholder text.
NOWWW what?
I am going to, FINALLY, FOR REAL THIS TIME, (lol) actually start making the game logic. (It’s about time!)
More updates sooooon!
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.