Introducing: FFR Tracker
A tracking tool for FFR players
Visit GitHub to download
Description:
FFR Tracker is a tool for players that want take control of their play data, and track their plays over time. It can also be used to add some context and storytelling to your FFR streams. It gets your 10 most recent plays with one click, and displays time, song name, and AAA Equivalent in a scrollable table format. Fetch your recent plays periodically to continue adding to the table. Your scores also get stored locally in a .csv file, in case you want to dig deep and do some analysis yourself. It's built on the FFR API, and requires an API key, so you'll have to visit this page and request an API key to make it work.
Getting Started:
(1) This program uses JavaFX and version 8 Java. You need to get Java in order to run it! Specifically, you want at least version 8 of the Java Runtime Environment (JRE). If you get a later version, note that it may not come with JavaFX (the visual part of Java). You can find later versions of JavaFX here.
(2) Get an FFR API key if you haven't already.
(3) Download and unzip the file from GitHub.
(4) Run the FFRTracker.jar executable that's in the folder.
(5) The program will display the Config Menu on startup. Fill out the "api key" and "username" fields, and then hit "Save Changes".
Now you should be good to go!
Bugs:
You say you've encountered a bug? Don't panic! It'll really help me out if you walk through the following checklist:
(1) Check and make sure you have the latest version from GitHub
(2) Check this thread and see if someone else has had the same issue. If so, no need to report it.
(3) Make sure you haven't restarted the program since experiencing the issue: the log file resets on startup each time.
(4) Having done the prior 3 steps: PM me the contents of your log.log file copied to a pastebin (see pastebin.com), along with a description of what happened. Don't post your whole log file in the thread please!
(5) If your bug is reproducible, post a description of how to do it here in the thread.
Not sure if bug or feature? Okay sure, go ahead and post in the thread.
Feature requests:
If there's interest in the program, I'll definitely devote some time to making it better!
A tracking tool for FFR players
Visit GitHub to download
Description:
FFR Tracker is a tool for players that want take control of their play data, and track their plays over time. It can also be used to add some context and storytelling to your FFR streams. It gets your 10 most recent plays with one click, and displays time, song name, and AAA Equivalent in a scrollable table format. Fetch your recent plays periodically to continue adding to the table. Your scores also get stored locally in a .csv file, in case you want to dig deep and do some analysis yourself. It's built on the FFR API, and requires an API key, so you'll have to visit this page and request an API key to make it work.
Getting Started:
(1) This program uses JavaFX and version 8 Java. You need to get Java in order to run it! Specifically, you want at least version 8 of the Java Runtime Environment (JRE). If you get a later version, note that it may not come with JavaFX (the visual part of Java). You can find later versions of JavaFX here.
(2) Get an FFR API key if you haven't already.
(3) Download and unzip the file from GitHub.
(4) Run the FFRTracker.jar executable that's in the folder.
(5) The program will display the Config Menu on startup. Fill out the "api key" and "username" fields, and then hit "Save Changes".
Now you should be good to go!
Bugs:
You say you've encountered a bug? Don't panic! It'll really help me out if you walk through the following checklist:
(1) Check and make sure you have the latest version from GitHub
(2) Check this thread and see if someone else has had the same issue. If so, no need to report it.
(3) Make sure you haven't restarted the program since experiencing the issue: the log file resets on startup each time.
(4) Having done the prior 3 steps: PM me the contents of your log.log file copied to a pastebin (see pastebin.com), along with a description of what happened. Don't post your whole log file in the thread please!
(5) If your bug is reproducible, post a description of how to do it here in the thread.
Not sure if bug or feature? Okay sure, go ahead and post in the thread.
Feature requests:
If there's interest in the program, I'll definitely devote some time to making it better!
Comment