[Beta] Scenario Scripting Engine

Forum Forums Discussion [Beta] Scenario Scripting Engine

This topic contains 119 replies, has 51 voices, and was last updated by Lyfox Lyfox 1 month, 3 weeks ago.

Viewing 15 posts - 31 through 45 (of 120 total)
  • Author
    Posts
  • #3274
    Timray
    Timray
    Participant
    0

    After reading my submitted post I think I need to clarify before someone says something:
    When I said “I’ve tried zoneGate(angle) and it does nothing. any ideas?”
    I used the angle number I was facing towards the gate and not the word angle 🙂

    #3276
    Lyfox
    Lyfox
    Participant
    0

    Can confirm, it doesnt work. Just tried it and it doesnt do anything. It says:
    Adventure calls! I have to jump into wormhole. (Angle: 2.87)

    And skips the function.

    Well until it gets fixed, i guess you can do this:

    holdKey(w, 5.0)
    afkFor(0:0:30)

    #3278

    ExarchCoercer
    Participant
    0

    While we are on the idea train I think it it would be really cool if we were able to retrieve items from a retainer. Something like retrieve(retainer_name,item, item_amount).

    #3279

    ExarchCoercer
    Participant
    0

    Can confirm, it doesnt work. Just tried it and it doesnt do anything. It says:
    Adventure calls! I have to jump into wormhole. (Angle: 2.87)

    And skips the function.

    Well until it gets fixed, i guess you can do this:

    holdKey(w, 5.0)
    afkFor(0:0:30)

    Another option is to click the Aetheryte and using keyboard commands to select zone you want in Idyllshire

    #3301
    Miqobot
    Miqobot
    Keymaster
    1+

    Thank you for reporting issues very much!

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

    Download Miqobot Beta

    The following problems were addressed:
    – Scenario Engine: An issue wherein function goToZoneGate() would not work properly.
    – Crafting: An issue wherein selected recipe in the Crafting Log would be changed accidentally under certain conditions.

    #3302
    Miqobot
    Miqobot
    Keymaster
    1+

    Thank you all for your requests!
    We will be working on improvements and additional modules after Stormblood arrival.

    Please keep providing feedback and sharing ideas!

    #3361
    gregye
    gregye
    Participant
    0

    Question for the workUntil Function

    My idea (stupid example but you know what i mean)

    Chapter1
    sit()
    standUp()
    workUntil(08:00et)
    repeatChapter(100)
    Chapter2
    mount()
    dismount()
    workUntil(08:30et)
    repeatChapter(100)
    repeatAll

    So the plan is to repeat chapter 1 till 0800et then switch to chapter 2. I wannt to repeat chapter 2 till 0830et and then swap back to chapter 1.

    Sadly I couldn’t bring this to behave the way I wannt it.

    Has someone an idea?

    #3370

    ExarchCoercer
    Participant
    0

    Request:

    Do you think we could please get the option to restart the scenario if a death occurs? I have quite a few scenarios that start with teleport and they would all run smoothly if a death occurred to restart at chapter one. There are so many times a simple mob walks in the wrong path and I die and it kills the whole thing.

    Thanks!

    #3378
    gregye
    gregye
    Participant
    0

    My idea (stupid example but you know what i mean)

    If worked out what I wannt in the end so here is the actuall thing 🙂

    chapter 3

    waypoint(2)
    workUntil(18:30et)// time-window about to close so miqo should stop here at 18:30et
    gather(1)
    waypoint(12)
    land()
    gatherTouch()
    waypoint(16)
    land()
    gatherTouch()
    repeatChapter(100)// repeat this chapter until time-window is close

    chapter 4

    //Dravanian Paprika spot at 19:00et
    teleportIF(Falkenhorst)
    job(BTN)
    gatherPreset(Dravanische-Paprika)
    grid(Dravanische-Paprika+Nav)
    waypoint(11)
    gather(1)

    Unless you are lucky and chapter3 line2 lines up perfectly at 18:30et miqo just say “WORK until: 18:30et (4139 seconds)”.

    If I code something wrong pls tell me 😀

    My current workarround would be to count how often she can repeat chapter 3 and work with the number but this is risky and I have to be there from the begining so not optimal.

    What also could help is an aditional argument on repeatChapter for time repeatChapter(18:30et) or repeatChapterUntil(18:30et).

    • This reply was modified 2 years, 8 months ago by gregye gregye.
    #3386

    rodgerdodger
    Participant
    0

    If I wanted to mine and bot clusters does anyone know how would I write a chapter to change jobs at a specific time?

    • This reply was modified 2 years, 8 months ago by  rodgerdodger.
    • This reply was modified 2 years, 8 months ago by  rodgerdodger.
    #3394
    gregye
    gregye
    Participant
    0

    If you mean those in Mor Dhona i would personaly do this in 2 chapters (for a better look)

    chapter 1
    //Cluster_BTN_1-5-9et
    teleportIf(Geisterzoll)//im playing on german client but this will work for you too
    job(BTN)
    gatherPreset()//put your preset-name here if you have one
    grid()//put your grid-name here
    waypoint()//if you work with a beacon put the beacon number here if not just put a number here withch is close to the stuff
    afkUntil(01:00et)
    gather(1)
    waypoint()//same as above
    afkUntil(05:00et)
    gather(1)
    waypoint()
    afkuntil(09:00et)
    gather()

    Chapter 2
    //Cluster_MIN_13-17-21et
    teleportIf(Geisterzoll)
    job(MIN)
    gatherPreset()//if you work with different ones else delet this line
    grid()//same
    waypoint()
    afkUntil(13:00et)
    gather(1)
    waypoint()
    afkUntil(17:00et)
    gather(1)
    waypoint()
    afkUntil(21:00et)
    gather(1)
    repeatAll()//put the number of runs here

    This way you can easy jump in to the scenario.
    Should be ready for copy-pasta.
    Ohh and make sure your grid is conectet to the aetheryte or delete the teleportIf line and walk manualy over.

    #3396

    kujah
    Participant
    0

    Hi Guys,

    Just enquiring about “gatherTouch” function, i seem to have an issue where i set it to navigate to a waypoint then gatherTouch, even though “Green” nodes are linked it does not touch due to distance, is it possible to specify in gathertouch() multiple waypoints or to search up to a certain number of branches before it errors out? or perhaps there is another way that i have missed.

    Many Thanks

    #3409

    rodgerdodger
    Participant
    0

    If you mean those in Mor Dhona i would personaly do this in 2 chapters (for a better look)

    chapter 1
    //Cluster_BTN_1-5-9et
    teleportIf(Geisterzoll)//im playing on german client but this will work for you too
    job(BTN)
    gatherPreset()//put your preset-name here if you have one
    grid()//put your grid-name here
    waypoint()//if you work with a beacon put the beacon number here if not just put a number here withch is close to the stuff
    afkUntil(01:00et)
    gather(1)
    waypoint()//same as above
    afkUntil(05:00et)
    gather(1)
    waypoint()
    afkuntil(09:00et)
    gather()

    Chapter 2
    //Cluster_MIN_13-17-21et
    teleportIf(Geisterzoll)
    job(MIN)
    gatherPreset()//if you work with different ones else delet this line
    grid()//same
    waypoint()
    afkUntil(13:00et)
    gather(1)
    waypoint()
    afkUntil(17:00et)
    gather(1)
    waypoint()
    afkUntil(21:00et)
    gather(1)
    repeatAll()//put the number of runs here

    This way you can easy jump in to the scenario.
    Should be ready for copy-pasta.
    Ohh and make sure your grid is conectet to the aetheryte or delete the teleportIf line and walk manualy over.

    Thanks! I’ll give this a try

    • This reply was modified 2 years, 8 months ago by  rodgerdodger.
    #3415
    riley
    riley
    Participant
    0

    Kujah perhaps someone else has a better work around but what works for me is placing a waypoint between to possible gathering nodes. I then instruct miqo to fly to that node and gatherTouch(). She automatically detects which one is closer/spawned and will go for it because both are in range that way.

    #3420

    kujah
    Participant
    0

    I can’t replicate the same behaviour ryue at least on nodes that are spread quite widely, i can have all nodes linked to the nav point with 2 possible green nodes and it fails because of the distance.
    I get the following:

    (14:23:49) 1 trip more..
    (14:23:49) Destination reached!
    (14:23:49) There is no gathering node to touch!
    (14:23:49) ERROR (Chapter 8, Line 5): Execution error
    
    • This reply was modified 2 years, 8 months ago by  kujah.
Viewing 15 posts - 31 through 45 (of 120 total)

You must be logged in to reply to this topic.