As for room-to-room, you got it exactly. I have no idea how many frames it takes, but the new room comes on screen faster than I can snap. It’s something I ought to keep an eye on though, especially when I add objects and object logic to the rooms.

I don’t have the entire game planned on paper. I have an idea of how I want the gameplay to be and how the player will interact with the environment, but I’ve only designed one test level. Once I have the basic game engine finished I’ll work more on level design. At some point I’ll want to make a map editor utility, but this early in the game I’m still making changes to how the data is stored which makes writing a map editor difficult.

I do make sure I have a plan before I start coding though. I like to know exactly what I’m going to write before I write it. I work out data structures, logic, algorithms, etc on paper first and then when I feel like I understand what I want to do I code it up.

Thanks for the encouragement! I’m glad you like the blog. btw, I don’t really have a preference what people call me.

So how do you handle room-to-room? When changing rooms, do you reload the base template, grab the wall data to write, then do the interior data? If that’s the case, do you know how many frames it’s taking, by chance?

I’m also curious if you have already planned the entire game on paper, or if you have started doing the coding, then plan to make out the puzzles as you go. Basically, I like to hear how other people approach the whole dev life-cycle dealy-o hehe

I’m loving this blog Thomas (Tom?, Metalslime?, not sure if you have a preference)! Also, thanks for the kudos : )