Forum Replies Created
-
Posts
-
Miqobot is not a virus.
Please report this issue to your antivirus vendor.As we already explained, false positive is a bug in antivirus. Unfortunately we have no affiliation with antivirus vendors therefore we can not help them fix it.
Even if you did not experience this problem before, it doesn’t mean that you never will. Antiviruses are updated often and each update has a chance to introduce a new false positive bug.Thank you for reporting!
At the moment we are not capable of reproducing high DPI issues in our labs, therefore we require assistance from the users who are affected by this problem. Unfortunately these reports are extremely rare and we still don’t have enough data to design a solution.
We need the following information:
- Your preferred High DPI scaling.
- A screenshot of 3D Radar overlay with Gathering window in the top left corner of the screen.
- A screenshot of 3D Radar overlay with Gathering window in the upper left quadrant of the screen (but not in the corner).
- A screenshot of 3D Radar overlay with Gathering window in the middle of the screen.
All screenshots must be fullscreen.
With this information we will be able to implement a potential solution.Thank you for your assistance very much!
This is an entirely different issue which is not related to Steady Hand or Basic Synthesis.
The setting “Ignore Quality” disables a certain subset of crafting abilities, however the internal algorithm stays the same. There is a chance that the recipe is a complex housing item which could require more than 8 steps of Progress, so disabling Tricks of the Trade and Durability skills could potentially result in a failed craft.
We plan to address this behavior by implementing a separate algorithm specifically for “Ignore Quality” feature which will estimate the number of steps required and disable additional abilities.
Since this behavior does not break the synthesis, it is classified as minor issue.Miqobot v1.3.1
New scenario functions are implemented.
Full documentation is available directly in Miqobot. Press?button to open it.- startSquadronDungeons() – Commence squadron dungeons activity and wait until it stops.
- deliverGCGear() – Make expert delivery to the closest NPC.
- repairNpc() – Mend equipment at the closest NPC.
- setSquadronFullClear() – Set “full clear” setting for squadron dungeons.
Thank you for providing the necessary information!
We analyzed the data you provided but we couldn’t identify any critical issues.Yes, we can see that Basic Synthesis is used without Steady Hand, however in this case it’s not risky at all.
There is 50 points of Durability left, therefore Basic Synthesis has 0% chance of failing the craft. The priority in this case is to complete synthesis with only one step instead of two. If Basic Synthesis would fail 4 times in a row until only 10 Durability left (which can happen with 0.01% chance), Miqobot would finally accept her fate and obediently refresh Steady Hand before finishing the craft.We have taken special care to prevent Basic Synthesis from staying unbuffed at the last 10 Durability step, and under normal circumstances this should never lead to a failed craft.
Still, you report that there were cases when it happened and this is indeed critical. Unfortunately, after several ours of testing we couldn’t reproduce your issue in our labs.
Therefore we would kindly ask you to keep the crafting logs enabled, and in case you encounter this problem again please report to us.Thank you for your assistance very much!
Please download the beta version from this thread: [Beta] Combat
Careful Synthesis III has an additional cost of 7 CP which does not justify a minor increase in progress efficiency. In general, CS2 is twice better than CS3 in terms of CP efficiency and HQ output.
You can find detailed analysis of Stormblood crafting abilities in the main sticky thread: Stormblood – Upgrade Stage 2However Miqobot should never prioritize Basic Synthesis over Careful Synthesis II, and if you encountered this behavior then it is indeed a critical bug.
Please check option “Enable logs” on Crafting tab under Solver settings. It will create two log files:
- miqo_crafting.log
- miqo_crafting_solver.log
Please put both of them in ZIP or RAR archive and attach here, along with a screenshot of settings used in Miqobot. We need them in order to reproduce and analyze your issue.
Thank you very much!Here’s two suggestions that you may want to take into consideration at a later date to add in..
1. A way for the bot to run somewhere and repair gear say after every 4 or 5 consecutive runs.
2. A way for the bot to head outside the room and hand in all the pink/green items to your bag for extra GC tokens.. say after every two or three runs. You could set it so this will only hand in items in pink/green items in your actual bag and not in your armor bag storage.. cos some of these dungeon items you might want to keep to use for other classes.Yes, both of these features are a part of Scenario Engine integration which is coming next.
Thank you for your request!Is there any ETA about when the other Dungeons will be out? Like lv 30 or 50, just a lv 40-50 dungeon would be great!!
At the moment we aim for weekly updates, but depending on the amount of bugs found and additional requests received it may take longer.
Please keep an eye on this thread, it will be updated regularly.And I believe everyone can see today very well where this Assist Mode could be very useful, Eureka Pagos, where everyone right now are destroying their hands by doing their rotations non stop for hours with no breaks for chaining mobs.
I would not mind taking care of moving myself, and switching target myself there, and just let Miqobot doing the rotations, because we really are damaging our hands and fingers with this content right now, which is stupid.As active players, we are also disappointed with the release of Eureka Pagos.
New content is supposed to be fun, at least for the first week. The fact that it becomes extremely grindy in the first hour means that something went wrong in development.We sincerely hope that this is just a simple misunderstanding.
We assume that the only adjustment that was implemented during maintenance on Aug 13 is a hint to players.
Lowering HP of monsters in certain Pagos FATEs can mean only one thing – Square Enix wants players to focus on these FATEs. Perhaps this is a key to increasing the NM spawn rate.This Reddit thread looks very promising: Pagos Bunny Fate Theory
So if I understood correctly, with the Assist Mode, Miqobot would be able to pick up the DPS there anywhere during my rotation, keep a high enough DPS (better than fillers), letting me focusing on dealing with mechanics on my own, until I feel safe to go back on full manual mode?
For example, for BRD, if she sees a Trick Attack, or Chain Stratagem, or Battle Litany, would she refresh DoTs to snapshot them? Maybe even double snapshoting them?
Yes, absolutely.
Miqobot is fully aware of currently active buffs / debuffs and uses a complex priority system for battle rotations. Priorities are calculated on the fly and allow Miqobot to pick up at any moment in the fight, pretty much like Crafting Solver does. Remembering DoT snapshots and analyzing the best moment to refresh them would require some extra work on our side, but it’s also possible.I didn’t tested yet Miqobot with the VPN and Fastconnect. But when I watched her, I’ve seen her spamming keys for oGCD, but not for GCD, and she’s not spamming the keys a lot.
So my question is, would it be enough in my case to avoid her to clip abilities? I’m trusting you guys a lot when it comes to theorycrafting and maths, but I’m so used to spam keys before an oGCD trigger, or even with GCD, that Miqobot look overconfident. For GCD, the reason she’s not spamming is to not queue the GCD in case she would find something better to do?No, Miqobot is not doing it the right way at the moment. Queueing GCDs is indeed better and would result in more DPS. Spamming keys however would not.
We did not implement queueing yet because it was easier to make the first version stable this way.
But of course we will.
For Miqobot it will result in about +2% DPS.Pressing a GCD key about 400ms before it becomes active creates an action queue and sends a network packet, which is the intended way to overcome ping-related issues. It forces an action to go on cooldown as soon as possible both on client and on server at the same time (assuming your ping is lower than 400ms).
Pressing a GCD key more than once within that 400ms window has absolutely no effect.In addition, every GCD or oGCD action initiates a soft animation lock of about 750ms. During a soft animation lock, you can move your character and queue another action but it will not trigger until the lock ends. Some actions create a hard animation lock (like NIN Assassinate) during which you can not move, however its length is also 750ms. The only exception is DRG jumps which are twice longer – 1500ms.
So during any kind of animation lock, the first action you put in the queue is guaranteed to go on cooldown at the end of the lock. The queue can contain a maximum of one action and can not be overwritten.
That’s why spamming keys more than once does not result in more DPS.Miqobot spams keys only because an action queue may be interrupted by lag spikes or certain debuffs (like Paralyze). But she tries to do it as sparse as possible.
At the moment we use an empirical delay of 200ms which seems to work pretty well. During this 200ms window Miqobot does other important things. (Manage squadrons, rescan enemies, plan positionals, etc.)In my case, I know I can double weave with VPN and Fastconnect, but I’m only able to achieve it in openers, or some specific calm moments during a fight, because it requires me to be so quick and to spam so hard, so, my question is, will Miqobot be able to perform double weave constantly on a connection that is at the bleeding edge limit of allowing that?
To summarize all of the above, yes, it’s absolutely possible to perform double weave as long as your ping stays constantly below 200ms. “Constantly” here is the key.
For example, if your ping is 170ms on average but then you experience a lag spike of 500ms, this will inevitably break the double weave and result in clipping GCD. Connection stability is the most important factor.You guys said your theorycrafting allow a 90% efficiency for now, which is already incredible, are you confident you can reach higher efficiency down the line?
Yes, we have a lot of ideas to reach higher than 90%, however we will make no promises about 100%.
Pareto principle is inevitable in this case. The higher in efficiency we go, the more complex algorithms are required for the next +1%. After 96-97% it would be more efficient to implement a custom rotation designer and use it with specific encounter in mind.Would Miqobot be able to refresh the DoTs each time I’m switching on a target when the DoTs are about to fall off?
Would Miqobot be able to see that the 2 targets are close enough to each other to use Rain of Death instead of Bloodleter?
Would Miqobot be able to see that I’m close enough from the 2 targets, that are also close enough themselves, to use Quick Nock instead of Heavy Shot?Yes, yes, and yes.
You can already observe Quick Nock on 2 targets during Halatali runs.
