5 seconds for leaving reive area isnt enough

[Clou777]

im getting sick of being chased to the border of the reives and accidently going over and before you know it, ur completely out and the mark wears off. we need this time extended and maybe a visible line of where the rieve battle area is

[OmnysValefor]

Seconded. There's a few reives that are so small i've been knocked out of them while supertanking. Moh Gates particularly.

30 seconds would be more appropriate.

[Clou777]

5 seconds only gives you enough time to maybe notice and read the warning and by the time you react to it you've been kicked

[Kristal]

Seconded. There's a few reives that are so small i've been knocked out of them while supertanking. Moh Gates particularly.

30 seconds would be more appropriate.

30 seconds is way too long, you could pull the mobs through half the zone in that time. 10 seconds should be enough.

[Fynlar]

5 seconds wasn't enough for Voidwatch either.

I don't know why they couldn't have kept it at 10. Not so short that you end up getting booted by accident, but not so long that you can't make an escape when you actually WANT to escape.

[Daemon]

Not only that, I hate it when you are trying to go to a colonization Reives only to have a lair reive in your way. Once going through the Lair reive just to get to the colonization reive, you have to wait 5 minutes to join. Well after the new update making Reives easier, you'd be lucky if a colonization reive will even last 5 minutes >.>

[oliveira]

The point of this mechanic is avoid us players exploit the behavior of the monsters to prevent them from killing us by leaving the area of the fight.

The OP is complaining exactly about having to leave the area to not be killed. If you don't want to leave the reive, let yourself be killed at a "safe spot" where you can be raised or re-raise.

If you go to a reive and expect to not be bested by a bunch of angry mobs, you're doing it wrong. ;)

[Anjou]

The point of this mechanic is avoid us players exploit the behavior of the monsters to prevent them from killing us by leaving the area of the fight.

The OP is complaining exactly about having to leave the area to not be killed. If you don't want to leave the reive, let yourself be killed at a "safe spot" where you can be raised or re-raise.

If you go to a reive and expect to not be bested by a bunch of angry mobs, you're doing it wrong. ;)

Actually the OP is wanting the timer to be longer to get back into the fight if something like running out of AoE range happens to put him out of range.

[Clou777]

or have a visible line of where the battle area starts/ends so people know to stay in that line

[Daniel]

Agreed, don't even need a good reason to support this, its just common sense.

[Kaisha]

or have a visible line of where the battle area starts/ends so people know to stay in that line
Been wanting this ever since Voidwatch came out. Have it visible when you're given the engagement buff icon or something.

[Kombys]

if you want to run away because too many mobs on you or someone decided mpk accidentally, 5 secs are enoughbut 10 should be just more ideal

[Trumpy]

I have literally gotten the first part of the message that you are out of bounds and immediately turned back and not gotten back in time. I think lag makes this worse sometimes. So many times I have been aoe pushed out or just didnt notice it til its too late (this is worse if you have two characters).
Doesnt help that you need to be at the max distance from the nest or root or what have you to safely fight one mob without agroing others most times (even then you can still agro others and end up having 3-4 mac trucks wailing on you). So trying to fight smart you then get pushed out of bounds with tons of melee hits aimed at you by the time the message pulls up, if you even notice it in your panic to stay alive and cure yourself, you get timed out.
I duo all the time and my whm gets pushed out without me noticing and I am as good as dead, which now i have to wait 5 mins before my whm can re enter and raise me since he cant do anything while im marked and he isnt. I wish raise could be cast at least to people in reives.

[Umichi]

or have a visible line of where the battle area starts/ends so people know to stay in that line

the line is the distance to disengage from the roots/rocks by running from it.

[Demon6324236]

If that's the case its even worse, if your targeting the objective with your weapon out and are forced to pull back you can very easily end up running away & making yourself put your weapon away, if its on the border for getting kicked, it will only stop you from getting back inside, thus, kicking you out all the same.

[Umichi]

the distance is quite huge....

[Clou777]

the line is the distance to disengage from the roots/rocks by running from it.

not everyone melees though, mages are back line jobs and it would be nice to simply know where that line is

[Umichi]

engage roots/rocks back up slowly until you disengage. walk back into perimeter. another good way to check and see if by casting.. because casting range is the same maximum distance as disengage range for mele.

[Umichi]

engage roots/rocks back up slowly until you disengage. walk back into perimeter. another good way to check and see if by casting.. because casting range is the same maximum distance as disengage range for mele.

once you get a feel for it you won't have to be cautious.

edit: sorry for double post i meant to edit my previous....

[FrankReynolds]

engage roots/rocks back up slowly until you disengage. walk back into perimeter. another good way to check and see if by casting.. because casting range is the same maximum distance as disengage range for mele.

AT several rieves the monsters pop and roam all the way to the line. I've had my white mage knocked out of the battle by knock back and not been able to get back in numerous times. Then there is the lag issue. Sometimes the line actually moves due to lag. I've sat in the same spot casting nukes and cure for 3 minutes and then suddenly been unable to target someone. Looking back through the log reveals that "surprise!!!" the game has decided that that spot has moved and it is no longer in the reive battle area even though I haven't moved my character the whole fight.

[Rwolf]

Yeah, I agree with this. It's really not a hard fix. Testing where the line is doesn't help all the time. As stated by some already, some areas the reive monsters go all the way to the line. Especially when you're in places like Sih Gates where the reive area is so small and you have multiple Craklaws spinning and knocking you around and stunning you. 5 seconds isn't a lot of time to react. If there is significant lag, you may lose a few seconds and just see your chat log filled all at once.

Solution:
1. Extend time outside of Colonization Reives and Lair Reives to 10 seconds.

2. Separate timers for entering Colonization Reives and Lair Reives (5 minutes still). So for example, you can bypass a Lair Reive once to get to a Colonization Reive. However, now you can't enter another Lair Reive for 5 minutes. This removes the abuse of running out of range constantly to de-aggro the same Reive.

3. Put a glowing blue dotted line at the perimeter of reives when the reive is up. FFXIV has a dotted line like this for zone perimeters. We know it's possible in FFXI through various glowing seals you walk through. (Windurst [S], Abyssea Martello/Bastion)

[Tsukino_Kaji]

The big problem isn't the 5 seconds, it's the delay before it tells you that you left. You start running back, but dont' make it in time, because you were 30 yalms away before it started counting.

[detlef]

The big problem isn't the 5 seconds, it's the delay before it tells you that you left. You start running back, but dont' make it in time, because you were 30 yalms away before it started counting.What you said isn't untrue, but that doesn't mean that 5 seconds isn't also the big problem.