Originally Posted by xero

I'd say the best fix specifically to this event, is to limit or completely eliminate refreshing opponents. The simplest implementation that pops into my head for them to do this is to just have the server cache the results a player gets for each possible query type, and clear them when the player attacks. There aren't enough players that the size of the cache will be much of a problem (and of course the second i post, i think of something simpler, and requires you to cache even less information). All being said, they probably won't implement something like that, but it would close pretty much all of the cheap and easy loopholes with this particular event.

You're making a basic mistake here, thinking there's only one server involved. Nutaku manages the server load with services from Amazon AWS, so there's actually dozens of virtual servers being spun up and down all the time (Meh, all the time being a relative term for those that know how virtual servers are instanced and spun)