Add event on_blueprint_placed

[saors]

It'd be nice if there was an event for when the player placed a blueprint.
This event would give info like the bounding box of the blueprint and what surface the blueprint was placed on.


Other details might be nice too, but I don't need them specifically...
(like read the blueprint contents or what logistics network it's placed in (if any)).

[Rseding91]

The player built entity event is fired for each entity in the blueprint.

[saors]

The problem I'm currently experiencing with player_built_entity is that if you do calculations on the location that the individual entity within a blueprint is placed, then you get severe lag (especially on servers) as the calculation is being done on each entity.
If the blueprint is large enough, players are kicked from the server after timing out while "The server is not responding".

I figured the best way to tackle this would be to have different logic for individual entities compared to a blueprint.

[Rseding91]

The problem I'm currently experiencing with player_built_entity is that if you do calculations on the location that the individual entity within a blueprint is placed, then you get severe lag (especially on servers) as the calculation is being done on each entity.
If the blueprint is large enough, players are kicked from the server after timing out while "The server is not responding".

I figured the best way to tackle this would be to have different logic for individual entities compared to a blueprint.

Just ignore the fact it came from a blueprint - that doesn't matter anyway. Treat it like any other entity built and handle it as such.

[saors]

Thank you for the quick responses.

I don't currently have logic for if it's a blueprint or not, which is the problem. If a player places a 300 entity blueprint, the event (on_built_entity) is called 300 times (very quickly) causing severe lag.

I don't think my suggestion will help anyway, as even if I were to get the bounding box, I can't tell the on_built_entity event to ignore those entities without running into the same problem of calling the event a few hundred times.

I think a better API improvement request would be to have the ability to limit the number of responses an event gives per x seconds (ignoring the rest of them if it reaches the max).
I'm going to tinker with this idea some more and if it's unnecessarily difficult to manually implement then I will probably just open a request to see if it's be possible and get some feedback.

Thanks!

[Rseding91]

What is your mod doing that it's taking so long to process in the entity built event? Do you have a working mod example that shows the slowdown?

[saors]

Please ignore this post. I've made a huge mistake and wasn't filtering properly, which was allowing a complex method to be ran every time an entity was built...

I'm very sorry , thanks for the responses though!

[steinio]

Please ignore this post. I've made a huge mistake and wasn't filtering properly, which was allowing a complex method to be ran every time an entity was built...

I'm very sorry , thanks for the responses though!

No, please post your failed and successful code so we can learn from it.