phflack's thread of questions

[phflack]

Few things I need for a script

• can an event tell if it was triggered with named brick or self?
• can a bricks coordinates be modified or must it be duplicated and deleted to move?
• can a brick be floating but have the float check be overridden to being grounded?

more might come later

[Ad Bot]

[Eeposs]

I think number 2 is possible, there was a mod for this but it's a crap-on so i can't send you it ;c.

[Destiny/Zack0Wack0]

Few things I need for a script

• can an event tell if it was triggered with named brick or self?
• can a bricks coordinates be modified or must it be duplicated and deleted to move?
• can a brick be floating but have the float check be overridden to being grounded?

more might come later

1) Definitely. I don't know the code to do it, but if you muck around with trace you'll be able to find it.
2) It needs to be duplicated and deleted.
3) Yes. It will be fail binned if it's not a private mod.

[Brian Smithers]

3) Yes. It will be fail binned if it's not a private mod.

My lightbike makes a ton of floating bricks but it was never failed.

[Treynolds416]

My lightbike makes a ton of floating bricks but it was never failed.

He means allowing players to plant custom floating bricks with their ghost brick, most likely.

[phflack]

3) Yes. It will be fail binned if it's not a private mod.

why would it be failed? or what if there was a limit to the number a player could have?

[Treynolds416]

why would it be failed? or what if there was a limit to the number a player could have?

Bricks aren't meant to be floating for several reasons. Among them, the chain killing of bricks, proper trust management, the breaking of other mods, and people complaining that they wanded their entire build by accident and how this game sucks because you lost the save

[phflack]

that's the point of having the brick faking being grounded, to prevent the whole build from breaking and letting the hammer break stuff

[Treynolds416]

that's the point of having the brick faking being grounded, to prevent the whole build from breaking and letting the hammer break stuff

Oh I see what you're trying to do. You'll have to rewrite something, whether it's the isBaseplate (can't remember if it's a function or a property) or whether you package hammering, undo-ing, and removal of bricks. Maybe even all of them, it won't be a simple task.

[phflack]

I feel like there's a function that is called when breaking something, like willCauseChainKill() or something
wouldn't that just have to return false on the brick?

[Lugnut]

will cause chainkill is the same as saying
if(1 == blah)

it's not like it will CAUSE the chainkill, it's only telling you if it WILL

i can't make sense of this

[phflack]

I thought destroying a brick would call that function to see if the bricks around it should die?

[Lugnut]

I thought destroying a brick would call that function to see if the bricks around it should die?

i have no facts to back this, but theoretically:

beating on a brick with a hammer will call that to check if the hammer should break the brick

if it returns false, it'll call %brick.killbrick();


I guess, anyway.

[Treynolds416]

Lug, did you change your name?

phlack, here's my suggestion: package isBaseplate (I think it's a function) and have certain floating bricks act as baseplates, set them to a variable and have isBaseplate return true.

[phflack]

I was unaware that baseplates could be floating