Bump because I'd love to have projects the ability to set cloud variables “for this user only” !
There should this limit : Each project cannot set more than ONE single variable for the same user. It would then have the name of “private cloud variable” or smth similar. You don't create them.
If this gets implemented, the user whose his account gets to store variables must have the ability to delete them from a menu in the account settings page. Like if you go to the save files management screen of a GameCube's BIOS UI, but without anything else than just deleting the save file.

i foresee the possibility of being able to manually modify cache through the console to cheat.

jmdzti_0-0 wrote:

i foresee the possibility of being able to manually modify cache through the console to cheat.

I foresee this thing called “SEE INSIDE”

Alex5002 wrote:

Bump because I'd love to have projects the ability to set cloud variables “for this user only” !
There should this limit : Each project cannot set more than ONE single variable for the same user. It would then have the name of “private cloud variable” or smth similar. You don't create them.
If this gets implemented, the user whose his account gets to store variables must have the ability to delete them from a menu in the account settings page. Like if you go to the save files management screen of a GameCube's BIOS UI, but without anything else than just deleting the save file.

sure, but cloud variables cost ST money (I assume the cost is the main reason their down all the time), and this would only make it worse.

CrazyCoder1247 wrote:

Alex5002 wrote:

Bump because I'd love to have projects the ability to set cloud variables “for this user only” !
There should this limit : Each project cannot set more than ONE single variable for the same user. It would then have the name of “private cloud variable” or smth similar. You don't create them.
If this gets implemented, the user whose his account gets to store variables must have the ability to delete them from a menu in the account settings page. Like if you go to the save files management screen of a GameCube's BIOS UI, but without anything else than just deleting the save file.

sure, but cloud variables cost ST money (I assume the cost is the main reason their down all the time), and this would only make it worse.

by this I mean scratcher-specific cloud vars

CrazyCoder1247 wrote:

CrazyCoder1247 wrote:

Alex5002 wrote:

Bump because I'd love to have projects the ability to set cloud variables “for this user only” !
There should this limit : Each project cannot set more than ONE single variable for the same user. It would then have the name of “private cloud variable” or smth similar. You don't create them.
If this gets implemented, the user whose his account gets to store variables must have the ability to delete them from a menu in the account settings page. Like if you go to the save files management screen of a GameCube's BIOS UI, but without anything else than just deleting the save file.

sure, but cloud variables cost ST money (I assume the cost is the main reason their down all the time), and this would only make it worse.

by this I mean scratcher-specific cloud vars

If ST and MIT manage to serve cloud vars for projects, they can for users as well ! Else they are not reopening cloud variables at all (that would be sad). If they want, they could add a limit of, idk, 10 user cloud vars per user, so if there is an 11th project that wants to create a user cloud var it would either fail or cause automatic deletion of the one with the oldest latest read/write date.

CrazyCoder1247 wrote:

jmdzti_0-0 wrote:

i foresee the possibility of being able to manually modify cache through the console to cheat.

I foresee this thing called “SEE INSIDE”

There would be a system that makes the variable unreadable and unwriteable directly, but requires to be read and written unsing the project that have set it. There will always the posibility to unset/delete it from account settings and the project that has set it.

CrazyCoder1247 wrote:

jmdzti_0-0 wrote:

i foresee the possibility of being able to manually modify cache through the console to cheat.

I foresee this thing called “SEE INSIDE”

Being in the editor already disables cloud access, so it will for user cloud vars too, of course except if the project is yours !

Alex5002 wrote:

m e g a s n i p

still tho cloud vars cost moolah whereas if they implement cache variables its free!!!