a [point towards x( ) y( ) block

MTM828

Bruh, saying this can be programmed is like saying:

set [varName v] to [0]
Isn't necessary, you can do: :: operators
change [varName v] by ((varname) * [-1]
Or vice versa: :: operators
Set [varName v] to ((varName) + (1))

Support, speeds up coding GREATLY.

Last edited by MTM828 (Sept. 8, 2020 12:43:23)

4mat

Can this be closed please? It's rejected.

fdreerf

4mat wrote:
Can this be closed please? It's rejected.

citation needed

4mat

fdreerf wrote:
4mat wrote:
Can this be closed please? It's rejected.
citation needed

Ah I could swear it is rejected but I probably confused TOLORS with TWTFSB (bruh that's a neat abbreviation).

Last edited by 4mat (Sept. 8, 2020 13:29:20)

Paddle2See

4mat wrote:
Can this be closed please? It's rejected.

Not rejected that I am aware of.

donotforgetmycode

4mat wrote:
fdreerf wrote:
4mat wrote:
Can this be closed please? It's rejected.
citation needed
Ah I could swear it is rejected but I probably confused TOLORS with TWTFSB (bruh that's a neat abbreviation).

what's TWTFSB?

a_guy_who_made_games

You can use this script.

define get direction (x) (y)
set [direction v] to ([atan v] of ((x) / (x)))::green
if <(y) < (0)> then
change [direction v] by (180)
end

4mat

donotforgetmycode wrote:
TWTFSB?

The Workarounds To Frequently Suggested Blocks

donotforgetmycode

4mat wrote:
The Workarounds To Frequently Suggested Blocks

thanks

p-p-p-p-p-p-p-p-p-p-

TheBus_2 wrote:
Please add these ideas, Scrachteam.
<color [#ceb767] is touching [sprite1 v] ?>
when [my variable v] > (10)
when [size v] > (10)
Color variables?
set [color v] to [#72c08b]

set pen outline to (10)

repeat () or until <>

end
That is supposed to be like the forever block.

Please don't blockspam. This is off topic and you can suggest each one in a new forum. These are really easy to replace. If you need help to find the workaround, let me know and I can provide assistance! Thank you and scratch on!

sportfan999

turkey3 wrote:
You can use trigonometry to replicate this: so if I want to point toward x:40 y:60
point in direction (([atan] of ((((60) - (y position)) / ((40) - (x position))))) - (90))
Sorry if that's a bit off.

Going to make it with real Scratchblocks:

point in direction ([atan v] of ((((60)-(y position))/((40)-(x position)))-(90))

gosoccerboy5

Yes, but no one wants to do that lol

I have a slight improvement on this topic.

Zoomer_X

when this event happened :: events hat
set [deltax v] to ((WantedX) - (x position))
set [deltay v] to ((WantedY) - (y position))
if <not <(deltay) = [0]>> then 

  if <(deltay) > (0)> then
point in direction ([atan v] of ((deltax)/(deltay))
else
point in direction ([atan v] of (((deltax)/(deltay)) + (180))) 
end
else
if ((deltax) > (0)) then
point in direction (90)
else
point in direction (-90)

end

(I copied from the Workarounds to Frequently Asked Suggestions)

Last edited by Zoomer_X (Oct. 26, 2020 17:39:59)

portalpower

not so easy workaround

point in direction  (([atan v] of (((x) - (x position)) / ((y) - (y position)))) + ((180) * < ((y) - (y position)) < (0) >))

ScratchCatHELLO

You can either use one of the workarounds or add an empty sprite, put that sprite where you want to point, and make the sprite that would have the point to block in it point to the empty sprite.

Genius398

So_Awsome wrote:
DaSpudLord wrote:
So_Awsome wrote:
DaSpudLord wrote:
No support. Workaroundable. Look them up.
What do you mean?
I mean that it is possible to program it yourself.
You're absolutely right, it is possible to program it yourself, but if you don't know trig, or you are new to scratch, it would be very hard.

Agreed

the2000

Support, Scratch has had a lot of blocks with two variants for coordinates and coordinates of another objects (i.e go to, glide to), so I don't see why the point towards block should be any different.

DentInTheWall

dupe and in the official workarounds list

gosoccerboy5

DentInTheWall wrote:
dupe and in the official workarounds list

Oops. I think this is the earliest such topic (I encourage you to find an earlier one), and the official workarounds list says here:

shradibop wrote:
In the suggestions forum, you might have a suggestion for a block. But, if it gets rejected, have no fear! On this topic, you can easily ask for workarounds for block. Still don't get it? Confused as to why you can't just get the block added? @Za-Chary is here to explain that to you.
Za-Chary wrote:
Well, there's a couple reasons this is a useful list.

The “previous costume” block is not rejected, but it just hasn't been added to the editor. For those looking for something that works the same as a “previous costume” block, they can look at this topic for a workaround so they can effectively code their project.

The “when stop sign clicked” block is rejected, so we will not be adding it (and in this case, yes, there is something “wrong” with implementing the suggestion). Some Scratchers still might like to simulate its effects, however, so they can look at this topic for a workaround so they can accomplish what the block would do.

The purpose of this topic isn't to tell you to “stick” to workarounds — it's to provide you workarounds for blocks that you might be looking to use. It will likely save you time by using the workaround instead of waiting for us to implement a block.

So just because it's in that list doesn't mean it shouldn't or can't be added.

SpinningCube

Support. I would find many uses for this block, and I always prefer an official block to a tedious workaround.

Last edited by SpinningCube (Feb. 3, 2021 18:26:53)

Discuss Scratch