How do you get a new position from a part, increase it by 10 (based on orientatantion)

[lapis heron]

So pretty much im using tween service and want to tween a part forward by 10 studs

so for example i have this arrow which shows the direct that its facing, so on a rotate i wouldnt manually be able to add 10 to x it would be either - or y so im unsure how to go about this

[narrow burrow]

what have you tried so far?

[lapis heron]

well im not sure where to start

[narrow burrow]

you seem to have that problem a lot

[lapis heron]

i do indeed

i only ask here if im like struggling

as these kinds of issues im not sure on

[narrow burrow]

this is something else

[lapis heron]

im guessing that you would have to get the orientatantion anyway but then how do you use that

[narrow burrow]

this specific problem is just getting a direction vector like cframe.lookvector, which is simple enough and you probably could have figured that out with some googling https://www.google.com/search?q=roblox+how+to+make+a+part+move+10+studs+based+on+orientation --> https://devforum.roblox.com/t/how-do-i-make-a-part-move-relative-to-its-rotation/2179031

[lapis heron]

ahh right thank you

[narrow burrow]

google is your friend, youtube too, and the docs https://www.youtube.com/watch?v=Vmphd-361qk

[lapis heron]

ahh right okay thank you

sorry about this

i knew it was simplier then some of the other issue i have faced

[narrow burrow]

its fine

[narrow burrow]

your other issues are fairly simple too, it's just you don't know about it, the fact that you can't find out for yourself is what bothers me, i think you're lacking something to teach yourself?

then you wouldn't get stuck so often ;p

[lapis heron]

true but like for example, https://discord.com/channels/448986884497211392/1367897438769250324, i have never seen anyone do this therefore no clue

[narrow burrow]

yes that's a simple problem too, i'm pretty sure i know what it is but more details helps

i think you're overcomplicating it for yourself

like you're thinking in the high-order of code, rather than the implementation details. kinda like, "oh just make a killbrick that kills players whenever they touch it", but in the actual implementation, you need to run through all sorts of little things like collectionservice for all the bricks, touch event, filter for player.character, search for humanoid, and then there's 4+ ways to kill the humanoid (.health=0, :takedamage(.health), changestate(dead), neck:destroy(), and there's probably more like just player.character:destroy).

[lapis heron]

oh right

i mean my guess is that for that issue i could just move the weld right?

that controls the length of the texture

[narrow burrow]

no what i'm saying is i think you're missing a few little concepts that will help you to get stuck far less often, and there's 2 i can think of on the spot that you probably never heard before.

[narrow burrow]

you're on the right track with this

[lapis heron]

but then if so that leads to another issue of how do i make sure that i expand the part across others, don't go behind or diagonal or pass a non belt part

if you understand what i mean

[lapis heron]

i mean yeah i think so

i kinda just go into all this raw

[narrow burrow]

i meant that you're breaking down the problem to smaller and simpler components, which is exactly what you need to do.

[lapis heron]

i use previous knowleage from other languages and just put it together and just dig in deep. Dont get me wrong its a bad idea but its fun and i learn a lot along the way

[narrow burrow]

that helps a tonne

[lapis heron]

yeah right thats what i was thinking okay well ill try that

[lapis heron]

i mean knowleage of others does 100%

but the small things that are exlucive are the stuff that im struggling with

[narrow burrow]

you may be familiar with the keep it simple, stupid and it applies a lot to programming. most problems are simple, and you'll feel stupid when you figure them out, and that never changes with code. one you may not be familiar with is rubber duck debugging which you may have inadvertently experienced but didn't know it actually has a name ;p

[lapis heron]

ohh right this makes much more sense

[narrow burrow]

if you were to explain your conveyor belt texture problem to a rubber duck, it would probably be something like you have 2 conveyor belts next to each other with a moving texture and the textures don't line up. the next obvious question is what would it take to make the textures line up? and the obvious answer is they need to be the same texture, repeating pattern, and moving in the same direction at the same rate with the same starting position, so that they are all showing exactly the same texture except moving.

the problem, and its solutions, becomes obvious, if you keep asking yourself the most obvious questions

[lapis heron]

ahh right thank you man

[narrow burrow]

if you weren't sure about setting up all that texture stuff, keep asking the dumb questions like what is a texture, how does it show on a part, how to make it move, etc. it takes a long time to learn all these little tricks, but i can guarantee you the first trick of rubberduck debugging can be used to make practically anything, even if you've never made it before or seen it before good luck with your game