I'm making an app which works like a 'Top Trumps' card game, for airliners. However, I'm facing problem after problem which I'm not able to find the solution for. Note: This app requires 2 devices to work, as it is a multiplayer game.
Would it be possible for someone to please help me out by fixing these bugs and making it work like a proper 'Top Trumps' game? I'm attaching a Drive folder with the images and .aia file for reference.
It leaves the global list as a blank text instead of an empty list if blank text comes back from Firebase. That poisons subsequent list actions against that variable. Also, the global list does not contain the player's name. (I don't know if that is intentional or not. If it's intentional, the variable should be named OtherPlayers.)
I skipped past how you pass data from Screen1 to game_screen, to see why I did not see a table of card deck values in your Media folder.
I found bad news, indicating that you have not used dictionaries or tables for the card deck:
Unfortunately, Discourse can't load the cleaned up blocks image for that screen, so I will show the mistakes snip by snip:
You have dozens of these:
You pay for that mistake in the Play procedure:
(again, too large for Discourse, with all its repeated code, so here's another snip)
This makes sense. However, I'm not very familiar with using Dictionaries and the other things, so I may not be able to work it out well... What is my best way forward?
Wait for the player left of the dealer to choose a card and read 1 of the stats. Invite the first player to read over their card and choose a “stat,” or card description, with a high numerical value.
So the player that starts off a round is not forced to use the top card of his stack, and is allowed to look through his stack to see which card he can play?
If you had encoded your deck in a Google Sheet, one row per plane, with headings over each attribute, you could have downloaded it as a CSV table into your app's Media folder, and read that table at run time.
All the lookups you do by hand could have collapsed like a telescope.
Here's a tip on building up compound Firebase tags:
If you put a '/' between the parts of your Firebase tag, it makes it easier to see the tag/value structure in the Firebase console. The '/' imposes a tree structure on the data, so you can adjust your bucket to zoom in on one branch and its sub-branches. That becomes useful if you want to run more than one game at a time. It also allows grabbing an entire branch and its sub-branches as a dictionary.