Hello
others as me can’t save games. we have message as failed to save game. maybe your bug is the same than other problem ?
1 Like
I don’t know if it’s a bug exactly but I figured it out just a few minutes ago! The problem was that one of my save slots was at the end of the demo, the page where it says “play again” and stuff, and it wouldn’t save for that reason. All I did was delete that specific slot and then it let me export the save file:) let me know if it works for you!
2 Likes
I just did a pretty significant update to both cogdemos.ink and moody.diy.
On cogdemos.ink:
I pulled the Patreon plugin a short while ago. I was able to connect to my Patreon account after a minor hiccup that I fixed. If you see any issues with it, please let me know.
On moody.diy:
I pulled two changes. The first is an overhaul of how local saves are handled. They will now use indexedDB instead of local storage. The second added some extra logging to the Patreon plugin, so we can better track problems. I want to leave this running on moody for at least a week before pulling it to cogdemos.
To those who have had issues with local saves, please try playing the few games that are on moody and seeing if the new save system works for you and let me know how it goes. We’re hoping that fixes the issue with local saves, even on apple devices.
Next up is a back button… 
Also, we will be taking a look at game versioning or, at the very least, a way to set it up so you aren’t forced to restart a game from the beginning when only minor changes occur to the startup.txt file. I’ve been tinkering with a script that will compare a player’s save file with variables declared in startup to find missing variables.
Not sure where to go from there, so it will have to fall to the dev. I actually wondered if there was a way to force load them into someone’s save file with a default value so they can continue where they left off. Or maybe users to just alter their save files and add whatever is needed so it won’t bomb.
Along with this, I intend to get a load function working so, for sequels, players can load saves from the cog steam save manager at the beginning (if authors want to allow it, anyway). I think it would help with beta testing sequels and, hopefully, minimize release day problems that could’ve been found sooner if saves from the end of the previous game could be loaded.
10 Likes
When I first start a game I always go to settings to turn off page animation. The issue is, after I do that, the “Return to game” button at the top doesn’t work. To clarify, I’m talking about the “Return to game” button near the “show stats” button, not the choice option at the bottom of the page. The choice option works fine.
Minor issue, but something that gets me every time.
2 Likes
I’ll ask the dev about it. I’m sure that’s some front end thing and every time I touch the front end, everything goes to hell.
2 Likes
Ya, whenever you go to settings that return button doesn’t work. Its not been working for a long time, I think I even mentioned it once before
1 Like
Hi I’m the one who had issues with exporting the local storage saves.
Between IndexedDB and local storage option presented on moody.diy, I had no idea which one should I choose to test, so I did both lol.
I tested exporting and importing with 15+ saves on moody.diy. I cross-platform tested for mobile devices and PC.
And I think there’s a thing that needs to be worked on. The order of the saves created via IndexedDB storage gets mixed up.
I tested this on game ‘weeping gods’ and ‘test game’ and ‘the kings veins’, issue happening both on PC and mobile web.
https://imgur.com/RsLRQRb
(since I cannot embed a screenshot, here’s a imgur link to the screenshot😅
As you can see in the screenshot, the order of the saves are mixed up when using IndexedDB storage.
This issue does not occur when using local storage.
https://imgur.com/a/h0FTSAi
Otherwise, it worked like a charm!(at least for me, so far) I can’t wait to export all of my local saves of cogdemos games and try it out on different devices. Thanks for the hard work. I really appreciate your dedication.
2 Likes
hello i have tried weeping gods and king’s veins with the 2 types de saves on mobile and its works ! thanks for your work !
2 Likes
Just a head’s up to everyone. Tonight, I will:
- On cogdemos: pull the newest tested code (the code that is now on moody.diy, with indexedDB saves and more in-depth logging for the Patreon plugin).
- On moody.diy: pull code with back button functionality and sorted indexedDB saves (will test for a week to make sure everything runs smoothly).
Once this is done, I’ll let you all know, but if you notice some hiccups for a few minutes on either server, that’s the reason. I do a full backup of the entire app and db before I pull, just to be safe, and that takes it down for a couple of minutes.
6 Likes
COGDemos is updated now, so indexedDB is a choice for game storage and there’s better logging for the Patreon API (no one cares about that but me until a problem occurs).
On moody, the back button now exists and seems to work. Whoever has a chance, please test it. It seems to work (probably shouldn’t show on the first page of a game, but I will mention that to the dev).
If you see any problems with the back button, please document them and let me know. If you close your browser, then open it and return to the game, it probably won’t work. Same with saves, if you load them (because it’s using your in-memory history to go back). Other than that, it should work.
6 Likes
It’s working just fine and it’s a great feature. I can’t wait for it to be put on cogdemos. Congrats, @EvilChani, you did it!
3 Likes
Yeah ! its works ! Thanks for that ! 
2 Likes
I think I found a bug for the cover image resolution?
The tooltip say a minimum of 320 x 180
But going with that an scaling up will cut off the sides. If you have a cover with a border, for example, the resolution needs to be at least 320 x 213 or 270 x 180.
3 Likes
Hey there Tina! I’m back with another issue, I’m sorry 
I’m having a strange bug with Moody. The same game runs fine on Cogdemos, but on Moody it’s having major loading problems. A couple of readers have complained about it, and in fact, when I tried it myself, the game completely froze after about ten choices:
(Infinite loading here)
Do you have any idea about what could be causing this issue?
EDIT: I just realised that it’s probably related to the *gosub_scene command, so it (mostly?) happens when changing files. In that specific instance where it froze, it has two *gosub_scenes.
2 Likes
Hi!
No need to apologize! Do you mind if I take a look at your code? It’s weird that it works on cogdemos, but not on moody–the only difference between the two, at this point, is the added back button, sort order for indexedDB saves, and some changes to block scrapers on the site (I got DDoS’d on moody, so I locked it down a bit more).
Although, I wonder if that could be causing the gosub issue–it only allows so many requests per second or it blocks them. I don’t think the rate limiting would block multiple gosubs at once, but it might be possible, especially since the rate limiting I have set up on cogdemos isn’t quite as strict.
Anyway, if you have no problem with me taking a look at the code, I can test it on my local machine and try to duplicate it. If that’s okay with you, just let me know which file the two gosubs are triggered in. If that’s not okay, then I can try tinkering with the rate limiting and see if that fixes it.
I will pass this to the dev. I don’t mess with front end changes anymore. I broke it too many times!
Also, I had planned to pull the changes with the back button to prod this weekend, but @Daleko’s problem makes me a bit hesitant to do that (the way the back button handles temporary state saves might be the issue, and it may be bombing due to the gosubs). I’m going to wait until I can figure out that problem before pulling the back button and rate limiting changes to prod.
3 Likes
Absolutely! If you already have access to the files, I think you can quickly test After Dark yourself (otherwise, let me know and I’ll send them to you); you’ll notice the game slows down progressively until it completely freezes at line 855 of the file routeone_1, on the *page_break. Lines 862 and 863 contain two *gosub_scene commands, which can’t be loaded on Moody (infinite loading). However, this issue doesn’t seem to be present in Cogdemos.
Also, please note that I haven’t modified that file in over a month (and certainly not those lines), but the problem seems to have started in the last week.
Thank you for your quick response!
3 Likes
Okay, thanks! I can log into the server and grab the files. It will probably be tomorrow before I can get to it, but I’ll load the game on my local server and see if it has the same problem.
Since the problem started in the last week, I’m certain the update is the issue. I just need to figure out if it’s the back button code causing it or my changes to rate limiting. I’ll let you know what I find. Whatever the problem, we’ll get it fixed! 
3 Likes
I have no doubt that you’ll get to the bottom of it! Thanks again for your help 
3 Likes
hello saves works perfectly but there aren’t in order😉
Again thanks for working !
2 Likes
Hi, will it be possible to change the username and the game title in the future?
1 Like