Return of Reckoning

Hey all,

I just wanted to post about the events in RvR on the evening of 2/15 and the results of these events.

Let's start with the vod:

https://www.twitch.tv/videos/1739144580

We have destro sieging a keep, with an unknown number of defenders inside.

at 28:30 we see the first Order warband enter the keep through a guarded door unflagged by exploiting something that's been a problem since live.

29:30 we see warbands TWO THREE AND FOUR enter the keep the same way, through the same guarded door, unflagged!

At this point, starting at roughly 45 minutes into the VoD, someone on destro decided that it's only fair to pull the keep lord outside and kill it, so the postern door is no longer defended and destro is able to push in through two doors instead of one. Destro, after all, still does have to fight through those 4+ warbands of order to secure this keep lol.

As a result of this, certain people received a short ban. As far as I am aware, It was any destro that partook in the siege, regardless of their participation in this event but I can't say for certain. A lot of the discourse regarding this event is available on the official RoR Discord.

I guess as responsible players of r0r, we really have to ask the 4 warbands who exploited into the keep: *Who needs a defensive position when you can ignore the defensive position?"

Look forward to hearing what the community thinks about these events, good luck out there!

The 30s delay to getting rvr flagged is working as intended, annoying as it is for some keeps.

Killing the lord outside is not intended.

/Thread?

Great feedback, let's hear from our next community member!

ban xrealmers

The problem here is this: "someone on destro decided that it's only fair to pull the keep lord outside and kill it".

It is not up to individuals to 'decide' whether or not an exploit is 'fair' or not. And to expect nothing to happen when a GM is made aware of actively exploiting something is pretty questionable in itself.

We're aware of the 30 second flagging being an issue with some keeps and are looking at adding some stopgaps to make this less of a problem - additional screenshots and suggestions to which keeps this is heavily impacting to the BT would be beneficial.

Trying to identify and replicate the lord exploit is much harder however and is taking us longer to address - which is why in the interim we have warned, and given temporary suspensions to those who actively abuse it.

If any individuals feel that their ban was unjust, they are welcome to post a ban appeal - but we're not going to have an open discussion on 'is this exploit exploitable and if not why is this exploit not exploitable'.