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
We'd like to be able to build a tool that can track game results over a longer period of time within our group. To that end, we'd love to be able to pull in data directly from the app so that we can feed it into the tool.
As a solution, either an exportable JSON (With the seat number, player id, role assigned, reminder tokens set, whatever data that is currently set by the Storyteller, which team won, etc) or some sort of API onto the back end that we can query to get the data currently stored by the server (if there is any).
We've considered building our own reporting tool to accomplish this, but we feel we'd basically be reinventing the wheel with the current client design.
The cleanest method would be a JSON export from the client initiated by the Story Teller after a game is listed as ended.
The text was updated successfully, but these errors were encountered:
Hey, this makes sense to have, but it also ties into the user statistics that the app is / will track for you automatically. I'm not sure if getting access to the raw data is going to be part of the first release of that, but it could definitely be added later down the line.
We'd like to be able to build a tool that can track game results over a longer period of time within our group. To that end, we'd love to be able to pull in data directly from the app so that we can feed it into the tool.
As a solution, either an exportable JSON (With the seat number, player id, role assigned, reminder tokens set, whatever data that is currently set by the Storyteller, which team won, etc) or some sort of API onto the back end that we can query to get the data currently stored by the server (if there is any).
We've considered building our own reporting tool to accomplish this, but we feel we'd basically be reinventing the wheel with the current client design.
The cleanest method would be a JSON export from the client initiated by the Story Teller after a game is listed as ended.
The text was updated successfully, but these errors were encountered: