That’s…irritating lol.
The smPlugin is what’s causing the error.
smPlugin is the plugin used on dashingdon for saves. It is not used on cogdemos, so it needs to be removed from startup.txt before being uploaded to cogdemos. Once you remove it, that error should be gone.
Explanation: smPlugin requires a server side load of the plugin for the plugin to operate. Unfortunately, the plugin doesn’t work with the new code–we are working on getting local saves next, at which point players can save locally in lieu of logging into the site and saving to the server. Even then, it will not use the plugin, so any code uploaded will need to remove the reference to smPlugin in startup.txt.
3 Likes
I looked at my start up file for DoH on CoGDemos and the code that looks for the plugin is behind a comment, so that would be odd to trigger.
*comment *sm_init DawnOfHeroes | 6
I can remove it, but I have a feeling that it won’t resolve this issue they are having with my demo.
Do you mind if I grab your files and set it up in a hidden game under my name to test?
(it will have to be later this afternoon–I’m working and can’t step away for a few hours)
And thanks!
Permission granted
1 Like
Hey, again I can’t play any Game in this new Moody. it caamm an error message. It says we Apologize Try again or later. If I do refresh the Page it fix nothing.
does any one have the same Issue? If yes how I can make it work. another thing when I’ve writting here inthe past. I manshioned that they are allot of good Games from the old Moody I like to play it again here in this new one. Thats what I ment befor because I cant find thim in this new one. Thank you so much
1 Like
In testing, I’ve found the following:
- You can save without a problem until you go to the stat screen.
- Once you go to the stat screen, then return to the game, the next time you try to save, it throws the error.
- If you go to a different game and load it, go to another screen, then return to your game, saves work as they should… until you go to the stat screen again.
- It only happened on the prologue and chapter 1–I haven’t been able to get it to trigger the error once I hit chapter 2 and beyond.
- I had a save near the beginning where I ‘died’ (I was just randomly making choices) and, after that, when I tried to go back to a previous save, I still landed on the “play again” screen where I was dead (I did save there, but I restarted!). After going to another game and coming back to yours, I deleted my save on the ‘play again’ screen and was able to proceed with the game, but still had the same issue when trying to save after going between the stat screen and playing the game.
- @Havenstone’s game has the same issue at the beginning of the game, but not further into it (at least I haven’t been able to trigger it).
I’m going to look at it some more tonight and see if I can troubleshoot. If it was consistent throughout the game, I could understand it, but once I figured out how to trigger it (save, go to stats, go back and try to save again), I figured it should always trigger.
I’ll get it fixed. Please be patient while I try to figure out what’s causing it.
And you’re going to cogdemos.ink? I haven’t seen this issue before. Also, what browser are you using? Do you have javascript enabled on your browser?
6 Likes
I don’t think this is it. Yet another reader wrote in with the same problem, and they’d tested much more extensively.
Anonymous bug reporter wrote:
No matter what the restart menu comes up and no matter what you do you have to restart. If you load a save made before the prompt you just get the prompt again (even if it’s on the prompt screen or before it). Restarting from that prompt does seem to make it work for a little bit but the prompt returns. I have tested this 7 times and I have yet to be able to make it to the end of the [demo] without it coming up eventually. You get a little more each time you restart but you HAVE to restart.
So I think this is a more serious problem than just site maintenance happening. Especially since now a lot of people are reporting experiencing it in different places/at different times.
2 Likes
You know I had my problems with Moody but at least it was functional and easily navigable.
Even once it switched to cogdemos it was fine until recently when the front page changed to not have the games in any sort of coherent order (and no way to sort) and suddenly saves don’t work if you ever open the stats screen once?
Hello, I use Google Chrome.
I don’t mean to be rude, but I am single-handedly taking care of cogdemos. I pay for it out of my own pocket, and I spend my free time trying to get it working for everyone with the newest version of choicescript. I have one person helping me with the coding, and I am paying him from my own pocket.
I understand the complaints and I am addressing them as I can. I have a full-time job, a husband, an elderly mother, and a dog to take care of, in addition to dealing with this. So I would appreciate a bit of consideration for the fact that I am doing this without asking anything from any of you.
I will also add that I asked for beta testers before pushing this to production. I got one, and that’s it. In essence, this is the official beta test, since no one saw fit to contribute and try their games out on the test site I set up.
Bottom line: if you don’t like cogdemos.ink, don’t use it. I will get it fixed as soon as I can. Until then, complaining helps no one and only serves to irritate the single person you have trying to get it running.
Good day, I have to get back to work.
Edit:
Just FYI… the site may go down temporarily. I believe the problem with the stat screen error is fixed. Tested on my home server and it worked. About to push to prod, but it will likely be unavailable for a few minutes while I set it up.
20 Likes
I believe the problem with saving after looking at the stat screen is fixed. @Dvalor53, I tested your game after pushing up the fix and it is saving now after I go back and forth to the stat screen.
I did delete my saves before trying it, because I think my saves were all hosed from what I was doing last night while testing. If you see the issue again, please let me know.
As for the problem where people are being thrown to the “play again” screen, it’s going to take longer to figure it out. I got it once while testing @Dvalor53’s game, but haven’t seen it elsewhere. If anyone knows somewhere it’s happening consistently, please let me know. Until then, the next project is local saves and sorting options for public games.
10 Likes
Thanks for all the work; please take your time. I really appreciate having somewhere to host things that’s being looked after. 
7 Likes
You’re very welcome, and thanks for letting me know it’s something you’ll find useful! I do want to make sure it’s running correctly and is stable as soon as possible, though. I don’t like it when things aren’t working as they should. I’m doing my best to make sure that happens, but it’s normal to have bugs after recoding a project like this one. It’s just a matter of finding them and fixing them, and for inconsistent problems, that isn’t easy to do.
7 Likes
1 Like
Sorry to bother you again, but errors keep popping up. There was an update to my game (CoGDemos) and people keep getting this error in the new content:
Which is usually an old save error. But the problem is, they get it even when they start from the opening page. Again, hitting restart seems to solve it. The achievement errors that I wrote about before are still being reported to me, with different achievements this time and I couldn’t replicate those. Hitting restart solves those too, maybe, but I can’t check because the error didn’t come up for me when I tried.
I know nothing about websites, so I have no idea if this is still a browser cache issue or not, I just find it weird that no other game seems to be experiencing these 
(although I’m very glad that at least I’m not getting the replay error). Anyway, just wanted to let you know in case it’s something you wanted to be aware of, and thanks for all your hard work! 
Btw I really like the new design, and I LOVE that the new update date shows up under the titles. Love it.
1 Like
I will take a look at it and see if I can figure out what’s going on. It may be Monday before I get to it, because I’m going to be busy tomorrow.
One good bit of news, though…
While sitting around tonight, I ended up adding a sorting option for the public games page. The guy handling the bulk of the coding hasn’t seen it yet, so it’s not merged into master yet, but it seems to be working well.
So right now, prod is running off that branch. I figure I’ll leave it for a day or two, and give the programmer a chance to check my code before we merge it. Let me know if you see any issues with the sorting.
Also made the titles clickable @LiliArch .
7 Likes
Yay!
Thank you so much and no rush! The errors at least aren’t game breaking 
One thing I just remembered and maybe you would find it useful info, is that when I first uploaded the game to the cogdemos website, the whole chapter1 file was already finished with all those achievements that are now getting the errors, with no problems back then (the game has been tested on dashingdon previously). So the new saves after the website update shouldn’t have affected those because there is no old save or an old file where the achievements haven’t been set yet (or at least not on this site. The old files are all on dashingdon). I also deleted my browser’s cache after the website update, and I still managed to get the achievement error once after it, hence why I’m unsure if this is a cache issue or not. Like I said, no idea what’s going on, and I’ll be very grateful if you find anything, but no rush, the game is still playable as it is after a few restarts.
I checked the sorting and it works (and YAY, SORTING!!!) but when I sort by update, the dates are… off? Maybe it’s just because the dates of the individual games haven’t all been updated after the new setup? It looks impressive, everything you’ve done in such a short time, it must have been a massive work. Hats off to you, seriously.
EDIT:
~gasp~ Guess what:
I got it again! Here is what someone wrote to me yesterday about the error: “I noticed they happened if you load a save that occurred before the achievement was about to be earned, then when you achieve it again the error pops up. For example, if you save when certain character appears, keep reading until any point, then reload that save and go through the path again that earns the achievement, the error comes up.”
I tried this yesterday and I didn’t get the error. But right now, when I opened the game again, it started straight with an error message. (sorry for the awfully long post, I just got excited when I saw the error just now)
1 Like
Thanks. I passed it along to the guy who’s doing the bulk of the coding. He said he thinks it’s because he was using the interpreter from the old moody site (he just adjusted it to account for the new features in choicescript). He’s going to rewrite the interpreter from scratch to get the problem resolved. It may take up to two weeks, so please be patient with the achievement issue.
Also, he mentioned to me today about implementing a versioning system for both the games and saves, so save compatibility could be tracked between game updates (and authors can better track their changes between versions without having to create another game to back up their previous version). Is this something you all think would be helpful?
Also also… he’s done with the coding on the local saves. I just need a couple of days to test functionality and security before I upload it to prod. If all goes well, that should be available in prod by Thursday or Friday.
1 Like