So, you have to be ranked as a Scratcher to use cloud variables. In my opinion, though, this is unfair and leaves New Scratchers out. Pretend you can't play the MMO project on trending at school because you are a New Scratcher on your account. (Yes, I know TurboWarp can bypass this, but that doesn't count.)

Here's how it should actually work:

• Logged out users and the Offline Editor can't use cloud variables. (This already exists)
  
• New Scratchers have a limit to the number of cloud changes they can make per day. (Around 500 cloud variable changes per day.) If this limit is reached, Cloud Data shuts down for the NSer.
  
• New Scratchers can only create 1 cloud variable per project.
  

I know this might break a lot of projects, but this limit is anti-spam while letting New Scratchers use these variables.

What do you think?

I do agree with this. Some new scratchers can’t figure out how to get scratcher status ( though they will get it eventually ), if they can’t find the forums. I feel that it’s unfair for them, and I support letting them use some cloud variables.

Hmm, interesting. I think this might work, better than what I proposed a few days ago.

For anyone wondering, this does not count as a duplicate of my topic (the solutions for this issue are significantly different).

Bump

New Scratchers have a limit to the number of cloud changes they can make per day. (Around 500 cloud variable changes per day.) If this limit is reached, Cloud Data shuts down for the New Scratcher

I feel that the data should be counted in minutes, not in cloud changes, maybe 15 minutes a day.
Otherwise, i see no problem with it.

The_Blue_J wrote:

(#5)
I feel that the data should be counted in minutes, not in cloud changes, maybe 15 minutes a day.
Otherwise, i see no problem with it.

I was actually thinking of making it work like that but spammers could still overload the servers with a lot of cloud changes (DDoS attack?)

Dont most multiplayer projects update like… really fast? you could easily use up 500 changes and then it's just the same issue.
also doesn't solve the issue of spamming the servers (and other things, like hacking) since all you have to do is make a new account. It's only about 2 weeks and after that you'll never have to deal with it.

doggy_boi1 wrote:

Dont most multiplayer projects update like… really fast? you could easily use up 500 changes and then it's just the same issue.
also doesn't solve the issue of spamming the servers (and other things, like hacking) since all you have to do is make a new account. It's only about 2 weeks and after that you'll never have to deal with it.

You can only change cloud vars 1/10th of a second, so at most you can perform 10 changes per second. So in a little less than a minute 500 changes would be used up on, say, any multiplayer platformer.

A-MARIO-PLAYER wrote:

• New Scratchers have a limit to the number of cloud changes they can make per day. (Around 500 cloud variable changes per day.) If this limit is reached, Cloud Data shuts down for the NSer.

This would make it a lot more difficult to tell New Scratchers why they can't use the cloud variables in the project's descriptions, and Bugs and Glitches would get spammed with “cloud variables not working after a little while” messages.

Plus, if cloud platformers make 5 variable changes a second. If you do the math (5 changes per second x 60 seconds in a minute = 300 changes in a minute), it turns out to be less that 2 minutes of cloud platformer time.
I think I got the math right.

ilovestories wrote:

(#9)
Plus, if cloud platformers make 5 variable changes a second. If you do the math (5 changes per second x 60 seconds in a minute = 300 changes in a minute), it turns out to be less that 2 minutes of cloud platformer time.

Well, how about 250 changes per minute? Is that better?

A-MARIO-PLAYER wrote:

ilovestories wrote:

(#9)
Plus, if cloud platformers make 5 variable changes a second. If you do the math (5 changes per second x 60 seconds in a minute = 300 changes in a minute), it turns out to be less that 2 minutes of cloud platformer time.

Well, how about 250 changes per minute? Is that better?

That's still less then three hundred. At that point you may as well just be suggesting that they use cloud.

also doesn't solve the issue of spamming the servers (and other things, like hacking) since all you have to do is make a new account. It's only about 2 weeks and after that you'll never have to deal with it.

This would allow people to easily break and even post innapropriate things onto cloud based projects via API and alt accounts.

(Hmm… looks like this was removed)

PaperMarioFan2022 wrote:

yadayadayadagoodbye wrote:

This would allow people to easily break and even post innapropriate things onto cloud based projects via API and alt accounts.

That's why the Report button exist

The entire point of the new scratcher status is to prevent bad things from happening in the first place. Evidently, something happened (or could've happened) that got these restrictions placed. You can still spam and you can still do bad things. If everything that broke the TOS immediately got reported and nobody ever saw it, then we wouldn't have filters and anti spam timers either.

PaperMarioFan2022 wrote:

yadayadayadagoodbye wrote:

This would allow people to easily break and even post innapropriate things onto cloud based projects via API and alt accounts.

That's why the Report button exist. And the OP said that:

New Scratchers can only create 1 variable per project.

You realize im talking about API abuse, which the report button is useless against and requires using contact us to solve?

yadayadagoodbye wrote:

You realize I'm talking about API abuse, which the report button is useless against and requires contact us to solve?

I do believe I realized that, but entirely missed the point. Sorry to confuse you if I did.

But I have to agree, this is a little unfair for New Scratchers tbh, so it is what it is.

yadayadayadagoodbye wrote:

This would allow people to easily break and even post innapropriate things onto cloud based projects via API and alt accounts.

Then don't let New Scratchers use cloud data in other people's projects, something I suggested in a topic that is very similar to this one (but had other flaws so I closed it). That would prevent API abuse altogether, because they wouldn't have a way to access the cloud data API outside of their own projects.

+9999999999999

Bump

MillionOfficial wrote:

+9999999999999

Please keep the discussion constructive, and explain why you support the suggestion.

how is this related

Wetwu262 wrote: