HQs of HQs

[LargeSlowTarget]

While adapting Treespider's CHS mod to 'my taste' (more ressources / less oil - in my ongoing PBEM I have oil for 2 years and ressoures for eight days of production...), I have set the 'higher HQ' for NorthPac HQ (slot 101) and SouthPac HQ (slot 103) to the historically correct CentralPac HQ (slot 102).

To my suprise, when running the game, all bases and units assigned to the NorthPac HQ now BELONG TO THE JAPANESE!

SouthPac bases and units though remain loyal to the Allies. When I switch 'higher HQ' of NorthPac HQ to itself, all is normal.

Fuzzy Theobald made quite a mess as COMNORPAC, but this is a bit strong!

Any ideas?

[el cid again]

I suggested this to Joe Wilkerson when we worked on CHS - and he replied

"I don't think you understand what HQ means in WITP code terms - it doesn't mean what you think it does"

HQ appearnely are independent of each other - and control certain units and functions - mostly in the same hex - otherwise within the command radius of the hex.

Frustratingly - the AI will assign units to some HQ on its own - HQ that are not supposed to be used in that way. I think they intended more than we now see - that the HQ might turn into something more someday.

[JWE]

Hi LST,

Code looks at certain main HQs top-down. The AI expects to see certain stuff hard coded. Changing names is cool, but changing data is problematic. It can be done, but you gotta know where the bumps are. If you send me a pm, think we can figure out how to do what you want.

[el cid again]

Why not disclose the way it works in the Design Forum?

Matrix once disclosed an undocumented feature to Andrew and myself - how to make the cavalry symbol appear -
and we not only used it in CHS and RHS - we explained it so anyone can do it. If the purpose of the Forum is to make the mods richer - why not implement it so all can use the information?

[jwilkerson]

Iin stock (WITP) the "Command" HQs ... the "Higher" (or Highest) level of HQ are effectively hard coded ... they must be in the slots they are in. And for zillions of reasons they cannot be touched ... like there are many internal array in the code that load these in from arrays defined in the code. So getting the scenario data out of synch with the code with cause BAD problems. So bottom line - don't touch the higher HQs. The except is that they can be renamed a bit. And in CHS we did try to move them around - however - I seem to recall issues with that. Like we tried to convert an Indian HQ to a second Aussie HQ (one restricted one not). I think this "almost" work but I seem to recall there were issues.

So again - messing with the Command HQs is problematic. Proceed with caution if at all.

[jwilkerson]

ORIGINAL: el cid again

Why not disclose the way it works in the Design Forum?

Well because "how it works" would be actually be 100+ answers - because "how it works" is scattered about the code - here and there. So "how it works" it not a simple, single node type answer.

This is not even something we messed with much in AE - even though we tried a bit. It is part of the decentralized "back bone" of the system. It is what it is. You can learn as much about it from testing (and probably quicker) as you can by staring at the 400,000 lines of code.
[:)]