Apex Forever | LIGHT-FARM | UNIQUE CONCEPT

[stimpy]

You should wait untill they fix the new bug,then hope for no more bugs as major as this one.

[xftxft333]

Wait. Server is offline.

[Aesteris]

Wait. Server is offline.

Yes, the server was offline; Patch for the latest issue has been made and it's currently being updated, we'll be back online in a minute!

[twostars]

Yes, the server was offline; Patch for the latest issue has been made and it's currently being updated, we'll be back online in a minute!

We're just looking into the mob thing first, since that's the only other major issue that's persisted. I haven't had a chance to look into it personally yet.

Registered an account and logged in for the first time just fine. After that a huge lag ingame happened so I exited before seeing the DC msg which caused that warning that my account is in use when I tried to log back in. So I waited, a lot, but the msg persists to show. Any idea on what I should do?

It's not you. The server was just still "up" because we were inspecting it, so your session never actually "disconnected". It has now though, now that we're done with it. Sorry for the inconvenience!

[silentdj]

If you have time, a lot of us after the first patch cannot receive armor from the NPC, only getting uniques and weapons, Ty!

[Manhattan]

It's not you. The server was just still "up" because we were inspecting it, so your session never actually "disconnected". It has now though, now that we're done with it. Sorry for the inconvenience!

No problem at all. On a side note, you should really open a shoutbox in your forum for a fast communication between you and the players, just to keep us on the loop.

[cop]

Guys why are you even mad? If this would happen in official it would be bad. It's essential to run all this through before the official release. Right?

[LADY]

when will up?

[Dogamon]

Guys why are you even mad? If this would happen in official it would be bad. It's essential to run all this through before the official release. Right?

Well I hope every bad thing happens on beta so that we wont have any problems on official launch.

[razor]

23;00 daadadadada

good thing tomorrows saturday eh?

[FrenchItUp]

I just came home from work, is server offline? :B

[LADY]

good thing tomorrows saturday eh?

dont understand u

[twostars]

If you have time, a lot of us after the first patch cannot receive armor from the NPC, only getting uniques and weapons, Ty!

I'll get Aesteris on that after we get the mob thing out the way. That, at least, can be handled live.

when will up?

Very soon. We're working through the problem at the moment, but we'll give it 10min and if it's not fixed by then, the server's just going up regardless, while we continue at it.
We'll get it, just worried we're taking too long is all. The issue only affects Moradon, so it's not a *huge* deal. Just rather annoying.

I just came home from work, is server offline? :B

Yes.

No problem at all. On a side note, you should really open a shoutbox in your forum for a fast communication between you and the players, just to keep us on the loop.

I'm against shoutboxes, but in this case it does work. Thanks. Right now we're communicating via IRC, so people in the people in there are helping us spreading the word while we're working on stuff, but that'd help somewhat (assume people check the forums).

[LADY]

i'm against shoutboxes, but in this case it does work. Thanks. Right now we're communicating via irc, so people in the people in there are helping us spreading the word while we're working on stuff, but that'd help somewhat (assume people check the forums).

like in sweet 90's

[twostars]

Alright, we took a little bit longer, but the issue should be fixed now. Build server's just compiling it now, so once that's done (may take up to 10min to finish), we can update beta and start it back up again.
While that's happening, Aesteris is handling the armour issue. :-)

Thanks again for your patience!

EDIT:
Nope, it's built already (yay!). Updating the server now and starting it back up.

EDIT 2:
Well, okay. While we (thought) we repro'd it locally, and the issue cleared right up, it seems to still be occurring on beta. We'll continue to investigate that, no worries there.