[Update: Kotaku has obtained a report from the Classification Board which spells out the specifics of the decision -- an Alien Anal Probe weapon and "alien narcotics" -- and led to this fine sentence: "In the Board’s opinion, a weapon designed to penetrate the anus of enemy characters and civilians constitutes a visual depiction of implied sexual violence that is interactive and not justified by context and as such the game should be Refused Classification."]
Even with the existence of the R 18+ rating, Australia's Classification Board has decided against classifying Saints Row IVwith an age rating. According to the board, the decision had to do with "interactive, visual depictions of implied sexual violence which are not justified by context. In addition, the game includes elements of illicit or proscribed drug use related to incentives or rewards."
"Deep Silver can confirm that Saints Row IV was denied an age classification in Australia," begins a statement provided to Destructoid. "Volition, the developer, are reworking some of the code to create a version of the game for this territory by removing the content which could cause offence without reducing the outlandish gameplay that Saints Row fans know and love. Saints Row IV has been awarded PEGI 18 and ESRB M ratings where fans can enjoy their time in Steelport as originally intended."
You know, of all the games that could have been the first to not get an age classification, it would be Saints Row, wouldn't it? Shame for Australian gamers.
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.