Everything wrong with 5.3 AST sleeve draw [Translated JP duplicate thread]

[hiz]

While I'm a it...

But nevertheless there still stands issues with technical accessibility -
1. Controller players. I don't think I need to say much more about this.
2. Players with high latency. I used to have bad ping which affected my opener because cards came up with a delay which made it harder to react to, as well as being unable to double weave. This adds more to the "clunkiness" as you're stuck playing solitaire for a longer time if you can't even double weave redraw and play/MA in the same window.

True, and I know you probably agree with this but to spell it out for others technical accessibility (especially latency) are issues that ideally should be resolved independently from your job toolkit. I've played myself on 300 ping once for a few years and boy that felt... not good, but I would rather them fix their networking than rework every job to cater for pings like that because it would ruin the game experience for everyone else.

It depends if you go for full min maxing Dnc or not,

I apologize for not being concrete enough. Why would anyone care to optimize in PF...? By PF context I was pointing to environments where your tanks immediately start pulls without countdowns and no one cares about buffs. I can't speak for Western DC's but this isn't uncommon in JP. When both jobs are forced to not wait, DNC can still fight, AST can't. That said, I understand that in optimization context the issue was already there and agree with your point that it contradicted the Aetherflow lock.

As for controller players, my personal take is that it's their fault for choosing to play on controller. I also understand the view that if SQEX is going to support controller, they should do it well... but in my opinion this should not come at a cost for the rest of the population, especially when device for most players is just a matter of choice. I'm not asking for agreement, but I will just put it out.