ServerCmdPlantBrick Description

[tyler0]

When you plant a brick this is what blockland returns:

Entering ServerCmdPlantBrick(10635)

   Entering fxDTSBrick::onAdd(14744)
   Leaving fxDTSBrick::onAdd() - return

   Entering fxDTSBrick::onColorChange(14744)
      Entering fxDTSBrickData::onColorChange(212, 14744)
      Leaving fxDTSBrickData::onColorChange() - return 212
   Leaving fxDTSBrick::onColorChange() - return 212

   Entering fxDTSBrick::onRemove(14744)
   Leaving fxDTSBrick::onRemove() - return

   Entering messageClient(10635,
25)
   Leaving messageClient() - return

Leaving ServerCmdPlantBrick() - return 14744

What does this do?

Entering fxDTSBrick::onRemove(14744)
   Leaving fxDTSBrick::onRemove() - return

I up it into a package and forced fxDTSBrick::onRemove to not return a parent, and nothing changed. Any idea what this is for?

And also what is 14744?

[Ad Bot]

[Ipquarx]

onRemove is when it's removed, in other words deleted.

14744 is it's objectid.

[tyler0]

onRemove is when it's removed, in other words deleted.

14744 is it's objectid.

Why is it being used when you place a brick?

What can you do with an objectid?

[Ipquarx]

Why is it being used when you place a brick?

What can you do with an objectid?

1. Don't know.
2. What can't you do with an objectid? Without the objectid you couldn't access the object, so it'd be useless.

[otto-san]

Why is it being used when you place a brick?

Ghost brick, maybe.

[Treynolds416]

onAdd also registers ghost bricks, but onPlant and onLoadplant do not

[otto-san]

onAdd also registers ghost bricks, but onPlant and onLoadplant do not

Because they aren't planted.

[Treynolds416]

Because they aren't planted.

If that wasn't obvious enough from my post, yes

[Xalos]

Yes, but that's not a ghost brick. PlantBrick is called ON a ghost brick, not to CREATE a ghost brick.
My guess would be that it's testing to see if it can plant a brick (::onAdd), but then finding that it can't (::onRemove and messageClient [for the plant error icon]).

[Treynolds416]

Yes, but that's not a ghost brick. PlantBrick is called ON a ghost brick, not to CREATE a ghost brick.
My guess would be that it's testing to see if it can plant a brick (::onAdd), but then finding that it can't (::onRemove and messageClient [for the plant error icon]).

What are you saying that isn't apparent already