Keep getting Game Error... about salien-bot HOT 14 CLOSED

This is an issue with Steam's servers and not with this userscript.

from salien-bot.

Except for the fact that when I disable the script the game loads just fine. It's only happening when I have the script enabled.

from salien-bot.

This is the error in the chrome dev console window
https://i.imgur.com/09ucZ2X.png

which seems to only happen when I have your script enabled, if I disable the script nothing ever pops up in the console window..

from salien-bot.

Because the script is automatically trying to start the game, that error is because the games API is returning a 500 server error. It has nothing to do with the script.

from salien-bot.

Yep figured that out now, the script is broken for *monkey ways, have to manually click play and go to an world and open console and use it that way otherwise it'll just always throw the error and require page reload on a constant loop.

from salien-bot.

It's probably because the script only works if the url has play/ at the end.

@meepen this line should probably be changed

to something like

 // @match        https://steamcommunity.com/saliengame/play
 // @match        https://steamcommunity.com/saliengame/play/

from salien-bot.

Can confirm that doing the above works so I'd suggest making the change above @meepen

from salien-bot.

I fixed this in a PR, make sure you update your script.

from salien-bot.

I still have this, even with v3. It doesn't show the dialog anymore, it's just stuck in a loop refreshing the page.

from salien-bot.

for some reason the merge thought it was just another line added instead of changed?
fixing now

from salien-bot.

@meepen the merge was correct, there was supposed to be a // @match https://steamcommunity.com/saliengame/play and a // @match https://steamcommunity.com/saliengame/play/ both of them. There wasn't a removal at all just an addition.

from salien-bot.

oh whoops
sorry im new at this

from salien-bot.

Sorry, I should have been a bit more clear in the pull request I made.

from salien-bot.

This still happens to me both in firefox with violentmonkey and chromium with tampermonkey, the solution in #16 (comment) works, maybe adding it to the readme would be a good idea as a workaround.

from salien-bot.