Author Topic: A hammer that only checks the brick you hit  (Read 2312 times)

Basically just a hammer that doesn't do any floating-brick checks or whatever, it just removed the brick you hammer.
So precisely like the duplicator cut function actually, just in a hammer tool.

Right now when I use hackplant and hammer bricks, the entire structure gets removed client-side but is still there serverside, which is annoying as forget.

Right now when I use hackplant and hammer bricks, the entire structure gets removed client-side but is still there serverside, which is annoying as forget.

Sounds like said add-on is broken. I don't know why you're asking for a new hammer, and not for that to be fixed

Sounds like said add-on is broken. I don't know why you're asking for a new hammer, and not for that to be fixed
Because a non-check hammer would be useful in and of it's own really.
Pretty often i can't hammer some floating bricks from the bottom up, which is annoying.

Sounds like said add-on is broken. I don't know why you're asking for a new hammer, and not for that to be fixed

It's not a fixable issue. It can be avoided by duping and replacing the bricks, but the issue will persist next time bricks are loaded as a save. I'd like to see this though, I end up using the cut function on dupe to do this often.


It could be fixed if it were adjusted to delete the bricks instead of killing them.

You don't want the bricks to be killed or deleted though.

You want the bricks you hit with the hammer to be killed or deleted. Why else would you use it?

It's not a fixable issue. It can be avoided by duping and replacing the bricks, but the issue will persist next time bricks are loaded as a save. I'd like to see this though, I end up using the cut function on dupe to do this often.



Sounds like bullstuff. If dup can plant the floating bricks correctly, and this add-on can't, then it's broken.

Sounds like bullstuff. If dup can plant the floating bricks correctly, and this add-on can't, then it's broken.
Yeah but you can't hammer the supporting ones when you use dup.



You want the bricks you hit with the hammer to be killed or deleted. Why else would you use it?

Thought you meant all the bricks that would be deleted due to float instead of just the hammered ones, my bad.

Sounds like bullstuff. If dup can plant the floating bricks correctly, and this add-on can't, then it's broken.

The dupe prevents hammering of supporting bricks. Hackplant considers many bricks as supporting and deletes them for the client when just one of them is hammered.

You could probably fix this by setting isBaseplate to true on all bricks. Though you need to set it both before and after planting because .plant() changes it back.

I mean, that would fix the issue of bricks disappearing but that still leaves the need for the requested tool.

The Delete Launcher does what you want, I believe.


You could probably fix this by setting isBaseplate to true on all bricks. Though you need to set it both before and after planting because .plant() changes it back.
the issue seems to be is that the client prediction kills all the bricks but the server doesnt
the solution is to delete the brick and if wanted create a fake brick at the location and kill it to prevent chain killing