No teleport option for daily hunts about huntbuddy

[graphicschyk]

Trying again since images didn't load.

[graphicschyk]

If it's not broken can you tell me how to make it so the hunts in current area shows me the same info others have where it marks them on the map?

[PrincessRTFM]

As you can see at the top of the main window, ARR hunts are not supported. We do not provide locations for them. Frankly, I'm surprised that they're showing up in the local hunts window at all, since they aren't supposed to.

The purpose of HuntBuddy is to collect hunt marks from the three daily bills in each of the post-ARR expansions into a single interface, so that you don't need to check three different bill stacks to see if you have any hunts left in a particular zone, from the total of fifteen that you receive. In ARR, you have one stack of five, and two or three of those are always FATE targets, which don't even exist until the FATE is active. As a result of this, we - the developers - decided that ARR hunt marks will not be supported.

[graphicschyk]

Ahh I did not understand that. Okay. I’ll just only take hunts in post ARR cities then I guess. On Jul 11, 2024, at 4:31 AM, Lilith ***@***.***> wrote: As you can see at the top of the main window, ARR hunts are not supported. We do not provide locations for them. Frankly, I'm surprised that they're showing up in the local hunts window at all, since they aren't supposed to. The purpose of HuntBuddy is to collect hunt marks from the three daily bills in each of the post-ARR expansions into a single interface, so that you don't need to check three different bill stacks to see if you have any hunts left in a particular zone, from the total of fifteen that you receive. In ARR, you have one stack of five, and two or three of those are always FATE targets, which don't even exist until the FATE is active. As a result of this, we - the developers - decided that ARR hunt marks will not be supported. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>