Events/2019 Shutdown: Difference between revisions

From Blockate Wiki
m
1 revision imported
(Created page with "==frame|A photo of the Blockate game page.The Shutdown of Blockate == September 18th 2019, Blockate was put under review by ROBLOX administraitors fo...")
 
m (1 revision imported)
 
(41 intermediate revisions by 22 users not shown)
Line 1:
{{Event Infobox
==[[File:Blockatesnap.png|frame|A photo of the Blockate game page.]]The Shutdown of Blockate ==
|title=Blockate 2019 Shutdown
September 18th 2019, Blockate was put under review by ROBLOX administraitors for an unknown reason. It took about 6 hours until every player left.
|image=Blockate Shutdown.png
|caption=An image of the game being unable to be played
|date={{date|month=9|day=18|year=2019}} - {{date|month=10|day=1|year=2019}}
|effect=*Blockate temporarily unable to be played
}}
 
==Overview==
[[Blockate]] was put under review by Roblox administrators on the {{date|month=9|day=18|year=2019}}. This is known as the 2019 shutdown. Blockate came back on {{date|month=10|day=1|year=2019}}. This was caused due to many users putting Discord server invite links in their worlds, and creating inappropriate builds.
 
==Effect==
The effects this had was that Blockate was unable to be played during the period it was down and Halloween Event Submissions were extended to the 15th of October.
 
{{EventNav}}
 
[[Category:Events]]
 
 
==Speculations and Theories==
Many users suggested that Blockate was shut down for being a copy of Blocklr or for just being too similar to ROBLOX, these claims were radical and not very crediable.
 
Another theory is that Blockates head developer (Fox/Fewks) had broke ROBLOX TOS and got Blockate shutdown, this theory was also not very credible. 
 
The most credible and believable theory is that the player-base has caused the shutdown, with many users thinking they were funny by building "items" that were against ROBLOX TOS, or most likely, the use of Discord Links.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.