Runes of Magic US / AU

i for 1 am tiring of the constant bugs of this game i fear my time in Runes of Magic is coming to an end its to bad this game is awsome if you can overlook the horrible support system and poor programming not to mention Siege war has been in beta since 2009 hmmmmmmmmmm wondering why i ever spent any money

Is anyone else getting server logon or incorrect password errors?

I just tried my logon. First it took it two minutes to load the character data screen, then it told me I was entering an incorrect password when I know it was correct and caps lock was not on.

Will try again in an hour. *sigh*

Yea i'm getting frustrated about the lag issues with mail, AH, house, and other things. I don't want to quit ROM but man they're pissin me off to no end on some of this stuff lately. Is it just me or is it getting worse as the days go on?

its spreading.......seeing some unusally long delays in login. on indigo.

theres chatter of mailbox issues here but i havent noticed personally yet.

Seems everything is breaking now, people cant log into the game, cant enter their houses, cant open their mail, cant open the ah. Some cant loot mobs. I know their is a lot more breaking atm, should hire another squirl for the wheel.

I finally managed to log into the game after restarting the client and my laptop. Game ran ok, but the mailbox wasn't working, and for a minute or two the AH failed to search anything.

I ran DL with a pug group last night. We ended up not being able to loot the last boss, despite the fact that he was all sparkly. 10 mentos down the drain. I won't even get started on DOD- won't let me in to fight the boss, won't let me back out of the instance (portal was missing in Erekat's room), won't let me progress through the instance when the boss I've just killed has been looted.... and occasionally fails to spawn bosses at all.

Quoted from "LadyMacV;500114"

I finally managed to log into the game after restarting the client and my laptop. Game ran ok, but the mailbox wasn't working, and for a minute or two the AH failed to search anything.

I ran DL with a pug group last night. We ended up not being able to loot the last boss, despite the fact that he was all sparkly. 10 mentos down the drain. I won't even get started on DOD- won't let me in to fight the boss, won't let me back out of the instance (portal was missing in Erekat's room), won't let me progress through the instance when the boss I've just killed has been looted.... and occasionally fails to spawn bosses at all.

I was also in a group that was running DOD for mems tonight and Maxim failed to spawn at all on one of the runs. It was around the same time other people in the guild were complaining that the AH & mailbox weren't working and they couldn't enter their houses.

Luckily when that starts happening within a few minutes everything seems to "catch up" but it's REALLY frustrating when it does happen! Especially when I'm in the middle of a transaction with a diamond seller!

On Reni trying to get into either House or Guild Castle failing. Will update after relogging to see if still an issue but have heard reports from others on this as well.

Edit:
Well after relogging was able to get into house but still what's causing these issues??

Quoted from "LadyMacV;500114"

I finally managed to log into the game after restarting the client and my laptop. Game ran ok, but the mailbox wasn't working, and for a minute or two the AH failed to search anything.

I ran DL with a pug group last night. We ended up not being able to loot the last boss, despite the fact that he was all sparkly. 10 mentos down the drain. I won't even get started on DOD- won't let me in to fight the boss, won't let me back out of the instance (portal was missing in Erekat's room), won't let me progress through the instance when the boss I've just killed has been looted.... and occasionally fails to spawn bosses at all.

I'll add on to this. I ran DL the other night and had the same thing happen. Luckily, my silly pet was able to loot with perfume active and I got my mems, and the rest of the party was able to roll on the other items. But yes, the whole server is acting stupid.

Well, might as well add. I've been sitting at the load screen for about 5 minutes now after trying to enter the game from the character selection screen. I guess the houses are lagging as that is where my toon was parked.

Remember start screenshotting all ya stuff, cause who knows maybe the bugs/glitchs will reach the bowels of the server nodes where character data is kept and the virtual gods will vaporize items , smell that bbq hardware :p

It's a little disturbing that server maintenance doesn't seem to be happening as frequently as it used to. I just hope Runewaker is using the time to fix the coding/game engine, as opposed to releasing more patches.

Nevermind. it's just really slow logging in.

ladymac , far as i know they still do maint every tues nite/wed morning except for the one week it was delayed.

So far it's been 22 minutes and I'm stuck at the loading screen. Oh boy is this gonna be fun if we crash during siege

We are investigating the Loading and server issues you reported.

For our investigation, it would be helpful to get a bit more information from affected players.

Could you please do the following, when you are encountering issues with loading or AH/Mail, and give us the results?

1. In Execute(/Search) in windows, type "cmd"
2. Press enter
3. type tracert <IP according to your Server> for example
"tracert 64.127.104.210"
4. and let it run
5. Once the tracert is complete, rightclick in window and select Mark, then mark all tracert result text and copy it here.

Server IPs:
Worldserver Artemis,Govinda = 64.127.104.217
Worldserver Osha,Grimdal = 64.127.104.212
Worldserver Reni,Indigo = 64.127.104.214
Worldserver Palenque = 64.127.104.216

Edit: In Addition please do a similar command, depending on server you play on, for example:

"Ping 64.127.104.217" and add those results here as well.

Much thanks.

Tracing route to 64.127.104.212 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 7 ms 15 ms 76.49.0.1
3 16 ms 16 ms 17 ms gig3-12.wkshwiwksh-swt401.wi.rr.com [24.160.230.48]
4 9 ms 10 ms 9 ms tge1-5.nwblwinbln-swt401.wi.rr.com [24.160.229.186]
5 43 ms 18 ms 19 ms gig5-0-0.milwwirtco-rtr2.wi.rr.com [24.160.228.26]
6 9 ms 16 ms 10 ms network-024-160-225-064.wi.rr.com [24.160.225.64]
7 13 ms 19 ms 17 ms tge2-1-0.tr00.chctilwc.mwrtn.rr.com [24.160.229.197]
8 11 ms 13 ms 12 ms ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
9 16 ms 40 ms 9 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
10 29 ms 34 ms 31 ms te1-2-0d0.cir1.chicago2-il.us.xo.net [216.156.72.5]
11 39 ms 48 ms 36 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
12 251 ms 203 ms 96 ms te-4-1-0.rar3.denver-co.us.xo.net[207.88.12.22]
13 116 ms 99 ms 89 ms te-3-0-0.rar3.sanjose-ca.us.xo.net [207.88.12.58]
14 90 ms 100 ms 104 ms ae0d0.mcr1.fremont-ca.us.xo.net[216.156.0.138]
15 67 ms 68 ms 66 ms 216.55.28.22
16 66 ms 66 ms 73 ms 64.127.96.237
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

Quoted from "drkshadow0000;501801"

Tracing route to 64.127.104.212 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 7 ms 15 ms 76.49.0.1
3 16 ms 16 ms 17 ms gig3-12.wkshwiwksh-swt401.wi.rr.com [24.160.230.48]
4 9 ms 10 ms 9 ms tge1-5.nwblwinbln-swt401.wi.rr.com [24.160.229.186]
5 43 ms 18 ms 19 ms gig5-0-0.milwwirtco-rtr2.wi.rr.com [24.160.228.26]
6 9 ms 16 ms 10 ms network-024-160-225-064.wi.rr.com [24.160.225.64]
7 13 ms 19 ms 17 ms tge2-1-0.tr00.chctilwc.mwrtn.rr.com [24.160.229.197]
8 11 ms 13 ms 12 ms ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
9 16 ms 40 ms 9 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
10 29 ms 34 ms 31 ms te1-2-0d0.cir1.chicago2-il.us.xo.net [216.156.72.5]
11 39 ms 48 ms 36 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
12 251 ms 203 ms 96 ms te-4-1-0.rar3.denver-co.us.xo.net[207.88.12.22]
13 116 ms 99 ms 89 ms te-3-0-0.rar3.sanjose-ca.us.xo.net [207.88.12.58]
14 90 ms 100 ms 104 ms ae0d0.mcr1.fremont-ca.us.xo.net[216.156.0.138]
15 67 ms 68 ms 66 ms 216.55.28.22
16 66 ms 66 ms 73 ms 64.127.96.237
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

this really just means that you hit a hop that denies ICMP requests. This is done very often to help prevent Denial Of Service attacks and other security issues. It doesn't at all mean that the hop is experiencing any trouble. If you're able to ping the final destination, then obviously that hop is still routing.

If you saw something more like this, there'd be cause to worry:
15 67 ms 68 ms 66 ms 216.55.28.22
16 1250 ms * 800 ms 64.127.96.237

I'm surprised a gm/fm/cm hasn't said its people's computers that are faulty .
Also the tech's that maintain the actual server nodes, why not get them to do a diagnostic on the server's hardware...Or do people not do that there?

Hi - we are seeing server issues on Palenque yesterday and today. Very long delays at character loading screens, lag with mail, and lag with auction house.