Skip to content
This repository has been archived by the owner on Feb 3, 2024. It is now read-only.

Multitude of Suggestions #104

Open
WesCook opened this issue Oct 8, 2020 · 2 comments
Open

Multitude of Suggestions #104

WesCook opened this issue Oct 8, 2020 · 2 comments
Labels
Enhancements New feature or request good first issue Good for newcomers

Comments

@WesCook
Copy link

WesCook commented Oct 8, 2020

I discovered HunterPie today and have been playing around with it. I like it a lot so far. I definitely prefer it to other available solutions, and appreciate that it's open-source.

I had some miscellaneous suggestions which I thought might improve things. If you'd like me to create a separate issue for each I'm happy to do so. Though I thought it may be a bit spammy otherwise.

App General/UI

  • I'd like if I could disable background transparency. Depending on your desktop, it could be more difficult to use.
  • I find it irritating that HunterPie always asks for confirmation to quit. There's no risk of data loss from closing it, so this seems unnecessary.
  • I think I had my settings reset by editing config.json while the program was running. Either that or I made an illegal edit (setting UI scale to 1.1).

Monsters Widget

Feedback: The customization is great. I'll need to fight a few more monsters to figure out which parts are worth showing. Generally head, horns, wings, severable tail. I find leaving these on permanently is easier to read than having parts shuffle in and out.

  • There's two Flash entries. I believe one is for the actual flash stun, and one is for the discombobulated monster status that acts erratically. Maybe change one of these labels to help differentiate?
  • The ailment toggle settings weren't labelled as requiring a reset, but I often had to restart the app for them to update.
  • I know I just said I prefer parts to be displayed permanently, but a few ailments really are situational. eg. Traps, dung pods. I turned them off to reduce clutter, but having them only show when active would be useful.

Harvest Box Widget

  • I found the UI a little unintuitive at first because there's a label for the Harvest Box at the top, but it includes other info (Steamworks, Argosy, Safari).
  • I find this widget both useful and not. I can read it and make sense of it, but it requires asking questions like "Is 350 Steam almost full?". I feel it could be more actionable (3 hunts until harvest box fills up, 2 hunts until tailraider safari returns).
  • Maybe a setting specifically to enable in the Guiding Lands, because that's the only time I can think it's worth checking mid-hunt. Mostly to avoid losing your fertilizers.

Damage Meter Widget

  • The timer clock is very useful. I think it would be more useful though if it counted down (time left), not up.
  • The average DPS doesn't make much sense to me. Is it averaged out over the entire hunt? I think showing average DPS over the last X seconds would be a lot more useful.
  • I'd like to disable the HR/MR number. It's not too relevant during a hunt and it just helps clean up the UI a bit.

Class Helper Widget

  • The note at the bottom mentions class-specific settings, but I'm not sure where to edit these.
  • Hunting Horn is disabled by default. Is it buggy, or was this unintentional?

Other Thoughts

  • I haven't tested Discord integration or the abnormalities tray yet.
  • The overlay could probably be removed from the quest completion screen, just to clean things up.
  • Some of the videos in the documentation don't appear to load. eg. Specialized Tools Widget page

Hope this is useful feedback for you. Thanks for the great app.

@Haato3o
Copy link
Member

Haato3o commented Oct 9, 2020

Hey, thanks for the suggestions, I will definitely take them into consideration. Answering some of them:

I'd like if I could disable background transparency. Depending on your desktop, it could be more difficult to use.

You actually can do that, HunterPie lets you customize some of it's UI more thoroughly using theme files or directly overwriting the styles in the HunterPie.Resources/UI/Overwrite.xaml. Pasting the following styles in the Overwrite.xaml file will remove the background transparency.

<SolidColorBrush x:Key="CONSOLE_BACKGROUND">#FF141414</SolidColorBrush>
<SolidColorBrush x:Key="CONSOLE_HEADER_BACKGROUND">#FF141414</SolidColorBrush>
<SolidColorBrush x:Key="CONSOLE_SIDEBAR_BACKGROUND">#FF141414</SolidColorBrush>
<SolidColorBrush x:Key="CONSOLE_WINDOWBAR_BACKGROUND">#FF141414</SolidColorBrush>

I think I had my settings reset by editing config.json while the program was running. Either that or I made an illegal edit (setting UI scale to 1.1).

You should never edit the config.json directly, you should use the design mode for scaling the widgets/moving their position (the default hotkey for that is ScrollLock, but can be changed in Settings -> Overlay).

The ailment toggle settings weren't labelled as requiring a reset, but I often had to restart the app for them to update.

They don't require a restart since their settings are applied when you press the "Save" button. Not sure why you had to restart HunterPie to apply it, I'd have to look into the code and see if there's a bug or something.

I found the UI a little unintuitive at first because there's a label for the Harvest Box at the top, but it includes other info (Steamworks, Argosy, Safari).

That's because when HunterPie was first released, the Harvest Box widget would only show the harvest box information. Other activities were added months after, so I never really bothered to change the texts.

I find this widget both useful and not. I can read it and make sense of it, but it requires asking questions like "Is 350 Steam almost full?". I feel it could be more actionable (3 hunts until harvest box fills up, 2 hunts until tailraider safari returns).

You can have a maximum of 700 natural steam fuel, and when you reach that number a red pulsating icon will appear on top of the steam machine icon. Now for the "hunts until...", you can't calculate the harvest box based on that since it depends on the fertilizer and items you're harvesting. Also, that's exactly how it works for safari and Argosy. For safari it will show the number required of days you need to wait until they return and for argosy it will show the number of days until he returns, when argosy is back, a red pulsating icon will appear and show the number of days until he leaves again.

The timer clock is very useful. I think it would be more useful though if it counted down (time left), not up.

That's not really possible, the clock isn't a quest timer, it's just a session timer that resets whenever you go to another area (hence why it doesn't stop after the quest is over), and HunterPie doesn't currently track anything about the quest you're doing so it can't get the quest time limit.

The average DPS doesn't make much sense to me. Is it averaged out over the entire hunt? I think showing average DPS over the last X seconds would be a lot more useful.

The DPS is calculated after the first hit, it's Your Damage / (Time Elapsed - Time from first hit)

The note at the bottom mentions class-specific settings, but I'm not sure where to edit these.

I meant that you can place each class in a different position or have them at different scales even though it's only 1 widget.

Hunting Horn is disabled by default. Is it buggy, or was this unintentional?

That was intentional, I disabled it by default because it shows the exact same thing as the game does (the song/notes queue). I only added it because I intend to add a health/stamina bar soon, so the game one can be disabled.

The overlay could probably be removed from the quest completion screen, just to clean things up.

I found player action id in memory very recently, so that might be added soon.

Some of the videos in the documentation don't appear to load.

Hmm, they're loading for me, might be some browser/compatibility problem.

@Haato3o Haato3o added Enhancements New feature or request good first issue Good for newcomers labels Oct 9, 2020
@WesCook
Copy link
Author

WesCook commented Oct 9, 2020

Thanks for the info! I figured a few of these were due to limitations of what was available in memory, like the timer.

Regarding the video in the docs, it looks to be a Chrome thing. It loads fine in Firefox. Maybe a decoding problem, but Chrome should be able to understand webms.

Feel free to edit my first comment if you want to use this issue to track changes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancements New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants