Wouldn’t need to remove anything from the title, I’d think. It’s just about how the code generates the url (and it needs to be able to deal with this kind of thing anyway) and what the current folder name is in relation to what the code wants it to be.
You can leave the title as is–all I changed is the link, and now the link on the public listing works correctly. The link is:
https://cogdemos.ink/play/viisbae/the-bureau-halloween-special-witchy-woman
Edit: Just so you know what I did… I renamed the game folder so it only has one dash, and changed the link in the game table of the db to reflect that. Once I did that, it worked.
One thing I noticed, by the way - you can’t play a game from the list by clicking its title, you have to hit the button. Which means I keep hitting the title half a dozen times and wondering why nothing happens before I remember. 
Is there a reason for that?
Organization, more than anything else, but I can change it and make the title clickable as well. Give me a day or two and I’ll get it changed and test before dropping it into prod.
2 Likes
Hi, sorry to be a bother, but I’m getting the exact same problem as VilsBae had earlier, with both the public version of my demo and the one I use for private alpha testing and such. Is there a general fix for this? I don’t think the link has too many dashes in it or anything.
ETA: never mind. I’ve found the solve, I think.
2 Likes
I had to remove my bookmark and save it as a brand-new link to get everything to work as far as reaching the home page.
In case someone still is having issues.
1 Like
I’m not sure if this is related to the website or not, but some people started getting an error message that an achievement is not defined in the game. When I checked, the error didn’t come up for me. There is no error in the quicktests and randomtests either, only in some people’s playthroughs on the website. Can’t be an old save problem because saves had to be restarted, and there was no change in the code since then. I reuploaded the game files again, but some people are still getting the error. Could this be related to the new website features?
Edit: Okay, the error comes up now no matter what. The entire game won’t start because of it.
Edit 2: cancel previous edit. The problem is with that one achievement for some reason and when I achieve it (which I did in a playthrough to check if the error comes up) the error didn’t come up for me during the reading, but it comes up now when I try to play the game again. Not sure how much sense this makes sorry, but the problem is not in the code itself. Could this be a cache error?
It could well be a cache issue. Is the game you’re seeing this on public? If so, can you send me the link so I can play test to see if I can reproduce the problem?
https://cogdemos.ink/play/jc/weeping-gods-public-demo
It’s public. So far, it only seems to happen with one achievement. This is the error message: Chapter1 line 11154: the achievement eagleeyes was not declared as an achievement in startup.
Several people wrote to me about it, but it doesn’t seem to happen every time. I got the error message earlier today but now when I replayed it, it didn’t happen. Kinda weird.
I did not get that error once in my playthroughs, must be some error when the achievement is triggered
That’s what I’m saying, that it doesn’t happen every time, and I’m not the only one getting it because more than one person wrote to me about it.
So I went to check, and when I earned the achievement in-game, the error didn’t trigger for me. Then it triggered randomly when I opened the game hours later, on the opening screen. I refreshed the page, the error was still there. I canceled the error message, restarted the game, the error went away.
That’s why I’m not sure what’s causing it because it’s not an error in the code, otherwise it wouldn’t behave like that, and the quicktests and randomtests would’ve caught it. (also, I didn’t change anything in the achievement parts of the code in the past few weeks, and this error only started popping up now after the maintenance). I’m thinking it might be some redundant ghost bug in the browser’s cache that appeared after the website maintenance. If ignoring the error message and restarting the game can solve it, then I’m gonna tell the others to do so, I’m just not sure if it only solved it temporarily, or permanently, because I have no idea what caused it in the first place
Didn’t that happen with beta testing the new code too…?
But random errors that happen sometimes and sometimes not are really hard to debug because they don’t happen reliably so it’s really difficult to find what’s causing them, unfortunately.
Ja also on my side…
But because of this 
I personally just chucked it out as a cache issue and the fact that I didn’t access the page in a while.
Once clearing the cache that error didn’t pop up… I wonder though, are we all using chrome? Because read somewhere above that someone solved all their errors by using Firefox. (Maybe it stores cache differently)
I’m using Opera, but when I tried it in Firefox, the same error popped up. And this happened AFTER I cleared my cache. So, yeah, I don’t know. But canceling the error message and restarting seems to make it go away.
1 Like
I think this might be a new issue; at least, I hadn’t noticed it upthread.
I have people playing a demo who say that, in the middle of their playthrough, they’ll seemingly randomly get the ‘play again’ screen. They haven’t reached the end (one had only just left startup.txt, whereas for another it was much later on).
This does not happen to the same people in the same place, either—the one who got the early restart went back through to the same place and was able to continue normally, which (along with the instances of other people, including me, being completely fine upon testing this), means I don’t think it’s any error in the code on my end.
1 Like
That sounds like either server maintenance or site updating; both of these interrupt current play sessions, regardless where the reader is in the game.
(Sigh) Game’s too big to have saves somehow not working on both sites.
On cogdemos I get “game can’t be saved on stat screen” no matter what and on dashingdon it says like “error” or whatever
Yeah, I know that. 
If you save on the stat acreen in dashingdon it causes an infinite stat screen loop. I said on COGDEMOS it says this:
As you can clearly see in the background I’m not on the stats screen
Here’s what it says on dashingdon:
@HarJa –
I combined the two posts and moved it here, so @EvilChani sees it.
Hopefully, she will be able to assist further.
1 Like
Okay, thanks.
For cogdemos I think it’s a bug that once you visit stat screen, you can’t save despite having having gone to a new page. I had to log out and log in back to fix this issue
1 Like