Runes of Magic US / AU

I am a person who lives on the East Coast and this totally stinks for me, I get about 5 hrs of sleep a nite anyway and now its going to be one less. I understand trying to see if different times will help the lag but is there no reason it couldn't have been pushed up an hr instead of back an hr.

I totally agree, especially after they saw the uproar when it was pushed back an hour when EU first took over, then reverted back.

ALSO: Whoever has access to posting this new time for siege on the game, please do so.
There are only a handful of people who visit these forums.

I'm actually pleased with the seige time adjustment. May actually get to log in more often now. And yes, I'm EST More importantly - let's hope the lag is fixed by this.

Honestly I think it's a misdirection to move siege later so less WILL log on, less stress on the connections and TADA less lag... omg they fixed it!

Quoted from "Lateralus923;511615"

I'm actually pleased with the seige time adjustment. May actually get to log in more often now. And yes, I'm EST More importantly - let's hope the lag is fixed by this.

Dont quite understand how moving the time of an in-game feature impacts your ability to log into the game

Didnt Frogster already manipulate the in-game clock to try to fix the item shop and it had no effect other than agitating the community

Can someone at Frogster alleviate the confusion by shedding a little light on how this may be a path to solution

.

I suppose it's something.

Just, please, move it back if the time change doesn't actually resolve the issue. Less people on = less lag is not a real resolution. Unless of course the new data center can't actually handle what you expected them to do, then this may be the only resolution. Unfortunate if that is the case, just means that someone didn't ask the right questions before the move.

As many have pointed out, it seems odd that the issues, as we have them, now started with a change of hardware configuration, ie data center move, not with changing the time of Seige start.

Seems to me that if the time change resolves it, this likely means the new data center has very heavy load during siege time and is not capable of handling it's clients needs.

Though starting at the same time every night with the same steady build up in lag for only some/most in Seige still points to an issue with the node or segment that is handling those toons and the Seige servers return communication to them.

Also I thought the limit for guild regging was changed to 150. The script daily shows 160 regged.

.

This is BS, I'm not east coast but alot of my guildies are, 10pm was pushing it but 11pm is ridiculous. This is not the solution, moving it BACK 1 hour I can understand but this... Bah I'm done, I give up EU is one thing after another. Sure lets make it so people with jobs who pay and can't stay up late will just quit. Do you all even have meetings?

I guess Frogster Eu doesn't understand that some ROM players actually have a life and work and have to get up at 8am and going to sleep at 12am is pushing it. (I'm in the east coast) SW is one of the things keeping me playing this game and for the last month or so i just log on do dailies, minis (only to help gear my sister) and either log off or do the dl, hos, zs crap. I really just want Frogster Eu to man up and tell us whether or not SW can be fixed. If it can't that's fine, Ill move on. But even if this one hour shift works it will still drive people away since alot of people already push their schedules by logging on at 10pm. If things keep going like this I hope my sister will hurry up and get bored of being finally being op (:cool so that I can free up 8gb on my hard drive.

We had a period of time around DST adjustment when SW was at 11pm EST. Somehow the world didn't self-destruct from this blatant violation of natural order.

Before the restless natives go running off a cliff screaming that the world is ending, can we all reread Dionaea's post?

There is no reference that the siege war start time being changed is permanent; they are troubleshooting.

That said, I am one of the restless natives who is not pleased with siege war issues that we have experienced for a month now. I do hope that if moving siege war to a later time directs RoM IT people to the source causing siege war lag, the result is NOT that siege war will forever start an hour later. Starting siege at 11 P.M EST is too late for those in our guild who live on the East coast.


For Rom QA:

For the past week [i.e. before this week's server maintenance] I *attempted* to siege five of the seven nights. On four nights the same old, same old: 20 minutes in, lag started, by 40 minutes in was lagged at least 3 minutes = unplayable. On these nights, some people lagged, some did not. I was just one of the unlucky ones. I do not even bother to list guild/server match ups, because that info does not appear to be relevant regarding 'why' people are timing out.

Last night, however, very few of us lagged out, including me. It did appear that several in the opposing guild were lagged out.

Pure luck that we were not lagging out or not? We only had 14 players in - but not for the entire siege. I and few others came in after the midway point.

I expected to be lagged out of siege no matter what, because my ping yesterday in RoM - even in normal gameplay - was TERRIBLE. I consistently ran at 96ms to 109ms all day, when I normally have a ping of 47ms.

Ironically, I did not timeout during siege last night, although my ping stayed in the 109 range..had an isolated peak of 170 or so.

I ran tracert several times yesterday during normal gameplay: the speed decrease consistently occurred when traffic was handed off to 'ae-2-2.ebr1.Miami1.Level3.net'. All traffic/IP's from that point on, looks to be associated with Vaultnetworks - and routing slows down.

I did not log in yesterday until late afternoon, so I don't know if the ping increase is time/interval related [i.e. heavier traffic periods for Vaultnetworks, they are choking, etc.] or a fluke.

I just logged in today. My normal gameplay ping is running its usual 47ms today.

Wiffo 6 days, announced and we were told it was for DST, don't get your high horse goin to fast there slick, you're not the only one with a memory, but fanboy on...

Did you consider moving the tempest heights event BACK to its original time of 8pm central, 1 hour before SW like it used to be? Yeah - moving SW back an hour certainly will help, because there will be a LOT less participation.

Quoted from "moroon81;511647"

Did you consider moving the tempest heights event BACK to its original time of 8pm central, 1 hour before SW like it used to be? Yeah - moving SW back an hour certainly will help, because there will be a LOT less participation.

Is there a problem with tempest heights event that requires it to move? I thought that run on native server and thus not affected by the server issues.

Quoted from "Regentego"

Wiffo 6 days, announced and we were told it was for DST, don't get your high horse goin to fast there slick, you're not the only one with a memory, but fanboy on...

I'd reply to this if I had the first idea what it actually meant to say.

I wish I could say great for the SW time change. I am Eastern and 11pm is to late during the week for me. If it fixes it for the rest of you, I am glad for you.

Quoted from "vfwiffo;511649"

I'd reply to this if I had the first idea what it actually meant to say.

I am bored so i will play the guessing game. I believe earlier you said that his has happen before and everything was fine. World didn't end.

They replied said that when it has happened in the past we had gotten an announcement about the change 6 days before it happened and we were told it was for DST. The rest i believe is flaming you or something.

Quoted from "kingzamorak;511653"

I am bored so i will play the guessing game. I believe earlier you said that his has happen before and everything was fine. World didn't end.

They replied said that when it has happened in the past we had gotten an announcement about the change 6 days before it happened and we were told it was for DST. The rest i believe is flaming you or something.

I would surmise you are right about this guess as to what the message meant to say. But, that is not what happened. We had DSL time shift occurring mid-week and so the time was shifted during the weekly maintenance. The explanation was that for the first part of the week SW would be off 1 hour, but as soon as DST adjustment hits, it would be back at its usual time. It was not pre-announced, and people were complaining about that.

Probably right about the rest of the message being an attempt to flame. Not particular incendiary one, though.

Last night our siege went without a hitch. Not just for a few of our members, but all of them. We also hit the cap on allowed players into siege so it wasnt as a result of non attendance. The guild we were facing also seemed to have no troubles. The siege went the full duration and there was no more than the to be expected lag spikes of about .5 to 2 seconds which almost immediatly subside the way they used to a month ago. Other than Tuesday last week, when siege appeared to be fixed only to return to unplayable the following night, this is the first night since the troubles started all those weeks ago that we have had no issues. I was expecting to come on here to see everyone saying the same but it appears thus far that our experience was not shared by other guilds. Battalion - Artemis.

So the fix to the lag is to cut out most of the east coast players from playing siege due to making it too late to play? This is beyond ridiculous now. Is this a temporary things for testing and trouble-shooting or will it be permanent? Will siege be at 10pm when DST reverts in two weeks time?

Sorry, I have get up early to work so that I can afford to play your game. I can't stay up until midnight to siege. If this a going to be a permanent thing I'll have no choice but to quit the game. After many of us waited patiently for this game to be fixed, this is our reward? No offense, but how is that going to help your business model when you are alienating the East Coast players?

My patience and goodwill are at an end. I find this kind of treatment for a geographic customer base to be, quite frankly, untenable.

Keep in mind the fact that the IT person is very busy doing his/her main pizza delivery job. It is quite likely to be some time before there is a big enough break in deliveries for IT to find the time to switch siege start time again.

Quoted from "GarryL;511757"

Keep in mind the fact that the IT person is very busy doing his/her main pizza delivery job. It is quite likely to be some time before there is a big enough break in deliveries for IT to find the time to switch siege start time again.

You didn't hear? The pizza guy's main gig said his delivery job was suffering from the hour a week he was spending contemplating the possibility of a fix for this year. He had to refocus and we are back to square one.