FANDOM


Warn blue
This article needs some work!

This page's content has been marked for improvement. Help us out by improving it!

The /b/ incident/raidings refers to a failed series of raidings on July 15th 2014 apparently set up by the /b/ board on 4chan against ROBLOX. Many OT'ers thought that they would eventually get to the ROBLOX forums. However, it seems the mods succeded in banning all raiders and the raids failed.

One of the supposed raiders made a now deleted HQ on the raiding account "xXswagboy420Xx"

It Was An Inside Job

One thread on OT suggests that the whole thing was actually done by someone who also forumed on Off Topic, who somehow convinced /b/ to be his/her personal army and raid ROBLOXl. The OP of linked thread also posted a thread by an OT'er saying that he/she posted the raid thread on /b/.

The thread at the top is now deleted.

OT's Reaction

The whole situation generally freaked OT out, with the front page being filled with threads about 4chan for a while. Some people were freaking out over the whole thing, while others said that "4chan couldn't even do anything".

Major Incidents & Raids
OTermination Sep. 25th 2013 / Day 1Day 2Day 4Day 5
Group/Place Raid YES! MagazineStarbucks DescriptionStarbucks CopyrightFrappeFEAR
3 Restaurant GroupsRSF & Electro LegionPinewood CoreYummiez
ROBLOX-Related April 1st 2012Forum 49Extra-Life StreamTNL Porn-site HistoryHQ "Bomb Threat"
OT Chatroom CuteGirlDeputy U.S. Marshal Mark Elder
Flamewars CyanmareSuicide GirlOTDinosaurLolerisForumGameROBLOX+
RT BronyBernie SandersAkrylix & Dtownboy
Mass Trolling/Fads Zayn Did 9/111b4Ilovemom11111LockedServerSmiley Virus
Tiger War 2014Tiger War 2015Russian Bombing
Raids on OT C&G Otaku Raid2014 Purge/b/ (4chan)2015 SpambotsiPad Bots2016 Spambots
Groups/People Bulban EmpireAir CannonWinVariablexxKaitlynBoostmoji

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.