Forum Replies Created
-
AuthorPosts
-
January 13, 2021 at 4:07 am in reply to: Infinite Universal Diadem Scenario Botanist🌱, Mining⚒, and Fishing🎣 #26199
By the author’s request, this thread is reopened.
(Phase 4) Infinite Universal Diadem scenario Botany and mining
January 13, 2021 at 3:29 am in reply to: Infinite Universal Diadem scenario Botany and mining #26181January 13, 2021 at 2:46 am in reply to: Infinite Universal Diadem Scenario Botanist🌱, Mining⚒, and Fishing🎣 #26177This thread is related to Phase 3 of Ishgard Restoration.
With the arrival of Patch 5.41, it is outdated.If you wish to share a new scenario for Phase 4 Diadem, please create a new thread.
Thank you for your contribution very much.If you have technical issues with Miqobot v1.3.40, please contact our Tech Support: https://miqobot.com/#support
With the release of Patch 5.41, the layout of gathering nodes in Diadem has changed.
This is the same as it happened in Patch 5.31.
All previously created Diadem scenarios are not compatible with Phase 4 of Ishgard Restoration. If you wish to farm new Diadem, you need new navigation grids and new scenarios.We don’t see a reason to change the algorithm to hex codes, because it already works with any arbitrary fish name in the game.
Fish name is automatically converted to hex code, if there is a match in Miqobot’s internal database. If there is no match, the algorithm will simply attempt to identify the fish by its name directly.Would you please clarify your request?
What kind of new feature would you like to achieve by specifying hex codes instead?another possible solution could be to to prioritize AoE healing if more than one person has taken enough damage to constitute a heal, and/or an option to prioritize group healing > solo heal.
AoE healing is already prioritized.
However, if the party is spread out, it prevents AoE healing spells to be triggered.How feasible is it to potentially implement custom thresholds for healing?
This feature would take a full development cycle of 4-8 weeks.
It is already planned, but at the moment it’s not a priority, because Gathering and Scenario Engine updates are in higher demand: Upcoming FeaturesA good solution would be setting a flag so Miqo would only apply Regen to tank roles.
Very well. It appears there are no strong objections to this solution.
It will be implemented in the next version.Done the Heroes Gauntlet run some times now, and on last boss I find that the bot’s movement out of the holes when boss casts Wild Rampage. Movement seems to be threading the needle to the point, that it has failed a couple of times. Maybe just prolong the wait a little longer so it’s not right on the edge?
All right, we will adjust the algorithm for Wild Rampage mechanic.
Thank you for your feedback.Crafting solver gets stuck in several situations with the new recipes.
Of course, as it was announced in the main status thread, new expert recipes are not supported.
Please read the answer in the post above.Miqobot v1.3.40 – Patch Notes
- New Diadem location is supported.
Please keep in mind:
- The layout of gathering nodes in Diadem has changed.
All previously created Diadem scenarios are not compatible with Phase 4 of Ishgard Restoration. If you wish to farm new Diadem, you need new navigation grids and new scenarios.
- Grade 4 Expert recipes are not supported.
In accordance to the previously announced schedule, they are under research and will be implemented in 3-5 days.
Please do not attempt to use Crafting Solver for Grade 4 Expert recipes. It will not work and will most likely crash Miqobot.
Of course, as it was announced in the main status thread, new expert recipes are not supported.
New expert conditions did not exist before Patch 5.41, therefore it was impossible to support them beforehand. As with every new feature, we have to analyze it first and implement the necessary improvements in the source code.
Please do not attempt to use Crafting Solver for new Expert recipes. It will not work and will most likely crash Miqobot.Please refer to the main status thread for updates: Shadowbringers – Miqobot Status
Miqobot is fixed for Patch 5.41!
Please restart your Miqobot for the changes to take effect.
All active license codes are extended with bonus time.
Thank you for your patience and unceasing support!Important Note
The updated Diadem is a completely new location.
The previous version of Miqobot is not aware of this and will not work inside updated Diadem. This issue can not be fixed without releasing a new version.The next version of Miqobot is scheduled for release in several hours.
3D Editor is already compatible with new content. You may begin creating navigation grids for new Diadem, but you won’t be able to test them until next Miqobot release.
However, please keep in mind that Diadem is an area of high player congestion. Players are aware of bots’ existence. Due to the PvP nature of Ishgard Restoration, they will suspect and report anyone who spends too much time farming skyward ranking points.
Please be very careful during the rankings period. And if you decide to leave Miqobot unattended, please make sure that you understand the risks.Miqobot does not enforce any limits on your activity, but we encourage you to play wisely.
As it was previously announced, the arrival of new game patches may affect the development schedule.
Fixing Miqobot for Patch 5.41 will obviously take priority. New Collectable Gathering is not ready for release, therefore it will be put on hold until the necessary upgrades for Patch 5.41 are implemented. Here is an updated schedule.
- Approximately 1 day.
Core upgrade for Patch 5.41.
Complete Miqobot downtime.
All active subscriptions will be compensated for this downtime.
- Approximately 3-5 days.
Implementation of gameplay changes.
New Expert recipes support.
- Approximately 1 week.
Implementation of new gathering mechanics.
- Return to the original development plan: Upcoming Features
but miqo keeps moving back in close. even with positionals off.
This is not supposed to happen. When Blind Positionals are disabled, Miqobot should not move your character.
If you can confirm that this indeed happens, this is a bug and we have to investigate it further.
Please contact our Tech Support: https://miqobot.com/#support -
AuthorPosts