New Warhawk patch coming, Arbiters introduced
The PlayStation Network multiplayer title Warhawk is seeing some improvements by way of a new patch, as well as with the introduction of in-game watchers called Arbiters.
The PlayStation Blog updates us on the upcoming v1.1 patch, coming at the end of October. The biggest fix is to some stats and connection issues that some players were experiencing. Also, the Max Clan limit has been upped from 32 to 64.
Warhawk Arbiters have been put in place to fix cheating issues.
Dylan Jobe, Game Director for Warhawk, says, "We are also responding to complaints about wankers that are stat-padding, griefing or just messing with the Warhawk community in general. This is incredibly frustrating for players and we are not taking it lightly!!"
Arbiters are members of Warhawk's online services groups in both the US and Europe that will be watching over gamers, stats, and leaderboards, making sure that everyone plays nice. They will remain unnamed, but can call out players, sometimes even "rendering judgment." Arbiters can ban players, post comments about them in forums, blast players a warning email, and even wipe a player's stats clean.
Hit the jump for a list of updates.
Setup email comments
* Stat database stability improvements
* Improved server stability
* Max Clan limit changed from 32 to 64
* Viral Rank-up bug fixed and correct for players that were accidentally ranked up.
* “Time-in-Vehicle” Stats fixed so certain awards can now be granted properly.
Client-side updates for Patch v1.1
* Stat connection, fetch/post fixes
* Significantly improved client connection stability
* Quad “????” Ping display bug fixed.
* Added support for Player-Ranked Servers.
* Game synchronization fixes due to fluctuating network conditions (packet-drop).
* Crash fixes for end of game and split screen.
Please report harassment, spam, and hate speech to our moderators
, and flag the user (we will ban users dishing bad karma
). Can't see comments?
Apps like Avast
or browser extensions
can cause it. You can fix it by adding *.disqus.com to your whitelists.