Runes of Magic US / AU

Something was definitely messed up. We were able to get in fine and stay in but our opponent (from another server) was apparently fighting two guilds at the same time and only one of them could get into our match. The rest were fighting the other match! Siege is bonkers sometimes.

Yeah, siege blew up for us, which was very disappointing, because we were looking forward to the fight. I got to kill 1 person before I got killed, then boom! everything died. I blame me getting killed for the siege crash, you should of let me live lol. But in all seriousness, it was very disappointing to have the only thing I look forward to and actually play (my girlfriend plays Sasha the rest of the time usually) be broken.

Quoted from "welshde;365216"

Only 100 siege results again tonight. This seems to be the new SW limit.
(Down from 120)

If thats the case then... Sign up early folks!

Not sure about this...

I signed up yesterday after I got home from work, and then checked the RegisterCount value, and found we were number 231 on the signup list. So, it seems 240 guilds went to siege last night.

However, I also hear about guilds getting kicked out of siege (early on) and not being able to get back in. Maybe this is what is happening. 40 guilds get randomly kicked to drop the number of results down to 100 matches.

I hope Bene gets in...

I enjoy my once-a-day Siege War recounting

They are legitimate.

NOO what happened to dragonlance on grimdal

Ya I've been around since beta and they have been around since beta and Apocs are top now? lol I used to rape some of them

dragonlance died a long time ago. Now we dominate.. people instantly die as we walk past them nowadays

Quoted from "Satiar;365471"

I hope Bene gets in...

I enjoy my once-a-day Siege War recounting

Three nights in a row, we've been disconnected in the first 45 seconds of siege war. You know the drill. Both teams kicked back to the login screen. When you get back in, the siege war battle list no longer shows your match.

I swear... either the game engine these guys use is the most unstable one on the planet Earth, or the RW coders couldn't find their butts with both hands and a mirror.

I write code for a living, and I'm appalled at the apparent lack of version and/or module control. If I wrote code with this many recurring flaws, I wouldn't just be fired, I'd be sued.

EDIT: Now, four nights in a row and counting. Last night, we were kicked off the list before the matches were even set up.

Quoted from "Kaelani;366392"

Three nights in a row, we've been disconnected in the first 45 seconds of siege war. You know the drill. Both teams kicked back to the login screen. When you get back in, the siege war battle list no longer shows your match.

I swear... either the game engine these guys use is the most unstable one on the planet Earth, or the RW coders couldn't find their butts with both hands and a mirror.

I write code for a living, and I'm appalled at the apparent lack of version and/or module control. If I wrote code with this many recurring flaws, I wouldn't just be fired, I'd be sued.

Second third and whatever else SW since the last patch has gone from crappy and unstable to flat unusable and I thought the old SW was horid and annoying having spent a great deal of cash over the time on this game I expected better but anyhows so much for hopes just saying I agree with sw being utter crap hire new programers or get better hardware or hell both.....

Quoted from "Tiduz;335978"

I wonder if their Tidus is as sexy as me!

hahahh guess well find out :p

Dragonlance didn't exactly die... they were all banned for using the duping bug. Or most of them were. I haven't seen one since, in any case.

For only a second time over past 6 days, my guild had a good Siege. Good meaning, we did not get booted after 2 minutes, and there was little to no DC's or lag. Had a great clean fight against Core. Had some fun one on one fights with Realkiller, beast of a W/R .

It is well known across Reni that one guild with many players with t10 weapons, has also either used the duping bug or hacked. A clean t10 stated brown nem blade ftw. GM's can PM if they want info.

But lets not derail this thread any further. SW is borked lately. Intially the new patch seemed to help with lag and DC's while in SW. The problem is not being able to actually enter the battles or having everyone kicked from a battle and SW shutting down for those guilds.

Quoted from "brogue;367070"

It is well known across Reni that one guild with many players with t10 weapons, has also either used the duping bug or hacked. A clean t10 stated brown nem blade ftw. GM's can PM if they want info.

I didn't know about this :p But then maybe I'm just too out of the loop and don't pay enough attention anymore.

Quoted from "welshde;369548"

It seems that Froggy settled on allowing just 80 sieges per night.

I hope the 80 siege limit is only temporary though.

I've now asked this in two different threads in two days.

One thread got locked without an on-topic answer...
http://forum.us.runesofmagic.com/showpos…58&postcount=13
http://forum.us.runesofmagic.com/showpos…75&postcount=16

and one thread got moved to Suggestions and Feedback without any answer at all.
http://forum.us.runesofmagic.com/showthread.php?t=52328

The siege war signup filled up last night in 2 minutes and 53 seconds.
Only one half of the active guilds that participate in siege war were allowed to participate. (Using numbers from Siege War Top 50 site.)
Got that? Only 50% of all guilds that want to siege are currently able to do so.

But, nobody cares. It's just you and me in here, Welshde...

Any time FA wants to bury a topic, it gets moved to the "proper area" (read Black Hole), where it quickly dies.
If you think this is just opinion, and not fact, then look at this thread, for example.

488 replies and 29,512 views in the 3 months it was in the "Discussions" topic.
In the last month it has spent in this "Fansite" topic, this thread has had an anemic 30 replies and 98 views.

10,000 views per month down to 100 views per month.
All they have to do is not answer a question, and move the thread out of "Discussions".
It's never heard from again.