different server.
when you think about that the majority (if not all, i do not know) pf EU servers are located geographically near to Germanys biggest internet exchange DECIX in Frankfurt , you still wouldnt want to play something as timing-sensitive as pvp on a server on the other end of the world. (Having 25 or 250ms in PVE probably does not matter THAT much as long theres no rubberbanding happening...) Yours is probably on US Eastcost now...
So ofc were running not on the same physical machine , but if i got the QA guy here right, its atm the same settings within the obviously same software. So your machine either has some strange random problem, or cant handle the load (anymore?) for whatever reason, or a unknown incompatibility occured. This CAN be hard to track down to the source and then fix it or have it fixed. But as they already said, they think its a tech problem on Frogsters end, so its probably not the siege software itself (= Runewaker).
EU SW is just the usual laggy and crit-error crap like its always been, but nowhere near as bad as yours in the past two or three weeks.
Ouch. Posts like that one make me sad.
I've been racking my poor slushy brain, trying to figure out where/how the problems started, and what they might have caused in subsequent maintenances, that Frogster could have somehow messed up. Couple'a things came to mind:
1. Siege starting a few minutes too early and ending a few minutes too early. Frogster had serious issues fixing the expired sales in the cash shop (it took them nearly three weeks to fix the "mechanical" issue). I'm going to assume the Battleground server was taken offline temporarily for the move, and was rebooted/restarted a few minutes or hours prior to siege, thereby causing Siege to start and end earlier than it should. If the Server is programmed to have siege start at exactly 8 pm, and the software was running before that, it would likely be causing at least a few compatibility issues.
2. I'm glad someone mentioned the warden fix, because it was specifically designed to keep players from crashing out of siege due to a Warden using a specific skill. One or two maintenances after the official fix comes out, players start crashing, lagging, showing up in two different sieges, etc... I'm not letting Runewaker off the hook totally for this particular problem until someone can confirm that it isn't their Warden fix that is causing the issues.
I'm also curious as to how many people actually bothered to remove the player made fix before installing Runewaker's patch with the official fix in it, because although they're essentially the same thing as far as I'm aware, there might be some redundancy issues being caused in the client from the two "fixes" interacting with and/or overriding each other.
And last but not least:
If the hardware has gone bad, the software will follow shortly after.