• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Realm Works Login Down

The_Traveller

Active member
As of 8pm GMT Realm Works server is unreachable. I've tried on 2 different computers. One will not start as it cannot register the computer with the server, the other will start but will not login, Login Unavailable.
 
Would have been nice to have some sort of post

My apologies for not posting an official company update.
Unfortunately, this occurred the one time all week I stepped away and had spotty cell signal. By the time I returned the issue had already been fixed and consumers were posting as much. I’m just grateful the devs worked to repair the issue on their days off.
 
My apologies for not posting an official company update.
Unfortunately, this occurred the one time all week I stepped away and had spotty cell signal. By the time I returned the issue had already been fixed and consumers were posting as much. I’m just grateful the devs worked to repair the issue on their days off.
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.
 
Even with an internet that is always available it won't help the customer if the servers are down. Not an RW issue but maybe an HLO issue - since I heard that updates are server based.

Each and every time I read "servers are down" (which is completely acceptable and to be expected, because it can happen for a an online consumer grade product) I know, that I am not belonging to the target audience. Because it's just murphy's law, when I would like to play and access is required at this very moment, it wouldn't work and I would be just upset :P Again, with RW it's no problem, most of the stuff can be done offline - which is a good middle ground. Only thing that is so annoying is that I cannot copy around my master realms between my laptops. I'm wondering already how I will manage when the subscription runs out :)

I just hope that there will be always enough people to make companies turn around or at least mind of the customers that wish offline products, so they continue to develop products that work without internet at full capacity. Especially when (and here iam just speaking about applications in general) an "always online" functionality is just a "nice to have" feature and with little benefit for the customer.

The expectation I have to any application is, that I dont want to add additional (avoidable) risks compared to usage of pen & paper, because that's what I will be measured against, when I'm the one using electronic tools and some other player is not. :)
 
Last edited:
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.

+1 on that
 
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.

Actually it makes sense that the dev would not be the one making the update notification. Communication of issues normally would be sent via manager/talking head/spokesmonkey to ensure the appropriate information is given in a consistent format. it also ensures that the feedback is going to one focus point.
 
Actually it makes sense that the dev would not be the one making the update notification. Communication of issues normally would be sent via manager/talking head/spokesmonkey to ensure the appropriate information is given in a consistent format. it also ensures that the feedback is going to one focus point.
Not on any team I've ever managed and I've been a project manager for 15 years. When something like this happens off hours and a dev or two is dealing with an outage and a short post or tweet needs to be made just to let the users know that the team is aware of the problem, a fix is underway and possibly an ETA of when service will be restored there is no need to get the social media rep involved. That just adds more delay before the users get information they should have ASAP. As the incident Sunday showed they may never get the information at all. The may only find out service is restored by trying to use the service or by some other user doing so and then posting somewhere that it is back up. Which erodes confidence in the company's customer service.

If you can't count on your devs to post "We're aware the log in server is down. We're working on a fix and hope to have the service back up soon." you need to reconsider your devs.
 
Our most sincere apologies for the dropped ball.

When you see a ball there on the ground you know it was definitely dropped, and sometimes you care to know how it got there. For those who do, I'll explain.

It typically falls to BJ or a member of the Customer Support team to make a post announcing an outage. This was just a strange circumstance on a Sunday where EVERYONE who would normally post about an outage was out at the same time and it simply didn’t occur to the dev who fixed the issue to make a post as it’s not normally his job to post anything at all.

However, this led to a new protocol. I will now be posting these notices. I repeat, Rone now has the ball. Give me a three-steps-out-the-door headstart?
 
Not on any team I've ever managed and I've been a project manager for 15 years. When something like this happens off hours and a dev or two is dealing with an outage and a short post or tweet needs to be made just to let the users know that the team is aware of the problem, a fix is underway and possibly an ETA of when service will be restored there is no need to get the social media rep involved. That just adds more delay before the users get information they should have ASAP. As the incident Sunday showed they may never get the information at all. The may only find out service is restored by trying to use the service or by some other user doing so and then posting somewhere that it is back up. Which erodes confidence in the company's customer service.

If you can't count on your devs to post "We're aware the log in server is down. We're working on a fix and hope to have the service back up soon." you need to reconsider your devs.

Well kbs66 in my experience communication between the dev teams and external clients is controlled. Given that every word of a communication here is dissected, analyzed, and interpreted for hidden meaning it makes sense why devs are not posting here in official capacity. It would only lead to "well so-and-so said X".

But hey, YMMW.
 
Back
Top