Support, but what happened to sport variables?

(⚽️ savedata)

when gf clicked
repeat until <@greenFlag destroyed> {
crush downwards :: cap grey
when gf clicked
}@loopArrow :: control

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

(+['-']⋯)

((\(o)_(o\)))

move (if <> then {} ::control stack) steps

when times green flag clicked > (10) ::hat events

try {} except ( v) {} ::control

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

Not necroposting, but blockspam: https://en.scratch-wiki.info/wiki/Necropost

supernavoAlt wrote:

Support ~snip~

Please state why you support.

AHypnoman wrote:

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

Not necroposting, but blockspam: https://en.scratch-wiki.info/wiki/Necropost

supernavoAlt wrote:

Support ~snip~

Please state why you support.

not blockspam either, as they are asking about something RELATED to the topic. Sprots variables was a similar suggestion to this, if I remember correctly

atmost this is offtopic (which makes it a necropost lol)

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

necroposting does not exist on the suggestions forum (:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

What are ‘sport variables’?

-TheEmptyVoidOfSpace wrote:

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

necroposting does not exist on the suggestions forum (:

Sorry… Their post seemed off-topic, and also like it belonged in QaS, so that's why I said necropost.

(+['-']⋯)

((\(o)_(o\)))

move (if <> then {} ::control stack) steps

when times green flag clicked > (10) ::hat events

try {} except ( v) {} ::control

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

That wasn’t a necropost.. or a blockspam..

MyScratchedAccount wrote:

(#400)
Also, what if multiple people use it and there is swear words In there or if you switch browsers? Is it IP based

No, it is not IP based. This suggestion will literally tell the browser some numbers and say to save them for later (cache them). When the Scratcher switches to another computer, the progress won't be there because it's physically on that one computer. If there are bad words, the project will have to make them In the first place which is against the rules (and probably won't happen).

AHypnoman wrote:

Minecraft_Master3964 wrote:

supernavoAlt wrote:

Support, but what happened to sport variables?

(⚽️ savedata)

Please don't necropost. Necroposting can be when you post off-topic stuff. Create a new topic.

Not necroposting, but blockspam: https://en.scratch-wiki.info/wiki/Necropost

Not block spamming nor necroposting as long as it is constructive, I think the sport variables were connected to the topic, please correct me if not.

Support
This would be fantastic to not have to use codes to put in a document!

Support because I want to be able to make projects that use this feature.

Anyways, this IS SAFE because only you can access the newly created information put into the “cached” variables. Also, if it came with bad information, report the project. This feature is IMPOSSIBLE to hack if nobody hacked your computer because this only exists on YOUR computer.

crabraveprogrammer wrote:

Developing wise, how would the scratch team do this?
They would have to use cookies, but there are some huge disadvantages of cookies.
1. That would take up a lot of space on the users computer. There would have to be a new cookie for every project the user opens.
2. Cookies are very easy to hack. I personally know JavaScript, and it is very easy to hack a cookie by sticking JS in the console window.

For #1, there will only be one cookie created once for each “cached” variable. For #2, the

set [ v] to []

block could also be used.

Scratchifier wrote:

epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

The cookie variables are NOT bad because they are only just simple data.

thirdlion wrote:

epninja wrote:

Scratchifier wrote:

epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

You've got the wrong idea. They will not be tied to your account They seriously won't contain anything that is worth hacking and nothing that can be used to attack others. If you could hack someone with the word “Chair”, then sure, hackers can use them to hack people, but you can't.

i think it is a good idea but it could maybe give private info away love it though you should get this idea out there!

It is NOT able to give away information on its own because it is ONLY able to exist on your computer.

54387a wrote:

crabraveprogrammer wrote:

Developing wise, how would the scratch team do this?
They would have to use cookies, but there are some huge disadvantages of cookies.
1. That would take up a lot of space on the users computer. There would have to be a new cookie for every project the user opens.
2. Cookies are very easy to hack. I personally know JavaScript, and it is very easy to hack a cookie by sticking JS in the console window.

For #1, there will only be one cookie created once fore each “cached” variable. For #2, the

set [ v] to []

block could also be used.

for #1:
Yet if I, for example, open 50 projects with cached variables, thats still 50 extra cookies
for #2:
That doesn't help with the fact that you can easily manipulate cookies to give you what you want

54387a wrote:

snip-
The cookie variables are NOT bad because they are only just simple data.

That doesn't stop me from taking up your computer's memory, now imagine if I store hundreds or even thousands of cached variables on your computer? and even if there is a limit on how much variables I can have (I believe you've stated its 1), I can still add a whole lotta data to it, theres literally a minecraft hack which freezes other people's games for a few seconds by sending characters with extremely high unicode serials (and its only a few hundred characters, the hack doesn't even spam)



Im not saying I do not support this, I very much do, if anyone understands the pain of savecodes, I do (not me spending over 30 hours trying to do savecodes back in 2020), however, security risks should be adressed

I couldn't use this as my browser is set to clear cookies and cache on exit.

This suggestion is similar but would store data in a user's account.

wow

define among us
say [How do i create among us with HITBOXES TASKS ONLINE, EVERYTHINGGGGGGG!]

SAVVYSCLUTTER wrote:

I couldn't use this as my browser is set to clear cookies and cache on exit.

This suggestion is similar but would store data in a user's account.

The difference would be where the info is stored. Storing in browser would allow for more storage space and freedom in exchange for the lack of safety and the issue of clearing cookies, meanwhile, storing on the scratch servers would get rid of the issue of manipulating cookies and clearing them, HOWEVER, it will most definitly introduce a very limiting size limit to the variables

blablablahello wrote:

SAVVYSCLUTTER wrote:

I couldn't use this as my browser is set to clear cookies and cache on exit.

This suggestion is similar but would store data in a user's account.

The difference would be where the info is stored. Storing in browser would allow for more storage space and freedom in exchange for the lack of safety and the issue of clearing cookies, meanwhile, storing on the scratch servers would get rid of the issue of manipulating cookies and clearing them, HOWEVER, it will most definitly introduce a very limiting size limit to the variables

This topic is 7 years old, how come we havent gotten a st response for this (please correct me if there is a st post about this)

Why would there be a size limit (that anyone could easily get to)? Browser cookies can easily be dozens of megabytes and a save code doesnt take much more than 200 bytes so a cookie would easily be able to fit many save codes even if they are all uncompiled?