Forum Replies Created
-
Posts
-
I dont know if i can get behind the hand holding logic here. You say your a bot. but you dont want us to bot to much. you can use one game in one place but not another.. i think it should be up to the user on where to use the bot that they paid for. idk maybe im outta line here.. but i dont think you should restrict users based on that.
Perhaps you are right.
But in this case, we are talking about several weeks of development that may result in a massive ban wave. If the majority of the community ends up losing their accounts, they will blame us. And they will be right to do so, because if such feature did not exist it wouldn’t happen.We would prefer to receive claims of being a bad developer rather than destroy numerous lives.
Yes, they are indeed in memory. Direct links between keybinds and skills have always been in memory.
But this data is nonlinear and is extremely difficult to work with. It would require redesigning about 80% of low level interaction modules.The link above describes a workaround that allows minimizing the clutter on your screen to a small semi-transparent bar.
Would you please clarify, is this a significant problem to you?We don’t think that implementing housing minigames support will make it less bannable.
We have received information from multiple sources that playing the same minigame for several hours non-stop is likely to result in account suspension, even if this activity is performed in a private locked house. There is reason to believe that a server-side script is constantly monitoring your private house activity.
In fact, we are concerned that implementing this option will significantly increase the ban rate.
As players will be deceived by a false sense of safety in their houses, they will leave Miqobot running unattended for much longer than they usually would at the Gold Saucer in the presence of other players. Therefore this feature remains a low priority for now.Yes, this feature is already implemented.
You can find it in Advanced Settings:Positionals Hotkey.
A shortcut to toggle Blind Positionals setting.
You can use it to control Miqobot without switching between windows.
It works the same way as Pause Hotkey. The hotkey is defined on a system level after pressing Start and is automatically undefined after pressing Stop.
When hotkey is set, an additional P+/P- status will be displayed in the top right corner of the game.Is there a way to make Miqobot actually retain my catnip license/the values I input previously? (yes, I click the save checkbox)
Miqobot saves your settings and presets in these files:
- settings.miqo
- presets.miqo
- catnip.license
They are generated when you first start Miqobot and are automatically updated when you close Miqobot.
Do you see these files being created and updated next to your Miqobot application?
If not, then something is blocking her from saving your settings.
Please try the following solutions:- Try running Miqobot as Administrator.
- Try moving Miqobot to a different folder.
- Make sure that Miqobot has full write access to the folder she resides in.
- Make sure that your antivirus and firewall do not interfere with Miqobot.
yeah me too its say Emergency! Couldn’t connect to the catnip server! 🙁 . its miqobot down?
This issue is not related to the original question. Miqobot servers are up.
If you require technical assistance, please contact our Tech Support: https://miqobot.com/#supportYes, you can use Scenario Engine to combine several gathering rotations together.
All you have to do is create a second rotation with 1x Bountiful Harvest and then use a simple scenario:rotationIfGP(4x Bountiful) rotationIfGP(1x Bountiful) gather()Please note, however, that constantly triggering a 100 GP rotation will not allow you to regenerate 400 GP, so 4x Bountiful rotation will never be used.
This case would be equivalent to simply using a 100 GP rotation.Yes, Quality-of-Life updates are currently in development.
Upcoming FeaturesMSQ and Questing features are not supported at the moment.
Our community assigned a low priority to Questing due to inherent danger posed by open-world combat. Therefore we focus on implementing private instance activities and Assist Mode instead.
For additional information about open-world combat, please read this thread:
Asking the community: Thoughts on Open World Combat and User ProtectionWe will consider your voice in our development plans.
Thank you for your request!If you do not enjoy the Main Story, we would recommend to purchase Scenario Skip Item from Square Enix.
The price on this item is comparable to Miqobot subscription, while the effect is instant and completely safe from any potential account suspensions.
Scenario Skip – Item GuideWe never stated that Scenario Engine was restricted on purpose.
As with any other feature, we implement new tools in order of their complexity. And it just so happens the tools easiest to implement are also easy to use.There are many improvements planned for Scenario Engine, including the ones you described.
Technically speaking, nested function calls and conditions are the only elements that separate Scenario Engine from creating formal algorithms by definition. And we will be progressively adding new elements as long as there is enough demand.There are only two problems that everybody has to understand:
- The more complex a feature is, the more time it takes to implement.
If we start working on nested function calls or conditions support, it will be the only feature added to Miqobot during the next several months.
- The more complex a feature is, the less players will be using it.
Each of the elements discussed here is objectively an improvement. However, only players with programming background will utilize them to create new scenarios. As we have seen many times, non-IT players experience problems when simply using finished scenarios, not to mention making modifications.
Therefore in order to start working on these features, we have to make sure that they are in demand and that this decision is supported by the majority of Miqobot community.
Additionally, functions that set options or parameters for future actions (such as
setCraftRecipe()) may (but also may not!) reset back when the chapter ends.This behavior is standardized as follows:
- If a function changes a UI setting, it does not reset the value after chapter ends. Resetting such values may conflict with user actions, such as adjusting UI settings on the fly.
- If a function is an extension and does not have a corresponding UI setting, it resets the value after chapter ends. Leaving such values in memory without any means to reset them outside of special scenario functions may lead to unpredictable behavior and extremely elusive bugs.
