Okay, so:
Global Cloud Variables:
They are worldwide, storing information on everybody viewing the project as one value.
Private Cloud Variables
They store unique information for every user who views. The values are separate for everybody.
Offline
This is a great idea, but I'm nuetral on this because as kayybee said above ^^, there is a workaround.
Offline
But what if it's a complex game, with hundreds of values, such as xp, hp, attack, defense, and level?
Offline
MOAR VARIABLES :p
Offline
+1
Offline
berberberber wrote:
But what if it's a complex game, with hundreds of values, such as xp, hp, attack, defense, and level?
You put it in as a save code.
Such as 13c039d8f2e18a9b
Where 13 is my level, c0 is my exp, 39d is my hp, 8f is my attack, 2e is defense, 18a9b is my items, etc.
As a programmer you should be figuring out these kinds of things.
Offline
if you want to be organized, you will have a separate list for each variable you want to store, then add another list for user id, then have the item #'s of each list correspond to the other values in other lists that the player is storing.
Offline
kayybee wrote:
This can be done with a cloud list (or two, for safety's sake).
One for the value and one for the userID.
True, but it'd still be useful for the sake of simplicity - not every Scratcher will know how to implement this kind of system with good ol' lists. c:
Offline
technoguyx wrote:
kayybee wrote:
This can be done with a cloud list (or two, for safety's sake).
One for the value and one for the userID.True, but it'd still be useful for the sake of simplicity - not every Scratcher will know how to implement this kind of system with good ol' lists. c:
Perhaps. But this way does work.
Offline
technoguyx wrote:
kayybee wrote:
This can be done with a cloud list (or two, for safety's sake).
One for the value and one for the userID.True, but it'd still be useful for the sake of simplicity - not every Scratcher will know how to implement this kind of system with good ol' lists. c:
Then they learn.
Offline
Chokkan wrote:
And what about the returning users? It would be a poor way to store their passwords in a cloud variable that anyone can see.
I don't think that the cloud variables would be viewable unless the owner of the project wants them to.
Offline
ErnieParke wrote:
Chokkan wrote:
And what about the returning users? It would be a poor way to store their passwords in a cloud variable that anyone can see.
I don't think that the cloud variables would be viewable unless the owner of the project wants them to.
You could just see inside...
But there's no point in having passwords stored, because you can verify people with the userid block.
Offline
kayybee wrote:
ErnieParke wrote:
Chokkan wrote:
And what about the returning users? It would be a poor way to store their passwords in a cloud variable that anyone can see.
I don't think that the cloud variables would be viewable unless the owner of the project wants them to.
You could just see inside...
But there's no point in having passwords stored, because you can verify people with the userid block.
Nevermind about what I said. I can see where I went astray. And yes, using the username block is much more practical.
Offline