Creation of Client Cache (WDB) page.

[TheSCREWEDSoftware]

Closes: #863 // [Feature Request]: A page on what the client caches.

• Creates file client-cache-wdb.md
• Simple explantion about what table, packet and client cache files and that they may or not be need to be deleted.

Below all had a small text added (to say they about their cache)

• item_template
• creature_template
• gameobject_template
• quest_template
• page_text
• npc_text
• gossip_menu
• gossip_menu_option

[TheSCREWEDSoftware]

@heyitsbench do you know if i've missed anything here?

[Nyeriah]

What's display ID? Models? Creature/gameobject models are not cached
gameobject flags are cached e.g interact condition
I could be wrong but I also don't think any of those quest fields are cached, at least I don't remember having to clean cache before
npc_text is cached, menu and menu_option are not (gossip options are not cached)

[TheSCREWEDSoftware]

Those fields are refering to the fields in wdb file, not every cache file means they need to be deleted, theorically when changing them the server side equivalent you may or not have to clear your cache.

Example for CreatureCache

It caches the type, family, flags?, DIsplayIDs up to 4 (0+3). While not every cache value needs to be deleted (as it probably get re-written by the server or just ignored), PageTextCache has only 4 fields, ID, Lenght, NextPageID and the string, for this case i think string value (pagetext) is the one that requires client clearing.

[Kitzunu]

you are missing reference in the documentation index

[TheSCREWEDSoftware]

Done @Kitzunu