Today devlog 02 (Translated into Papago)
I was going to complete the Options menu today.
However, I upload the development log because I thought that I should just sleep while struggling with bugs that I don't know the cause.
Before creating an option, create a save file so that the settings are not initialized every time you play the game.
I made a recall of saved files.
Rather than making it from the beginning, I took the code that was written in the previous version of this game and improved it.
It was written in April or May, and at that time, I thought it was such a cool code that I thought I had no place to fix it.
Looking at me now, there were a lot of strange things.
I'm going to transfer the variable I referred to in a single tone to another variable, and then I'm going to replace it with a single tone.
Or unused variables that don't cause any problems with annotating.
There were many cases where the two above were combined and so on.
I've improved these parts more intuitively and simply, and I've also recently used the functions that I found while searching for new game ideas.
'wrapi' and 'range_lerp'.
Thanks to "wrapi," I was able to move the menu directly from the last menu to the first menu when I was touring the rudder like any other game.
'range_lerp' now allows the computer to convert to a specific range of values without having to create complex equations by itself.
It worked out well, but there's an unexpected problem.... In the Options menu, there was a part that referred to the option value written on a single tone and marked it on the "text" value of the Label node.
I made a case for each reference value using 'match'. But somehow the function didn't recognize the value at all, and I used the print to print it out in the debug window, and the value itself was fine.
When I created an exception case called '_:', all of the cases made of 'match' were against the exception case.... I just plastered it with 'if / elif' and it worked fine.
Is it an engine bug? Not long ago, there was a similar problem. It was to distinguish the number value by 'match', but I couldn't recognize only one number, so the exception case handled it.
I still don't know why this problem happened.
I thought I could complete the option menu if I got a little bit more bite. That's what I usually do, but Devtober does it all October, so I thought it'd be a good idea to rest a little bit for the long-distance race.
If I do what I have to do first, I don't know what to do until I make my next plan, so I'm thinking about doing it little by little and planning ahead.