Hello world! And welcome to dev diary numero dos.
Today's agenda: What in the world is wrong with the save/load feature, and what have I been doing to fix it? I will hopefully answer all your burning questions, and also let you know about imminent re-release of Prologue. The Problem As a new programmer, I foolishly waited until the very final stages of development to implement the save/load feature. This is a big no-no and led to a problem where the game engine didn't know how to properly access a save file, in turn causing a whole host of problems. So, when a save file was loaded, the game was basically looking for data in the wrong place. The Solution A whole lot of coding fixes. The game engine has become a bit monstrous, as I've used the programmer equivalent of massive amounts of duct tape. With that said, I've been testing it myself A LOT (essentially trying my best to 'break' the game) and I can tentatively say there have been huge improvements to stability. The code is really ugly to look at, but it does the job properly now. For the next Adesaw game, it'll all get cleaned up to a more streamlined system. But that's all under the hood shop talk! The important thing to know is this: Prologue now knows how to access the save file. Tomorrow, I'll be releasing an internal beta to players who already have the game installed. I ask that if you update your game, please try it out! And more importantly, send me an email if you run into more problems! If the beta runs smoothly, I hope to put Horror at Adesaw: Prologue back on the Google Play store by the end of the weekend.
0 Comments
Leave a Reply. |
About the DocDoc Fishopolis Operations is a one man Android dev team. Archives
September 2018
Categories
|