Page 1 of 1
defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Fri Jan 10, 2025 7:47 pm
by Quezler
It is read only.
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Sun May 25, 2025 2:17 am
by Rseding91
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Sun May 25, 2025 5:08 am
by curiosity
That doesn't make any sense either. You can't specify one of the predefined states with that.
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Sun May 25, 2025 8:36 am
by Rseding91
Hmm, It looks like I fell for the same thing whoever wrote that doc line did. Oops.
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Sun May 25, 2025 8:38 pm
by Quezler
Also i found it quite curious that the default custom status for merely container prototypes was added just to support the crash site, i wonder why it doesn't just set the custom status via script as it generates the crash site since i can hardly imagine when someone would want to set a data stage custom status just on/for containers.
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Mon May 26, 2025 6:46 am
by curiosity
I assumed that it was a legacy artifact, but after looking into it I've found both broken status and custom status (and default status for containers) have appeared in 2.0.7. Really makes no sense.
Re: defines.entity_status.broken cannot be set through LuaEntity::status
Posted: Mon May 26, 2025 12:20 pm
by Therenas
Fixed for the next release, thanks.