simulate username ():: sensing // Makes the username block return the value entered.

stop username simulation:: sensing // Returns the username block to the username of whoever is on the project.

Support:
michaeljackson1365

Semi-support. This can be a really useful tool for doing something specific to a specific user. However, what if a bad user uses this to do more bad stuff like prohibiting good users from viewing their project?

michaeljackson1365 wrote:

Semi-support. This can be a really useful tool for doing something specific to a specific user. However, what if a bad user uses this to do more bad stuff like prohibiting good users from viewing their project?

I have a way to solve that. A new way to report a project for abusing the username/simulate username block would solve your problem.

michaeljackson1365 wrote:

Semi-support. This can be a really useful tool for doing something specific to a specific user. However, what if a bad user uses this to do more bad stuff like prohibiting good users from viewing their project?

I mean, you can already do that with the existing username block, and has been done before (it's already disallowed, however).

support, it seems useful if you want a custom name for a player (or a set nickname) however variables can be used as a workaround.

trolley_explodes wrote:

-snip-

Or just use a variable and a place to enter your name

ask [What name would you like to be called by?] and wait
set [Username v] to (answer)

Why would this be useful? This is literally just a variable.

cherry_cola_lover wrote:

trolley_explodes wrote:

-snip-

Or just use a variable and a place to enter your name

ask [What name would you like to be called by?] and wait
set [Username v] to (answer)

This seems like a much simpler approach without having to introduce two new blocks.