What did you do?
I have added 3 new enemy autoplace control. They work, however, 2 of them have conflict on nauvis and I couldn't figure out the reason. The autocontrol name and noise expressions have different names.
Discovered in 2.0.21 and tested again in 2.0.23.
What happened?
The redarmy autocontrol slide is somehow controlling the protoss autoplace. Protoss autoplace slider doesn't do anything to protoss spawns on Nauvis. But it does on the new planet (Aiur).
THe protoss autocontrol works fine for Nauvis after I disable the redarmy mod.
Other autocontrol sliders work fine with redarmy enabled. The ones from Enemy and Zerg.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
The Protoss autoplace control should not affected by the red army autoplace control.
Does it happen always, once, or sometimes?
Always
How to replicate:
1. Go to mod setting.
2. Select "Nauvis Enemy" to "2 way split",
3. select "enemy_erm_toss" in "2 way split positive axis" and enemy_erm_redarmy in "2 way split negative axis"
4. Confirm to restart game
5. Start a new freeplay game.
6. Open the preview
7. Select preset to "ERM Debug"
8. Go to enemy tab
9. Drag the redarmy silders and observe the preview.
10. Drag the protoss silders and observe the preview.
To prove protoss silder is working.
11. Select planet Aiur in preview.
12. Drag the protoss silders and observe the preview.
Mods (My Dev build, 500mb+): [closed]
Extract them into mods, it include mod-settings.dat, but you should double check the settings just in case.
Here is my investigation so far:
The spawner autoplace are using the correct noise-functions, based on the prototype browser.
Looking at the Nauvis (space-location) object in prototype browser. The autoplace_controls and property expression names look fine to me as well.
When I dump the noise-expression for the 2 way noise-expression manipulations, they also look fine to me.
/c game.print(serpent.block(prototypes.named_noise_expression['erm_2_way_negative-enemy_erm_toss--nexus--1'].expression))
so ya. I don't know what's missing? or is it bugged?
Point of interest:
Data phase autoplace manipulations
enemyracemanager/prototypes/map-generation.lua
enemyracemanager/prototypes/noise-funcitons.lua
-- New enemy Autoplace controls and its noise-functions are defined in here
erm_redarmy/prototypes/noise-functions.lua
erm_protoss/prototypes/noise-functions.lua
[2.0.23] Enemies autoplace control conflict?
[2.0.23] Enemies autoplace control conflict?
Last edited by heyqule on Mon Dec 02, 2024 10:12 pm, edited 1 time in total.
Re: [2.0.23] Enemies autoplace control conflict?
Ok. It's not a bug.
Having seed1 collision caused this issue. It's fixed after changing seed1 to a different value.
Having seed1 collision caused this issue. It's fixed after changing seed1 to a different value.