
Sucker Punch Productions studio head Brian Fleming has spoken publicly about the dismissal of developer Drew Harrison, who was fired following a social media post referencing the assassination attempt on political commentator Charlie Kirk.
The controversy began when Harrison, a nearly decade-long employee at the PlayStation-owned studio, wrote online: “I hope the shooter’s name is Mario so that Luigi knows his bro got his back” on the day of the incident.
Less than 24 hours later, she confirmed her termination, with Sony stating at the time: “Drew Harrison is no longer an employee of Sucker Punch Productions.”
In an interview with Stephen Totilo’s Game File, Fleming addressed the matter directly. “The facts are accurate. Drew’s no longer an employee here. I think we’re aligned as a studio that celebrating or making light of someone’s murder is a deal-breaker for us, and we condemn that, kind of in no uncertain terms. That’s sort of our studio, and that’s kind of where we are,” he said.
The situation has fuelled debate across social media and YouTube comment sections beneath trailers for Sucker Punch’s upcoming PlayStation 5 release, Ghost of Yotei.
Some commentators, including Mark “Grummz” Kern, have called for further scrutiny of employees across the industry who engaged with or shared Harrison’s post.
Other publishers have also faced backlash. Bethesda deleted a post featuring a clip from Indiana Jones and the Great Circle after some interpreted it as mocking Kirk’s supporters.
Microsoft similarly confirmed it was reviewing employee activity, with a spokesperson stating: “Comments celebrating violence against anyone are unacceptable and do not align with our values.”
Despite her dismissal, Harrison shared support for her former colleagues, writing: “Sucker Punch is amazing & one of the last few bright shining lights in the game industry. I still support them and I cannot condone any animosity directed at them.”
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ