WARFRAME Wiki
Advertisement
WARFRAME Wiki
OrdisArchwingtrailer
“I want more... Operator, please hurry! This story is getting quite good!”
This article is a stub. You can help WARFRAME Wiki by adding a sentence or two.

WARFRAME's network architecture consist of a mixture of centralized and distributed architectural design to facilitate a live-service game that involves gameplay sessions between multiple players in a cooperative fashion. Currently, players are not restricted to playing with others on the same platform (PC, PlayStation Network, Xbox, and Nintendo Switch), but there are still some limitations to cross-platform functionality (crossplay and cross save).

Overview[]

Centralized components of WARFRAME's network architecture include:

Note that centralized components may have distributed systems for redundancy or widespread availability (e.g. there may be multiple Conclave servers, each hosted by a different computer in different locations). Centralization in this case strictly refers to authority.

Distributed components of WARFRAME's network architecture include:

Network Compression[]

The game uses Oodle for data compression of packets sent over network.[7]

Encryption[]

Packets sent to and from WARFRAME services will use OpenSSL.[8]

Ports[]

By default, WARFRAME uses UDP ports 4950 and 4955.[9][10]

Test Cluster[]

Main article: Public Test Cluster

A separate test server exists for testing content and features that are currently not available in the public global build of WARFRAME.

Replication[]

Replication is the process of maintaining a consistent state between the host and its clients. WARFRAME uses a state replication model where clients get their own individualized data packets from the host about the state of the current game session they are in.[11]

Game state may include:

  • Objects such as projectiles[12][13] or item pickups[14]
  • Current reward pool
  • Enemy/NPC locations and activity
  • Player's avatars[15]
  • Player's avatar animations and special effects[16][17]

Patch History[]

Hotfix 31.0.4 (2021-12-21)

  • Added an option to the launcher to disallow the use of network caches (these are allowed by default because they can greatly accelerate updates but on some networks these caches can be misconfigured and cause lengthy stalls in the launcher). The launcher will now restart the update process when changing allowed network caches.
  • Added a workaround for Network Not Responding warnings at the Navigation console when stuck on misconfigured networks.

Hotfix 29.6.8 (2021-01-25)

DTLS Roll-Out

We are testing some new network code out in this Hotfix. Even though we’ve tested it extensively on the Test Cluster we need more coverage!

The primary goal of these changes is to improve networking for Xbox players by replacing some proprietary network code; when these changes make it to Xbox they will enable our automatic proxy service that already helps players with Strict NAT and other network problems on other platforms (this is something we’ve wanted to get to Xbox players for a long time).

The added advantage of this new code is that it should be more secure and more robust on networks that corrupt network packets (we already defend against this to some degree but the new code is more thorough). This won’t make your ping any better but if something is mangling network packets we might be able to avoid it causing bugs in the game.

We’ll be monitoring the roll-out closely and will be able to disable quickly if we encounter problems. Please comment any related issues you have in this thread - thanks!

Hotfix 27.1.2 (2020-02-18)

  • Rewrote how Navigation caches the active session counts to reduce latency and reduce server load (it should now update roughly 5x as frequently).

Update 27.0 (2019-12-13)

  • Improved network protocols to improve matchmaking, presence, and game-invitations in certain Eastern European regions without open access to the internet.

Update 24.4 (2019-03-08)

Client-Authoritative Changes
  • Swapping weapons as a Client will now feel more responsive because we've made it Client-Authoritative.
  • Automatic Doors have been made Client-Authoritative. Previously there were cases of door not opening in tandem with the Host if any latency was experienced.

Update 15.12 (2015-01-30)

Additions:

Network Compression and Congestion Control changes are being made to Warframe! What does this mean for the average player? The tl;dr is that better Network Compression means lower latency during Missions, and a lot less stress on your bandwidth! If you’d like to know more about the technical side of this exciting update, please read the full explanation: here

Strict NAT Improvements:

Strict NAT is a problem that affects a small portion of our playerbase, but for friends that want to play together having multiple layers of Strict NAT can be an issue. Earlier this week (and with more work in this update) we’ve begun to test a solution that will help players suffering from Strict NAT better connect with friends without needing to worry about their own network configurations. For more on this exciting update, please read the full explanation of our NAT testing: here

Update 14.5 (2014-08-28)

  • Added support for the NAT-PMP Protocol in an effort to reduce networking problems. See our Developer Workshop for more information: https://forums.warframe.com/index.php?/topic/298424-nat-pmp/?p=3396439#entry3396439

Hotfix 14.1.4 (2014-08-06)

  • We've made some networking port changes! See here for the official word

Update 11.8 (2014-01-22)

  • Server-side change on 1/20/2014: More frequent Grineer vs. Corpus invasions. Originally invasion system allowed for 2-5 days of downtime, this has been changed to only allow 1-2 days downtime.

Update 11.1 (2013-11-27)

  • Improved networking code to work around the OS delaying network port reuse; previously some users were forced to use arbitrary ports which rendered UPnP or manual port-forwards useless and prevented connections.

References[]

  1. Sokolowski, Danielle (2022, June 6). [PSA] PC Relay, Dojo, Town Hub & Matchmaking Server Maintenance Today @ 2:30 PM ET (Complete). Warframe Forums. Accessed 2022-06-09. Archived from the original on 2022-06-09.
  2. Sokolowski, Danielle (2022, June 7). [PSA] Consoles Relay, Dojo, Town Hub & Matchmaking Server Maintenance Today (Complete). Warframe Forums. Accessed 2022-06-09. Archived from the original on 2022-06-09.
  3. Everett, Megan (2022, October 19). Warframe’s Next Update: Echoes of Veilbreaker. Warframe Forums. Accessed 2022-10-20. Archived from the original on 2022-10-20. "There are a few key reasons why we cannot Hotfix the first is that we are required to pull over every integration needed for Echoes of Veilbreaker to the Test build, which is what gets deployed to the Public server. Once that occurs, we cannot Hotfix without reversing that process, lest we release unfinished content as well. Secondly, we cannot Hotfix or Update once Consoles have been submitted to Cert, as it would mangle the order in which the integrations are organized to go live, which is crucial for Cross Platform Play. Our goal is always to Hotfix all crucial and eligible fixes up to this point before we enter Cert.".
  4. Ford, Rebecca (2013, April 18). Server Upgrades, Complete!. Warframe Forums. Accessed 2022-04-23. Archived from the original on 2022-04-23.
  5. Miner, Glen (2015, January 26). Strict Nat: Improvements And Testing. Accessed 2022-04-06. Archived from the original on 2022-04-06.
  6. Miner, Glen (2015, March 26). Distributed Nat Proxies. Accessed 2022-04-06. Archived from the original on 2022-04-06.
  7. Siniło, Maciej (2015, January 26). Network Compression And Congestion Control. Accessed 2022-04-06. Archived from the original on 2022-04-06.
  8. (2022, August 11). PSA: OpenSSL Connectivity Issues. Warframe Forums. Accessed 2022-08-11. Archived from the original on 2022-08-11.
  9. Miner, Glen (2014, August 6). New Network Ports. Accessed 2022-04-06. Archived from the original on 2022-04-06.
  10. Digital Extremes (n.d.) . The Warframe network analysis tool detected a problem with your network. Accessed 2022-06-09. Archived from the original on 2022-06-09. Error message page when there is an issue with client's network.
  11. Siniło, Maciej [Digital Dragons] (2017, June 13). Maciej Siniło: Networking Architecture of Warframe. Digital Dragons. YouTube. Accessed 2022-04-06. Archived from the original on 2022-03-08.
  12. "Changes to weapon projectile logic. The motivation of this change is that we want weapons like grenades that explode to end up in the same spot on host and client (in sync) without having the traditional delay of a replicated projectile" - Update 11.5 (2013-12-19)
  13. "Fixed Corpus Mine Osprey mines and other replicated projectiles affecting across Limbo’s Rift on Clients." - Hotfix 15.0.5 (2014-10-27)
  14. "Fixed Scintillant sound not being replicated for Clients, resulting in Clients not seeing Scintillant and thus inability to obtain it." - Hotfix 29.5.6 (2020-12-01)
  15. "Fixed a crash that could occur if a non-replicated avatar (ie. Mirage Clone) was affected by a friendly buff." - Hotfix: Specters of the Rail 0.1 (2016-07-08)
  16. "Fixed Ivara’s Navigator cast animation not being replicated between Host/Client, resulting in no sound or movement." - Hotfix 27.0.12 (2020-01-23)
  17. "Fixed Host Revive FX being replicated for Clients." - Hotfix 25.7.5 (2019-09-09)

Further Reading[]

See Also[]


Advertisement