Apex Legends

Apex Legends players discover hilarious end to Loba’s Execution

Published: 19/May/2020 0:44

by Alan Bernal


Apex Legends players are finding that Loba’s Executions can lead to their untimely demise in the battle royale – especially if their spatial awareness is a bit lacking.

Taken by ‘Yvkarist’ on Twitter, a player wanted to finesse their opponent with the High Society Thief’s acrobatic finisher. The only problem was that they had barely enough space to stick the landing.

The Crypto on the ground was near the edge of the map’s cliffs, with an instant death fall lying mere feet away from his eventual grave. While the game gave plenty of room to execute and walk away, the animation left the player in an awkward spot.

Respawn Entertainment
Loba’s execution is a great way to kill an opponent, given there’s enough room to do it safely.

Moments after, Loba can be seen moving ever so slightly, straight to their elimination and one of the most unfortunate fails to come out of the Season 5 Legend’s gameplay.

“I guess he deleted the game after this…,” Reddit user ‘blitz3nn’ said of the outcome. The play looked near majestic given its setting, but that would soon be the crux of the accidental death.

Just with most other Legend executions, the stylistic movement isn’t just an animation. The character model in the game actually moves, ducks, and even blinks into the interdimensional rift, temporarily affecting the character.

I guess he deleted game after this… (twi/ Yvkarist) from apexlegends

When Loba was done with her victim, the five steps out toward the cliff she took afterward put Yvkarist on the edge. But he didn’t seem to notice before it was too late.

Not long after the kill sequence ended did Loba plummet to her doom, making it a far more memorable finisher that it otherwise would have been.

There’s been instances of executions across titles putting the player in a precarious situation. Modern Warfare had an issue with Ghost’s finisher on Rust at the turn of Season 2.

Sneaking up on an opponent made him pivot toward the back of the opponent, but would result in him falling to his death if it took place near a ledge.

Though Loba’s finisher didn’t cause something quite as heinous as Ghost’s did, Apex Legends players should still pay careful attention to their surroundings if they’re trying to finesse a kill.

Apex Legends

What is code:truck error in Apex Legends & how to fix it? Latest from EA

Published: 2/Dec/2020 1:06

by Tanner Pierce


After Apex Legends received its Holo-Day Bash update, many fans are reporting a brand new code:truck error that’s preventing them from entering the game. Here’s what you need to know about the odd server issue that everyone seems to be getting.

Earlier today, the Holo-Day Bash update went live for Apex Legends, which added in a slew of new content, including some skins and a brand new LTM.

Unbeknownst to players, it seems to have added something else to the game that’s causing a lot of people headaches as they try to log-in.

The Apex community is now reporting a new error code:truck when they attempt to log-in, which is causing some major issues and seems to be caused by the Holo-Day Bash update, although this part is a bit unclear. Here’s what you need to know about the error and if there’s anything that can be done to solve it.

What is the code:truck error in Apex Legends

According to the error messages seen by players, either the game itself or the player is “out of sync with the server.” What that actually means is anyone’s guess.

What we do know about code:truck is that it’s preventing people from logging into the game. It’s affecting a large number of people on all platforms, although the exact extent of this is unclear as of the time of this writing.

Hopefully more information will be available soon.

What can be done to fix the code:truck error?

Unfortunately, there doesn’t seem to be a surefire fix for the error. As of 7:10 EST on December 1, 2020, Electronic Arts and Respawn haven’t released a fix for the bug. That being said, they did comment on the error, saying they are looking into the problem.

Beyond that, however, we have no update as to what’s causing this error for some players, how extensive is the problem, and, most importantly, what the fix is for it.

Over on Reddit, some players are reporting on a few different fixes but none of the them are confirmed. One player reported that they were able to workaround the issue by changing the date and time on their PS4 and few others confirmed its success.

Hopefully a fix becomes available in the near future to avoid it spreading to other people, which would result in the amount of players logging into Apex Legends to plummet.