Please nerf Death Palace floor 50 Boss!

[Capriana]

In all honesty, I don't remember ever doing a tutorial with the eye animation. It was the first time for me seeing the eye in Palace. Then again I quit getting to lv 50 and came back after 2 years. Maybe they added the tutorial somewhere along the lines I was away ...

To the point. I was one of those stupid people, along with everyone else in my party at the time and we wiped easily. Then I made it my responsibility to study it online and learned all the mechanics, then I made a macro explaining the mechanics, which wasn't easy being on PS4 with no keyboard. Then every time I get to floor 49 exit, I do the macro. Without fail every time the party kills the boss and nobody gets hit by the AoE attacks.

Not gloating, but perhaps instead of ranting and complaining and spreading negative energy, you can just do the same and force teach people the mechanics, don't just ask them if they know and assume they do ... Teach them, help the community grow.

[Felis]

In all honesty, I don't remember ever doing a tutorial with the eye animation. It was the first time for me seeing the eye in Palace. Then again I quit getting to lv 50 and came back after 2 years. Maybe they added the tutorial somewhere along the lines I was away ...

Some "area of view" mechanics had the eye animation, some not. At one point the devs streamlined all mechanic animations and all "area of view" mechanics got the eye animation. There is no tutorial, just simple mechanic learning by doing dungeons.

And buy a keyboard for your PS4. A cheap one for 10$ is all what you need.

[Vidu]

In all honesty, I don't remember ever doing a tutorial with the eye animation. It was the first time for me seeing the eye in Palace. Then again I quit getting to lv 50 and came back after 2 years. Maybe they added the tutorial somewhere along the lines I was away ...

Serious question: Why do you think we need a tutorial for this? Or: Do you really think we need to get an explantions of mechanics straight away when we see them?

We have a lot of mechanics in this game that we had to somehow figure out - stack markers, dont-stack markers, turn around, get close to the boss, get far away from the boss, stand in this AoE to share the damage, get over in that puddle to get a status-effect that protects you from the next mechanic, tank switch once your Co-tank got so and so many stacks of that debuff, cleanse one debuff but not the other one...
For me a lot of fun comes from running content blind and figuring mechanics out by myself (well, within a group of friends who like to do the same thing) - isnt part pf the fun in more or less any RPG to figure out how to deal with a boss?

Having this eye for every "turn around"-mechanic now is them streamlining it - so one can say "Oh, I've seen this before - back then this worked, lets see if it works here aswell!" or if they havent seen it before they can figure out how to deal with the mechanic - but do we really need an ingame guide for everything? Flashy texts on the screen that are flavoury but instead instructions on how excatly to handle a mechanic?
And wouldnt that make the game pretty dull (or even more dull...)?

[Kaethra]

Serious question: Why do you think we need a tutorial for this? Or: Do you really think we need to get an explantions of mechanics straight away when we see them?

We don't.

I did a trial roulette yesterday. Titan HM popped. I didn't see people screwing up when the bombs popped. It seemed everyone knew to stack on the bombs that popped last and then move to the first once they start exploding.

There's no tutorial for that. Fight is much more complex than Edda. Everyone seems to know that one despite no tutorial. Why is that? Because its general player knowledge. That's part of this being a MMO, not everything is handheld for you by dev created mechanisms. Sometimes the players need to step in. Its how we succeed. And sometimes we get a player or two who aren't up to par. And then we have to work a little harder. It happens, but its part of the plan you signed on for when you queued for the content in question.