Runes of Magic US / AU

@ipeacefrog, We are silent for the simple reason that we have no update for you. We don't plan to shutdown Siege War until we fixed it. Our IT and Runewaker are still working on the existent Siege War issues (And a lot more has been done then just moving servertime ) , but as of yet - no fix has been implemented or is available.

I merged your thread with the big thread.

.

Thank you for the feedback/update.

.

Quoted from "Roeksha;512611"

@ipeacefrog, We are silent for the simple reason that we have no update for you. We don't plan to shutdown Siege War until we fixed it. Our IT and Runewaker are still working on the existent Siege War issues (And a lot more has been done then just moving servertime ) , but as of yet - no fix has been implemented or is available.

I merged your thread with the big thread.

Im sorry Roeksha but what you just said makes absolutly no sense to me. How the hell is there no update? The only possible reason there is no update is if there is absolutly nothing being done to attempt to fix the problem. The entire game community is crying out to kept in the loop of what is being done daily to fix the problem. Seriously how hard would it be for someone to jump on here for 5 minutes per day to outline whats being attempted? You have yourself admitted that loads more has been done other than moving server times, information on all those things would infact be several updates would it not? My blood boils everytime someone takes the time to come on here and simply say something is being done whilst it seems they deliberatly leave out any details. This makes absolutly no logical sense what-so-ever. If you took the time to bullet point a few details daily on what is being done i can guarantee it will cause there to be far less flaming here and inject some faith in people that this is a priority and not just something that is only dealt with on the side whilst you prioritise your efforts on new aspects of the game that directly earn you more revenue. You are adding fuel to the fire by not letting your customers know whats going on constantly considering the hundreds of millions of dollers this company has turned over as a direct result of these customers.

Quoted

[COLOR=black !important]My blood boils everytime someone takes the time to come on here and simply say something is being done whilst it seems they deliberatly leave out any details. This makes absolutly no logical sense what-so-ever.[/COLOR]

We don't provide more details for many reasons. One of them is the protection of data and internal server information. I can guarantee you that a lot more has been done then moving the server time. A lot of functions and settings have been checked. Both Runewaker, Frogster and even Network Vaults are involved in trying to fix the problem.

I am sorry, but I have no intention to share more details.

Quoted from "Roeksha;512650"

We don't provide more details for many reasons. One of them is the protection of data and internal server information. I can guarantee you that a lot more has been done then moving the server time. A lot of functions and settings have been checked. Both Runewaker, Frogster and even Network Vaults are involved in trying to fix the problem.

I am sorry, but I have no intention to share more details.

Nah im not buying that.

DAY 1: Today we attempted a few simple server side software tweeks and tested them to see what effect they had but to no avail. There is also 3 people working round the clock implementing other minor changes that may solve the problem or at least highlight something we missed.

Day2: Same as yesterday and plans set in motion to have hardware tests done to ensure nothing on that end is malfunctioning.

Day 3: Possible bug found blah blah blah

Simple stuff. Very few people would understand anything technical anyway. Im not talking about blocks of code being posted. Right now every single person this is affecting doesnt believe this is being treated very seriously. Constant communication with your client base, no matter how vague or simple your details are will make your incredibly loyal customer base not feel the company they invest huge sums of money in will only supply them with the lowest quality product and customer care that they can get away with.

Quoted from "Xyrrth;512610"

Well duh, with only around 7 people able to get in Siege RoMwide, there better not be any lag.

Sorry was only giving QA what they have asked for.

They need to hire a problem solver on this. It costs money yes but siege being down costs more. Guild now has problems running 2 groups in instances as many are on hiatus or have cut their hours of play.

.

Like I said:

“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time." - Abraham Lincoln or P. T. Barnum (Your choice)

.

Quoted from "Almondnut;512668"

Sorry was only giving QA what they have asked for.

They need to hire a problem solver on this. It costs money yes but siege being down costs more. Guild now has problems running 2 groups in instances as many are on hiatus or have cut their hours of play.

"Oh... I've got a raging clue"

Quoted from "Roeksha;512650"

We don't provide more details for many reasons. One of them is the protection of data and internal server information. I can guarantee you that a lot more has been done then moving the server time. A lot of functions and settings have been checked. Both Runewaker, Frogster and even Network Vaults are involved in trying to fix the problem.

I am sorry, but I have no intention to share more details.

This little response is better than we've had all week. We'd just like more it more often.

Frogster is only a little 200 person company (including CMs, GMs, IT, etc), don't expect overnight miracles.

It would be nice if Siege were returned to its proper time.

Quoted from "Xyrrth;512680"

This little response is better than we've had all week. We'd just like more it more often.

Frogster is only a little 200 person company (including CMs, GMs, IT, etc), don't expect overnight miracles.

It would be nice if Siege were returned to its proper time.

I meant to point that out also. That kind of stuff daily is exactly what im talking about.

Quoted from "Roeksha;512650"

I am sorry, but I have no intention to share more details.

Well....I think that may be part of the problem. Lack of any intention to be transparent about whether the problem will be fixed. Did you really mean that? Or did you actually mean that "there is nothing more I can share at this time unfortunately"?

If you are feeling generous today Roeksha, I'd like direct answers to the following Siege-related questions:

1) Have you at this point identified what is causing the problem with Siege War?

2) If yes, can it be fixed and do you have an estimated time frame?

3) If Siege War cannot be fixed does the company have any plans to replace it with something else, perhaps something better? (hint hint)

4) Will siege be restored to its regular time so that east coast players in the US can play at 10pm EST?

I can see a few scenarios here from a business perspective.

Clearly a segment of players are not happy about Siege taking so long to fix, despite waiting through several maintenance cycles. Based on the fact that Tergothen Bay was pretty much a ghost town last night, my guess is that Frogster has lost a signficant number of players or is seeing significantly decreased activity in certain areas. Is it possible that Siege was a much bigger draw than anticipated?

So, when losing a segment players (*cough* "customers"), which I will refer to as "siegists", for suddenly not being able to provide a desired feature of the game, what do you do? Well, from a business perspective you could:

1) Try to Fix it quickly and pay the cost of fixing it. This is what most customers probably want to happen.

2) Discontinue the feature due to cost to fix it, realizing you will probably lose the siegists, but perhaps eventually new players will come on board, never having experienced siege and won't miss what they didn't have in the first place. Maybe the server pops will recover eventually.

3) Tell people you're working on fixing it without providing much information or status, hoping they won't leave and will stay on and continue to support the game while they wait for it to be fixed. This is basically the same as option 2, except you don't commit one way or another and siege stays in the repair shop indefinitely. The difference is that people (mainly the siegists) leave less quickly due to uncertainty and investment in the game. From a business perspective, I think this option would be the least risky and most profitable if the cost of repairing siege was high. After all, players come and go all the time.

Clearly there is a significant portion of players that don't care about siege one way or the other. So the question is, can the game survive without siege? It probably can, as long as there is content that people want that can support income generation through diamond sales. And if that's the case, why fix siege at all if it doesn't impact the bottom line?

Quoted

1) Have you at this point identified what is causing the problem with Siege War?

2) If yes, can it be fixed and do you have an estimated time frame?

3) If Siege War cannot be fixed does the company have any plans to replace it with something else, perhaps something better? (hint hint)

1. No, but we still have some 'ideas' as to where it may come from. Those are currently being investigated.
   
2. See above.
   
3. No idea.
   

.

Thanks for the feedback.

.

Quoted from "Roeksha;512700"

1. No, but we still have some 'ideas' as to where it may come from. Those are currently being investigated.
   
2. See above.
   
3. No idea.
   

As with anyone who was playing RoM when Siege was introduced, the current problems are so, so familar.

We had these all before,

the heavy lag starting a set period (20 minutes or 30 minutes or 40 minutes) after Siege starts;

the "nothing happens for 2-3 minutes when you try to enter Siege then kicks you back to login";

the overall lag during Siege, sometimes with crashes or kicks to login.

Frogster fixed these problems about 18 months ago, the server move awakened them. It appears unfortunelately the information about what was done previously done to fix was lost (no QA troubleshooting logs were kept? Or the people have left taking the information in their heads). Sigh.

Quoted

[COLOR=black !important] Frogster fixed these problems about 18 months ago, the server move awakened them. It appears unfortunelately the information about what was done previously done to fix was lost (no QA troubleshooting logs were kept? Or the people have left taking the information in their heads). Sigh. [/COLOR]

No, actually, the solution to the problem last time, is not the solution for the current issues, even though the symptoms are the same, the problem is different.

Quoted from "Roeksha;512709"

No, actually, the solution to the problem last time, is not the solution for the current issues, even though the symptoms are the same, the problem is different.

well that sucks.

thank you for finally posting some sort of acknowledgment of the problem after oh over a month of nothing, the silence was worse then the problem itself imo.

3) Tell people you're working on fixing it without providing much information or status, hoping they won't leave and will stay on and continue to support the game while they wait for it to be fixed. This is basically the same as option 2, except you don't commit one way or another and siege stays in the repair shop indefinitely. The difference is that people (mainly the siegists) leave less quickly due to uncertainty and investment in the game. From a business perspective, I think this option would be the least risky and most profitable if the cost of repairing siege was high. After all, players come and go all the time.

They don't have to pick one, they've clearly been doing this very thing forever.

So Roeksha does that mean yall tried what was done to fix this problem last year and it didnt work or some tech told you thats not the problem because their pride doesnt want to admit it could be as simple as doing the same thing as was done before? honestly we are all losing faith in frogsters technical staff at this point and no matter how confident u are in their abilities, it seems this problem is spiraling out of frogsters hands completely. i agree with what someone said already, in this thread or one of the many other threads created about siege, wich tells you how important it is to many in game, you need a problem solver, someone who is known for finding what typical technicians overlook. much as i hate to say it, sometimes it is so obvious that a complex oriented technician will ignore the possibility of say, a loose cable or something to that effect.


but for realsies, guilds are falling apart. not mine, we still holding together, but the fact that we faced and defeated guilds in the 3k bracket lately, before siege broke again tells me key people are leaving rom. people im certain spent a lot of money to be able to pwn in siege. until then, arena anyone?

Technical problems develop alot and can be a challenge to solve when company's "Cut" the hamster workforce, and not hire intellectual hamsters to fill in those vacant cages. Brilliant programmers can pretty much figure out any code in any language no matter who wrote it. However, those type of programmers are becoming extinct if not already extinct.

That popular quote "Hope for the Best prepare for the Worst", seems the techs/corporate heads did to much hoping and not enough preparing.

SW started at normal time, everyone in my guild that tried to enter sw was able to. Those that logged on after sw started were able to join also. The opposing guild was also able to get someone into sw. I did not experience lag but seems some of our guild did have some lag.