When a planet is registered via PlanetsLib:extend(), any property_expression_names defined in the planet table are lost. After the call, data.raw["planet"]["velora"].map_gen_settings.property_expression_names does not contain the values set before the call.
Steps to reproduce:
Define a planet with custom property_expression_names (e.g. enemy_base_probability)
Register it via PlanetsLib:extend({ velora })
Check data.raw["planet"][name].map_gen_settings.property_expression_names immediately after — values are missing
Expected behavior:
property_expression_names defined in the planet table should be preserved after PlanetsLib:extend()
Actual behavior:
property_expression_names is empty or missing after PlanetsLib:extend()
Workaround:
Manually patch data.raw["planet"][name] after PlanetsLib:extend():
luaPlanetsLib:extend({ velora })
data.raw["planet"]["velora"].map_gen_settings.property_expression_names["enemy_base_probability"] = "velora_enemy_base_probability"
Mod affected: Velora 1.3.1
When a planet is registered via PlanetsLib:extend(), any property_expression_names defined in the planet table are lost. After the call, data.raw["planet"]["velora"].map_gen_settings.property_expression_names does not contain the values set before the call.
Steps to reproduce:
Define a planet with custom property_expression_names (e.g. enemy_base_probability)
Register it via PlanetsLib:extend({ velora })
Check data.raw["planet"][name].map_gen_settings.property_expression_names immediately after — values are missing
Expected behavior:
property_expression_names defined in the planet table should be preserved after PlanetsLib:extend()
Actual behavior:
property_expression_names is empty or missing after PlanetsLib:extend()
Workaround:
Manually patch data.raw["planet"][name] after PlanetsLib:extend():
luaPlanetsLib:extend({ velora })
data.raw["planet"]["velora"].map_gen_settings.property_expression_names["enemy_base_probability"] = "velora_enemy_base_probability"
Mod affected: Velora 1.3.1