im umm probably stupid or something but im getting an error code whenever i open the game and the game itself just wont open umm
sorry !
############################################################################################
ERROR in
action number 1
of Alarm Event for alarm 0
for object oEvent:
ds_list_size argument 1 incorrect type (undefined) expecting a Number (YYGI32)
at gml_Script_LoadPrefsInstances
############################################################################################
gml_Script_LoadPrefsInstances (line -1)
gml_Script_LoadPrefs
gml_Object_oEvent_Alarm_0
i think i saw someone else mention this but im like stupid or something
Looks like your game is having trouble accessing the write folder. Can you check if you can find the /AppData/Local/Debucon folder?
If you can't find it, something might be preventing the game from writing files on your computer, which is what would be causing the error. If you do find that folder, I'd need to take a look at the UserSettings.ini file that should be in there.
You don't have to make one, the game should take care of it as long as it has the rights to write in your AppData/Local folder.
You'll have to find what's preventing the game from writing to that folder, I can't provide much help with that since the issue is on your side. You can try running the game as administrator to see if it changes something and check if your antivirus isn't blocking it.
Wait a minute, that's not your first time running the game, right? I can see you commented a few month ago.
Are you sure you can't find that folder? The AppData folder should be located in C:\Users\[your windows username]\, it's a hidden folder. If you have already successfully run the game, the folder should exist, but the UserSettings.ini file is probably corrupted. Once you've located the folder (ask google how to find the AppData folder if you're having trouble), navigate to AppData > Local > Debucon and find the UserSettings.ini file. Open it with notepad/notepad++/your preferred text edition software, and copy its content here. We'll figure out how to fix it.
I'll look into implementing a foolproof in-game fallback solution in case of corrupted save files. It should be a rare occurrence, but better safe than sorry.