These can detect what you're location, such as state or country
Like this:

(current [Country v])

are you sure it's a safe idea

set [user's city v] to (current [city v])
set [user's state/province v] to (current [state/province v])
set [user's country v] to (current [country v])
set [user's location v] to (join (join (join (join (user's city) [, ]) (user's state/province)) [, ]) (user's country))
say (join [u live in ] (user's location)
script that encodes string to cloud var: data (join (join (username) [: ]) (user's location)) ::custom
say [now I know where you live]

No support for reasons above.

Zro716 wrote:

are you sure it's a safe idea

set [user's city v] to (current [city v])
set [user's state/province v] to (current [state/province v])
set [user's country v] to (current [country v])
set [user's location v] to (join (join (join (join (user's city) [, ]) (user's state/province)) [, ]) (user's country))
say (join [u live in ] (user's location)
script that encodes string to cloud var: data (join (join (username) [: ]) (user's location)) ::custom
say [now I know where you live]

no support

ok this is a bad idea

they-might-be-cats wrote:

Zro716 wrote:

are you sure it's a safe idea

set [user's city v] to (current [city v])
set [user's state/province v] to (current [state/province v])
set [user's country v] to (current [country v])
set [user's location v] to (join (join (join (join (user's city) [, ]) (user's state/province)) [, ]) (user's country))
say (join [u live in ] (user's location)
script that encodes string to cloud var: data (join (join (username) [: ]) (user's location)) ::custom
say [now I know where you live]

no support

No support cuz you can put in CLOUD VARIABLE and find out ur city!!! Isn't country enuf?

No support, because the only uses I can see for this are doing creepy things that would make moderating a nightmare.

ohhh BAD IDEA

set [cloud variable v] to (join (username) (join (current [country v]) [is where he lives]
say [HAHAHAHAHAHA NOW YOUR COUNTRY? I WILL GO FOR YOU I KNOW YOUR COUNTRY HAHA

If it was just the country (not the city or county), I don't think it would be much of a safety issue.

But the other thing to think about is how useful would it be?

Paddle2See wrote:

If it was just the country (not the city or county), I don't think it would be much of a safety issue.

But the other thing to think about is how useful would it be?

statistics

if <(country of user :: sensing) = [United States]>
change [US users v] by (1)
end
//etc...

Or how about a block

(distance from city [New York v] to (username)::sensing)

That way, you have to triangulate their location.

I don't want Scratch projects tracking me.

Deleting google cookies is about enough for me. xP

Cyoce wrote:

Or how about a block

(distance from city [New York v] to (username)::sensing)

That way, you have to triangulate their location.

How would that be more useful than just a location block?

Support for a country block, more detail than that might be too sensitive.

One problem that arises is translation, since the output of a reporter can't be translated. So if I used the country block, I would get

(country :: sensing) // United Kingdom

but if I changed the language, it would still report the same:

(国家 :: sensing) // United Kingdom

which would cause problems for people coding in languages other than English.
(it could report ISO codes, or be a boolean with a dropdown for a specific country, but both of them have their disadvantages.

It would not be able to find the exact location. It will just find the country on your profile.

No support because

Zro716 wrote:

are you sure it's a safe idea

set [user's city v] to (current [city v])
set [user's state/province v] to (current [state/province v])
set [user's country v] to (current [country v])
set [user's location v] to (join (join (join (join (user's city) [, ]) (user's state/province)) [, ]) (user's country))
say (join [u live in ] (user's location)
script that encodes string to cloud var: data (join (join (username) [: ]) (user's location)) ::custom
say [now I know where you live]

I have an idea for this


As far as I am concerned, Scratch can probably make a longitude and a latitude block that doesn’t save into a variable.

(latitude)

(longitude)

(current country)

No support! Not useful. And the mere existence of such a block might drive certain scratchers away.

Though, i get why it might be useful, it is a danger as you should not give private info out. Also, it could be bypassed by using a certain software.

Why is everyone talking about the city here? The OP didn't even specify whether a city would be in the dropdown list; they only talked about the country and state/province/(it depends on the country).

stickfiregames wrote:

-snip-
One problem that arises is translation, since the output of a reporter can't be translated. So if I used the country block, I would get

(country :: sensing) // United Kingdom

but if I changed the language, it would still report the same:

(国家 :: sensing) // United Kingdom

which would cause problems for people coding in languages other than English.
(it could report ISO codes, or be a boolean with a dropdown for a specific country, but both of them have their disadvantages.

There's a “language” block in the Translate extension that can be placed in a dropdown in the “translate () to ()” block, but that wasn't there when stickfiregames' post was made (“:: extension” reporter is used, but Scratch 2.0 makes it look black):

(translate (country \(doesn't exist yet\) :: sensing) to (language :: extension) :: extension)

Also, it seems like the OP wanted the topic closed from the vague wording, but this topic is still open:

Jaker747 wrote:

ok this is a bad idea

I've created (by accident) a dupe, but you can read it, I've stated a few reasons why this would be useful. But if you're lazy:

The upsides are language settings and stuff,
the downsides are racism and special clubs or country exclusive projects.