Author Topic: Random request: stuff Brick Mode Mod  (Read 773 times)

What this is is a way to make some bricks for things like simple demonstrations to show people stuff, like events, what a noob's build looked like...an then easily deleting it.

You start by pressing a keybind, which starts stuffbrick mode.  You build your thing-these bricks become stuffbricks, perhaps on seperate baseplates, not on baseplates, very far away, then when you are done with your thing, you press the stuffbrick keybind again, and deletes the stuffbricks you made in that stuffbrick session.  The bad thing that could happen would be that you could forget that you're in stuffbrick mode, build your amazing build, then use stuffbrick mode again and delete it all, this is where a fail dad would be used.  Every pre set interval in either time or bricks, it pops up a warning saying "you are in stuffbrick mode".  Something else that could help reduce this problem would be a command to change your stuffbricks into regular bricks.

This was just a thought I had when I was remaking a kid's house to show my friend, and it was all confettied baseplate spam, so I had to manually delete it, with the Dwand.  Too much effort.


what is this
He's basically suggesting you can press a keybind, and during that time you can build something, and when you press that keybind again the bricks go away, basically to show a friend a neat trick, or something like that, without wasting your time.

He's basically suggesting you can press a keybind, and during that time you can build something, and when you press that keybind again the bricks go away, basically to show a friend a neat trick, or something like that, without wasting your time.

yup

it's called a macro...?
the new buildbot loads builds with events now, so events shouldn't be a problem if a macro doesn't do it for you.

This isn't a macro.
Read, Sami, read.

What could be done is that when it is active every brick placed is added to a stack on the client.  Then when it is turned off every brick in the stack is then removed from the world and the stack is set to null awaiting it to be activated again to start the cycle anew.

P.S. I cannot think of a way to do this client sided

What could be done is that when it is active every brick placed is added to a stack on the client.  Then when it is turned off every brick in the stack is then removed from the world and the stack is set to null awaiting it to be activated again to start the cycle anew.
or you could, you know, just set it into a simgroup and be done with it. then delete the simgroup or something.
P.S. I cannot think of a way to do this client sided
log the number of bricks planted, then do for(%i=0;%i<numplantedbricks;%i++) commandToserver('undobrick'); or 'undo'. not sure.

Simgroup is the right direction for this.

As for client side, even doing that loop might break your normal build.

Simgroup is the right direction for this.

As for client side, even doing that loop might break your normal build.
not if the numbers are right?
i've used methods like that in the past to rapidly clear precise numbers of bricks.

What if you hammer a brick? That doesn't remove it from the undo stack.

Plus what about overlap and such?