Maps are random (between some parameters ofc), but pre-seeded in the Campaign so you roughly get the same mission if you start it more than once (that is, if you reload the game and start the same mission again).

Originally posted by Aliza:

Maps are random (between some parameters ofc), but pre-seeded in the Campaign so you roughly get the same mission if you start it more than once (that is, if you reload the game and start the same mission again).

Thank you but it's not explaining multiple cases, including the special case quoted in OP, for which I got two very different maps for the exact same mission and phase and at exact same time turn in the cmpaign.

Bugs? :-) Or at least unintended?

All missions are generated to be unique. If you started the *same* mission multiple times, it being not always the same as "before" is not a bug, as there is no "before" a mission--it is a single instance. Reloading to before the start of a mission is kinda breaking the space-time continuum. :P (The are other internal parameters for RMG so even with the same seed the final map can vary a bit.) The question in OP was if missions are fully procedurally generated. They are. The scenario you described doesn't contradict that, on the contrary: even a fixed seed is not totally fixed.

One more thread title a bit misguiding, sorry.

But if you read OP, you'll quote I started wonder if it was really procedure generated because I couldn't guess the seed logic from cases I quoted:

1. Most often, I load before the mission part, or the mission start, and start again the new mission and new part, and get the exact same area and first enemies at exact same positions.

2. Sometime, with same process, I get another area totally different, three cases quoted:
- Get area A, get area B, get area B
- Get area A, get area A, get area B
- Get area A, get area B, get area A (that one felt very weird like a travel back in time, it's because of this case I created the thread)

Clearly if reload before a mission or mission part is breaking the space-time continuum, I got many cases totally weird with space-time continuum reconstituted at exact same state despite broken.

I'm no specialist of space-time continuum, but those events seem break math probability laws, that I got one incredible case perhaps, but not many like 4/5.

That said if you want keep hidden the seed logic, ok.

The seed logic is not a secret, but either not that important. Key elements are:
- sectors for base-building are pre-seeded
- each sector has a pre-seed to be used in any kind of mission performed on it
- horde and faction missions are all instances, you'll never get the same
- EXCEPTION is when you reload to before a mission and start it again (that's the point of the seeding, so you can't "save scum" until you get a more favorable layout), when there can be some "secret" moving parameters that get you either map A or map B. These parameters are not pre-seeded, and are major limited forks in RMG logic, that's why you can get A or B, but not C, D, E, etc.

Twice I was happy the save scuming rather limited (once or twice, total/big disaster and difficulty to decipher a proper solution) worked to give me a different generation.

Other times was more related to big mistakes on squads setup, otherwise reload auto save at start is enough.

So there's those parameters that can create variations over a global seed for the campaign.

I quoted one minor case, squad position in the map has links with squad setup.

I suspect other cases:
- The game records secretly mission or mission part lost and accept change its generation in such case at least at Normal difficulty.
- The game uses existing auto saves in a way. Variations I had could come from that, sometimes I rage enough to delete them and sometimes I ignore.

Anyway thanks for the answers, my curiosity is fully satisfied. :-)