GTA 5 Cheaters Get The Perfect Punishment With New Patch

GTA 5 players have been using an exploit to get a huge advantage in multiplayer. Instead of removing the exploit, Rockstar Games implemented a hilarious punishment for the cheaters.

The exploit centered around the Duke O'Death, a heavily-armored muscle car available exclusively to players who upgraded from the PS3 or Xbox 360 version of GTA 5. It's supposed to be a single-player-only vehicle; its nearly indestructible chassis and great speed make it too unbalanced for online play.

However, GTA 5 is full of people looking for easy money or gear so someone eventually found a way to get the Duke O'Death into multiplayer. They even figured out how to save it to their garage so they could keep it permanently:

Most developers would just remove the loophole that lets players bring the car into multiplayer. However, Rockstar opted for a more creative solution. Now, whenever players try to enter the Duke O'Death in GTA Online, the car blows up. A video from xKoingWolfx (via Kotaku) shows this poetic justice in action:

Even if you get Mors Mutual to replace your car, that won't fix the problem. Your replacement Duke will blow up in your face as well. Looks like you'll need find a new ride for GTA Online.

This sinister punishment was an unlisted change in Patch 1.1 for GTA 5. This update also fixed the graphics downgrade on PS4 and Xbox One, along with the random appearance changes many players noticed with their characters.

Rockstar's always had a knack for creative punishments. In the past they've also restricted many GTA 5 cheaters' matchmaking so that they can only play online with other offenders. This means they'll be subjected to the same kind of cheap crap they inflict on other players.

I wish more developers took this kind of approach toward cheaters. These players get their enjoyment at the expense of others so why not let everyone get some entertainment at their expense in turn? Maybe the humiliation will be enough to steer them back to good behavior. If not, the developer can then swing the banhammer.