Forum Replies Created
-
AuthorPosts
-
If they’re so inclined, they can maintain the current difficulty of unsyncing content by just making level differences have a huge impact on damage done/taken (in fact, I bet that is what they’ll do because it is the easiest way to keep unsynced content easy). We might go from (say) 120k hp to 20k hp in 6.0 but it doesn’t matter if level 61 monsters do 10% damage to us because of the level difference.
I don’t know if that’s what SE is going to do but I wouldn’t be surprised if that was their solution, since Yoship explicitly said he was conscious of people liking being able to unsync old content.
Thinking about it from a logical business perspective, because at the end of the day this is Square we’re talking about, making it less easy to unsync content means more time spent in the game, which in turn means more end revenue for them and more active time in the game which means people might re-sub more.
I can see YoshiP wanting it to be like that to appease and reassure players that like unsyncing content, but until it lands I won’t be overly optimistic about it purely because it makes more sense not to.
Having a level 61+ unscyned dungeon would still be worth even with the sync nerf. The nerf wont be as noticeable as people seem to think. While unscyned content will be slightly harder maybe then it is now you forget that there is still going to be a level cap increase. I would assume worst case scenario unscyned level 70 dungeon for level 90’s will feel like what they are now for level 80’s which is to say not easy like 50 under but not impossible. But level 60-69 stuff should still be doable solo for a level 90 job with miqobot.
That said its not something that is super important to have as it is only for the tank mount achievement. I personally dont think this needs a rush and it should fit under the umbrella of “Quality of Life” as in it is nice to have but not something im gonna stake my miqobot sub over.
Did you not see the presentation they gave? The squish is going to be massive, it’s not going to make unsync’d content “slightly harder”, it’s going to be balls to the wall unsoloable, for most of it. Unlike now.
They’re bringing the numbers down very very substantially.
Stat nerf is for 50-80 range. When youre level 90 unsynced will be just as easy.
They are reducing the entirety of the curve. So the curve will continue post lv80, from 50-90.
As in, no “full casting” of healing mode. In the sense that you would Divine Benison the person with the highest aggro (MT), you’d Regen them (because why not, it’s only 1 GCD), Tetra, Plenary Indulgence.
You can already do this by simply putting GCD heals on a single hotbar and telling Miqo to ignore it in advanced settings.
How did I miss this. This is BIG. Thank you very much
I actually might have found a way to make WHM assist work wonders if you’re willing to adjust to casting your own healings so you’ll actually only have to think about when to heal and Miqo handles the rest for you.
Here’s my proposal to the Miqoteam, can we have a button that handles/prioritizes oGCD stuff? As in, no “full casting” of healing mode. In the sense that you would Divine Benison the person with the highest aggro (MT), you’d Regen them (because why not, it’s only 1 GCD), Tetra, Plenary Indulgence.
But every actual healing would have to be steered into the bot before the next cast kind of thing. No unnecessary Medica 1/2s, no random Cure 1.
It’d actually be like an inbetween full heal support and damage prioritization only.
It seems simple enough to implement and adjust the current setup. (This could also apply to Scholar and AST)
March 26, 2021 at 4:00 pm in reply to: Would love to see level 57 – 60 dungeons in the squadrons #28986Flat 50-60-70 Dungeons do not give good experience, only the in-between numbers (say 50 to 60)
This is why because Squadrons can only go up to 60, the dungeons at the end yield crap experience in comparison with an in-between dungeon.
- This reply was modified 3 years, 9 months ago by Andylynyn.
Thats not surprising considering the average item level today is i520.
I doubt that’s really the average unless you’re only counting the people who raid every week. It’s likely closer to 510 with people wearing Exarchic gear.
Raid Gear is 530.
You can comfortably get 520 by this point on more than one class.What can you actually get from TT? Nothing but more TT cards and some MGP. MGP can already be farmed with Miqo.
Also, if you start using miqo to play in tournaments against other players you didn’t win, miqo did. That will also risk drawing attention to miqo just like if it had PvP support. I suspect the TT community is pretty small and people mostly know who’s in it, if a bunch of new people show up and start winning it’s gong to draw attention and possibly actions from the devs that can impact everyone who uses Miqo.
So even without having BLU in the equation TT support seems like not the best idea.
BLU actually allows easier synced soloing of content that can be used to earn a variety of things like relics.
Would agree with this, but you already have both One-Shot scenarios for BLU and it can still viably complete Squadron missions if you want to grind dungeons.
I vote for Triple Triad before BLU, because of the grindy nature of collecting cards from NPCs. Some drop rates are very low (i.e. Bahamut from King Elmer(?) in Gold Saucer) and I’d love for Miqo to be able to automate this. But of course, other features are more important at the moment, so ultimately I’d consider Triple Triad low priority.
I second this, before BLU. Word for word.
She already told us the standard is 4 – 8 weeks. With how perfect they like for their features to be something that may seem simple could still take 4 – 8 weeks.
Which is why I still asked directly, for a reply from the source instead of speculating.
The question to ask the Miqo team here is:
How hard would it be to implement it, in terms of resources and time? Would it need a full 4 week development cycle as well, or is it something of a more simple nature?
- This reply was modified 3 years, 9 months ago by Andylynyn.
This is not something the Miqo team can fix. This is with Windows Defender definition files, they blacklist things that are not “lol legal”, annoyingly, as a deterrent to people using them.
(I’m assuming in Miqo’s case because it tries to hook into FF’s process and read memory)
- This reply was modified 3 years, 9 months ago by Andylynyn.
You start crafting in FF, you start up the crafting part of the bot, it’ll appear to “freeze” or “not respond” for a bit while the solver does it’s thing running scenarios to try and find the most efficient route according to your parameters.
As soon as the solver is done, Miqo will be responsive again and it’ll immediately start crafting ingame.
I’ve found that if you want to do savages well and still have the bot propel you along the ride as a WHM, just use Combat Assist without heals and apply them yourself while the bot handles the DPS side of things, less forced weaving gives you much more control over when to weave things in like Divine Benison or Regens/Asylum while moving for example, at the more appropriate times.
There’s just no way to make healers completely automated in terms of healing in a very high end manner without sacrificing something. In this case it’s poor weaving causing your DPS to sink hard and the constant need to top everyone off.
(source: been clearing current savage tier as WHM like this.)
-
AuthorPosts