Hammond is the latest addition to Overwatch who takes advantage of the game’s physics in a way no other hero does. Which can sometimes lead to players using that for a pretty interesting, and slightly unfair advantage.
Hammond’s Grapple allows him to get basically anywhere on the map by swinging around, and one player has figured out a way to contest the point on Nepal’s Shrine stage for over three minutes using a bit of imagination.
So far it’s the only map where this exploit seems to work even though there are other maps, like Hanamura’s Garden stage that present similar opportunities.
The video of the exploit was posted by YouTuber CryBox7, who starts out on the point before shooting their Grapple toward the ceiling and swinging up on top of the center structure’s roof.
From there, they essentially just hang out while simultaneously contesting the point.
Since the enemy team doesn’t have an airborne hero to clear the roof, nobody can really do anything about it.
The opposing side would need someone like Pharah, D.Va, or even a Lucio to get up and knock him down. But since their team’s composition doesn’t have any of those characters, they can’t reach CryBox7, leaving them team with no chance to take the point while Hammond is nestled up there.
Alternatively, the opposition could just pick another Hammond, do the same thing, and make the round go on forever.
As far as we know, this exploit only works on Nepal’s Shrine stage and even then, the team with the player doing it will be at a 5v6 disadvantage every fight.
But that doesn’t matter if the other team isn’t able to get Hammond down, since he’ll just keep contesting the point forever.
The latest Overwatch update has made some key adjustments to both Wrecking Ball and Lucio, along with a huge assortment of Workshop changes to make creator’s lives easier.
Wrecking Ball and Lucio are two heroes in Overwatch that depend on their movement abilities. One swings around with a Grappling Claw while the other sticks to walls to get around the map. Both have been changed for the better in the latest patch.
The October 20 PTR update focuses a great deal on additions to the Workshop, as well as an improvement to networking in Custom Games. However, two big character changes also snuck into the patch notes.
Whether you’re a Tank or Support main, there’s good reason to be on top of these changes before your next session. Here’s everything Blizzard updated in the latest Overwatch patch.
Wrecking Ball’s Grapple Claw should work as intended moving forward.
After accidentally ruining Wrecking Ball’s movement in a September 23 update, Tank players can now rest easy. The new PTR patch has “improved target detection to help with the consistency of connecting to walls.”
Instead of launching the claw and fumbling, you should now be able to grapple around the map as you could before. Given that this change is being tested on the PTR first, there’s a chance things could still be a bit clunky. But expect to see improvements make their way to the live servers over the coming days.
Lucio’s movement is also improved as part of the October 20 patch. The Support hero will now “perform his wall jump boost immediately upon releasing Jump to leave the wall.”
This will be the default option moving forward. Instead of having to manually jump again after leaving a surface, Lucio will now launch forward automatically.
If you prefer sticking to the walls at all times, your life just got a whole lot easier.
If you still want that manual control, however, Blizzard has provided a setting to toggle this off. Ultimately, it should come as a welcome change to Lucio mains. It’s one less mechanic to worry about when gliding overhead.
Last but not least for character changes, Lucio can also cancel wallrides easier than ever before. A simple press of the crouch button will now drop the hero off of any wall without triggering a jump.
Alongside these improvements, Blizzard also included a ton of quality of life updates for custom games and the Workshop.
There is a new ‘minimum latency’ option for private lobbies as the ongoing global crisis forces most competition online. This should result in a more balanced state of affairs for online matches and community tournaments.
Log to Inspector gives a workshop coder the ability to write their own custom logs. This is really useful, because it helps w/debugging. However, logs can be exported, and anything that is exposed to the Workshop can be logged. Which means….Workshop Stats 2/x
Moreover, creators will be happy to see a ton of improvements to the Workshop kit in Overwatch. From new functions to a brand new log with game-changing potential in scrims, there’s plenty to sink your teeth into. You can find the full list of Workshop additions below.
Feature Update: Minimum Latency Support
Competition is at its best when it’s fair. Historically, we’ve run tournament events like the Overwatch League and the Overwatch World Cup with teams competing head to head, in person, with local servers to provide the lowest possible latency and the best player experience.
In today’s world, with so many events and tournaments moving online and teams spread across the world, we wanted to provide a mechanism to ensure that the experience is as fair as possible, regardless of how close the teams are to the tournament’s servers.
The Minimum Latency option sets a target latency for Custom Games, leveling the playing field between competitors whether they’re 50 or 500 miles away. Players with latency lower than the minimum setting will automatically have their network traffic delayed to meet the minimum target, while players with latency higher than the target won’t have any additional delay introduced.
This feature is designed to work with a variety of network conditions, and will generally keep players within 8 milliseconds of the target setting.
We hope this feature will be useful, especially for community-driven competitions that want to Play Nice, Play Fair.
CUSTOM GAMES UPDATES
New Custom Game Maps
Workshop Green Screen
By default, Lucio will now perform his wall jump boost immediately upon releasing Jump to leave the wall, instead of requiring a second Jump press immediately after leaving the wall
Lucio can now also drop out of wall rides by pressing Crouch, which will not trigger the automatic jump
This new setting appears inside Lucio’s settings page as “Wall Jump On Release”
Improved target detection to help with the consistency of connecting to walls
Increased max Workshop Element Count to 32768
Added Type field to Start Forcing Player Outlines
Added Spray options to Communicate, Is Communicating, and Is Communicating Any
Added Sort Order field to Workshop Settings Values and increased the max Workshop Settings Count to 128
Allow Button, Disallow Button, Press Button, Start Holding Button, Stop Holding Button, and Is Holding Button now accept Button Values
Create Beam Effect, Create Effect, Create HUD Text, Create Icon, Create In-World Text, Play Effect, and Start Forcing Player Outlines now accept Color Values and support options for Color Value Reevaluation
Added Black, Gray, Rose, and Violet color options
Added a new option to the Apply Impulse action allowing horizontal and vertical velocity to be modified together (instead of each considered separately) when canceling contrary motion
New Workshop Actions
Log to Inspector
Set Knockback Dealt
Set Knockback Received
Set Environment Credit Player
Stop All Assists
Create Progress Bar HUD Text
Destroy Progress Bar HUD Text
Destroy All Progress Bar HUD Text
Create Progress Bar In-World Text
Destroy Progress Bar In-World Text
Destroy All Progress Bar In-World Text
New Workshop Values
Workshop Setting Combo
Workshop Setting Hero
Update Every Frame
Number of Slots
Last Assist ID
Is Communicating Any Spray
Player Stat (limited to current match stats)
Player Hero Stat (limited to current match stats)
Evaluate Once can be used to isolate a part of a reevaluating parameter and “freeze” it at its initial value. One way this can be useful is when a reevaluating parameter (such as an effect’s position) makes use of a For loop’s control variable. For example, if you want to create a vertical stack of effects that move with a player, you could loop over a Create Effect action using Global.Y as your control variable and “Position Of(Event Player) + Vector(0, Evaluate Once(Global.Y), 0)” as your position (with reevaluation enabled). Doing this, the position of each effect would move along with the player, but thanks to Evaluate Once, the vertical offset for each effect would be frozen to the value of Global.Y when that particular effect was created (instead of the final value of Global.Y when the loop ends).
Update Every Frame increases the rate at which certain values will update. For example, “Position Of(…)” only updates 12.5 times per second, but “Update Every Frame(Position Of(…))” will evaluate 62.5 times per second for conditions and other logical checks and as fast as your framerate for visual output, such as effects and camera. This value can be used to create highly sensitive positional triggers and smooth movement for effects and camera work. Depending on your usage, this value could have a significant impact on server load, framerate, or both, so use it only when needed. That said, executing a single condition or action that contains an Update Every Frame is still much more performant than repeatedly executing an action in a tight loop to try and achieve the same result.
Fixed a bug with Capture the Flag that caused the overhead flag to not appear properly during sudden death
Fixed a bug that caused an animation issue with his Hero Select animation
Fixed a bug that caused Pharah’s eyes to face the wrong direction in her HUD portrait when equipping the Lifeguard skin
Fixed a crash that could occur when swapping the parent/child relationship between two players (using the Attach Players action)
Fixed a bug where Disable Messages was also disabling messages sent from Workshop (e.g. Small Message and Big Message)
Fixed a bug where setting multiple Ability Cooldowns within the same frame could fail
Fixed a bug where the camera override from Start Camera could be overridden from other sources (e.g. emote cameras)
Fixed a bug where Wrecking Ball could leave from ball form even if the Ability 1 and Primary Fire buttons were disabled
Fixed a bug where the user could lose focus when interacting with the Array Value in the editor
Fixed a bug where Set Move Speed and Set Jump Vertical Speed couldn’t set the speed to 0
Fixed a bug where Declare Team Victory could fail in Elimination
Fixed a bug where the Start Camera and Chase Variable actions would not update smoothly at high framerates or during slow motion
Fixed a bug where D.Va and Echo could use their flight abilities to break away from an Attach Players action
Fixed a bug where values with redundant parentheses would fail to paste from text correctly
Fixed a bug where values with mismatched units (for example, a directional vector instead of a positional vector) would fail to paste from text correctly
Fixed a bug where the element count could be higher than expected when pasting from text
Fixed a bug where multiple 0.016-second Waits running on the same player (or the global entity) could result in some Waits taking an extra 0.016 seconds to complete
Fixed a bug where the Phased Out status behaved inconsistently when applied to a dead player (since Phased Out and Dead are mutually exclusive)
Fixed a bug where a Set variable action (not a Modify) would behave incorrectly when a previously-Chased variable was on both the left and right side (such as Global.A = 1 – Global.A)
Fixed a bug where a player’s current health would be incorrectly limited to the player’s original max health between executions of multiple Set Max Health actions