Search Results for 'summoner'

[MiqobotKeymaster]

miko wrote:

Ruin II, III or IV are not oGCD abilities, neither are the Egi Assaults.

Of course they are not. The question was what GCD spell to use to weave oGCD abilities.

miko wrote:

During Dreadwyrm stance, Ruin III becomes an instant cast ability allowing for 2 oGCD weaves. Meaning you can use Summon Bahamut as an oGCD right after a Ruin III while Dreadwyrm stance is up.

miko wrote:

Now if we had saved up 4x Ruin IV, we can get those used as instant casts during Bahamut without need to ever use Ruin II. Ideally we also use the final Ruin IV at the end of Bahamut phase to get our 8th Wyrmweave in, but this might be too min-max than really needed.

All right, these suggestions are more specific and this is indeed something we can work with.
Thank you for providing the detailed feedback.

While working on Summoner rotation we already tried implementing it in a similar way, but we encountered multiple issues such as Summon Bahamut not triggering in time for second weave, GCD clipping, overcharging Egi Assaults, Egi Assaults going to waste due to Bahamut erasing pets, and several others. According to the preliminary development report, it could take 1-2 weeks to fix these issues and the overall gain from implementing the perfect rotation would be +1% DPS. This is the exponential cost that was mentioned earlier.

We can try implementing them again, but first we have to understand whether this is indeed what the community needs. We have recently discussed a similar problem with Machinist imperfection and Drill drift. So now we have to ask this question again.

Should we delay the release of next version for 2 weeks for Summoner optimizations?
And if we go this way with Summoner, why shouldn’t we do the same for other jobs?

[MiqobotKeymaster]

Yes, this is one of the guides we have been using when implementing Summoner rotation.
Miqobot tries to follow it as best as she can while keeping the algorithm reactive and adjusting on the fly. It is impossible to follow it with 100% accuracy due to multiple factors, that’s why our goal was 90% which is currently achieved.

miko wrote:

Miqo currently uses ruin II during bahamut phase, not causing a wyrmweave. Previously you could cause wyrmweave with ruin II but this has been changed since early shadowbringers and never adjusted.

We have just verified this information and we can see Bahamut reacting to Ruin II with Wyrmwave correctly.
Would you please clarify, are there any additional steps to reproduce this issue?

miko wrote:

Without consuming too much development time perhaps it’s prudent to just fix the use of ruin II during bahamut. And for future optimization if the expansion does not change it saving up as many charges of ruin IV’s as possible pre-bahamut trigger (without overcapping).

Thank you for your request.
However, it is not very different from the previous formulation. We still have to understand how to handle the contradiction described earlier.
If not Ruin II, what should Miqobot cast for oGCD weaving while both Egi Assaults are on cooldown?
If using Ruin IV before Bahamut phase is not allowed, what spell should be used to weave Summon Bahamut?

[mikoParticipant]

Hey miqo here is the information with regards to the theory behind it, hopefully it helps with regards to potential fixing the rotation.

https://www.akhmorning.com/jobs/smn/guide/rotation/#bahamut-phase

Miqo currently uses ruin II during bahamut phase, not causing a wyrmweave. Previously you could cause wyrmweave with ruin II but this has been changed since early shadowbringers and never adjusted.
Without consuming too much development time perhaps it’s prudent to just fix the use of ruin II during bahamut. And for future optimization if the expansion does not change it saving up as many charges of ruin IV’s as possible pre-bahamut trigger (without overcapping).

It’s not a huge priority for myself, but it’s one of the very clear rotational problems I’ve seen since early expansion handicapping summoner slightly.

[mikoParticipant]

Hey miqo while you guys are publishing a finalized version before expansion end, could you take a look on the summoner rotation and how it currently functions?

– Using ruin IV pre bahamut (should never be used unless overcapping)
– Using ruin II during bahamut (should be ruin III or ruin IV – 4 stacks saved up)

Ideally the rotation without movement would never use ruin II at least. And priority for ruin IV should ideally be saved up for bahamut phases without overcapping. It’s still a relic from early expansion logic you’ve released but never got updated.

Thanks in advance.

• This reply was modified 3 years, 11 months ago by  miko.

[pussyfootParticipant]

One thing I will mention and someone may have already said: classes that are busy with a lot of fast button mashing can have difficulty moving out of AEs.

For instance: Gunbreaker vs Paladin

Paladin rotation is pretty simple with very few button presses at 80. Clicks per minute are low. When orange hits the ground, you can move using your keyboard pretty easily.

Gunbreaker has quite a few clicks per minute (dark knight as well). Often Miqo will fight you, trying to get in those off globals and such. So you’re hitting your A key and you stutter step, often not getting out of the AE that you would have cleared easily on another class.

A work around is to move with the mouse, but muscle memory sometimes makes that a newly learned ability.

The classes I’ve found that work best are Bard, Mch, SMN, (though summoner has the same stutter step at times), Dragoon, and paladin.

Miqo is also a very adequate healer. Though there are some strange things that happen when in an 8 man group and someone just out of range. She sometimes seems to forget she’s healing and you have to step in and push a button. (It could be that 15 seconds for moving thing, but I’m not sure.)

Out of the healers, I find that SCH works the best. AST can often have so much going on that it fights you though it heals well. White mage, I dunno it goes from Regen every single time someone moves to never regening.

Another issue I’ve noticed is that miqo will always start SCH with a group shield the very moment you load. So I turn her off every time I load.

[MiqobotKeymaster]

Thank you for reporting.
We have managed to reproduce your issue based on this description.

Indeed, there is a bug that prevents certain Summoner abilities from being triggered under these conditions. Your assumption is correct. The algorithm of SMN rotation identifies Aetherpact as ready for activation and prioritizes it before everything else.
Unfortunately this issue does not have an easy fix, because the logic is rooted deeply in the rotation algorithm. At the moment Summoner oGCD abilities are not compatible with Ignore Hotbar feature.

We will reimplement the algorithm in the next version.
Until then there are only two workarounds:

1. Hide Aetherpact behind a macro with a different icon. In this case you will not be able to see the coooldown.
2. Place Aetherpact on a Cross Hotbar. In this case you will be able to see the cooldown, but there will be additional transparent artifacts on the screen from Cross Hotbar itself.

We apologize for inconvenience.

Used to auto farm Fleece. This may be a little messy, I just made it for my own personal use. I found that it gets approximately 100 fleece/10 min.
—————————————————————-
THIS ONLY WORKS WITH LONG RANGE ACTIONS
—————————————————————-
Keybinds:
Icon(8, 1) is a macro I have to set my status to “Busy on” so I can’t be bothered while afk

Hotkey must be set for “Target Nearest Enemy” I use F11, you can do something else, but you have to edit the scenario.

Hotbar 1, slot 1 is used for the attack(can be changed)

—————————————————————-

I have tested this multiple times, and it seems to run well. Using my LVL 70 Summoner with Ruin II for fast speed, and Ruin III for slow speed… With the fast one, you will arrive back at the start just as the Ornery Karakul spawn, with the slow one they’ll already be there.

Chapter 1 gets you to the location

Chapter 2 is for instant cast actions

Chapter 3 is for 3 seconds or less cast time

There are instructions on how to set up hotkeys and everything inside the scenario file.

—————————————————————-

If anything stops working, or you have any suggestions or your own edits to the file, feel free to share with me! 🙂

• This topic was modified 4 years, 4 months ago by  Phoenix147.
• This topic was modified 4 years, 4 months ago by  Phoenix147.
• This topic was modified 4 years, 4 months ago by  Phoenix147.

[MiqobotKeymaster]

darkpokemon wrote:

So when you guys get Miqobot up and running again with the lvl 80 trust dungeon all the classes will be back up and running with the assist mode?

Yes, when core upgrades are implemented, all Miqobot features will be the same as they were before the patch. Assist Mode will be functional, with the exception of Monk rotation.

darkpokemon wrote:

I was asking about the full 80 rotation for example will tanks be the first to achieve a full 80 rotation followed by casters the healers and melee and so forth, or is it just random how you guys do it will it be let’s say monk first since new to update, then drk then summoner etc etc

We implement them in the order of algorithmic complexity. The easiest abilities get implemented first, and those that require complex decision making will be implemented later.
Dark Knight and Summoner rotations do not require any updates in this patch, they will be working as before.
Monk adjustments are the easiest, so yes, it is coming next.

[darkpokemonParticipant]

So when you guys get Miqobot up and running again with the lvl 80 trust dungeon all the classes will be back up and running with the assist mode? (I don’t know if it was clear what I was asking about specific classes being targeted first?) I was asking about the full 80 rotation for example will tanks be the first to achieve a full 80 rotation followed by casters the healers and melee and so forth, or is it just random how you guys do it will it be let’s say monk first since new to update, then drk then summoner etc etc

[KreossParticipant]

Im going to be honest and play Devils advocate, and the reason for this is I don’t know the size of your team.

I think alot of things are a issue of communication and not clear road mapping. For all we know you could have 2 people in a basement, working till the wee hours of the morning, slaving away. Or you could have 30 people. You just say your Team is working on things. You also have like 10 different work streams that you are working on, Between crafting, gathering, assist, dungeon integration, gold saucer. We get it. The problem is that alot of the work your doing isn’t visible to the end user, and the things that the end user sees are few and far between. I am so glad you added the 75 dungeon, its awesome and greatly appreciated. But summoner still doesn’t use Energy siphon.

Now you could take this as me being a jerk, or you can understand where im coming from in stating I don’t know what your working on or what your priorities are. I have 2 accounts and 2 subscriptions, I love your service, but a little bit more transparency would help so we know objectively what your goals are to do when, rather than having a wish list that gets updates with long term goals occasionally.

Lastly regarding monetization, I again don’t know your team size, country of origin, or any of the other information, But I would highly encourage you to think very very very hard before you increase monetization. Currently your price is fair for the love and effort you put into it, but even just by registrations to the forums we can see you have a large following and people using it. If you think criticism of your timeline between features is bad now, Just wait if you start charging a extra 5$ for Combat assist plugin and its not optimized.

I don’t want you to take this poorly, I love your service, I pay for two instances of it, and I will continue to do so. But communication is a 2 way street, and I don’t feel you have set clear expectations (Actual times on your roadmap, priority of updates Ect..) and thats where a chunk of the negativity comes from.

Signed,
A MIqobot Fanboy and a big fan

[iifetapParticipant]

BlackUnicorn wrote:

Also I am 71 Summoner, not quite thru Shadowbringers MSQ because lvl locked until I lvl to 72!

Holminster Switch is your best friend then. Run it overnight and wake up level 76+

[BlackUnicornParticipant]

Appreciate the response. I think for now I will get Miqobot and use the job assist function until I get a better handle on the game.

Also I am 71 Summoner, not quite thru Shadowbringers MSQ because lvl locked until I lvl to 72!

[iifetapParticipant]

uwu wrote:

SMN is one notch below only because it might waste a Phoenix or Bahamut when mob is close to death. Other than that it works amazing

You mind sending me a picture of what your hotbars are like for Summoner?

[iifetapParticipant]

Thank you, I think I’m going to mess around with summoner now.

[mundaysParticipant]

Tohka Yatogami wrote:

So I can see that bard and machinist are pretty much good to go for end game raids with little to no manual input required for it. I was wondering what other classes are there with the most recent updates that are good to use for end game raids with little to no manual input required?

As for my questions for AST, is earthly star supported by combat assist?

with the latest miqo update, combat assist included FBT in the summoner’s rotation so summoners would be a very very good choice. you just have to deal with the minor inconveniences of casting times of skills like ruin III and outburst but the overall dps more than makes up for these lol