![]() So basically you can manually change "some parameters BUT not all" on the specific xml file of your specific tank. Perhaps they avoid additional toll on server processing, e.g when you change camo, change gun, change consumables, change ammo, they must be affected in real-time. Luckily, if the THIRD event is not done in real time, somehow the LOCKING script will use the xml file on YOUR DEVICE as default. Remember when your credit is not updated instantly after any number of battles? On last december, even the FOURTH and SECOND events is not done in real time. Instead it will be done later (it called batch processing). To avoid this "bad performance", sync on the THIRD event will not be done in real time. Lets back to the poor server performance. By default, the game will use the xml files on server. And MATCHMAKING script will not run before the LOCKING script run.Īfter the sync is completed, the tank stats that will be use on matchmaking process will be "lock in". Why? because SYNC script will run before LOCKING script run. It will be affected the server performance, especially on THIRD EVENT when most of player will experience long waiting time in battles cue line. In certain times when there is large amout of players log on and battles simultanously, these events will consume server resources. Similar routine method like second event apply here, server updated first and your device updated after. if any difference found the routine will checks if the difference is "by system" or not. It will sync all xml files related to specific tank that you have chosen to use into battle and its result. Similar routine method like first event apply here.įourth event, after the battle ended. It will sync all xml files related to specific tank that you choose to use into battle. How? by sync the corresponding xml files. After that, there is a routine that will cheks if the server successfully updated then it will update the corresponding xml files on your DEVICE. This event will always update the corresponding xml files on SERVER in FIRST PRIORITY. ![]() buy gold, converts credits, converts xperience, upgrade tanks, change camo). Second event, when you conduct any transaction in the game, except battle (e.g. If the difference found not mark as "by system" (e.g. not sync the data on second, third or fourth events) then the server will sync by COPYING the xml file from the server into your device. (by system means, if the difference due to server fault e.g. If any difference found, there is a routine that will checks if the difference is "by system" or not. It will sync all xml files except tank details. (fyi: sync means that the xml files kept on your device must be MATCH with the xml files kept on blitz server)įirst event, when you log on into the game. Those files will be sync in five significant times, lets call it "events": Basically all your stats (your records, tanks you owned, gold and credits you owned etc) is kept in xml files BOTH on your DEVICE and the wotblitz SERVER. but it did't have permanent effects (Warranty not included, you do it on your own risk).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |