Talk:List of review-bombing incidents

Latest comment: 22 days ago by 2A06:C701:774B:8600:5DE0:3C5:7197:8FAF in topic Entries suggestions for the list

Not really appropriate as a separate article edit

What's needed is to trim down the examples to the most predominate ones, not list every single case, particularly with some of them being low visibility review bombs. Trimming this will allow it to be returned to the main article and make that more comprehensive there. Masem (t) 02:58, 15 August 2023 (UTC)Reply

What would the criteria for a notable review bombing incident be in this instance? NegativeMP1 (talk) 03:36, 15 August 2023 (UTC)Reply
It should be cases where there was actual fallout or impact or changes that were implemented from the review bomb. Stuff like SW Battlefront or Warcraft III Reforged would be starting points. Masem (t) 03:40, 15 August 2023 (UTC)Reply
Agreed. Some of these examples kinda go nowhere. The Titan Souls/Total Biscuit one, for example, feels pretty inconsequential. Sergecross73 msg me 21:47, 15 August 2023 (UTC)Reply
  • Support selective merge back to parent article at review bomb. In its current form, this is an unmanageable list with no particular inclusion criteria. I agree with Masem's suggestion to restrict it to review bombs that actually did something in the real world, but that shorter list can comfortably fit in the main article. Axem Titanium (talk) 20:53, 21 August 2023 (UTC)Reply
  • @Sergecross73 and Cukie Gherkin: who commented at WT:VG#New Articles (August 7 to August 13) about this discussion. Axem Titanium (talk) 20:53, 21 August 2023 (UTC)Reply
  • Neutral on merge, support developing inclusion criteria - I do think it's possible that there's an article here, but I think it needs to be scaled back to more noteworthy examples that show some sort of impact or importance. If no one is willing to develop/implement them, then we should merge. Sergecross73 msg me 21:11, 21 August 2023 (UTC)Reply
Weak oppose on merge, support criteria - I think that having a separate article for this is a fairly decent idea that could make a very good list, but yes, in the current state it is completely unmanageable and needs some sort of criteria. There should be criteria to restrict it to review bombings that had real world impact or were severe enough that the creators of the review bombed product spoke about it. NegativeMP1 21:43, 21 August 2023 (UTC)Reply
  • I think, since WP:NODEADLINE, the thing to do is to develop the inclusion criteria, trim it down here, then revisit once we get a sense of what's left. I think that the criteria loosely proposed above is a great guiding star, but I do note that it doesn't necessarily cover major instances for non-video game media (The Last Jedi being one). Some of the major instances are caught by that criteria (i.e. RT puts up a notice warning about potential bombing), though. ~Cheers, TenTonParasol 23:59, 21 August 2023 (UTC)Reply
  • My major concern is that the first item I checked on this list had factual errors and non-RS citations. - Cukie Gherkin (talk) 01:58, 22 August 2023 (UTC)Reply

Criteria edit

As it is suggested we trim down first, I would like to suggest the following criteria:

  1. Recognize of the review bombing as a review bomb by at least 2 or more quality RS sources (eg not social media posts, not blogs). Only one source saying it was a review bomb would be inappropriate.
  2. The review bombing was for elements not directly related to the game. At the top of this, I would remove all review bombs that are primary related to DRM issues, as that can be covered as a general reason for a review bomb.
  3. There needs to be more to be discussed than just the mere existence of the review bomb. There should be some impact, whether the developer comes back to fix the issues, or address the matter at hand. Overwatch 2 fits here (the company has responded to say how they are moving forward given the review bombs) as well as Star Wars Battlefront II due to the changes EA subsequently made.

I would figure similar rationales could be used for the TV/Film section, though when I read through those, most are those relating to radical social differences in the viewing audience.

Once we've identified which cases to keep and to review for each area, I think we can work to also then summarize the removed cases into at least the main article. Masem (t) 01:43, 22 August 2023 (UTC)Reply

I agree with everything except the first sentence of #2, which I'd like a bit if clarification on. Sergecross73 msg me 03:24, 22 August 2023 (UTC)Reply

Entries suggestions for the list edit

Forgive me if I'm writing it just now, but I want to suggest some more review bombing incidents that wasn't included in the list. There are many that was notably went to become an "off-topic reviews" but I want to highlight some notable cases:

Subnautica, was review bombed on February 2018. [https://www.gamerevolution.com/news/367133-subnautica-review-bombed-dev-fired-hateful-tweets?utm_source=rss&utm_medium=rss&utm_campaign=subnautica-review-bombed-dev-fired-hateful-tweets]

Shadow Of The Tomb Raider, being review bombed on October 2018. [https://kotaku.com/shadow-of-the-tomb-raider-gets-review-bombed-for-going-1829919139]

Night in the Woods and Depression Quest, both being review bombed on August 2019. [https://www.pcgamesinsider.biz/news/69604/night-in-the-woods-studio-and-publisher-cut-ties-with-alec-holowka-over-abuse-allegations/]

Factorio, unsucsesful review bombing incident that happened on June 2021. [https://nichegamer.com/factorio-founder-kovarex-interview-cancel-culture-and-secret-support/,https://steamcommunity.com/app/427520/discussions/11/3055111535923946922/]

Any games on steam that was review bombed on March 2022 for supporting Ukraine during the Russian-Ukraine War. [https://store.steampowered.com/curator/36308017-Review-Bomb-Tracking-Off-Topic/list/91582]

Assassin’s Creed III: Liberation, being review bombed on July 2022. [https://boundingintocomics.com/2022/07/15/ubisoft-to-end-online-services-for-several-titles-revoking-player-access-to-previously-purchased-dlc/]

Doom Eternal, although it was already being review bombed before in 2020, the steam version of it was bombed on November 2022 due to other controversy. [https://www.ign.com/articles/doom-eternal-composer-alleges-unpaid-wages-and-abuse-in-lengthy-soundtrack-controversy-response]

Nexon games on steam, KartRider: Drift; Counter-Strike Nexon: Studio and MapleStory where review bombed on March 2023 as a result of the company taking down the game Dark and Darker. [https://mmofallout.com/2023/03/26/gamers-protest-dark-and-darker-on-nexon-steam/]

Dead by Daylight, another game that was review bombed on March 2023 due to a patch that wasn't recieved well by the players. [https://forums.bhvr.com/dead-by-daylight/discussion/373258/why-are-you-review-bombing-dead-by-daylight]

Shinobi Warfare, while not exactly a review bombing, the case where a steam developer give free items for positive reviews is quite interesting for the list. [https://www.gamingbible.com/news/platform/steam/steam-dev-accused-bribing-players-freebies-reviews-581706-20240321]

and lastly, The Crew Motorfest, with the release of the game on steam just today (April 2024), users where review bombed the game due to the ongoing drama with the first game on the series, The Crew, being taken off from the stores and revoking the licenses for players who bought the game. [https://gamingbolt.com/ubisoft-is-reportedly-revoking-the-crew-1-licenses-for-players-who-purchased-the-game]

I'll admit that the last game suggestion to the list is very recent, and some the sources might be not suitable for the list. However, if some of my suggestions would be eventually made to the review bombing incidents list, I'd be very welcome about it. 2A06:C701:774B:8600:5DE0:3C5:7197:8FAF (talk) 20:27, 18 April 2024 (UTC)Reply

  • What we really need is to trim down the current list given how frequent review bombing happens. Some of these may still be appropriate with that but I would have to check. — Masem (t) 20:59, 18 April 2024 (UTC)Reply
    No problem, i'm appreciating your reply. 2A06:C701:774B:8600:5DE0:3C5:7197:8FAF (talk) 21:31, 18 April 2024 (UTC)Reply