These variables are invisible no matter what you do, except

say []

blocks, or similar ones reports to user.

What are you suggesting?

I think he’s suggesting variables hidden from someone else
and its rejected (it violates remix policy)

This definitelly violates being able to remix in a way or another, no support

Rejected because remixing and downloading would be hard and this would go against that.
Also relatable already:

The purpose of this idea is getting cheaters away, for example; if you made a number guessing game, and user run out of tries; character can say “Number was 4”, this feature idea blocks wieving variables without code says it.

semisupport. would work good for clicker games and/or find the ____ games.

barisbogdan wrote:

The purpose of this idea is getting cheaters away, for example; if you made a number guessing game, and user run out of tries; character can say “Number was 4”, this feature idea blocks wieving variables without code says it.

That’s the entire point of the remix policy, to make sure stuff like this doesn’t happen

Umm… No support… Keeping cheaters away, but when you can use say then people will just put the variable into the say block. That's not that hard to do and as it would be a public feature, people would know it anyway. Also ,this makes debugging and remixing a lot les practical and could somewhat prevent people from remixing.

barisbogdan wrote:

The purpose of this idea is getting cheaters away, for example; if you made a number guessing game, and user run out of tries; character can say “Number was 4”, this feature idea blocks wieving variables without code says it.

Just do this then:

If you mean hiding it, even when stopped, then that wouldn't go with the remixing policy.
And they can just do this:

If the sprite is hidden: