fudge
I was toying around with the visuals of these blocks in desmos and realized the player coordinates don’t match with the point of rotation but instead go to the opposite coordinates 
so that’s why it ain’t really accurate on my part
or anyone’s for that fact lol
1 Like
So basically storm trooper aim?
Is that the only problem or-?
2 Likes
basically yeah lol
but also a problem I’m fixing rn is something wrong with the actual thing that counts the hit for some reason it only counts it when it is more than the actual distance when the fire button is pressed
but I fixed the first problem gonna update the guide soon
also fixed the hitbox spam thingy
3 Likes
So the Pseudo shot has to be longer than the actual distance to be counted?
That’s confusing.
2 Likes
yeah… it was but just fixed that to find out it still spammed the hitbox a moment later 
2 Likes
Youch.
I’d try to help, but I have absolutely no idea how to use block code. 
3 Likes
and nvm fixed the notifications but now I realized I didn’t fully fix the stormtrooper aim
._.
turns out I was getting negative angles which was interfering with the formulas (I think)
1 Like
brain fried on me and gave up taking a break for a while
if anyone wants to take a crack at it go ahead
var key table
c: the y coordinate formula for the directional point
b: the x coordinate formula for the directional point
r: radius which is what moves the projectile once increased
a: the angle formula
p: the current player x coordinates/aka the x origin of the circle
t: the current player y coordinates/aka the y origin of the circle
d: the delayed player x coordinates/aka the origin of the angle (not too sure that’s a thing)
w:delayed player y coordinates/aka the origin of the angle
b0:something I tried knowing it would backfire :p
c0:same thing as above
anything else is purely for visuals aside from the points
1 Like
currently reworking the entire thingy but also side tasking with other stuff
made it significantly more accurate but
not nearly enough 
_ turns out turning it 180 degrees in various ways isn’t really effective :p
idk if I can edit guide anymore tho
but here’s link to the improved version
updated var key table
(p,t) player coordinates/rotational point
(w,d) past player coordinates
(o_2 or just o2) is the projectile as labeled in the graph
(u) is the thingy that you will increase to move the projectile coordinates aka how you will launch it
o2,o3, and o are just so I could shorten it
but do note that the higher “u” is the more it’ll go off course
completely fixed just still same name 
project ver2 | Desmos (will update guide tomorrow)
aw :c forgot about the edit timer
hey @Turtle
can ye wikify this for a bit
please lemme know when ya do plz
1 Like
Turtle is gone now,
So uhh @twofoursixeight
Can you wikify this for Black fox?
3 Likes
will edit at lunch today
but also trying to re figure out how I did the mess of devices that was the fixed pseudo projectiles thingy so I can make the screenshots again :P
done editing but may have to reword a couple things later
cuz what I meant by duping the trigger loop is like removing the top if block and using just the distance formula to dupe
also noticed that this version is significantly optimized :D
1 Like
In step 5 is there more code to this part because I think that there is a bit of green ato the bottom.
i think that was just an if block i couldnt fit in
but i also think it was included in a later step
oh yeah now i remember that’s an old screenshot i didnt bother to change i separated the if block into a different device when i reworked it before the if block was in the same block as that one
Bumpo on a concepto thingo.
Haha projectile go brrr
1 Like
bump
1 Like
I can add visuals to this now (hasnt checked out the update yet so im hoping i can)
1 Like