Applying tool to character with a scale of <=0.6 causes them to be teleported away

Bug Reports Engine Bugs
1

I’ve noticed a problem with tools being parented to a character whose scale is low (0.6 in this example and anything lower)

When you parent a tool to a character with a scale of > 0.6 it works as normal, and the character is fine, however when the characters scale is 0.6 or below it teleports them away for no reason

Repro file. Script is located in ServerScriptService.
Tool bug Repro.rbxl (121.9 KB)
Just mess with the Scale variable. I find 0.65 works fine, but 0.6 and anything below gets the player teleported away.

local Scale = 0.6

local Rod = game.ReplicatedStorage.Rod

game.Players.PlayerAdded:Connect(function(player)
	local HumanoidDescription = game.Players:GetHumanoidDescriptionFromUserId(player.UserId)
				
	HumanoidDescription.DepthScale = Scale
	HumanoidDescription.HeadScale = Scale
	HumanoidDescription.HeightScale = Scale
	HumanoidDescription.WidthScale = Scale

	player:LoadCharacterWithHumanoidDescription(HumanoidDescription)
	
	local Character = player.Character or player.CharacterAdded:Wait()
	
	for i = 5, 1, -1 do -- Wait 5 seconds
		print(i)
		wait(1)
	end
	
	Rod.Parent = Character
end)
2 Likes
2

After some testing I found out that it is the size of the fishing rod. Maybe make a smaller sized rod and a normal sized rod. If the player is a kid, give them them the smaller one and if they are an adult, give them the bigger one.

3

I shouldn’t have to create seperate models based on each player size though

4

Its pretty simple to do it. And I tested it and thats your problem.

5

You could do it any way you want, but all I know is it has to do with the size of the rod.

6

Are the objects in the tool massless?

1 Like
7

Thanks for the report! We’ve filed a ticket to our internal database and we’ll follow up here when we have an update for you.

2 Likes
8

I am in the process of checking over bug reports and following up on some bugs that haven’t received any activity in a while.
Is this issue still occurring or can you confirm that this bug has been resolved?

1 Like