On Wednesday, it just went smoothly until I ran into a problem that no one would help me to solve, except by the engine manufacturer himself. It turned out that one of the functions returns an incorrect result only at the end of the loop (or for another strange reason). After figuring out this problem, I spent all my Wednesday programming on only one thing.
#tip DO NOT use integer FindString (str, findStr, ignoreCase, start)
A bug in this function form took me over an hour to catch it. Despite various tests, the last time the feature was used, it gave incorrect results for no apparent reason.
Due to this error, I did not program "writing to the configuration file" on Wednesday. I didn't start other stuff either. One of them is delayed, as I noted in the English-language Trello.
On Wednesday, I was supposed to write the following paragraph, but for the reasons described above, I did not have the strength.
"By default, the game engine blocks manual changes to the code of the scenes created with the wizard. You can turn off the ReadOnly mode and change the code, but it is restored to the previous state at the time of saving.
I can't wait to start making the map maker. I have it scheduled for Thursday, so it's tomorrow, but I need a way to save and read data from files first. But if I can do it today, maybe I'll start the wizard."
Hope to make up for it today (Friday). If not, I'll be doing the wizard next week. I don't know what else to plan yet.
So, I'm sorry for the delay and I'm already on my way!😄
#wednesday #devlog #MyFirstGame #bugs #AGK #AppGameKit #bugsmasher #debuger #delay #wednesdaybug
0 comments