Forum Replies Created
-
Posts
-
Thank you for reporting again!
Unfortunately we can not reproduce your issue based simply on Output Area.Please check option “Enable logs” on Crafting tab under Solver settings. It will create two log files:
- miqo_crafting.log
- miqo_crafting_solver.log
Please put both of them in ZIP or RAR archive and attach here. We need them in order to reproduce and analyze your issue.
Thank you very much!Please do not enable too many CPU Intensive settings. They lead to increased RAM usage which may not be physically available on your machine. An attempt to allocate nonexistent amount of memory will always result in a crash.
At the moment Miqobot relies on user understanding of RAM usage and trusts him with selecting the correct settings.
Yes, Veteran Trade by Name is scheduled for release in Stormblood Upgrade Stage 3.
You can read about it here: Upgrade Stage 2 – SpearfishingMiqobot will be able to utilize Spearfishing actions to affect the catch.
– Veteran Trade may be used with reference to undesired fish names.
– Calm Waters, Bountiful Catch, and Nature’s Bounty may be used after Veteran Trade on the same node, in order to improve yield or size of preferable fish.
– (Spearfishing abilities support is scheduled for release in Upgrade Stage 3.)In addition, special scenario functions will allow you to change gig heads and switch presets on the fly.
– (Spearfishing scenario support is scheduled for release in Upgrade Stage 3.)Thank you for your patience very much!
So I’ve been making really good success on the scenarios but the one thing I can’t figure out is how to reset from the point of accidental KO. I have the option turned on to revive but no matter what the chapter contains Miqo will revive and never try to re-complete the chapter
Yes, as we mentioned KO events are currently not handled by Scenario Engine. Advanced settings are not designed to restart Miqobot automatically, due to potential danger of running into the same trap many times in public.
But this is not the case with Squadron Dungeons.We plan to address this in the next version.
Yes, additional functions for inventory management are already planned.
However please note that Scenario Engine is still in Beta stage, and conditions are currently not implemented at the scripting core level. So we can only combine conditions with certain actions.Would you please tell us what action you want to perform based on inventory check?
Would you please verify that you have at least one of these skills on hotbar on all crafting jobs?
- Basic Synthesis
- Careful Synthesis
- Careful Synthesis II
If it doesn’t help, then please check option “Enable logs” under Solver settings. It will create two log files which we need in order to reproduce and analyze your issue.
Next time you encounter the problem, it will be written in the logs. Put both of them in ZIP or RAR archive and attach here.Thank you for your assistance very much!
Understood 🙂
Current UI of Miqobot uses default Windows settings.
It means you can install a different color scheme on system level, and it will affect Miqobot’s appearance. You can use it to adjust UI colors to your liking.And of course, we already have several UI layouts in progress with system-independent color scheme. We plan to implement a better design with customizable colors and fonts as soon as we complete the top priority feature pack.
Thank you for your request!A very good suggestion!
Not very hard on technical level, but definitely a separate feature pack due to sheer amount of settings entailed.We shall discuss your request with developers and try to break it down into several stages. If we spread it over several releases, we can probably implement it without delaying new versions too much.
Thank you for your request!
Yes, you can use Gather by Name to ensure GP usage only on certain items.
Please take a look at our gathering guide: Gather by NameFor example, this list will focus rotation on Clary Sage and gather Wind clusters in the process:
{clary sage} cluster *Now we can officially announce upcoming support for Squadron Dungeons!
As the Engage behaviour has been patched, we can implement a completely legitimate feature which:
- Does not rely on exploits and therefore does not put your account at risk.
- Is socially safe due to being performed in solo instances.
- Is not a product of temporary bug and thus will be available for a long time after implementation.
In addition, we expect this to become a special test area for creating and fine-tuning AI behaviours for each role and job.
We’ll be making additional announcements in the coming weeks.
