|
|
2021-10-28 20_24_05-AIWar2.png (193,992 bytes) |
|
|
I tried adding some output to help me debug in NecromancerFactionBaseInfo.cs, in IsPlanetEligibleForNecropolis, in order to understand what's going on. It seems that when a minor or defensive necropolis are built, the list ( List<GameEntity_Squad> necrops = this.Necropoleis.GetDisplayList(); ) doesn't contain them because I noticed that the for loop's (the one dedicated at passing all necropolis) counter stay at 0 and never increment to 1, whereas with a major necropolis that was indeed happening. The two new necropoleis have their tags in the XML correctly assigned. I ran out of time to debug it more and I'm not sure where the issue could be. Also, my assessment could be wrong (hopefully no). |
|
|
Here's some screenshots of the debugging. Sorry for the super ugly and rudimental debugging, but that's the only way I found of doing it. In the first screenshot you can see that I build a Major necropolis (it has a second necrofleet in the system) and in the log you can see that the loop counter is 0 (3 hops from homeworld), then 1 (0 hops) because that's where I just built the second necropolis. The other 2 lines are just checks inside the third if statement inside GetCanBeHacked at line 17 in NeinzulAbyss_Hacking.cs. In the second screenshot I built a minor necropolis and the loop counter stays at 0, that's why I assumed necrops.Count remained at 1. |
|
|
This is a known limitation until I work out how the fleet-bolstering code works |
|
|
Fixed. Note that you can now build a necropolis on any planet |
- Anonymous
