Author Topic: An Update to the Hammer  (Read 1274 times)

I'm sure I'm not the only one who's ever had the problem where you want to smash a brick with the hammer, but the brick won't break because it would also break more bricks and you can't for the life of you figure out which goddamn brick is the one causing the problem.

The duplicator, when you use it, highlights all the bricks that you've duplicated in a bright white for a second or two. It would be awesome if the hammer did the same thing, temporarily highlighting in glowing red whichever bricks were dependent on the brick you're trying to break. Doesn't seem to me to be to hard to do. Thoughts?
« Last Edit: February 28, 2013, 03:26:54 PM by StarHawk »

Won't using the Wand solve the problem?

So, instead of finally saving it, wanding it, and trying to figure out (if it's not obvious) which bricks collapsed, then loading again and trying to remember which ones need more support, you could just hit it with the hammer (in a certain mode, perhaps... or maybe a different tool altogether) to highlight dependent bricks?

That's


actually a really good idea

Yeah I like that idea, I'd love to see this done if it's actually doable

Yeah I like that idea, I'd love to see this done if it's actually doable
Yeah, /support.

Won't using the Wand solve the problem?

The objective is to destroy the brick without destroying any other bricks. You want to find which bricks need additional support and subsequently support them.

The issue is that there is not really a good way of calculating which bricks need support.
For an excellent example of that, see the Duplicator. Notice how randomly it selects tons of stuff you didn't want?

The issue is that there is not really a good way of calculating which bricks need support.
For an excellent example of that, see the Duplicator. Notice how randomly it selects tons of stuff you didn't want?
You need to limit the amount of highlighted bricks to something sensible like 128. You don't necessarily need to highlight all the thousands of bricks that one brick is supporting. In the situations where I've needed this I would only have needed to know which bricks are supported in general so even ~32 highlighted bricks would work.

You need to limit the amount of highlighted bricks to something sensible like 128. You don't necessarily need to highlight all the thousands of bricks that one brick is supporting. In the situations where I've needed this I would only have needed to know which bricks are supported in general so even ~32 highlighted bricks would work.

A supported brick is not the same as a connected brick. It's easy to find all connected bricks, but seeing what's actually supported is a whole different story.

A supported brick is not the same as a connected brick. It's easy to find all connected bricks, but seeing what's actually supported is a whole different story.
I'm pretty sure they are same thing.
Edit: Oh silly me. I was assuming you'd know which one is the supporting brick and you are hitting that. Never mind.

A supported brick is not the same as a connected brick. It's easy to find all connected bricks, but seeing what's actually supported is a whole different story.

The nature of the hammer itself is that it looks to see if any bricks are dependent on the brick you are trying to hit. Should it not be easy to write a program that simply highlights these bricks rather than simply making a "dink" sound?

The nature of the hammer itself is that it looks to see if any bricks are dependent on the brick you are trying to hit. Should it not be easy to write a program that simply highlights these bricks rather than simply making a "dink" sound?

Definitely not simple.

I made something that does this actually

It's really laggy because I haven't been able to write a good optomization in TS


Duplicator duplicates more than enough bricks as you want sometimes. It's a pain in the ass when it happens and sometimes it causes servers to crash.