Urgent.News

What's breaking now, across hundreds of outlets.

Tech

GTA 6 The End of the Road: Should you swim for it, or choose no surrender?

A choice (or two!) can lead to drastically different endings.

GTA 6 The End of the Road: Should you swim for it, or choose no surrender?

This story explores the various endings of Grand Theft Auto 6, specifically the final mission, The End of the Road. The mission features a choice between "Swim for it" and "No Surrender." If the player opts for "No Surrender," Jason and Lucia choose to shoot their way through a police roadblock, ultimately getting shot and killed with their hands still clasped. Tomas is then seen living a happy life with Lucia's sister and her family.

Choosing "Swim for it" leads to another set of choices. If Lucia follows through with the plan, she can either jump off the bridge with Jason or follow the prompt to exit the car. If they jump together, Jason gets arrested while Lucia obtains a deal that keeps him free, resulting in Jason meeting his son through a glass barrier. If Lucia remains in the car, both characters are shot dead.

The third "Swim for it" choice occurs when the player delays a mission until a $2 million savings deposit is made. In this scenario, Lucia uses the money to free Jason from prison, and the two meet Tomas, who holds his hand during the credits. The source article mentions there are other endings not involving these choices on the bridge.

Rewritten by urgent.news; may contain errors — check the original.

Source: pcgamer.com

Read the original at pcgamer.com →

Report a problem with this story

More in Tech

Why a no-signup Arabic chat room still beats an app in 2026

Most chat products in 2026 start with a 40MB download and a phone number. For a large group of users that is the whole problem: they want to talk for ten minutes, not create an identity.

  • No-signup Arabic chat room offers quick access for users
  • Lightweight mobile page outperforms app downloads in 2026
  • Privacy-focused design prioritizes Arabic-speaking communities

Day 34: a useful reply, no new paid work

Wye Co is an AI-run studio. This is the daily log of trying to land its first paid assignment without owner-funded capital.

  • No new paid work inquiries on 34th day of Wye Co's journey
  • Two unanswered eligibility questions from previous day
  • AI-disclosed reply to builder peer recorded but not new paid work

Nginx 504 Is a Read Timeout — Debug It Along the Request Path, Not in a Random Order

When a 504 alarm fires at 3 AM, the instinct is to grep the backend logs, restart the service, and bump the timeout. I've watched this loop close the ticket without fixing anything.

  • 504 error indicates upstream never sent data before proxyreadtimeout expired
  • Six root causes of 504 error occur sequentially along request path
  • Most common cause is misconfigured timeout at 40% of cases

More from Sunday 22 November →