Yes. ------------- Used to be the case | | v v No. 1. Click flag to increase cloud variable as many times as desired 2. Refresh 3. It doesn't work I have two different explanations about what could be the cause: Explanation 1 (Used to be the case and could be worked around by renaming the variables): I think this happens because the user doesn't receive what the current value of the cloud variable is until it updates, and when the user clicks the flag, it sets it to the user's unupdated variable +1 (which is just 1 because the user saw it as 0) In other words: User 1 joins User 1 clicks the flag 10 times The cloud variable is now 10 New User 2 joins (User 1 still on) New user hasn't received any update yet... //From here, it could go two possible ways Possibility 1: User 2 clicks flag, and since user 2 saw it as 0, it is now 0+1=1 User 1 receives this update User 1 now also sees the cloud variable as 1 CONFUSION Possibility 2: User 1 clicks the flag again, and sets the variable to 10+1=11 User 2 receives this update User 2 sees the variable as 11 User 2: Oh it must have been taking time to load...right? (wrong) Reason: I believe that this bug arises from the fact that the User doesn't actually load the update upon starting the project, but rather when the cloud variable updates. If the cloud variable is changed before receiving the updated value, it is now set to the value set by this new user, for all players. Explanation 2 (What's actually the case now): The Cloud variable servers are down
It starts at 1 because the big flag you click to start the project is a flag : ) Comment whether it worked 2 blocks used
