Bring back User ID block!

Chippy2Test

hotcrystal wrote:
medians wrote:
Could also work like this
(user [id v]::sensing
(user [name v]::sensing)
“user name” with a space just feels… weird.

I just don't agree. It is an objectively correct way to write it. it is the user's name.

MagentaDude1359

This would be awesome for cloud games. I support.

Emeraldore12

medians wrote:
Could also work like this
(user [id v]::sensing
(user [name v]::sensing)

I feel like the “user ID” may confuse new scratchers.

medians

Emeraldore12 wrote:
medians wrote:
Could also work like this
(user [id v]::sensing
(user [name v]::sensing)
I feel like the “user ID” may confuse new scratchers.

This suggestion is for “user ID” though.. soo

Last edited by medians (April 30, 2025 12:54:10)

kyavanyaisback

Support because cloud lists are a rejected feature and without them we can't make a workaround for this block

medians

tagrim123 wrote:
Can’t someone discriminate a specific group of people like this?
when green flag clicked
if <(user id ::sensing reporter)  = [insert person you don’t want to view your project here]> then
say [>:(]
else
…

1. It's hard to know what user id the person would have unless they say what user id they have
2. You can already report this, and this can be done with the username block already.
3. User ID might not be the same for the same user on different projects. The function of the block is:
“Each user had a different ID according to when they viewed the project (the first viewer was 1, the second was 2, and so forth). Users who were not logged in to an account were assigned the user ID 0. A user's ID remained constant for the same project and would not change.”

Last edited by medians (July 3, 2025 14:30:43)

portalpower

bump

VerySmartDummy

support

CodeComet6161

medians wrote:
tagrim123 wrote:
Can’t someone discriminate a specific group of people like this?
when green flag clicked
if <(user id ::sensing reporter)  = [insert person you don’t want to view your project here]> then
say [>:(]
else
…
1. It's hard to know what user id the person would have unless they say what user id they have.
2. You can already report this, and this can be done with the username block already.
3. User ID might not be the same for the same user on different projects. The function of the block is:
“Each user had a different ID according to when they viewed the project (the first viewer was 1, the second was 2, and so forth). Users who were not logged in to an account were assigned the user ID 0. A user's ID remained constant for the same project and would not change.”

4. You can just remove the code.

Dracandros

TheUniversalWorld1 wrote:
Do you mean this block?
(user id)
I am not sure.

its acctually

(user id::sensing)

Dracandros

medians wrote:
Emeraldore12 wrote:
medians wrote:
Could also work like this
(user [id v]::sensing
(user [name v]::sensing)
I feel like the “user ID” may confuse new scratchers.
This suggestion is for “user ID” though.. soo

i dont know what user id's are but im not new

Nibot242

I support this.

One instance user ids could be used for is cloud save data. Encrypting the username into numbers can be complicated and takes up more space then a user id. If the username is not needed, but a way to tell users data apart from other users is needed, user ids could work perfectly.

Discuss Scratch