You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2021. It is now read-only.
My Hearthstone directory on macOS is default as Blizzard wants it: /Applications/Hearthstone. After a recent track-o-bot update (perhaps 0.8.5, or maybe even earlier since I didn't play for a few weeks), my games weren't being logged. I've checked its settings and it reported that it's configured to look for Hearthstone logs in /Users/mislav/Applications/Hearthstone.
While this location could theoretically be correct on someone else's machine, I never had the practice of putting apps in ~/Applications, and I definitely didn't move Hearthstone installation between directories on disk.
My logging was fixed by re-configuring the Hearthstone directory in track-o-bot. I'm just letting you know about this oddity in case you got similar reports. (I couldn't find any by searching.) If you can't guess where this bug might be coming from, or can't reproduce, feel free to close this, as it's not a huge issue.
The text was updated successfully, but these errors were encountered:
My Hearthstone directory on macOS is default as Blizzard wants it:
/Applications/Hearthstone
. After a recent track-o-bot update (perhaps 0.8.5, or maybe even earlier since I didn't play for a few weeks), my games weren't being logged. I've checked its settings and it reported that it's configured to look for Hearthstone logs in/Users/mislav/Applications/Hearthstone
.While this location could theoretically be correct on someone else's machine, I never had the practice of putting apps in
~/Applications
, and I definitely didn't move Hearthstone installation between directories on disk.My logging was fixed by re-configuring the Hearthstone directory in track-o-bot. I'm just letting you know about this oddity in case you got similar reports. (I couldn't find any by searching.) If you can't guess where this bug might be coming from, or can't reproduce, feel free to close this, as it's not a huge issue.
The text was updated successfully, but these errors were encountered: