| The uni files follows a pattern also seen in the obj file.
This pattern at the start of records made it finally easy to write a program
that can split and and output the files in various formats together with
a interpreting logmodule.
With help of this tool it was possible to deconstruct the nodes and chop the file into its records or rewrite the data to csv-files enbloc ( for use in Excel) The following basic types where found by this processing:
|
|
| X-loc/Y-loc |
|
| side-codes |
|
||||||||||||||||||
| Differences between templates and save day X-XX-XX-XX files | (save0 save1 save2):The codes used are not in this range - Needs
further analysis!
When a game is saved for later continuation the country codes apply as stated above. This holds also for missions saved for use in Tactical Engagements provided that you repainted the team distribution to match with the above table. In stdr te_new the land is distributed between sideID 1 and 2
|
| unit-in-game-id |
|
||||
| Differences between templates and save day X-XX-XX-XX files | The templates have all id 0! So the above number
range applies only after a launched game is saved again!
See also side-code |
| Unit-records |
+WPSTREAM! |
| GroundUnit-records |
|
| Brigade-records |
| battalion-records |
| AirUnit-records | NO VARIABLES READ FROM STREAM! |
| flight-records |
| package records |
|
| squadrone-records |
|
| taskforce-records |
|