Questions for the Community Rep Moogles

[Zhronne]

I wasn't worried about AoE move on myself, more on my pet taking damage. But I'd probably be using RDM/WHM one so that shouldn't be a big concern.

And about pages, I think I'd much rather get the same one with the "repeat" option and repeat it over and over and over and over without having to go back to the Book.

Thanks for the hints tho

[Gael]

It's not 1 "boost" per page and per game day ?

[Zhronne]

Yes, just like the special book Points you get.
But the point is that I *personally* find it annoying having to stop to go back to the book, then back to the camp. So I prefer using the repeat option and stay there for a few hours at least

[Gael]

lol ok ok ^^


EDIt: it seems they updated this part, now you can have a boost on the same page, during the same game day

[HimuraKenshyn]

All i can say is SWEEEEEEEEETTTTTTTTTTTT........

[Annalise]

Things still missing:
Heat capacitor -> Supposed to remove the flame consumption ( was promised a while ago)

A few other people mention this I've seen...

Originally they said they were going to remove the flame consumption. Later on, they stated that they changed their mind and that they weren't going to. So really, they're no longer going to.

EDIT: Just looked... I can only find the part where they said they were adding it, then they said they were postponing it... I swear I saw one that said they were scrapping the idea... but perhaps I am wrong on that one.

And I was also thinking about the mana booster... If the fast cast is significant (i.e. casts the spell a few seconds faster) technically it still is reducing recast time, because the timer starts counting down recast faster. Also, individual spells should be up faster (i.e. Thunder V) which is nice.

[Kristal]

True. Spiritreaver shouldn't be too spammy. No more fear about wasted cooldowns for Drain/Aspir/Absorb-Int.
Still another thing that they should fix is the max range the pets can be engaged. I think atm it's something like 13/14 yalms?
Asking for them to give us >20' range would be too much, but at least they should allow us to reliably keep them at >15'.
The majority of TP moves are within 15 yalms of range after all, being able to keep them at that range would already be useful enough.

You can deploy your (caster) maton at 17' from target, but if the maton isn't closer to the mob then you it will run into melee range of it.

What needs to happen, is to increase max_deploy range to max_ranged_attack range (25') or max_weapon_draw range (30'), and then let the maton run towards the mob until it gets close enough to cast on it. That's the same distance normal mages stand when dealing with the overly abundant 20' aoe. If you want to deploy the automaton in melee range, all you need to do is run into melee range yourself, or use a combination of heads and frames.

[Zhronne]

I know what you mean, but asking for 20.1 yalms may be too much. I'd be happy enough to see it stay at 15,1 yalms honestly >_> It always get hit by 15 yalms AoEs
It was a pain especially at Anguis back at level 80, I Remember I had to abuse the deploy > let it start casting > retrieve, but it was still painful, Anguis has a lot of dangerous AoEs

Altough Anguis probably is not a good example here, since if I'm not wrong he has quite a lot 20 yalms ones?

[brayen]

i think the main point is there has to be a risk, even whm gets bombarded by spells and ja that require closer range, what they want is to make sure if we are going to be meleeing we cant just have a safe nuker/healer in the back. Weather this is overpowered or not i dun think it would matter but i dont think it is needed either. Only thing id liek ot see is a "Stay" command so its easier to position it if anything.

post these changes i would just like to see a tweak to maneuver durations, mainly for the pain and delay they cause. but they said they were not doing this already i think so hoping these changes are as good as they sound.

[Kristal]

i think the main point is there has to be a risk, even whm gets bombarded by spells and ja that require closer range, what they want is to make sure if we are going to be meleeing we cant just have a safe nuker/healer in the back. Weather this is overpowered or not i dun think it would matter but i dont think it is needed either. Only thing id liek ot see is a "Stay" command so its easier to position it if anything.

BLMs/WHMs generally don't bother with spells that put them inside the aoe range... and where a BLM/WHM can spam nuke/cure spells, the automaton can only cast one spell every so often. (Even the upcoming change won't let it spam cure spells like a WHM or RDM can.) So it's more of a risk vs reward thing, and automatons don't have the luxury of having other players around to cure them or to spam nukes (the reward) but still are expected to eat every aoe beyond 10' (and if you misjudge your deploy range, right up to melee).

A Stay command would be a nice thing, since it also allows the automaton to remain in position between battles and even to remain in combat mode. It would prevent Cure VI being cancelled because the mob died, allows the maton to cure/remove status effects between mobs without deploying on an unclaimed target, avoid having the rescue/reposition the maton due to the mob running to a party member and out of range. On the negative side, you run more risk that the maton cannot target the mob with enfeebling/nuke spells, or even to cure you or the tank due to walking or being knocked out of range. It would be like a WHM under the effect of unerasable Bind while the tank gets pummeled just outside cure range. So such a Stay ability would have to be used in the right place at the right time, or it might work against you. Perfect for PUPs