Building Tool Problem

[KingAchieve]

Hello again! You probably have seen me before. If not, welcome! Now today’s problem is about this thing. You move your cursor and a random brick pops up. It’s like build a boat’s building system but only cursor movement. There are a couple of problems I need to discuss.

The problem was when I was in - game moving my cursor the brick showed up (Good news) but bad news is it kept like going off screen and going into the ground. Here’s evidence:

See what I mean now?

script:

local player = game.Players.LocalPlayer
local workspacepart = game:GetService("Workspace")
local partsgo = Instance.new("Model",workspacepart)
	partsgo.Name = "ModelParts"
local madepart = Instance.new("Part",partsgo)
	madepart.Size = Vector3.new(3,3,3)
	madepart.Name = (player.Name.." Part")
	madepart.Anchored = true
local mouse = player:GetMouse()

while true do
	wait()
	madepart.CFrame = CFrame.new(mouse.Hit.x/1,mouse.Hit.y/1,mouse.Hit.z)
end

[Deferend]

Why are you dividing the x and y values by 1? You’d just get the same value…

Also, it is ill-advised to use Instance.new() with the parent argument, as seen below!

PSA: Don't use Instance.new() with parent argument

I’ve discovered a pretty bad performance issue in one of top games that has to do with Instance.new and wanted to write about this, since this is not obvious unless you know the system inside out. Tthere are several ways to create a ROBLOX object in Lua: local obj = Instance.new(‘type’); fill obj fields local obj = Instance.new(‘type’, parent); fill obj fields local obj = util.Create(‘type’, { field1 = value1, … }) If you care at all about performance, please only use the first option - I wi…

[KingAchieve]

Thanks for the response; I will check this method…

[KingAchieve]

I don’t think it really worked.

local player = game.Players.LocalPlayer
local workspacepart = game:GetService("Workspace")
local partsgo = Instance.new("Model")
	partsgo.Name = "ModelParts"
	partsgo.Parent = workspacepart
local madepart = Instance.new("Part")
	madepart.Parent = partsgo
	madepart.Size = Vector3.new(3,3,3)
	madepart.Name = (player.Name.." Part")
	madepart.Anchored = true
local mouse = player:GetMouse()

while true do
	wait()
	madepart.CFrame = CFrame.new(mouse.Hit.x,mouse.Hit.y,mouse.Hit.z)
end

[Danrich123 (dance_monkey)]

this is happening because mouse.Hit is moved onto the surface of the part and then the part gets moved onto the new mouse.Hit and this keeps on stacking which is why it goes of the screen. an easy fix to this is setting the TargetFilter property of the mouse to the part your moving so that mouse.Hit ignores it.

mouse.TargetFilter = madepart

if you want it to stop going in the ground you could add half of its y size to its cframe which just pops it up by half of its size.

madepart.CFrame = CFrame.new(mouse.Hit.X, mouse.Hit.Y, mouse.Hit.Z) + Vector3.new(0, madepart.Size.Y / 2, 0)

[roasthistorychicken]

(math.ceil(mouse.Hit.p.X), .5, math.ceil(mouse.Hit.p.Z))

I use math.ceil to get a rounded number and for the y I set it to .5 or 1 so its always the same.

also mouse.Hit.p and not mouse.Hit

[TheMagikMan12 (Magik)]

The issues that are shown here are 2 things. Brick is in the ground can be fixed by Vector3 movement to the brick by half of its y size. This is the same for anything you build. Position is the very center of the object. The second issue I saw was the part going all the way to the camera. This could be fixed by destroying a part and making a new one before you get the Mouse.Hit location.

[KingAchieve]

Thanks for the response. It did work!

[KingAchieve]

@roasthistorychicken

(math.ceil(mouse.Hit.p.X), .5, math.ceil(mouse.Hit.p.Z))

roas your response is good. I have a new problem.