Client Asset Cache

* See also Client ( Player's Machine )
* See also Server ( Game Companies Machines )
* See also Graphics_and_Rendering
* See also Game_of_this_type_-_Difficulties
--- --- --- --- ---
A file system on the Player's Client machine, containing game Assets transferred across the Internet connection.
The files would get saved and updated automatically and prevent requiring constant re-transmission.
A good part of the game's data would be Templates used in On the fly Auto-Generator done on the Client machine.
With the constant revision/additions of PlayerCreated Assets, this transfer and caching would be an important aspect of how the MMORPG operated ( without being inundated by Server to Client data and especially without requiring the games data to be static ).
--- --- ---
MMORPG - Preloading of Game Situation (For Players) On Login (A Game Mechanics Issue) :
With the additional greater level of game details in the MMORPG, there is more for the Client Program to Sync-up with than in the typical Low Detail/Static level-oriented MMORPG games. There likely would be a longer wait which needs to be handled/controlled/minimized, and the Player kept entertained while this process happens. 
Ideas :
1) To Cache on disk at the Client the data for the immediate vicinity/and general Game Map last state at Logout time ( speeding up the resolution of the visible vicinity ).
2) To delay login (Character-Activation) while the critical Change-Since-Last-Active updates are loaded from the Server ( to have adequate data to present their Avatar's local situation sufficiently )
3) To have optional delay of Character-Active while Fine Detail updates are loaded (streaming) for immediate vicinity of the Player's Avatar ( adequate filler detail is used until the actual data gets loaded ).
4) Player to have immediate access to in-game Mail/Auction House/Team-Task activities, to have something for Player to do while waiting for a sufficient update to take place.
5) Subsequent preloading of 'out of view' Adjacent Area state then works as normal ( to be ready when the Player suddenly moves into an adjacent area ) -- Big enough areas are preloaded so that disconcerting 'detail' transition isn't normally visible.
--- --- ---
"Ryan and Latency, Latency and Ryan" ( to Mis-Quote Sander Cohen ) :
This MMORPG is an Internet game. There are delays in Network Communication (Internet) that don't go away, no matter how fast your computer is.
The game's interactions should mostly be based on tactics/knowledge, and not on twitch reaction/action timing ( which is all screwed up by the network latency inherent in the Internetz ).
Compression of data and caching library on Players Client machine can optimize Assets which need to be suddenly loaded, the data is to be largely already there on secondary storage ( Client disk/SSDSolid State Diskdrive ) whenever possible ( see Templates )
--- --- ---
The Asset Loading (On The Client Program) ChokePoint :
Most games for simplicity load a level of static data ( which is why levels are so limited, and have limited content, and the games terrain is broken up into 'levels' *AND* you wait while a 'Splash Screen' is shown to cover up the delay ). Loading Assets takes time even with the much faster SSDs ( including M.2 - a new much faster storage interface for SSDs ). In the MMORPG, MANY different objects would get dynamically loaded all the time -- with their number they cannot all fit in memory to be loaded as a 'level'. Dynamic loading delays cause complications for the Player's view of the gameworld. The problem is the Player may move quickly forward into an area containing Assets which haven't had a chance to load yet.
* Preloading ahead of view
* Level of Detail placeholders
* Environmental Effects to partially/temporarily cover-up/obscure distant loading/up-detailing objects
SO the MMORPG game will need some creative ways to cover up ( the temporary lack of detail ) while things are being 'loaded' into the current scene in their higher detail. Maybe, many times you just pass by something without noticing - ie- foggy(obscured) shop windows, which unless you stop to look at/focus on what's inside the display window, or the interior of the store, it is NOT overly distinct/resolved ( It is fine then if the highest detail is not loaded, and temporary placeholders can be good enough, and you may pass bye without even looking ).
Pre-loading ( load-before-you-see-them ) can only do so much to handle this problem. Even in constricted view interiors ( this Rapture is NOT going to be so much of that BaSx Bloat-sizing ) in this game there are lots of Objects and detail within a close range, everywhere. Even Players/NPCs walking by have lots of semi-unique equipment or clothes details, which require the Assets to load before you can see them properly/completely.
One bonus of the continuing Progress of Computers is how much memory is available to hold the required data ( so that things can be pre-loaded at a lower priority when the primary game execution isn't as busy ).
More sophisticated techniques can be done like maintaining prioritized 'Scene Lists' at the Server to predetermine WHAT is in view and what Assets are required/most important to be shown ( both low-quality for distant viewing, and full-detail for close viewing ). That is so that pre-loading can be done earliest ( again to take advantage of slow processing moments on the Player's Client machine and secondary (disk) data storage ).
--- --- --- --- ---
.
.