Roblox Bug? Using the Same Code on 2 Rigs. Different Outcomes?

Hello , Fellow Robloxians!

Today , I ran into a very weired bug where I am using the “Same” Exact code on 2 different rigs.

The thing is , there are 2 different outcomes , even though its the Same Code

The Code is supposed to simply teleport a part to the Character’s Upper Torso’s CFrame!

I Will Present 2 Videos 2 all of you doing a rig comparison with the Same Code running. The Code can be seen at the start of the video. you can pause it. I repeat , it is THE SAME exact code In both videos!

–// When You Are A Blocky Rig!

–//When you are a Human Rig

This had me very confused. Is this a Major Roblox Bug? or is it something Im doing wrong?

There are no errors either!

Help!

–//T40

If this is a bug you shouldn’t post it here, Engine Bugs - Developer Forum | Roblox

How are you changing the Rig? Did you change the rig type via the game settings between R6 and R15?

If so then I believe the issue is somehow caused by the Rig changing from the players default R6 character to R15 character on load which somehow messes up the CFrame of the part. Other then that try reversing the parent statement, set the CFrame first then parent it into workspace and see if that changes anything.

Also posting the code would help since people will be able to copy and paste and try to debug the problem themselves.

I Figured it out. Turns out , I am not supposed to make the upper torso a variable.

I was supposed to use upper torso each time I needed to type it thought the script

Saving it as a variable literally saved that Instance and all the data of it within that time-frame.

I don’t believe thats how it works, the properties of the instance don’t “save” when you store it in a variable, you will get the properties of the instance at that current moment in time when you index it and you can test it through the following code:

local part = script.Parent --insert inside a part

while true do
	print(part.Position)--drag the part around and the position will change.
	wait(1)
end

I believe the issue is something else entirely in that the variable for part changes because of the change of rig from R6 to R15 due to game settings option somehow.

Also instead of editing the title you can click mark as a solution which does the marking next to your post already.

1 Like

Instead of putting [FIXED!] in the title of your topic, why don’t you mark the post that had the solution as the solution? There’s even a button for it and it looks cleaner and has a preview in the main topic.

I don’t think he is a regular yet…

Ive been here since early 2018. Just haven’t used the forum that much.