Latest news

  • FYI
    EDIT 29_07_2016 : Nothing new will happen until sunday 31th/monday august 1st (don't take this as an ETA please).

    After many tries and exchanges with provider it appears the new hardware doesn't fit to our needs and our actual provider doesn't want to make asked modifications or understand which kind of configuration we need.

    As precised ealier, IRL obligations doesn't help to be quick and none can actually replace/assist DaScoub in this very specific part. We are gonna change another time (...) the hardware (and maybe the provider) which causes some unexpected extra delay.

    We could have restarted the server with the exactly same config as before and you would be able to play right now. This would have been an half solution, exposing you and us to the same problems we experienced some weeks ago, which isn't expected. We are looking for stronger solutions and sadly it is much harder to manage.

    I would be very glad to announce you precisely when Ror will come back, but like you, i can just cross fingers and take my pain with patience.
    Fri Jul 29, 2016 8:38 am View the latest post
  • Some (small) news; behind the curtain.
    STATUS :

    Hi RoR peoples !

    I don't express myself very often but i feel it is important bring some light on the actual situation.

    As you can see and undergo, we are experiencing an important shutdown period since 2 weeks.
    To begin with, be assured that Return of reckoning will.... return (as soon as possible : read carefully).

    All the story started with massive DDOS atack. To be honnest, RoR and DDOS is a lonnnnnnng story and we are attacked quite every days since a years (or more). Some weeks ago DDOS has won.

    Because of that, we have experienced some DB issues ( guilds, loading datas...) and discovered some important issues in the project forcing us to modify part of the code ( i'm not a pro, so excuse me if i'm not very precise or accurate). Emu becomed unstable. The "alpha" phase is not just a word.

    Actually we are investing in new hardware and set it up is harder than expected. Be assured the guys who are working on it know their job and despite this, have big headashe.
    In the same time, team is still working on the project to improve your futur experience and make ROR better when he will come back.

    Summertime doesn't help. Some are going on holidays, some have IRL obligations ( work, family), and we all have to deal with it. I don't need to remind you that RoR team isn't a professionnal organisation, and sometime time to work on this project is short.

    This situation is stressfull for everyone. For you because you are quite blind of what happens ( Ror will come back? yes ? no?), and for us ( ror team), because we hopê everydays since a week to success to make the server up.

    So i apologize if some of you feels assaulted by some staff answers on this forum. We try our best to be back to a normal situation, and answering 1000x to the same "can't connect" post everydays may wire up.

    Until this banner
    become like this :

    Don't expect to connect.

    We have put this BIG visual information to be the more visible as possible on the homepage. I don't know how it can be missable. Sadly it seems some who are looking "everywhere on this forum" succeed to miss it (and feel offended when a GM have some rude reaction).

    So if you have a better solution i'm interested.

    Now i hope you all have a better understanding of the actual situation. I wish all this will be a bad remembrance in few days. I thank you all for your trust and for your patience.

    Tue Jul 26, 2016 12:55 pm View the latest post
  • A kind reminder and awareness to the community
    We've asked many times that the community to refrain from speculating who the perpetrator(s) are behind the DDoS attacks.

    I strongly advise you knock it off from now on as it's becoming a constant nuisance. Accusations based on false evidence or lack of evidence can and WILL be punishable for players.

    Any continuation of this behaviour can result in temporary bans. You've been warned...
    Fri Jul 08, 2016 12:52 pm View the latest post
  • Server Status

    A Note from Genisaurus:

    Genisaurus wrote:Earlier, I said this:

    Genisaurus wrote:There's no evidence that any one particular person is the culprit. Frankly, we're still compiling evidence whether or not it's even a DDoS - most of the symptoms are the same, but there is some other unusual behavior going on that makes it hard to confirm one way or another. Communication with the one or two people who might be able to say conclusively is blocked by time zones and busy schedules.

    We will let you know more as we know more.

    Well, the evidence has come in, been examined, and it's pretty clear that we are suffering a DDoS attack at the moment. Before receiving confirmation from our lovely network wizards, we were a bit in the dark: It looked like a DDoS, it walked like a DDoS, but it didn't quite quack like a DDoS.

    The problems observed by players over the last few days - when it has actually been up - have been caused by slow connections to the database. This includes things like guilds appearing to lose members, auctions seeming to disappear, characters missing, etc. The information is all there, it just isn't getting loaded properly. Now, there's a chance that this slow database connection might not actually be related to the DDoS, so we're taking the opportunity to make some much-needed improvements to our backend just in case.

    But the database aside, we're still experiencing incoming traffic roughly 10x higher than we usually do, and this is testing the limits of our bandwidth. In these conditions, we cannot operate. We're not going anywhere, but the server won't be able to be started until the attacks slow enough for us to accept the usual player traffic. The server will be available as the DDoS attacks slow, but expect it to be spotty and unreliable in the coming days.

    We do ask that our players not spend their time speculating as to whom the culprit(s) behind these attacks may be. DDoS attacks are notoriously difficult if not impossible to trace, and as such there is absolutely no evidence for any accusations beyond conjecture and circumstance. It takes an unstable and sad person to want to DDoS a private server, but the last thing anyone wants to do is to encourage other unstable and sad individuals to try to be vigilantes in our defense.

    For more information about the status of the server, refer to this topic: ... =8&t=15205
    Thu Jun 30, 2016 6:22 pm View the latest post
  • Changelog 27th, June 2016
    We took the opportunity to patch while the servers were dead. Here's what's new:

    [Anniversary event]

    The second year anniversary event has been extended by a week. Order now has a follow-up quest after the Slayer Chronicles Ending that allows them to pick up the cape, if they missed it the first time around. The dye quests in T1, T2 and T3 should now be repeatable and have no issues being completed. The gameobjects for both T4 event quests may continue being bugged; wait until a restart to attempt investigating the Dig Site or recovering the Slayer Heirlooms.

    [RvR Campaign]

    - Siege weapons will now decay once deployed and unused for a period of time. Using or towing a siege weapon should reset this time.
    - There can be no more than 2 GTAoE style siege weapons spawned per realm at any keep.

    - A siege weapon's owner can now reclaim the weapon when it is being towed.
    - Siege weapons can no longer be towed outside of RvR areas.
    - Fixed an issue causing players to be unable to deploy a ram if a keep was made safe.


    - Added cast times to the bomb/part dropoffs in Howling Gorge and Serpent's Passage

    -Added Khaine's Embrace scenario handler.

    Adressed Tickets

    - [6906] NPC: Rotting Greatsword - Fixed NPC faction
    - [6899] NPC: Blindwing - Removed duplicate spawn
    - [6896] NPC: Nurgling - Fixed NPC faction
    - [6893] Game Object: Unique Flask - Removed duplicate spawn
    - [6875] NPC: Aviden Mirithas - Fixed faction

    - [6943] Quest: Cold Hard Steel (dye quest) has been made repeatable.

    - [6938] RvR: Fixed an issue that prevented attackers from placing siege within an area that should have been acceptable
    - [6930] Scenarios: Howling Gorge will now bolster appropriately.

    - [6944] NPC: Nosebiter duplicated spawns removed.

    [Other Changes]

    - Corrected the endpoint code for pull abilities. Incidences of players being pulled to a single spot and being rendered unable to move should be reduced.

    - NPC: Fixed the faction of Rotting Masons.

    - Numerous quest conditions fixed/made possible.
    - Replaced worthless stats on many items to ones relevant to class (ongoing).
    - Deactivated the repeatable option on Wounded in Action quest.
    - Plugged Temple of Isha terrain exploit

    - Added a quest for Destruction akin to Order's 'The Mysterious M.B." achievement unlock quest; Da Stunty Mystery. It's given by Ryun Da Fawkz in the Inevitable City's Apex.
    - Cleaned up mob spawns around The Inevitable City's flight master, north of the Apex.
    - The Skullhorn Gors/Ungors, and Bloodpelt Gors/Ungors in The Inevitable City have been made neutral, and are now in a fighting stance with one another without claiming the Menacing Watcher between them for their own.
    Tue Jun 28, 2016 12:05 am View the latest post
Martyrs Square (EN)
Player count :
Up since:
2016-07-28 21:31:11
Faction ratio (Order/Destruction) :
Tier 1 (2) :
Tier 2 (2) :
Tier 3 (2) :
Tier 4 (2) :
Total :

Login  •  Register