I think the title is an admission that Mythic can’t code their way out of the server stability issues, that they have been confronted with. It’s also an admission that they can’t deliver on the full vision of Warhammer, that they must have originally hoped for. Whereas before I thought these problems were going to be confined to capping the number of players around a fortress/keep, it appears this zonal capping is being extended into ORvR. It’s got to be a bitter pill for Mythic to swallow. I mean, if you can put together code, to recognise the servers impending doom, then surely you can code a way around it. Unless of course, their current server architecture is the problem and the box + os is crumpling under the stress.
If the server thinks it’s going to have stability issues in a particular ORvR lake, it will perform a classic finger of doom manoveur and allow the gods of random chance to decide whether it’s your night for a swift kick to the side lines. In this case the honour of getting blown off to the nearest war camp of your realm. At which point you can make an choice about what you want to do with the rest of your evening. Heh at least you can say to your fellow realm mates “It wasn’t my night”.
Now honestly, what you are doing there in the first place. It’s certainly beyond me, since performance is always so sucky. However if that’s your cup of tea, then so be it. I am sure the odds of it happening to you, as a player, that often will be low. But I imagine it will be annoying the 1st, 2nd, 3rd ….. nth time it happens. I do wonder if the unsubscribe button will be getting the finger of doom as quickly.
I’m sure I’m blowing this particular issue beyond it’s real world impact. We can just see how it all pans out. It will probably blow over, just as quickly as the fortress capping issue did, when people just carried on as normal.
PS – I love the severely wounded option. Oh how I will laugh as my victim get’s ported out of my reach.