(Note: Reposted from the general forum)
A user in the previous thread pointed out that this tool might be viewed as cheating by the community. Coming from a Hearthstone background as a new player to this game, my perspective was shaped by tools like HDT or Firestone. In those environments, tracking open information to reduce mechanical memorization is a standard practice to help players focus on strategy.
I understand now that the board game community on BGA may have different standards regarding memory mechanics and external assistance tools. I respect those differing norms.
This script is shared purely as an open-source technical exercise. I have no plans to maintain or use it.
Project Summary:
Function: An experimental Userscript that tracks visible game state (cards seen).
Status: Core ID-based tracking works. UI is unrefined. The codebase is a proof-of-concept.
GitHub Repository: https://github.com/HailiangLoo/Forest_S ... racker_BGA
Feel free to review or fork the code if interested.
A user in the previous thread pointed out that this tool might be viewed as cheating by the community. Coming from a Hearthstone background as a new player to this game, my perspective was shaped by tools like HDT or Firestone. In those environments, tracking open information to reduce mechanical memorization is a standard practice to help players focus on strategy.
I understand now that the board game community on BGA may have different standards regarding memory mechanics and external assistance tools. I respect those differing norms.
This script is shared purely as an open-source technical exercise. I have no plans to maintain or use it.
Project Summary:
Function: An experimental Userscript that tracks visible game state (cards seen).
Status: Core ID-based tracking works. UI is unrefined. The codebase is a proof-of-concept.
GitHub Repository: https://github.com/HailiangLoo/Forest_S ... racker_BGA
Feel free to review or fork the code if interested.