• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

1.30.3 PTR caching?

Status
Not open for further replies.
I'm not sure exactly, but it's highly likely that WC3 caches a lot of data internally in-between game sessions. This is probably an artifact of older times to cut down on loading time, to avoid having to read all the game data from the MPQs each time you start a map.

In particular, I think object data stored in SLKs is cached. A side-effect of this can be seen when a widgetized map corrupts said cache, which leads to subsequent desyncs in future games if the game is not restarted.

There are probably several more types of data that is being cached, and subsequently somehow corrupted or miscached inbetween game sessions, which leads to differing data in game clients, which in turn leads to desyncs.

It however doesn't explain desyncs that occur on a fresh start on WC3, and those still happen from time to time (I've tested this numerous times with friends). Perhaps, there's a semi-random factor to this, due to a programming error that also corrupts caches.
 
Status
Not open for further replies.
Back
Top