Discuss Scratch

scratchastroLOL
Scratcher
1000+ posts

Variable Positioning

cooldude-222 wrote:

I support the
move [my variable v] to X: () Y: () ::variables

and why is that?
ScratchinWays
Scratcher
1 post

Variable Positioning

Although I'd totally love this feature, Scratch is supposed to be simple and easy. I'm sure that this is pretty easy to understand, but I'm just not sure that the scratch team would implement a block just to position a variable.
AmberdroptheWarrior
Scratcher
100+ posts

Variable Positioning

Full support!

ScratchinWays wrote:

Although I'd totally love this feature, Scratch is supposed to be simple and easy. I'm sure that this is pretty easy to understand, but I'm just not sure that the scratch team would implement a block just to position a variable.
Yes, but they also have some blocks that are too complicated for some people to understand right now. For example, this block:
 ([e^ v] of (9)) 
I think a variable postion block would be easy to understand. Positioning variables be would very helpful for games with boss fights you can move around in, to show which variable is your health or other and which variable is the opponents health or other.
Fernie_The_Great0512
Scratcher
6 posts

Variable Positioning

Just drag it, and then right click for the kind
EatNYeet
Scratcher
500+ posts

Variable Positioning

Fernie_The_Great0512 wrote:

Just drag it, and then right click for the kind
That's not a workaround. What you're saying is that instead of being able to do this:

if <(moveID) = (1)> then 
move [display v] to x:(0) y:(100) :: variables
display [display v] as [normal readout v] :: variables
else
move [display v] to x:(0) y:(0) :: variables
display [display v] as [large readout v] :: variables
end

Anyone playing the game has to manually see inside, drag the variable themself, and right click to change the readout for the game to show the variable in its intended position and readout.

That being said, major support, but all of the following should become blocks:

send [my variable v] to x:() y:() :: variables

glide [my variable v] to x:() y:() for:() secs :: variables

send [my variable v] to [sprite v] :: variables

glide [my variable v] to [sprite v] :: variables

change x of [my variable v] by () :: variables

change y of [my variable v] by () :: variables

set readout of [my variable v] to [large readout v] :: variables

(x of [my variable v] :: variables reporter)
(y of [my variable v] :: variables reporter)

Last edited by EatNYeet (May 9, 2021 17:42:49)

A-KouZ1
Scratcher
100+ posts

Variable Positioning

one might make this as extention
EatNYeet
Scratcher
500+ posts

Variable Positioning

bump
godved_66
Scratcher
1 post

Variable Positioning

I like the idea of a go to(x,y) block for a variable especially if you want to put a health bar over a boss or enemy or something like that
SDFTDusername
Scratcher
42 posts

Variable Positioning

bump
ElijahSlater
Scratcher
1 post

Variable Positioning

yes
amogus1123
Scratcher
500+ posts

Variable Positioning

ElijahSlater wrote:

yes
so you support it?


necroposting doesn't exist in suggestions? darn

Last edited by amogus1123 (Oct. 23, 2023 09:06:16)

lfg30700
Scratcher
1000+ posts

Variable Positioning

Bump

Powered by DjangoBB