Forum Replies Created
-
Posts
-
Because Six-sided Star sets your GCD loop on double cooldown, which implies it to be a disengage ability. It is a DPS loss in all cases except:
- When the boss goes into phase transition.
- When you plan to disengage from melee range for at least 5 seconds.
- When you plan to use Limit Break next.
- When this is the last GCD in the fight.
Miqobot doesn’t know when a phase transition is going to happen and doesn’t know about your intentions. Therefore she has no tools to identify the correct moment to use Six-Sided Star. Since you are the only one to know when you are going to disengage, you have to use this action manually.
We don’t have this information on hand, but our developers can perform a research for you.
For technical questions, please contact our Tech Support directly:
https://miqobot.com/#supportMiqobot emulates keystrokes by sending standard WinAPI messages to the game client, such as WM_KEYDOWN and WM_KEYUP. These are the same messages that are generated by Windows when you press a key on the keyboard.
If you wish to learn more about WinAPI techniques used by our developers, please contact our Tech Support and we will do our best to help you:
https://miqobot.com/#supportSo within a few/several weeks of the expansion the level 80 stuff will be back mostly? So we will be able to run level 80 trusts? Level 80 crafting? etc etc
Yes, all features that have been implemented to this date will be functioning once again.
If there are significant changes to existing game content, like job rotations revamp, then it will not be supported until we perform a corresponding revamp on our side.Will miqo break on the 19th when early access starts? or on the full launch date?
Miqobot will be broken by the arrival of new game client.
This will occur during Patch 6.0 maintenance which precedes the Early Access.Downtime depend on how much of the systems, backend, and memory mapping are changed behind the scenes.
When the Endwalker expansion arrives, it will break approximately 90% of core Miqobot modules.
We expect several weeks of complete Miqobot downtime. No feature will be functional in any form.After that, Miqobot will support only level 80 features.
It might take anywhere from 3 to 12 months before Miqobot is fully upgraded for level 90.Using ingame crafting macros with Miqobot is possible but not recommended.
Please refer to this thread for detailed explanation:
Crafting using a one button macroYou can disable the use of any action by one of the following options:
- If you don’t wish Miqobot to use a certain ability, you can remove it from your hotbar.
- If you still wish to be able to use it yourself, you can put it in a macro and hide it behind a different icon.
- If you need to see the cooldown as well, you can put it on a separate hotbar and tell Miqobot to ignore it via Advanced Settings – Ignore Hotbar.
- Alternatively, you can place it on a Cross Hotbar. Cross Hotbars are not evaluated by Miqobot.
In addition, you can create a simple hotbar manipulation macro that will remove certain abilities from your hotbar or quickly put them back with a single button click.
Assist Mode is not designed for automatic activities, therefore it is not available in Scenario Engine.
The feature you ask about belongs to Custom fights and Monster grind feature pack. The combat system is still in early beta and there are several critical updates that must be implemented before this feature becomes possible.In addition, Miqobot will not be able to perform dungeon mechanics until we manually implement each of them in Miqobot source code. Without additional algorithms, Miqobot will simply stand in acid puddles and AoE omens. So this feature will not allow you to farm any dungeon out of the box.
You can find more information in this thread:
Open scenario scripting engine for squadrons/combatusually crashes miqo for me
If you refer to the state of not responding after clicking Start, then this is the standard behavior of Crafting Solver.
The state of not responding means that Miqobot is going through the Solving phase.Enabling all CPU options and using 2:1
Please note that the time required to solve a recipe is directly affected by CPU Intensive settings that you select.
If you select Innovation, Manipulation, and Waste Not at the same time, it may take a lot of time to solve it. So in order to avoid this issue, please do not select all CPU Intenstive settings at once.Please use the guidelines from the Patch Notes to understand which of them are more useful:
Miqobot v1.3.34 – Patch NotesMiqobot always selects the next occurence of the specified time.
For example, here are two cases of repeatChapterUntil(14:00ET):
– If the current time is 13:59ET, the chapter will be interrupted in a few seconds.
– If the current time is 14:01ET, the chapter will keep running for the whole Eorzea day until next 14:00ET.
There is no margin of error, time comparison is exact.Please keep in mind, however, that time is evaluated at the first execution of the function inside the chapter.
If you put repeatChapterUntil() at the end, you introduce artificial delay equal to the length of the chapter. So for example, if you start the chapter at 13:50ET and there is a delay of additional 00:20ET before the first evaluation of repeatChapterUntil(14:00ET), the actual time at the moment of comparison will become 14:10ET.If you wish to avoid this issue, please make sure that repeatChapterUntil() is the first line in the chapter.
You have already requested it. Posting a forum thread is the correct way to make a request.
Now it’s up to the community. If the majority of users support your idea, we will include it in our development plans. This is a rather complex and heavyweight feature that would take several months of development, so before we prioritize it and push back other planned features, we have to see that there is enough demand.
Thank you for reporting.
However, we are not sure how we can help. Miqobot does not use code injections and does not alter the game client. Game crashes usually indicate problems in the game client itself and are not related to Miqobot.Our users have also reported that this issue may be caused by overclocking settings and / or overheating hardware:
FFXIV Crashing while Miqo is runningIf you have discovered a consistent way to reproduce this issue, we can try investigating it further, but we can not guarantee that a solution will be found.
Please contact our Tech Support and we’ll see what we can do: https://miqobot.com/#support
