Hi,
I am trying to set up a recurring event which will reset some data in a database each day. I have a database titled Character. It has a list of characters that have different traits. I need to reset values in this database for each character. Some fields will reset to 0, some will reset to different values for each character, i.e., character x will have a score of 10, character y will have a score of 20.
I have tried to set up the backend workflow as a recurring event.
And the Action being to Make a Change to a Thing. The Thing being the character database.
I’ve then set up a button to start the recurring event.
However, when I try to try to set up the recurring event as daily, it wants me to put in the Workflow Thing. I can’t put in Character.
I may be misunderstanding what the Thing refers to. But I don’t know what I am supposed to put in to ensure all characters data is changed in the database. Any help would be greatly appreciated.
Regards,
Brock.
What is use case. I can only imagine you might just consider making an option set for the characters and having a data type to store whatever data has changed. This way, no need to reset each day and instead just track changes users make to the values.
It’s essentially an app to play mystery parties through.
Each player is assigned a character. Throughout the party, they interact with other players and do specific tasks. For instance, they can transfer in-game money between each other. So, one character may transfer $20 to another character, in order to meet their goal. I have set up the transfer to take the value they send, minus it from the first characters total money value, and add it to the seconds.
But, at the end of the party, unless it resets, the first character will start with $20 less next time. I need the values to be reset to what they were at the start of the party. So, just resetting the value to, say, $100 at midnight each day, would accomplish this.
But if backend workflows aren’t the best way to do it, I’m all ears.
Okay, so character is not character how I imagined it where it was like a default avatar and name etc. that represents the character that can be used across the app by any user. Instead character seems to actually be a ‘Player’ who is participating in a ‘Game’ that you are referring to as ‘Party’…so if what I would call ‘Player’ is a ‘Character’ and what I would call ‘Game’ is a ‘Party’ as the idea of Mystery Party is basically a Game of Mystery, like a “Who Did It?”, then I would set things up like the following.
Data Type of Player will have a data field related to the data type of Game. On the Player data type there will be a field of User and all other fields relevant to the money or other point values the Player can accumulate during the Game. Then on the Game data type I would add fields that would be the ‘default’ values to add to each Player when a game starts. This would allow different Games in the database to have different rules, like how much money does each Player of the Game start with.
So when a group of Players are about to begin a Game you can create in the database the Player data types and set the data fields that are the values like Points/Money based on the values in the Selected Game data entry.
The data type of Player will act like a Game Session as well since you will have fields like User and Game, you will be able to search for things like Show this User all Games they have played, or Show the Admin all Users who have played this Game. But as the way Player data type can act like a Game Session is you will have a field that will be of type text that is a unique value assigned to each Player created at the start of Game so that one text field can be used to distinguish all data entries in the database for Player by Users, Game and which Game Session so you can say if a User has played the same Game 200 times, there would be 200 entries in the database under Player with the same User and same Game but 200 unique Game Session IDs. You can then search the Player database for all other Players whose Game Session ID is the same to match them as participants in the same Game Session.
