ANNOUNCEMENT: features that WILL NOT be added

[PrincessRTFM]

As stated by the plugin owner any time the matter has arisen, ARR mobs will not be added. The problem that HB aims to solve is that HW+ hunts aren't organised, allowing the same mob to show up in more than one hunt bill. ARR hunts don't do this. There's only a single hunt bill for ARR dailies.

Furthermore, a number of those mobs are FATE-exclusive, which means that either a total overhaul/rewrite would be needed to allow indicating this, or the location would lead you to a place where the mobs may well not exist at the time. The first option would be far too much work for minimal return, the second would only lead to an increased volume of complaints regarding incorrect locations.

At present, there are only two of us working on this project, and both of us are doing it in our spare time, unpaid. We do not consider this to be worth the significant effort required to implement it. Any further issues opened on the subject will be summarily closed and the opener blocked.

[PrincessRTFM]

Since it seems there's still some confusion, here's an explanation of features that will be unconditionally refused at this time. By "unconditionally" I mean that not only will we not implement them, we will also not accept PRs that implement them. These features have been discussed, considered, and rejected.

• ARR daily hunt marks
  • These are beyond the scope of HuntBuddy's purpose, which is to simplify handling of multiple stacks of bills, where you can end up with mobs in the same zone from two or three of them.
  • Additionally, every single stack of bills has multiple marks that are FATE-exclusive mobs. While it would be possible to add these to the database and display that information, the next-mark algorithm used by the /phb next command cannot handle them, because the plugin cannot determine which FATEs (if any) are active in a zone unless you are currently in that zone. This would inevitably lead to the command selecting a mark that won't be around for the next twenty minutes.
• Any kind of multi-location handling
  • Yes, we could probably come up with a workaround for multiple map markers. No, we're not dealing with that. The next-mark algorithm is already bad enough, trying to handle multiple locations for marks would be an absolute nightmare of complexity just begging for nasty bugs.
• ARR weekly hunt marks
  • Not only would this fall under the multi-location rejection, it would be utterly worthless. In general, these can spawn across the entire accessible map in their zone, which means it would clutter your map with markers and not actually provide any useful information.