banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

Za-Chary wrote:

I guess I don't know if it's objectively allowed or not, but I really don't see the point in changing cloud variables on another user's project. The main problem is precisely the harassment you would get from it — and aside from that, I don't know what benefit you get from this. Cloud variables are not intended to be modified in this way, so it's understandable that changing them in a manner which is not what the project creator intended could cause some Scratchers to be upset.

You should report any comments which take it too far — name-calling, claiming that they're reporting you, etc. — but I would also suggest that you stop modifying cloud variables on other Scratchers' projects, unless of course you are doing it honestly by playing the project as the creator intended.

colinmacc wrote:

It is absolutely not fine. Cheating by using external tools to modify cloud variables on other peoples projects is reportable to the scratch team and can result in a ban.

Assuming this is true, then this is the answer. (I wouldn't be surprised if the Scratch Team really is taking action against this. I've never seen action taken myself — but that's probably just because I haven't been looking too closely. I think issues with cloud variables have gotten more significant after I left the Scratch Team.)

It *is* getting worse, the more people are spreading the knowledge around. Griffpatch's projects have had some pretty high profile interference with innappropriate words inserted into score tables, etc. But pretty much anyone who gets a popular project is a potential target now.

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

Spentine wrote:

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch. It's like breaking someone's sandcastle just because there's no sandcastle laws! Brr, rude

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch.

Collin_The_Newmaker wrote:

it's not restricted on Scratch.

Thanks for letting me know!

I… feel kinda… offended

colinmacc wrote:

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

that at least i know, but the user in question likely was not doing it persistently, or at least they since stopped

Banana

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I'm not sure 1 or 2 days count as persistent, does it?

Also If I posted this twice I'm sorry

edit: i posted this twice oops

Collin_The_Newmaker wrote:

Spentine wrote:

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch. It's like breaking someone's sandcastle just because there's no sandcastle laws! Brr, rude

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch.

Collin_The_Newmaker wrote:

it's not restricted on Scratch.

Thanks for letting me know!

I… feel kinda… offended

This is Scratch, not Twitter…

banana439monkey wrote:

colinmacc wrote:

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

that at least i know, but the user in question likely was not doing it persistently, or at least they since stopped

Banana

The user in question went through about 6 of my projects maliciously destroying the high score tables in each. Luckily I've learnt to keep backups.

colinmacc wrote:

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

I know, I was just wondering what the point of showing the image was if it doesn't apply to me.

Spentine wrote:

Collin_The_Newmaker wrote:

Spentine wrote:

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch. It's like breaking someone's sandcastle just because there's no sandcastle laws! Brr, rude

Collin_The_Newmaker wrote:

-snip-
LOL, it's just rude to go and break a multiplayer game's data just because it's not restricted on Scratch.

Collin_The_Newmaker wrote:

it's not restricted on Scratch.

Thanks for letting me know!

I… feel kinda… offended

This is Scratch, not Twitter…

Thing you're doing rn are at least a more or less everyday on twitter, unlike on a kids website

colinmacc wrote:

The user in question went through about 6 of my projects maliciously destroying the high score tables in each. Luckily I've learnt to keep backups.

yes, this was one project and likely not malicious

Banana

Spentine wrote:

colinmacc wrote:

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

I know, I was just wondering what the point of showing the image was if it doesn't apply to me.

People were asking me to cite my sources!

Za-Chary wrote:

It is still understandable that some Scratchers are upset with you changing the cloud variable back to 0 — the (honest) high score prior to you doing that probably was not 0 (nor 10000), so if Scratchers were interested in seeing the “true” high score, then they can no longer do that.

Yeah, but before I hacked someone else advertised their discord server in the cloud variable logs, so they've already ruined the true value, and even before that, someone else was modifying it too!

I do understand that it would still be sort of morally wrong whether or not people have modified it before or not.

colinmacc wrote:

Spentine wrote:

colinmacc wrote:

Spentine wrote:

banana439monkey wrote:

colinmacc wrote:

yes, persistently

Banana

I only did it for 1 or 2 days, Not sure if it counts as persistently.

The report wasn't about you.

I know, I was just wondering what the point of showing the image was if it doesn't apply to me.

People were asking me to cite my sources!

Oh, they were asking for the sources to that report? I guess it makes sense.

Spentine wrote:

Za-Chary wrote:

It is still understandable that some Scratchers are upset with you changing the cloud variable back to 0 — the (honest) high score prior to you doing that probably was not 0 (nor 10000), so if Scratchers were interested in seeing the “true” high score, then they can no longer do that.

Yeah, but before I hacked someone else advertised their discord server in the cloud variable logs, so they've already ruined the true value, and even before that, someone else was modifying it too!

I do understand that it would still be sort of morally wrong whether or not people have modified it before or not.

Well, you joined this “variable riot”, so it was you too breaking the game.

Collin_The_Newmaker wrote:

Spentine wrote:

Za-Chary wrote:

It is still understandable that some Scratchers are upset with you changing the cloud variable back to 0 — the (honest) high score prior to you doing that probably was not 0 (nor 10000), so if Scratchers were interested in seeing the “true” high score, then they can no longer do that.

Yeah, but before I hacked someone else advertised their discord server in the cloud variable logs, so they've already ruined the true value, and even before that, someone else was modifying it too!

I do understand that it would still be sort of morally wrong whether or not people have modified it before or not.

Well, you joined this “variable riot”, so it was you too breaking the game.

It wasn't a variable riot, but I was also breaking the game.

Spentine wrote:

Za-Chary wrote:

It is still understandable that some Scratchers are upset with you changing the cloud variable back to 0 — the (honest) high score prior to you doing that probably was not 0 (nor 10000), so if Scratchers were interested in seeing the “true” high score, then they can no longer do that.

Yeah, but before I hacked someone else advertised their discord server in the cloud variable logs, so they've already ruined the true value, and even before that, someone else was modifying it too!

I do understand that it would still be sort of morally wrong whether or not people have modified it before or not.

That's exactly the reason why it shouldn't be allowed.

Spentine wrote:

Collin_The_Newmaker wrote:

Spentine wrote:

Za-Chary wrote:

It is still understandable that some Scratchers are upset with you changing the cloud variable back to 0 — the (honest) high score prior to you doing that probably was not 0 (nor 10000), so if Scratchers were interested in seeing the “true” high score, then they can no longer do that.

Yeah, but before I hacked someone else advertised their discord server in the cloud variable logs, so they've already ruined the true value, and even before that, someone else was modifying it too!

I do understand that it would still be sort of morally wrong whether or not people have modified it before or not.

Well, you joined this “variable riot”, so it was you too breaking the game.

It wasn't a variable riot, but I was also breaking the game.

If to find fault with words and turn everything inside out, like I've just seen in this topic, i can say:
Judging on the information spoken by people in this topic, I assume that many people who knew what they were doing - hacking - broke many online games using Scratch's API vulnerability. Imo, this is dis-res-pect-ful to other people, that is breaking the community guidelines on treating other members respectively. That is being ok to report.

Spentine wrote:

colinmacc wrote:

Spentine wrote:

Is it fine to modify cloud variables on another project objectively? Talking about a rule from the ToS, does it exist? After I modified the variable people kept coming to my profile to report me and to comment “stop hacking”, and then one person spammed each of my projects with a message telling me to stop in 24 hours… I reported each of those messages from that single user for breaking rules 3.1, 3.2, and 3.5.4.

Anyways, is it objectively ok to modify cloud variables to whatever? And do the people who come to my profile to report me have a valid claim?

I got tired of people bothering me, so I set it back to 0, but people still kept poking at me telling me to stop hacking.

It is absolutely not fine. Cheating by using external tools to modify cloud variables on other peoples projects is reportable to the scratch team and can result in a ban. Hopefully this can be stamped out because it's spoiling a lot of projects and is really annoying.

I appreciate your feedback, but can you quote your source? I was asking "Is it fine to modify cloud variables on another project objectively?", keyword: objectively.

Scratch ToS you can check out the link to Scratch's Terms of Use to see if I'm breaking any of the clauses. 3.5 is out because I'm not disrupting the service, interfering with anyone's use, or gaining unauthorized access, otherwise, Scratch would have disabled the API.

There's no law against bullying kids, so I'm going to a daycare to bully some 5 year olds

Why were you even modifying cloud variables in Griffpatch's project in the first place? He didn't give permission, and it certainly isn't your project

It’s disrespectful and unfair to everyone who will play, AND the creator, and now it’s zero and wasn’t that before, so the person who set that progress is lost