Miqobot

Forum Replies Created

Viewing 15 posts - 2,536 through 2,550 (of 3,056 total)
  • Author
    Posts
  • in reply to: Suggestion for the Miqo Team ;) #3534
    Miqobot
    Miqobot
    Keymaster
    1+

    Miqobot Team is currently implementing Upgrade Stage 1 as outlined in the status thread:
    Stormblood 4.0 – Miqobot Status

    The amount of changes is massive, so we can not promise any news in the next 24 hours.
    Thank you for your patience and understanding!

    in reply to: Stormblood – Upgrade Stage 1 #3532
    Miqobot
    Miqobot
    Keymaster
    6+

    This is the approximate list of upgrade stages.

    Stage 1:
    – Memory layout upgrade.
    – New zones support.
    – New mounts support.
    – New aetherytes support.
    – Keybind mappings.
    – Adjust existing gathering actions.
    – Adjust existing crafter actions.
    – New UI layout adaptation.

    Stage 2+:
    – Spearfishing. Seems like a new feature, will require dedicated logics design.
    – Swimming navigation. Floating in 2D, diving in 3D.
    – Adjust math for new mount speed.
    – Consumables during fishing. Assuming cordials can now be used without interruption.
    – Verify and adjust Precision Hookset for new fish.
    – New fishing actions.
    – New gathering actions.
    – New crafting actions.
    – New crafting math.
    – New crafting condition rates. Whistle system has to be revised. Quality Assurance (level 63 trait) may become life changing.
    – Upgrade FATE radar to reflect EXP bonus.

    Number of stages and priorities within each one are subject to change.

    in reply to: Stormblood – Upgrade Stage 1 #3526
    Miqobot
    Miqobot
    Keymaster
    7+

    Glancing through preliminary Patch 4.0 Notes, it becomes obvious that almost every Miqobot feature will require a thorough revise. Even for levels below 60.

    Therefore we accept the strategy that was suggested by our community a while ago:

    1. Upgrade will be performed in several stages.
    2. The first stage will adopt the most vital changes marked as 2.x and 3.x.
    3. The subsequent stages will adopt the rest of 2.x / 3.x / 4.x changes.

    In addition, to make things easier to handle, stable and beta versions will be merged.
    After Miqobot is successfully upgraded, new features of Scenario Engine (listed under Planned Functions) will be branched into beta once again.

    Details on upgrade stages will be posted later.

    Miqobot
    Miqobot
    Keymaster
    0

    The issue with gatherTouch() has been addressed in Miqobot v1.2.62 Beta.
    Thank you for your contribution very much!

    in reply to: [Beta] Scenario Scripting Engine #3522
    Miqobot
    Miqobot
    Keymaster
    1+

    This function is used when you want to teleport and repeat a certain chapter in the same zone. It is identical to teleport() with a simple addition of zone verification.

    And yes, it can also be used to help recover from KO events, but this behaviour will be implemented later.

    in reply to: Rotation: If GP >< statments #3521
    Miqobot
    Miqobot
    Keymaster
    0

    Accepted 🙂
    GP-based rotation selection will be implemented as additional feature for Scenario Engine.

    Thank you for your request!

    in reply to: Suggestion for Miqobot's devs #3520
    Miqobot
    Miqobot
    Keymaster
    1+

    Indeed, your idea is very good and it makes perfect sense to create a script to rebuild pointer tables.
    In fact, this is how the upgrade process looked like about a year ago, when Miqobot had less features available and relied mostly on pointer tables.

    As of today, pointers make up about 10% of the data required. There is a lot more to be upgraded:

    • Memory structures.
    • Icons recognition database.
    • Game assets recognition database.
    • Keybind mappings.
    • Navigation math.
    • Crafting math.
    • UI layout analysis.

    A general disassembler tool is not capable of performing this kind of work automatically.
    And while of course we extensively use the one you mentioned, our main toolset is of our own creation. We constantly improve it with every new patch and each time it becomes faster and more helpful.

    But since Miqobot is in active development, each new feature adds another layer to the work pool. Creating a fully automated toolkit would require a complete feature freeze.
    Considering the intensity of incoming feature requests, we do not expect a feature freeze anytime soon.

    We appreciate your interest in the development process 🙂
    Thank you very much!

    in reply to: Presets? #3519
    Miqobot
    Miqobot
    Keymaster
    0

    Yes, we indeed consider adding integrated presets database.
    However as correctly noted already, we have to make sure that presets in this database will be sufficiently randomized. This is planned for development after the core features are stabilized.

    Thank you for your feedback very much!

    in reply to: Sugestion, toggle hasty touch #3518
    Miqobot
    Miqobot
    Keymaster
    0

    Accepted 🙂
    Additional Crafting Solver option will be available for Hasty Touch.

    Thank you for your request!

    in reply to: Take care #3503
    Miqobot
    Miqobot
    Keymaster
    4+

    Based on the information above, we can provide recommendations that will help you avoid unnecessary stress during gameplay.

    1. Do not discuss usage of any third party tools in the game chat.
      Even with the closest friends.
      Even if these tools are not related to botting.
    1. Do not leave Miqobot unattended for an extended amount of time.
      Especially in times and areas of high player congestion.
    1. Switch between different zones and activities when possible.
      We recommend getting familiar with our Scenario Engine, as it was designed exactly for this purpose.

    We kindly ask every Miqobot community member to carefully review and memorize these recommendations.

    in reply to: Take care #3502
    Miqobot
    Miqobot
    Keymaster
    3+

    We have contacted SQUARE ENIX and consulted with them on the matter of account suspension.
    While may not be directly related to this case (as obviously neither we nor SQUARE ENIX can discuss private user information), we acquired an updated summary of the circumstances that may lead to account suspension.

    In general, for an account penalty to take place, two events must occur:

    1. A direct report accusing someone of illicit activity is received from another player.
      A report can be filed by any player, be it a close friend or a random stranger. In times and areas of high player congestion (such as Gold Saucer during recent MGP event) the probability of drawing another player’s attention is increased.
    2. A strong evidence of illicit activity is found.
      Evidence is gathered from several sources, the most common being:
      – chatlog history of account in question;
      – online observation of character in question.

    SQUARE ENIX keeps full history of the chatlog since day 1, including private messages.
    If there ever was a discussion of third party tools in the game chat, it is considered evident proof of illicit activity. In this case no additional observation or interaction with the character will be made.
    It doesn’t matter whether the player who filed a report participated in the said discussion. For example, the discussion could take place between friends but a complete stranger filed a report. In this case said discussion will still be considered a sufficient proof to the report.

    Additionally, if there ever was a discussion of a third party tool not related to botting (such as parsers or graphics modifiers), it may also be considered sufficient proof, because SQUARE ENIX can not selectively tolerate some programs and disallow others. All third party tools are equally against the game rules regardless of their impact on game process. The penalty type in each separate case is determined by SQUARE ENIX in its sole discretion.

    If no evident proof of illicit activity is found in chatlog history, a character in question will be observed online for a certain amount of time. During this time a SQUARE ENIX representative may or may not choose to interact with the character and ask to comply with certain requests.

    If no evident proof of illicit activity is found during observation, a counter claim may be automatically filed against the player who filed the initial report.
    Filing a report out of malicious intent is considered harassment and is equally against SQUARE ENIX’s policies and terms of use. In this case the player who filed the report may receive a warning or an account suspension, depending on the previous history of player’s actions and received warnings.

    in reply to: [Beta] Scenario Scripting Engine #3501
    Miqobot
    Miqobot
    Keymaster
    1+

    We review carefully all your requests and adjust our development plans accordingly. Additional features will be implemented after Stormblood release.
    Please refer to this section for more information: Planned Functions.

    Thank you for your feedback very much!

    in reply to: [Beta] Scenario Scripting Engine #3500
    Miqobot
    Miqobot
    Keymaster
    1+

    Miqobot Beta has been updated.
    Please redownload the latest version from the first post:

    Download Miqobot Beta

    The following problem was addressed:
    – Gathering: An issue wherein function gatherTouch() would not work properly when character was too far from a gathering node.

    in reply to: Take care #3461
    Miqobot
    Miqobot
    Keymaster
    1+

    Thank you for your feedback very much!

    This topic is now moved to private developer section for further investigation. If we require additional information we will contact you once again. We are very grateful to you for cooperation!

    in reply to: One more "I WANT!" idea. #3312
    Miqobot
    Miqobot
    Keymaster
    0

    Accepted 🙂
    This is very similar to how the combat navigation AI will look like.
    Combat is planned for release in v1.3.x series of Miqobot.

    By the way, while we are exploring navigation ideas, let us also share a picture. We would like to know your opinion of this riddle.

    Fill Riddle

    1. Given different waypoint types in different corners (foot / mount / fly), how should Miqobot behave in the middle of this area?
    2. How does the complexity change when there are more than 3 waypoints? (As in your picture above.)
Viewing 15 posts - 2,536 through 2,550 (of 3,056 total)