Blueprint Not Destroyed with Supporting Building

[ghost]

When using the OnlyOnThing option for CommunityCoreLibrary.RestrictedPlacement_Comp a blueprint is not removed/destroyed when the underlying thing is destroyed.

Tested by building on a wall with this XML:

<building>
  <isEdifice>False</isEdifice>
</building>
...
<comps>
  <li Class="CommunityCoreLibrary.RestrictedPlacement_Properties">
    <compClass>CommunityCoreLibrary.RestrictedPlacement_Comp</compClass>
    <thingDefs>
      <li>Wall</li>
    </thingDefs>
  </li>
</comps>
...
<placeWorkers>
  <li>CommunityCoreLibrary.PlaceWorker_OnlyOnThing</li>
</placeWorkers>

Then activate god mode and de-construct the wall, the blueprint is not removed. Once the blueprint is constructed the building is destroyed with the "A support was removed" message. Same behavior happens without god mode and letting a colonist de-construct the wall.

[ForsakenShell]

This could take a little while to solve. The problem is that the blueprint doesn't carry the thing comp to tick yet, so it can't check that it's restrictions have changed.

[ForsakenShell]

I think a possible solution to this is to switch from the comp checking the status of the building to a map component which does a periodic scan. This way buildings and blueprints alike can be destroyed as well as removing the requirement for the building itself to tick.