Discuss Scratch

bananamouse24
Scratcher
24 posts

Bring back User ID block!

julmik6478 wrote:

You can steal find this block in hacked blocks projects.
but currently, it only returns “undefined”
(user ID:: sensing)
cwkmichael25045
Scratcher
6 posts

Bring back User ID block!

han614698 wrote:

medians wrote:

han614698 wrote:

Since there's no way to get a username from a user ID, what would this accomplish?
This could be used for cloud or saving.
Also, the user id block was not the id of the user, it did sth different
https://en.scratch-wiki.info/wiki/User_ID_(block) (it was replaced by username)
Oh mb, I remember now.

Wouldn't it just be easier to encode their username which just remains the same every time they click the flag (AFAIK this doesn't?? and if it does, then this is just the same thing)

IDK actually. Could be a shorter system?
Hawaiiscratcher67
Scratcher
15 posts

Bring back User ID block!

han614698 wrote:

medians wrote:

han614698 wrote:

Since there's no way to get a username from a user ID, what would this accomplish?
This could be used for cloud or saving.
Also, the user id block was not the id of the user, it did sth different
https://en.scratch-wiki.info/wiki/User_ID_(block) (it was replaced by username)
Oh mb, I remember now.

Wouldn't it just be easier to encode their username which just remains the same every time they click the flag (AFAIK this doesn't?? and if it does, then this is just the same thing)
If you encode the username for each and every player, if the project gets popular then you won't be able to encode every single username.
IndestructableshadoW
Scratcher
16 posts

Bring back User ID block!

Although you can find it, old blocks don't work. For this block, “User ID”, it says nothing, and when plugged into other blocks, becomes “Undefined”.
TheCreatorOfUnTV
Scratcher
1000+ posts

Bring back User ID block!

It should use the User ID from the Scratch API instead.
DangerPuppy10
Scratcher
1000+ posts

Bring back User ID block!

Za-Chary wrote:

1.4 Social action reporter blocks
This block could be used, for example, to obtain the current number of loves of the project. However, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves. If a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal. Social actions are not intended to be a way to interact with a Scratch project.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.

(number of [loves v] :: sensing)


you could use this to report how many views a project has (if you have good coding skills), thus leading me to this rejection. I dont know if this rejection entirely related to the post, it's just something to think about.
medians
Scratcher
1000+ posts

Bring back User ID block!

DangerPuppy10 wrote:

you could use this to report how many views a project has (if you have good coding skills), thus leading me to this rejection. I dont know if this rejection entirely related to the post, it's just something to think about.
This has been opened for a while, and people who are logged out or are New Scratchers count towards the views.
Dragonmyflesh
Scratcher
500+ posts

Bring back User ID block!

Support.
TheCreatorOfUnTV
Scratcher
1000+ posts

Bring back User ID block!

medians wrote:

DangerPuppy10 wrote:

you could use this to report how many views a project has (if you have good coding skills), thus leading me to this rejection. I dont know if this rejection entirely related to the post, it's just something to think about.
This has been opened for a while, and people who are logged out or are New Scratchers count towards the views.
Someone could just use cloud variables to make sure that the user is a Scratcher, and restrict from there.
DangerPuppy10
Scratcher
1000+ posts

Bring back User ID block!

bump
Dragonmyflesh
Scratcher
500+ posts

Bring back User ID block!

Dragonmyflesh wrote:

Support.

That was a long time ago.
BigNate469
Scratcher
1000+ posts

Bring back User ID block!

Dragonmyflesh wrote:

Dragonmyflesh wrote:

Support.

That was a long time ago.
You still haven't said why.
DangerPuppy10
Scratcher
1000+ posts

Bring back User ID block!


This is kinda a dupe?
The topics should still be merged, because of the amount of discussion on this one.
lapisi
Scratcher
1000+ posts

Bring back User ID block!

DangerPuppy10 wrote:

(#653)

This is kinda a dupe?
The topics should still be merged, because of the amount of discussion on this one.
that other one's closed and there's literally no discussion on it
medians
Scratcher
1000+ posts

Bring back User ID block!

lapisi wrote:

DangerPuppy10 wrote:

(#653)

This is kinda a dupe?
The topics should still be merged, because of the amount of discussion on this one.
that other one's closed and there's literally no discussion on it
You can request for topics to be reopened, also that's why it's a merge.
DangerPuppy10
Scratcher
1000+ posts

Bring back User ID block!

lapisi wrote:

DangerPuppy10 wrote:

(#653)

This is kinda a dupe?
The topics should still be merged, because of the amount of discussion on this one.
that other one's closed and there's literally no discussion on it
I didn't know it was closed, I found another dupe though.

here

Last edited by DangerPuppy10 (Sept. 2, 2024 23:58:48)

medians
Scratcher
1000+ posts

Bring back User ID block!

Could also work like this
(user [id v]::sensing
(user [name v]::sensing)
Dragonmyflesh
Scratcher
500+ posts

Bring back User ID block!

BigNate469 wrote:

Dragonmyflesh wrote:

Dragonmyflesh wrote:

Support.

That was a long time ago.
You still haven't said why.

Forgot why.
medians
Scratcher
1000+ posts

Bring back User ID block!

Dragonmyflesh wrote:

Dragonmyflesh wrote:

Support.

That was a long time ago.
If July 2024 was a long time ago, I must be extremely old

TheCreatorOfUnTV wrote:

medians wrote:

DangerPuppy10 wrote:

you could use this to report how many views a project has (if you have good coding skills), thus leading me to this rejection. I dont know if this rejection entirely related to the post, it's just something to think about.
This has been opened for a while, and people who are logged out or are New Scratchers count towards the views.
Someone could just use cloud variables to make sure that the user is a Scratcher, and restrict from there.
Then that is already reportable xD if they are just locking people out for being a new Scratcher (unless the main project purpose of the project was cloud or something like that)

Last edited by medians (Sept. 3, 2024 20:57:13)

DangerPuppy10
Scratcher
1000+ posts

Bring back User ID block!

bump.

Powered by DjangoBB