|
When the population eats up a service letter like cattle does grass.
ML is developed as a client side app with connection to a server. The server just holds information, who is where with what HP doing what. You're phone is the processing all the information and data handling, not the server. For example, when Miya attacks a monster, your phone handles all the data processing burning up your phones processing power and then sending the information off to the server to hold. Your phone does all the calculations and does all the heavy work while the server just holds the information. You input your controls and commands and your phone will update the server with new information(location, hp, damage dealt etc etc) which is why you'll notice your phone gets very very hot when you play a round or two. Instead of the game processes occurring on the server ie: ML pays for the server to process information instead of being cheap and forcing the users to process the data.
If that being said, your PING SPIKES:
Ping is calculated by sending a packet from your phone to the server and waiting for a response. The MS between send and receiving is your "ping". The issue with the spike is that the phone can only process so much at a given time. A slow phone will have a higher ping. Now as your continue to play and use resources and heating up your phone, the processor will slow down and the operating system will try to recover whatever commands that need to be executed and "catch up" on skipped commands. This attempt at the operation system to recover data is what causes the giant jumps in ping.
TLDR
ML needs to move all the damn processing to a server instead of a clients phone. Use the phone a Viewer instead of a Controller in the MVC model. |
|