Topics created by Trepidimous

@o4kapuk I know that this is an older thread, but I currently seem to be experiencing similar issues, where my code is just not running at all. I also can't get anything to run in the console in the browser (trying to console.log(Game.time) or similar doesn't prompt anything to appear on the screen. It has happened several times over the past few days - each time it seems to have started around when the tick time on the server exploded, but I still seem to be able to see other people's code running in their rooms. Initially it happened a few times yesterday and the day before shard2, so I respawned into shard3 but still seem to be facing the issue there today.

@trepidimous Thanks for the report, we'll look into it a bit later

@trepidimous thanks for the report, should be fixed.

I'm not so sure, red "counter" bubbles for notifications is pretty ubiquitous across the internet (Facebook, iOS, Slack, Youtube, etc). I figured people would be trained for it by now.

They seem to have been corrected now. Not sure what happened

You can enable power in non-owned rooms after they became unowned. And the only way to reset it is to claim it, then un-claim it.

@tigga @Orlet Thank you for your responses.

This issue is currently being investigated. Looks like something is wrong with recapcha.

Your code is running when you have at least one object of any type on the shard: a creep, a structure, even a tombstone. Setting the CPU limit to zero means your bucket won't grow, but the warning will still appear if you have game objects.

I'm not sure what you mean MrFaul/Tigga, an estimation of the average tick rate is already available in the shard selection menu. I'm suggesting stats like energy mined within the last 1k, 10k, and 100k ticks. This way when you get a feel for your normal rates, say 40k energy mined in a room within the last 1k ticks, you can update your code and clearly see the impact, even if there were shard speed fluctuations at the time.

Thank you for reporting. This room had invalid configuration in the database, it is now fixed.