This article or section needs additional citations for verification. Its information may not be accurate. Editors can help by adding references. (December 2013) |
Below is a list of misconceptions about Scratch. Oftentimes, people will misunderstand a concept about Scratch or misinterpret a feature's function. The following misconceptions are categorized by type.
Scratch Program
This section is in question as to whether it is useful or not. You can discuss whether you think it should be deleted or not on its talk page. (September 2020) Reason: Most are common sense or not notable |
The Scratch program has multiple misconceptions on scripting and other features. These misconceptions are found among the Scratch program.
Blocks
The if () then block does not repeatedly check a condition. If this was the case, it would not have a joiner on the bottom. In order for it to repeatedly check a condition, it must be within a forever loop, as in the following script:[1][2][3][4]
when green flag clicked forever if<. . . :: grey> then . . . end end
- Broadcasts are also received by clones, which can cause some coding problems. However, it is possible to use the "delete clone" block to prevent clones from receiving it.[5]
- The when () key pressed hat block is not broken because of its erratic behavior when compared to key () pressed?.[5]
- Boolean sensors passed into custom blocks cannot update the parameter's value while the custom block is running. Boolean sensors only pass in true or false.[5]
- The tempo blocks only change the duration of notes and not the imported sound.[6]
Workarounds
It is common to do the following as an alternative to the timer:[citation needed]
when gf clicked set [timer v] to [0] forever wait (1) seconds change [timer v] by (1)
It appears to be accurate to the actual change of time, but after each block is a very minuscule wait. Therefore, after the blocks waits the specified number of seconds, there is another wait (one frame) before the timer changes. In a short period of time, the change is not too drastic, but if the variable timer continues this loop for a long period of time, the ratio of difference compared to the actual (timer)
will be visible; just over 7% off by 100 seconds, and 62.3% off by 600 seconds.[7][clarify]
In order to reduce the delay, you must wait 0 seconds.[8] It will cause a pause of 1 frame (1/30 seconds). This allows it to be much more accurate, and loses less than 0.1 seconds in 100 seconds.
when gf clicked set [timer v] to [0] forever wait (0) secs change [timer v] by ((1) / (30))
Another common misconception is that
set x to () set y to ()
is the same as
go to x: () y:()
But it turns out that Scratch runs the first block, then the second, separately. If using a pen extension, it would not draw diagonal lines sensibly, instead, draw horizontal and vertical lines. If not using pen, it can be a workaround and is not a misconception.
Games
Many Scratchers tend to believe that Scratch is specifically designed for making games, but this is false. Although games can be made in Scratch, a large variety of project genres are creatable including art, animations, music and stories, or even some "tools" and "simulations". There can even be a miscellaneous project genre. Rather than one stating that Scratch is used to make games, it would be more accurate to state that Scratch is used to design web-based projects.[5]
Disappearing Text Bug
- Main article: Disappearing Text Bug
The Disappearing Text Bug was not introduced in Scratch 1.3. It was first encountered in 1.3, but it was also later reported by users using older versions (e.g. Scratch 1.0.1), thereby falsifying this myth.
Scratch Website
This is for misconceptions about the website.
Main Site
- The old 1.4 and 2.0 beta site are no longer accessible, the former of which was deleted and the latter was updated to become the 2.0 website, and eventually the current website.
- "Weekend" is the oldest existing project, even though its shared time is 15 years later than that of "Sandwhich[sic]". The shared time only reflects the most recent sharing; "Weekend" was first shared on 5 March 2007,[9] and earlier than the 21 other existing projects shared that day.
Forums
- The old 1.4 forum can still be previewed, as can other parts of the site. However, the previewer cannot jump between threads. (See the first misconception in the above list.)
- The Report button is not only useful for reporting inappropriate material. It has other uses, too. For instance, moving forum topics when they are not in the right one is done by reporting.
- Deleted posts and threads wind up in the Dustbin, rather than being literally deleted. This one is common among people unfamiliar with what Community Moderators and Scratch Team members do on Scratch.
- Blockspam is spam only if the script is long, nonsensical, and off-topic. Using the block plugin to display on-topic messages is not spam.[10][11][12]
Other Places on The Site
ScratchR is often confused with "Scratcher", "Scratch Team member", or even "Scratch Resources". [citation needed]
Scratchers
Kaj
- Main article: Kaj#Misconceptions, Impersonations, and Conspiracies
- It is unknown whether Kaj was female, as is commonly portrayed, though one contact with the Scratch Team used male terms.
- Kaj did not hack or steal any accounts, as is commonly alleged.
Gobo
Many people thought gobo was a regular user, fake/joke account, or was controlled by Gobo[citation needed], but it is actually real and controlled by the Scratch Team, despite the rank saying "Scratcher".[13]
gdpr0000001
- Main article: gdpr0000001
gdpr0000001 is commonly believed to be the first account created on Scratch due to its join date, but the first user was actually andresmh, who created the site.[14]
It is also commonly believed a test account,[15][16] even by a Scratch Team member,[17] however it is just as likely that the account belonged to a regular user who wanted their data deleted under the General Data Protection Regulation act.
ScratchCat
Alongside gdpr0000001, ScratchCat is also believed to be the first account created on Scratch that still exists[18], due to its join date being the same as andresmh. However, its ID is much greater than that of andresmh[19][20], indicating that it was likely created many years later.
Some users, usually New Scratchers, believe ScratchCat is the only account associated with the ST. This misconception may have originated from the account's name.[citation needed] However, this is not true, as there are several Scratch Team members with different accounts.[21] These users often try to contact the ST on ScratchCat's projects, however there is usually no reply from the ST.
Scratch 4.0
It is commonly believed that Scratch 4.0 will come out in 2025 due to the evenly spaced amount of time between the previous updates. However, the “evenly spaced” time between updates is just a coincidence. The possibly of a Scratch 4.0 was first mentioned in November 2024[22] with developing new features being a priority in 2025, but this does not guarantee that it will be released in 2025. What features it may contain are still unknown, and it is possible that depending on the amount of new features added it may simply be an update to 3.0 instead of 4.0.[23]
False Reporting
- Main article: What happens if a project is false reported?
A number of users believe that if a project is reported by a certain number of users, whether or not something was actually wrong with it, this will lead to the creator being permanently banned or banned for a significant period of time.[24][25][26] However, all reports are reviewed by the Scratch Team, and if a project is taken down and the creator banned because a certain number of people reported the project, these effects only last until the Scratch Team reviews the reports, after which they will remove the ban and re-share the project if there was nothing wrong with it.[27] Additionally, intentionally reporting something when there is nothing wrong with it is a violation of the Community Guidelines and will result in consequences.[28]
Changing Usernames
It is commonly believed that it is impossible to a username to be changed through any means. However, on very rare occasions (such as if the username has private information, inappropriate content, or causes gender dysphoria), the Scratch Team has allowed username changes. [29]
References
- ↑ post:12106
- ↑ post:2166518
- ↑ post:3161451
- ↑ post:3465928
- ↑ a b c d topic:67468
- ↑ topic:77102
- ↑ projects:10941655
- ↑ projects:114798177
- ↑ https://api.scratch.mit.edu/projects/104/
- ↑ Za-Chary. (13/06/2020). "Small uses of scripts is okay for us — but long and laggy scripts in a place where it doesn't belong might not be." post:4123141
- ↑ Paddle2See. (15/06/2020). "If you find that somebody has put a bunch of blocks in their post that do not contribute to the conversation, that is off-topic or spamming... However, if they are using the blocks as a way to format what they are saying, that is not blockspam and should not be reported." post:4127402
- ↑ Za-Chary. (07/05/2020). "...'blockspam' is okay if the scripts are short and are related to the topic at hand." post:3993497
- ↑ users:Paddle2See/#comments-16325124[dead link]
- ↑ "
2007-03-05T10:41:06.000Z
" https://api.scratch.mit.edu/users/andresmh/ - ↑ post:4302389
- ↑ post:3835303
- ↑ users:Za-Chary/#comments-95466725[dead link]
- ↑ topic:520601
- ↑
{"id":139
https://api.scratch.mit.edu/users/andresmh/ - ↑ "
{"id":15883188
" https://api.scratch.mit.edu/users/ScratchCat/ - ↑ scratch:credits
- ↑ projects:1090906767
- ↑ cheddargirl. (14/11/2024). "It's not really official 4.0 work at this point. It's just an anticipated number change due to potential scope of project. But if ends up being a new feature built on top of 3.0 and not a huge change to 3.0 entirely, then it's still part of the 3.0 family. " projects:/287304470/#comments-434521453
- ↑ topic:141100
- ↑ topic:408356
- ↑ topic:450880
- ↑ post:4670186
- ↑ post:2732908
- ↑ Sliverus. (05/06/23). "But in some cases, such as if it contains personal information, inappropriate content, or it does not identify with your current gender, you may use Contact Us and ask for it to be changed.topic:682791"