Is resetGoodWeather() working as intended?

Forum Forums Discussion Is resetGoodWeather() working as intended?

This topic contains 2 replies, has 2 voices, and was last updated by jae jae 3 years, 10 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #25619
    jae
    jae
    Participant
    0

    I modified a scenario for the diadem, I found here, to check for weather conditions in the diadem. It worked fine until I condensed two chapters for checking for the right weather conditions for both miner and botanist and adding resetGoodWeather() after each job change, as I thought this would allow miqo to repeat this chapter for the duration of one diadem lockout using repeatChapterFor(). Can resetGoodWeather() only be called once per chapter?
    If this is not the case, could someone might look at the chapter and possibly see what I might have done wrong?

    job(BTN)
    resetGoodWeather()
    goodWeather(Umbral Duststorm)
    goodWeather(Umbral Tempest)
    skipBadWeather()
    workFor(00:04)
    gather(1)
    waypoint(6)
    
    job(MIN)
    resetGoodWeather()
    goodWeather(Umbral Levin)
    goodWeather(Umbral Flare)
    skipBadWeather()
    workFor(00:04)
    gather(1)
    waypoint(38)
    
    repeatChapterFor(01:25)
    

    This is what I noticed in the logs that made think it wasn’t clearing the weather conditions after the first use:

    (9:25:02 PM) Uh-oh 'Umbral Levin (87)'. It's a bad weather!
    (9:25:02 PM) WORK for: 00:01 (60 seconds)
    (9:25:03 PM) I don't want to WORK! It's a bad weather!
    (9:25:04 PM) Gathering started.
    (9:25:04 PM) 	Max node count: 1
    (9:25:04 PM) Scanning for shiny gathering nodes like '<anything>' *.*
    (9:26:02 PM) WORK time is over! Let's go to another chapter ^_^
    (9:26:03 PM) Gathering stopped.
    (9:26:04 PM) Adventure calls! I have to travel far away. (Grid: 'DiaUmb', Waypoint: 6)
    (9:26:04 PM) Going from 60 to 6 in 4 trips.
    (9:26:07 PM) 4 trips more..
    (9:26:11 PM) 3 trips more..
    (9:26:30 PM) 2 trips more..
    (9:27:07 PM) 1 trip more..
    (9:27:08 PM) Destination reached!
    (9:27:10 PM) I am 'MIN' now! :3
    (9:27:11 PM) It was a bad weather before! I'm already upset.
    (9:27:12 PM) I don't want to WORK! It's a bad weather!
    (9:27:12 PM) Gathering started.
    (9:27:12 PM) 	Max node count: 1
    (9:27:12 PM) WORK time is over! Let's go to another chapter ^_^
    (9:27:13 PM) Gathering stopped.
    (9:27:14 PM) Adventure calls! I have to travel far away. (Grid: 'DiaUmb', Waypoint: 38)
    (9:27:14 PM) Going from 6 to 38 in 2 trips.
    (9:27:14 PM) 2 trips more..
    (9:27:39 PM) 1 trip more..
    (9:27:39 PM) Destination reached!
    (9:27:40 PM) REPEAT chapter for: 01:25 (5100 seconds)
    (9:27:41 PM) (SCENARIO) Chapter 2 complete.
    (9:27:41 PM) (SCENARIO) Chapter 2 restart! (5100 seconds left)
    #25624
    Lyfox
    Lyfox
    Participant
    0

    resetGoodWeather() can be used many times per chapter. But it does not reset skipBadWeather(). From the documentation:

    skipBadWeather( )

    If weather is not found in whitelist, function will automatically set next activity limit to 60 seconds: workFor(00:01). Consequent calls to workFor() in the same chapter will not change the limit.

    It works this way because these functions werent actually designed for Diadem. They were made for legendary fishing. Its for those rare fish that have extreme weather conditions like Helicoprion that can be caught only during Heat Waves after Clouds or Fog. This requires checking weather twice at different times. Thats why skipBadWeather() effect persists through the whole chapter. But for Diadem you need the opposite behavior.

    So to use this feature in Diadem you have to split miner and botanist into different chapters.

    #25628
    jae
    jae
    Participant
    0

    I see, I didn’t fully understand skipBadWeather(), I’ll have to rewrite my scenario, thanks for explaining.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.