[kovarex][2.0.9] Entities locked behind research can be built via parameterization and bots
Posted: Thu Oct 24, 2024 4:56 am
What did you do?
I set up the following blueprint (parameter 0 is linked to assembler recipe, storage chest filter and fast inserter Enable/disable signal)
What happened?
When I placed down the blueprint, I selected active provider chest by mistake and the bots built the assembler with the active provide chest recipe even though this entity was not yet researched. I was able to create a few chests too. I tried again with buffer chests and this also worked.
What did you expect to happen instead?
The assembler should not have set it to the active provider & buffer chest recipes.
Does it happen always, once, or sometimes?
It happened with buffer & active provider chests multiple times but when recreating for this bug report, I can no longer do it. The assembler is correctly left to the "0" parameter value. So it's solved itself somehow?
But since I was able to do it a couple of times, I thought it worth submitting the bug report.
Save & log file attached.
I set up the following blueprint (parameter 0 is linked to assembler recipe, storage chest filter and fast inserter Enable/disable signal)
- 10-24-2024, 15-42-16.png (205.58 KiB) Viewed 1306 times
When I placed down the blueprint, I selected active provider chest by mistake and the bots built the assembler with the active provide chest recipe even though this entity was not yet researched. I was able to create a few chests too. I tried again with buffer chests and this also worked.
- 10-24-2024, 15-49-00.png (4.82 MiB) Viewed 1306 times
- 10-24-2024, 15-48-27.png (2.26 MiB) Viewed 1306 times
The assembler should not have set it to the active provider & buffer chest recipes.
Does it happen always, once, or sometimes?
It happened with buffer & active provider chests multiple times but when recreating for this bug report, I can no longer do it. The assembler is correctly left to the "0" parameter value. So it's solved itself somehow?
But since I was able to do it a couple of times, I thought it worth submitting the bug report.
Save & log file attached.