Fully Automated 7.0 Orange Gatherer Scrips!

Forum Forums Grids and Presets Fully Automated 7.0 Orange Gatherer Scrips!

This topic contains 29 replies, has 12 voices, and was last updated by  waosekka 2 weeks, 6 days ago.

Viewing 15 posts - 16 through 30 (of 30 total)
  • Author
    Posts
  • #41823

    NotABotter
    Participant
    0

    I Keep getting this.

    (7:55:30 AM) (SCENARIO) Started:
    (7:55:30 AM) ‘New Scenario’
    (7:55:30 AM) Chapter: 1
    (7:55:30 AM) ERROR (Chapter 1, Line 1): Syntax error. Expected format: function(arguments)

    Can you post your Chapter 1 please?

    #41825

    jj213
    Participant
    0

    I simply copy pasted your new script on to the scenario section on Miqo. Did I miss something ? Still a bit new to Miqo

    • This reply was modified 3 months ago by  jj213.
    #41830

    NotABotter
    Participant
    0

    I simply copy pasted your new script on to the scenario section on Miqo. Did I miss something ? Still a bit new to Miqo

    Which new script are you referring to? Did you use the new complete one or just swap the chapter for purchasing tokens?

    #41831

    jj213
    Participant
    0

    Tada!

    Fully fixed scenario for patch 7.1! No changes required for the grids fortunately! I did make some changes to the gathering rotations as well as fixed the chapter for buying tokens.

    “Gatherer-Orange-Scrips.txt”

    I used the one you attached to this post.

    #41835

    jj213
    Participant
    0

    Sorry. Figured out the previous problem.

    But now I’m getting “Uhoh. There’s no key bound to action ‘Switch to Hotbar 6″” on action: return() and teleport.

    They’re both keybound as well

    #41836

    jj213
    Participant
    0

    Tested other chapters. Seems to be several things not working for me.

    Chapter 2 token purchase isnt getting to the scrip turn in menu after targeting the npc.

    Chapter 3 randomWaypoint(24, 29, 30) is generating “Uhoh. There’s no key bound to action ‘Switch to Hotbar 7’.” Seems to be the same for other “waypoint” commands

    • This reply was modified 2 months, 4 weeks ago by  jj213.
    #41844

    NotABotter
    Participant
    0

    Tested other chapters. Seems to be several things not working for me.

    Chapter 2 token purchase isnt getting to the scrip turn in menu after targeting the npc.

    Chapter 3 randomWaypoint(24, 29, 30) is generating “Uhoh. There’s no key bound to action ‘Switch to Hotbar 7’.” Seems to be the same for other “waypoint” commands

    Hey jj213. I would like to really dig in to why you’re having so many issues with the scenario. Would you be able to join the Miqo Discord server so I can attack this in a much more timely manner?

    Here is the server invite link: 33mg5UFc
    (Link expires December 3rd)

    • This reply was modified 2 months, 3 weeks ago by  NotABotter.
    #41848

    jj213
    Participant
    0

    Hey. Got it to work after fiddling around with few things.

    Thank you

    #41859

    NotABotter
    Participant
    0

    Hey. Got it to work after fiddling around with few things.

    Thank you

    If you know what you did to fix it, I would love to know what you adjusted.

    #41862

    jj213
    Participant
    0

    “Chapter 2 token purchase isnt getting to the scrip turn in menu after targeting the npc.”

    This just fixed itself. Not sure how…

    “Chapter 3 randomWaypoint(24, 29, 30) is generating “Uhoh. There’s no key bound to action ‘Switch to Hotbar 7’.” Seems to be the same for other “waypoint” commands”

    This was just my mount hotkey keybound to something miqo did not recognize

    “But now I’m getting “Uhoh. There’s no key bound to action ‘Switch to Hotbar 6″” on action: return() and teleport.”

    I had 2 teleports on my hotbar. One keybound to something miqo recognizes, one not. Miqo was trying to use the one that wasn’t keybound. It worked fine after I removed it

    #41872

    bthelee
    Participant
    0

    I keep getting a few errors,
    (12:11:24 PM) Uhoh. There’s no key bound to action ‘Switch to Hotbar 3’.
    (12:12:03 PM) Adventure calls.. But it is ERROR! (Grid: ‘Radz-at-Han’, Waypoint: 14/11)

    and from there it just stops

    #41903

    PandaForce
    Participant
    0

    Hey there, gotta ask is it normal that after the collectability reaches max the bot only hits the node once to collect the item but if there are more attempts left he does nothing after the first hit?

    Kinda end ups looking like this if a node has still attempts left:

    (05:12:55) GP = 868. OK – rotation ‘Collectable 700’ (700).
    (05:12:55) Using action: (Start)
    (05:12:55) Using action: (Scrutiny)
    (05:12:58) Using action: (Meticulous)
    (05:13:01) Using action: (Scrutiny)
    (05:13:02) Using action: (Meticulous)
    (05:13:05) Using action: (Meticulous)
    (05:13:07) Using action: (Meticulous)
    (05:13:10) Using action: (Meticulous)
    (05:13:13) Using action: (Hit Once)
    (05:13:17) Using action: (+1 Attempt)
    (05:13:32) Using action: (+1 Attempt)
    (05:13:47) Using action: (+1 Attempt)
    (05:14:02) Using action: (+1 Attempt)
    (05:14:17) Using action: (+1 Attempt)
    (05:14:32) Using action: (+1 Attempt)
    (05:14:47) Using action: (+1 Attempt)

    Bot trying to hit it but nothing happening.

    • This reply was modified 1 month ago by  PandaForce.
    #41933

    Enya
    Participant
    0

    First of all, massive thanks for this scenario! Been running it while I’m sitting behind my desk to study 🙂

    I have noticed one issue which causes the script to kill itself. When I have more than 5 pieces of gear at 100% spiritbond, the extractmateria() command will constantly run into “cannot execute while busy” errors in the game and terminate itself because of too many errors in sequence.

    in miqobot it looks like this

    (17:58:05) Everything is gathered!
    (17:58:06) Left to materialize: 8
    (17:58:07) A suspicious error…
    (17:58:10) Left to materialize: 7
    (17:58:11) A suspicious error…
    (17:58:14) Left to materialize: 6
    (17:58:15) A suspicious error…
    (17:58:18) Left to materialize: 5
    (17:58:19) A suspicious error…
    (17:58:22) Left to materialize: 4
    (17:58:23) A suspicious error…
    (17:58:23) Oh no, I broke something. Too many errors 🙁
    (17:58:23) ERROR (Chapter 13, Line 14): Execution error

    I have tried placing the extract command at the end of chapters instead (reasoning that maybe it was coz miqobot tried to continue its script while still busy extracting) but to no avail.

    Any thoughts?
    I have run other scenario’s I made in the past with the same command without errors. Don’t know if it’s because of a recent change or just dumb luck tho. I will try adding an extractmateria() chapter only and see if it remains an issue (I usually do that and repair in a seperate chapter)

    • This reply was modified 4 weeks, 1 day ago by  Enya.
    • This reply was modified 4 weeks, 1 day ago by  Enya.
    • This reply was modified 4 weeks, 1 day ago by  Enya.
    #41937

    Enya
    Participant
    0

    follow-up:
    putting it in a seperate chapter still results in “unable to execute command while occupied” errors in-game and “a suspicious error…” in miqobot.
    I tried to stagger the rate of spiritbond so that no more than 4 pieces of gear would hit 100%, but it’s impossible due to the random chance of a revisit proc causing gear to cap at 100% again.

    Guess for now I’ll manually extract in between nodes and leave the auto-extract from the scenario.

    it was the “always yes” plugin causing interference with how miqo does the extraction. The plugin clicked yes before miqo could, making miqo try over and over to hit that non-existing yes button 🙂

    • This reply was modified 4 weeks ago by  Enya.
    #41951

    waosekka
    Participant
    0

    First of all, I’m Japan and use translation, so I’m sorry if the sentence is strange

    If you try to use this scenario, you won’t get to the Razahan token exchange location in the first place
    But you can exchange it at the script exchange place

    Even if I skip it and go to the next scenario, I get an error at all waypoints
    Why is this?

Viewing 15 posts - 16 through 30 (of 30 total)

You must be logged in to reply to this topic.