Forum Replies Created
-
Posts
-
strafe keybinds are shift a / shift d rather than a/d
This is a keybind conflict.
Using Ctrl, Alt, or Shift in any of the combat navigation actions creates a collision.
Keybind conflicts are described in details in our Keybinds and Icons Recognition guide.You can find the full list of actions used in combat in the main beta thread.
These actions must have valid keybinds. It’s highly recommended to assign each of them a single key.
- Move Forward
- Move Back
- Strafe Left
- Strafe Right
- Jump
- Point Camera Up / Down / Left / Right
- Zoom Camera In / Out
- Cycle through Enemies (Nearest to Farthest)
- Target Self
- Target Member 2 in Party
- Target Member 3 in Party
- Target Member 4 in Party
Note. Only strafing is used for side movement. Miqobot does not utilize Turn Left or Turn Right actions.
A single key means that it doesn’t contain any composite keybind modifiers like Ctrl, Alt, or Shift.
Yes, Blue Mage support is planned, but at the moment it is not a priority.
During the past year, there was only two questions regarding BLU including this one. Therefore its priority has not increased.But of course, our development plans are driven by the community demand.
If the majority of users support your suggestion, we will start working on Blue Mage rotation upgrade.Here is the current view of the roadmap for the next few months: Upcoming Features
The standard development cycle of each feature pack is 4-8 weeks.
If you would like Blue Mage support to become a priority, please let us know which of these features we should postpone.Thank you for the detailed report.
We have managed to reproduce this problem based on the information you provided.Indeed, there is a critical bug in the GUI library used by Miqobot that crashes the application under the described conditions. We will investigate the problem and will try to design a solution to prevent it in the future versions. Thank you very much.
Yes, and this is why we usually don’t like to give ETAs.
It is impossible to predict how many obstacles we will encounter during development or how fast we will manage to overcome them. When the community started pressing us for a better ETA, we were going through a rough development stage, therefore we had to increase the estimate. But it took only two days to find a solution in the end.
It has always been this way. And yet for some reason players perceive estimates as some kind of final truth. While in reality asking for an ETA is the same as asking us to generate a random number.
Perhaps we should cease announcing ETAs from now on. It seems to do more harm than good.
The requirement to enable Debug privilege is a consequence of the changes introduced by Patch 5.18.
In Patch 5.18, the game installation process was changed. The game launcher modifies certain permissions in the game process, and in order to connect to the game correctly, Miqobot requires additional Debug privileges granted by Administrator account.Depending on your Windows installation, different permissions may be required. Therefore Miqobot uses a combination of several solutions when connecting to the game.
You can find additional information in the patch notes: Miqobot v1.3.30 – Run As Administrator
Hexadecimal codes are now supported: Miqobot v1.3.41 – Patch Notes
Just wanted to say the crafting solver is working amazingly. Wanted to asked if there is any plans to support Careful Observation? I think that would make it even more amazing. Thanks.
Yes, Careful Observation support is planned.
In fact it was scheduled to be implemented in this version, but due to numerous user requests to release the update as soon as possible it had to be postponed. It will be added in the next Miqobot version, but it will not arrive in time to have an impact on the current phase of Ishgard Restoration.now that miqo supports expert 4 it does work really nicely
only fails twice coz low quality so far :3Yes, the algorithm is not perfect and may result in low collectability under unlucky RNG conditions.
Yes, the list of functions does not have a clear structure, because it’s still in the same beta state as it was released. There hasn’t been any major upgrades for Scenario Engine yet.
Functions are grouped as follows:
- Start activity functions.
- Preset functions.
- General functions.
- Fishing functions.
- Gathering functions.
- Crafting functions.
- Navigation functions.
- Chocobo Racing functions.
- MGP Minigames functions.
- Combat functions.
- Utility functions.
This adjustment was specifically requested by the community in order to address the excessive usage of Regen:
Quick Question about WHM Regen
If you believe this adjustment is not an improvement, please join the discussion and voice your opinion.Grade 4 Expert recipes are supported.
Thank you for your patience very much.Please refer to the main status thread for details: Miqobot v1.3.41 – Patch Notes
Miqobot v1.3.41 – Patch Notes
Crafting
- Fixed an issue, wherein r513 recipes were incorrectly identified as r511.
- Fixed an issue, wherein Miqobot would miscalculate progress because of Malleable expert condition.
- Fixed an issue, wherein Miqobot would get stuck during synthesis because of Primed expert condition.
- Fixed an issue, wherein Crafting Solver would operate out of bounds of the solution map.
- Grade 4 Expert recipes are supported.
Combat
- (WHM) Regen will only be applied to tanks.
- When fighting Spectral Berserker in (Lv80) Heroes’ Gauntlet, Miqobot will stay inside puddle for 0.5 seconds longer after Wild Rampage cast.
Scenario Engine
- The following functions accept hexadecimal codes as fish name:
– addFishMoochPreset()
– addFishMoochBlacklist()
– holdFishMoochUntil()Hexadecimal values allow correct identification of fish not included in Miqobot database.
Example: 0x808B.
This value refers to Grade 4 Artisanal Skybuilders’ Meganeura.
The exact value of each fish can be confirmed in the message log after the catch or via any external game database.
We have reached the first milestone for the new recipes upgrade.
The algorithm is not perfect, but it is stable. All major issues are addressed and Crafting Solver is capable of synthesizing the latest Grade 4 Expert recipes without manual intervention. In accordance to multiple user requests, the release is published at the earliest opportunity.The next version of Miqobot will be available in 3 hours.
Thank you, but unfortunately this information does not help.
The information you provide is related to the game client data. While the issue lies in the multidimensional solution map generated by the Crafting Solver. Explaining the details of internal data structures of Crafting Solver will probably take twice more time than implementing the upgrade. If you excuse us, we would like to focus on the development process.This is our final post in this thread.
When the upgrade is ready for release, the announcement will be posted in the main status thread:
Shadowbringers – Miqobot StatusThank you everyone for your patience very much.
I don’t understand the skepticism others have here. Wasn’t miqo available for past rankings? If the devs were ok with having miqo up and running for the first 2 rankings, why wouldn’t they be ok with it up for the 3rd?
The simplest explanation here is the one the devs have given us – it’s more complicated this time. Square is known for throwing small wrenches into their updates to thwart bots (e.g. shifting diadem nodes slightly and making it a new area).
But I can accept that the team have told me that the bot isn’t going to work properly (or at all). I guess its human nature to try and push things to break 🙂 I am grateful that although its not working, I can still partially automate these recipes.
I’ve been very happy with miqo so I’m in no particular rush, personally on it being implemented. I manually got my titles (and never wish that on anyone). The fact that I can partially automate achievement hunting now is something I’m thankful for.
Thank you for your patience and understanding very much.
We will do our best to address the issue as soon as possible.
