That's what I thought at first, but apparently Yoshi is trying to remove the need for jobs to wait before pulling. That's why I suggested a separate action so it wouldn't put Aetherflow itself on cooldown, removing the need to wait for Aetherflow before pulling.I agree on everything but the "second" aetherflow outside combat, I think that they simply should remove the "Can only use in combat" restriction instead of giving us another skill that do the exact same. Hope the devs listen to the feedback and make changes for 5.05/5.1 version, right now scholar feels awful.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.


Reply With Quote

