Mercutial Admin replied

503 weeks ago

Ok… So I want to talk a bit about Digititis. I agree it's a garbage mechanic. But so was Brand in T12 and people didn't complain nearly as much about that even though it relied on the same server tics along with having a limited window to make the pass during the cast bar. In fact, one could argue that it was MORE difficult in that way.

That being said…. I would like to clean this up. And as such, I have quite a few ideas on how to do so. To be honest, I'm extremely comfortable with it and would be lying if I said I didn't hope I got it every time so I could control it. So let me share a couple of insights that may or may not be known in the hopes that we can start working on adds nearly every single pull.

1) Those marked head immediately to their respective spots. EVERYONE else hang back. Simple enough and I trust we do this.

2) IF two marked people are knocked back to the same area, do NOT both run forward together - unless you'll both be swapping. In this case, do not count on making the swap on the run. What you see on your screen is not what Joe Blow sees on his/her screen. That's why it always looks on like you're out front during resin drops after jumps in A1S. You're not. This is known as screen latency. Don't trust it. It will screw you over. Once at your marker… FREEZE. The other person will do the same. Server tics do not take long even if you're on the ass end of one. However, they will reset the register window if you move. If both got there and froze and did not make the swap, one or both of you took too long. Plain and simple. Sorry

3) IF two marked people are knocked back in the same spot and they are NOT swapping, do NOT both run forward immediately. Instead take a split second to separate left and right before it registers. Think of them as mini-chains to break. I understand this takes a bit of raid awareness to not run in the same direction, but the key (like all chain mechanics) is to commit to one direction and stick with it. Don't juke and jive second guessing your initial decision. So many people can't figure this out and that's why chains in Thordan give some people so many issues. At most, one person will correct and move accordingly. Unfortunately, this is one of those either you get it or you don't things. I have faith that everyone here gets it. Once that second of distance is established run to your respective markers and freeze. Light a cigar if you feel so inclined.

4) If two marked individuals that are NOT meant to swap are going to be crossing paths on their way to the markers, the person who has to run the longest distance gets precedence. For example, if tank and DPS are both knocked East then DPS gets to go first to B. Tank holds back for a split second before heading to C. Again raid awareness wins the day here. Every single one of us should be able to tell the rest of the group who was marked by what every Digititis. If not, you're not seeing the board and that will be a death sentence in final phases.

In closing, I know it's a wonky mechanic. And SE could have obviously done more on their end to clean it up. However, groups that have it on lock only really see it fail once in a blue moon. It's not a "maybe it will work… maybe it won't" situation that most scrubs would have you believe. I understand that there will be instances where we can't fully explain it. But failing it more often than not and then preceding to justify it with an endless chorus of "well on my screen… yeah me too…. this is BS…. I SWEAR I was there on time" only sets us up for continued failure. Let's take charge of the situation and control it. We're all better than such a stupid little mech. Thanks guys.

Solarus Othmithus Admin replied

503 weeks ago

Like you say, Merc, the teams that are clearing this, or at least getting past this phase, are dealing with the same tick, the same SE, the same game as we are, and they've mastered it. We are at a point where we can not, to be honest with ourselves, blame the tick for this. We should have this timing figured out. I feel the same way, Merc: I love getting the icon b/c I know just where to go, sit still and wait for Hannah to come to me. Or when I don't get it, i freeze and don't move I see everyone moving in front of me.

I'm not sure if I agree w/ "precedence for the one who has to run further" because that seems to be more calculating then necessary, but the point you make that I think is the MOST CRUCIAL is RAID AWARENESS. I don't know if people are so fixated on pushing dps so much that they're losing track of what's around them, or trying to cast that last cure, or whatever, but MECHANICS COME FIRST. We do not need to jump back to Liquid so fast that we risk botching this mechanic.

So like Merc says, when the knock back comes, STOP! DON'T MOVE! It takes less than a second to check your icon (I don't trust graphic b/c the person next to you may trick you). If you have the icon, GO! If not, stay the extra second, smile, than make your way to A. It really is that simple.

There will always be the occasional slip (ie, me and Josh swapping when we were both running to our spots), but the errors with this mechanic have definitely far too frequent for our level and the time we've spent in there. In my example, I know Josh is always hitting sprint, and is always running to B. So being aware, even if I'm going to C, I will stop and let him go b/c I KNOW he's running faster than me. Think about what's going on, adjust, and let's clean that up!

Let's be strong, but also smart. Not only can we afford to take that short moment to make the smart decision, it's a necessity.

Mercutial Admin replied

503 weeks ago

Giving the person who has to run further the green light first avoids the several times we have had intersecting unintended swaps. I'm not overly calculating it. It's pretty much common sense. In fact, i would argue that this is the number one reason we fail this mechanic. "I accidentally swapped with so and so.."

For example… if you and Josh are both marked and knocked to a spot on the East side of the map that would force you both to cross paths, there would be no reason not to let Josh get the jump first. It's suicide not to. What I keep seeing hearing and seeing though are people lamenting "damn… we accidentally swapped" or "what are you doing?!?". Or hold up… hold up.

You say "There will always be the occasional slip (ie, me and Josh swapping when we were both running to our spots)". This nips that all in the bud. Know who is marked. Immediately assess the angles. And act accordingly.


last edited 503 weeks ago by Mercutial

Solarus Othmithus Admin replied

503 weeks ago

Josh and I swapped that one time, not because he and I were knocked into same area, but because I was running north, he was running west, I thought I had timed it to be ahead, forgetting he had sprint. Totally my fault, but because I wasn't being aware, he cut right through me and we swapped. I file that info away, and I adjust like a good little raider.

I do exactly what you state: if I find myself knocked back with someone else, regardless of debuff, my first instinct is to take that step away from him/her to avoid it (common sense). In that second, I'm taking note 1) do I have a debuff? No? Keep my ass here. Yes? Then 2) did I see a graphic on that person next to me? No? GET MY ASS TO C!!!! Yes? It's not Hannah, let them go first. It is Hannah? Run it together.

Mercutial Admin replied

503 weeks ago

That's the way. I will say the mistakes on Digititis have been fewer and fewer of late. I would just like to weed 'em out even more.

Thejoshfoote Admin replied

503 weeks ago

What works for me really well as a healer. Is I pop sprint right before wash away and start running while knocked back. I can be at b within a second from knockback usually find myself waiting. That being said I always run straight to b. The only thing I avoid is direct middle and running by c

Solarus Othmithus Admin replied

503 weeks ago

No, i WANT you doing that, and I hope Hannah does it as well. Like I said, it was my fault for not being aware at that moment. I saw your position and mine and thought "I'm good". But I knew you had sprint on, and I ran into you. I'd love to say "but you see I didn't do it again!" but we never got back to that spot.

Mercutial Admin replied

503 weeks ago

No reason you should be avoiding direct middle Josh. If you're knocked back due North, then run right thru middle please. Taking the long way (sprinting or not) can sometimes be bad.

Thejoshfoote Admin replied

503 weeks ago

I don't avoid middle but I never run straight thru it. I make a straight shot to my mark. No dodging or weaving. like I said tho if u pop sprint and run straight to ur spot sometimes I'm there and ppl are still waiting to see there marker. That being said since I know I'm guarenteed to need to make a switch I just bolt I never check or wait for anyone or even to see the markers.

Solarus Othmithus Admin replied

503 weeks ago

That's it right there, Josh. You and Hannah have a set spot EVERY time, so it's mechanic that you guys hit sprint and run to straight to B/C every time. Kahlan or I have a set spot EVERY time, so as soon as we get knocked back, it's simple: go to C or not. Only one DPS needs to run to B, so three people should NOT be moving, and yet we run into people in the way.

The truly frustrating thing is that it really is SO SIMPLE. If you have the icon/debuff, get to B/C and trust that others are out of your way, only worry about the 1 other person running across that you MAY encounter. If you don't have the debuff, step back and away, and just wait the 1-1.5 seconds for it to be obvious that the ones who DO have the debuff are handling it and you have a clear path to B.
Please log in to post a reply.