Forum Replies Created
-
Posts
-
Function deliverCollectables() does not explicitly detect scrip limits. However after 4 ingame errors are displayed, function will stop and break scenario flow. It means that Miqobot will stop after exchanging 4 extra items.
Early detection of scrip limits is also considered, as part of future Scenario Engine updates.However, we are not sure whether skipping would be a good decision. If Miqobot continues scenario execution without delivery, it may lead to inventory clogging which could cause more severe errors and unpredictable behaviour.
This is something that we have to design carefully, therefore it will take more time.In the meantime, please utilize the built-in error detection feature.
Thank you for your request!I honestly rather they improved the GUI before releasing combat, better management for grids, pause option in scenarios and crafting, etc.
Quality of Life features are being implemented independently from Combat support.
Thank you for your concern!Hmm… I’m so curious. Can we get a % mark about how far the battle system / the next version of Miqobot is like we had with the update 4.2 here?:
We’ve managed to reach the mark of 60% before Patch 4.2.
The most notable milestones are seamless omnidirectional battle navigation and AoE dodging. Here is a visual upgrade of 3D Radar with Combat support.
Unfortunately Patch 4.2 brought an immense increase to malicious activity, and once again we are bound by daily investigations of payment fraud and crack attempts. The development process is moving forward albeit slowly.
Therefore any numeric form of progress can not be treated as ETA indicator.We are working nonstop to release new features as fast as possible, and we kindly ask for your patience and understanding.
Strictly mathematically speaking, Lyfox is correct.
It doesn’t matter how many times Patient Touch fails. If Crafting Solver decided to switch strategy after a few unsuccessful steps, it would lead to even worse HQ output in the end. Miqobot always selects the most optimal route based on the current situation, regardless of previous RNG history. She does not consider emotions, only pure math.The fact that Miqobot uses Patient Touch at all means that the recipe you craft is too complex to HQ with only 100% abilities. Otherwise she would detect this case and skip Patient Touch completely.
(You can disable 100% routes in Advanced Settings for a small computational boost, but here we assume you didn’t do it. Please correct us if necessary.)Therefore forcing Miqobot to use Patient Touch only once and never again is a suboptimal route.
According to our calculations, it will decrease average HQ rate by 9.4%.However, we understand that for a human player less RNG is usually a more enjoyable experience. All right, we will implement an advanced setting that will force AI to abandon Patient Touch after third IQ stack.
Thank you for your request!We considered implementing Macro + Solver feature, but unfortunately it turned out too complex in both code and design. So we decided to put it under low priority for now.
As for Maker’s Mark, we’ve been receiving completely opposite requests so far.
Our users don’t like to wait, and Maker’s Mark effectively doubles the time required for sythesis. Therefore we adjusted the algorithm to allow this ability only for the most complex recipes.Would you please give us an example where you would like to utilize it despite Miqobot’s current strategy? Is it a recipe above or below your level?
Thank you for reporting!
Yes, as we don’t have enough data samples for 70*** recipes, the current prediction formulae used by Miqobot is slightly incorrect. This behaviour is described in our primary Crafting guide.
Would you please enable crafting logs as @Krude suggested? The more data we have, the better algorithm will be in the next version.
Hi, I don’t know if this is possible but could we have Miqo tells us the (approximately ofc or perhaps best case, worst case, average) % chance of HQ before it actually starts a craft? So, before we risk a more expensive craft we get an idea of what to expect at the end?
Yes, we consider adding this feature in the future.
However the final output is highly affected by RNG, so at the moment we are not sure whether this feature will be useful. The usual worst-best range in crafting may be as wide as 15-100% HQ rate.Is there going to be another analysis post into crafting 3** L70 recipes? I found your previous 3** L60/2** L70 posts to be most interesting, would like to see a new one if anything has changed since
There are no significant changes at new crafting tier that would be worth another analysis post.
However there will be an additional Miqobot upgrade with new math adapted to 70*** recipes. At the moment we are still collecting data samples so please report any unexpected behaviour you encounter.We want new stuff and we want it NOW!! =O
Thank you for your interest very much!
Initial combat functionality is planned for release in the next version of Miqobot.
In the meantime, you can use Scenario Engine to emulate combat with the help of ingame macros. You can find examples created by our community in the following threads:
Requests are now discussed in the publicly available section and you can find the latest one here:
[Request] Leveling/Farming with Squadron Dungeons
In fact we consider opening the Feature Requests section of the forum, but we’ll have to reorganize it first.We apologize for temporary inconvenience.
