Loading...
30
2 years ago

For day 384 of coding, I have moved the code for updating the results message into a new function. that function will then run after each total point update

This is to ensure better message accuracy, and to cut out the redundant message checks




0 comments

Loading...

Next up

For day 1032 of coding, the exit detecting debug is closer to functioning properly. I just need to work out some problem areas

I've added a #Pumpkin to finish up this year's Joltober collage

#HappyHalloween everyone

For day 1033 of coding, the exit detector is now working properly

@NEOWIZ_QUEST 's NARRATIVE JAM has begun!

Create an original narrative / story game in 10 days for a chance to win cash! 

Join the game jam: https://bit.ly/GameDevCommunity

Start Narrative Jam-inspired quests: https://bit.ly/narrativejamquests

#gjbroadcast

For day 1036 of coding, I fixed the crashing problem from yesterday. Now there's a weird issue further in that I'll need to fix later

@NEOWIZ_QUEST 's NARRATIVE JAM is underway!

Create an original narrative / story game in 10 days for a chance to win cash! 💸

Join the game jam: https://bit.ly/GameDevCommunity

Start Narrative Jam-inspired quests: https://bit.ly/narrativejamquests

For day 1038 of coding, I was what could be causing the endless loop. I will also need to do some refinement afterwards on room construction

For day 1037 of coding, I have fixed the issue with the exit's appearance. Now there seems to be an endless loop problem that I'll need to take care of next

@NEOWIZ_QUEST 's NARRATIVE JAM is underway!

Create an original narrative / story game in 10 days for a chance to win cash! 💸

Join the game jam: https://bit.ly/GameDevCommunity

Start Narrative Jam-inspired quests: https://bit.ly/narrativejamquests

For day 1035 of coding, I have addressed the game crashing in one area only to find another game crashing problem