If you appreciate the work done within the wiki, please consider supporting The Cutting Room Floor on Patreon. Thanks for all your support!

Bugs:Blocksworld

From The Cutting Room Floor
Jump to navigation Jump to search

This page details bugs of Blocksworld.

So very stubbly.
This page is rather stubbly and could use some expansion.
Are you a bad enough dude to rescue this article?

Hoo boy, get ready for this; Blocksworld is quite a janky mess of a game. This page documents (as of now) most bugs and oddities in the game.

Error 505

Error 505 was a bug first occurring around March of 2019 and again in October of the same year. Error 505 was simply a server outage that prevented players from uploading worlds or viewing the home page. The first time that this server outage occurred had gone on for a week, and then later in October it would last until the game's eventual discontinuation in July of 2020.

Lose message bug

This bug is only present on the Steam version of Blocksworld. If you trigger the Lose script in a published world (without restarting it), the message will still show up on the front end and will only go away once you reload the same world or play another.

Retrieved from "https://tcrf.net/index.php?title=Bugs:Blocksworld&oldid=1513865"