Forum Replies Created
-
Posts
-
Thank you for providing the requested information. We should be able to reproduce the problem now. It appears to be the result of a rare combination of expert crafting conditions which occurs once every 100,000 crafts. It will be addressed in the next version.
Thank you for your assistance very much.This is good.
No, they do not overwrite.
There should be two files next to Miqobot application: miqo_crafting.log and miqo_crafting_solver.log. Please put them both in ZIP or RAR archive and attach here or send to our Tech Support email. Our developers have the necessary tools to analyze the log files, so they will be able to find the matching log entries.Yes, Crafting Solver has been recently upgraded and is compatible with Patch 5.3.
You can find the most relevant information in the main status thread: Miqobot v1.3.34 – Patch NotesHowever, please note that Patch 5.31 will introduce new recipes and we don’t know how complex they will be. It is impossible to predict whether Crafting Solver will be able to solve them.
Yes, we are aware of this issue.
This debug message was present in all previous versions as well. It occurs when the confirmation window takes too much time to load and Miqobot starts analyzing it before it loads completely.This is just a minor debug message which does not affect Miqobot’s performance.
We apologize for inconvenience.Please keep in mind that Gathering updates will not be available during the first weeks of Patch 5.31.
The standard development cycle of 4-8 weeks applies to every feature pack.We believe we should clarify this, in order to avoid misunderstanding in the future.
Please continue providing your feedback.
Thank you very much!Very well.
We need one more week to finish critical Patch 5.3 features and then we will be able to change development priorities.This thread will stay sticky for the next week.
We kindly ask the community to share your opinions on this matter.Should we postpone the feature packs mentioned above and implement the level 80 Trust Dungeon next?
What i meant with the one class support is that it may help to implement easier, better one class than none as a compromise
It was so in the past, but this is no longer the case.
Combat rotations and new dungeons support have been split into different modules and can be upgraded independently from each other. If a certain job does not have level 80 support, Miqobot will continue to use the level 70 variant but she will be able to clear the dungeon nonetheless.I think that question is hard to answer, if we don’t know a rough estimate how long each feature will take or what is planned to be in there.
The standard development cycle is 4-8 weeks.
At the moment, however, we are in the period of congestion due to the series of game patches. Each game patch downgrades existing features and extends the workload by 1-3 weeks.Currently gathering updates are “partly implemented”, so I guess it wont make any sense to delay this topic, as it was already started to be implemented.
The note “Partly implemented” refers to fishing improvements which have already been released.
They are mentioned in the main status thread: Miqobot v1.3.35 – Patch Notes
We are currently at one of the milestones which allows us to switch priorities, if necessary.For further Gathering updates, we are planning to implement:
– New conditions for gathering rotations.
– Better Diadem support.
– Additional Legendary Fishing functions.
– Identical Cast and Identical Gig support.
– About 20 other minor improvements.Some of these features have been postponed for more than a year, and there are users who get very frustrated over this fact.
Please keep in mind that these updates will not be available during the first weeks of Patch 5.31.
The standard development cycle of 4-8 weeks applies to every feature pack.I for myself am interested a lot in the “scenario engine update”.
Scenario Engine has accumulated over 100 feature requests, so it will take several development cycles to implement them all.
If I would know that a new trust dungeon would take you (for example) 4 weeks and scenario updates 12 weeks.
Yes, these numbers are close. Though a better way to describe estimates is via lower and upper values, therefore it would be 4-8 weeks and 12-24 weeks respectively.
This issue usually indicates that you haven’t removed keybind conflicts from chat actions.
You can find instructions on how to avoid this problem in the [Beta] Combat thread.Important Note!
Please remove any keybinds from “Reply” and “Switch Chat” actions.If you use the common WASD style for navigation, there’s a very high chance that a keybind collision will occur if Miqobot sends key input at the same time.
For example, if you assign Alt+1 – Alt+= to a hotbar Miqobot uses at the moment and press S at the same time, the resulting keybind will become Alt+S which by default triggers “Temporarily Switch Chat Mode to Say”. This will activate the chat mode in the middle of the fight and break your movement completely.
In order to avoid this problem, we recommend to fully clear the Keybind -> Chat tab.(You can leave the first two actions intact: “Ready Chat Log” and “Ready Text Command”.
Assuming they contain no Ctrl / Alt / Shift modifiers.)(Lv75) Qitana Ravel support is implemented.
Miqobot v1.3.35 – Patch Notes(Lv80) Heroes’ Gauntlet support is implemented.
Miqobot v1.3.39 – Patch Notes-
This reply was modified 3 years, 10 months ago by
Miqobot.
New scenario functions for advanced fishing are implemented.
Miqobot v1.3.35 – Patch NotesWe have just released (Lv75) Qitana Ravel support and we were planning to improve other features next.
At the moment we are working on Gathering updates and there has also been a lot of requests regarding new scenario functions. Additional Trust Dungeons are planned after that:As much as we would love to implement everything, we can not work on multiple feature packs at the same time. So if you wish to see (Lv80) dungeon support earlier, we would have to postpone other features instead.
Do you think we should do so?
-
This reply was modified 3 years, 10 months ago by
