Currently, using the Verse API, the Tracker Device only allows you to read it’s completion value, increment/decrement the current value, and check if the device is completed. However, updating the tracker device to allow the current tracked value to be queried opens it up to a lot of utility.
For instance, I’m using a tracker to manage an ammo overflow which automatically adjusts the player’s current ammo based on an arbitrary maximum; a tracker is used to keep track of how much ammo is in the overflow at any given time. Using the tracker, I can keep track of this value persistently between sessions while using the completion value as the maximum; however, to actually determine how much ammo is available at a given time, I have to run an awkward timer script that counts up to completion, keeps track of the counts in a separate variable, resets and counts back up to the original value using the variable, and then goes from there, which is an operation that incurs a load time that wouldn’t be necessary if I could just read the tracker value in the first place.