Page 1 of 1
XML Tags descriptions
Posted: Sun Dec 31, 2017 8:47 am
by John T_MatrixForum
Hi
In the OOB XML
Some Units have a NEXT tag
What does that mean ?
the order units are shown ?
Is there a documentation of the XM structures (Most make sense but some are harder to guess)
AND Is there a log of the OOB load procedure ?
Right now I have a OOB file that just locks the editor.
Sometimes it gives very good errormessages but sometimes it just disapear into oblivion
RE: XML Tags descriptions
Posted: Sun Dec 31, 2017 10:02 am
by Oberst_Klink
ORIGINAL: John T_MatrixForum
Hi
In the OOB XML
Some Units have a NEXT tag
What does that mean ?
the order units are shown ?
Is there a documentation of the XM structures (Most make sense but some are harder to guess)
AND Is there a log of the OOB load procedure ?
Right now I have a OOB file that just locks the editor.
Sometimes it gives very good errormessages but sometimes it just disapear into oblivion
Alter Schwede,
dump the .XML or .OOB here or somewhere into the cloud. sometimes there are parsing errors because of some syntax and tags missing. Also have a look at the Tutorial '42- Editor sandbox scenario where I explained how to work with Notepad++ and Andy's Editor to create .TOW, .UNIT, .FORCE, .OOB files.
Tutorial '41:
tm.asp?m=4382552
Tutorial '42:
tm.asp?m=4387818
Tutorial '42 - Editor: tm.asp?m=4401098
Tutorial '43:
tm.asp?m=4390285
Tutorial '43 - Combat:
tm.asp?m=4394374
Tutorial '44:
tm.asp?m=4397183
Klink, Oberst
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 5:50 pm
by John T_MatrixForum
The pure crashes are slightly frustrating but with NP++ and an the compare plugin
you can move forward stepwise and find the error within reasonable time.
I still don't get how to install Andys editor
(Reinstalled TOAW III and the editor there after but still don't get it)
Anyhow what I was looking for was the meaning of tags in the XML file
Formation is rather selfexplanatory:
<xs:element minOccurs="0" maxOccurs="unbounded" name="FORMATION">
<xs:attribute name="ID" type="xs:unsignedByte" use="optional" />
<xs:attribute name="NAME" type="xs:string" use="optional" />
<xs:attribute name="PROFICIENCY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPLY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPORTSCOPE" type="xs:string" use="optional" />
<xs:attribute name="ORDERS" type="xs:string" use="optional" />
<xs:attribute name="EMPHASIS" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
But I have more problem with Unit:
<xs:element minOccurs="0" maxOccurs="unbounded" name="UNIT">
<xs:complexType>
<xs:attribute name="ID" type="xs:unsignedShort" use="optional" />
<xs:attribute name="NAME" type="xs:string" use="optional" />
<xs:attribute name="ICON" type="xs:string" use="optional" />
<xs:attribute name="ICONID" type="xs:unsignedByte" use="optional" />
<xs:attribute name="COLOR" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SIZE" type="xs:string" use="optional" />
<xs:attribute name="EXPERIENCE" type="xs:string" use="optional" />
<xs:attribute name="CHARACTERISTICS" type="xs:string" use="optional" />
<xs:attribute name="PROFICIENCY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="READINESS" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPLY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="GOINGTOX" type="xs:unsignedByte" use="optional" />
<xs:attribute name="GOINGTOY" type="xs:unsignedShort" use="optional" />
<xs:attribute name="EMPHASIS" type="xs:string" use="optional" />
<xs:attribute name="STATUS" type="xs:unsignedByte" use="optional" />
<xs:attribute name="ENTRY" type="xs:unsignedShort" use="optional" />
<xs:attribute name="REPLACEMENTPRIORITY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SECONDARYICON" type="xs:string" use="optional" />
<xs:attribute name="X" type="xs:unsignedByte" use="optional" />
<xs:attribute name="Y" type="xs:unsignedShort" use="optional" />
<xs:attribute name="NEXT" type="xs:unsignedShort" use="optional" />
<xs:attribute name="CHARACTERISTICS2" type="xs:unsignedInt" use="optional" />
<xs:attribute name="PARENT" type="xs:unsignedShort" use="optional" />
</xs:complexType>
</xs:element>
CHARACTERISTICS - the bitpattern of the units all equipment capabilities ?
What is the difference between GOINGTOX and X ?
NEXT seems to point to another unit in the same formation but I don't see the logic
CHARACTERISTICS2 ???
PARENT -seems to be the same unit or if the unit are divided ?
Cheers
/John
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 6:26 pm
by Lobster
Why are you even using this???? [:D]
The game editor does all of this.
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 6:46 pm
by Oberst_Klink
ORIGINAL: John T_MatrixForum
The pure crashes are slightly frustrating but with NP++ and an the compare plugin
you can move forward stepwise and find the error within reasonable time.
I still don't get how to install Andys editor
(Reinstalled TOAW III and the editor there after but still don't get it)
Anyhow what I was looking for was the meaning of tags in the XML file
Formation is rather selfexplanatory:
<xs:element minOccurs="0" maxOccurs="unbounded" name="FORMATION">
<xs:attribute name="ID" type="xs:unsignedByte" use="optional" />
<xs:attribute name="NAME" type="xs:string" use="optional" />
<xs:attribute name="PROFICIENCY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPLY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPORTSCOPE" type="xs:string" use="optional" />
<xs:attribute name="ORDERS" type="xs:string" use="optional" />
<xs:attribute name="EMPHASIS" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
But I have more problem with Unit:
<xs:element minOccurs="0" maxOccurs="unbounded" name="UNIT">
<xs:complexType>
<xs:attribute name="ID" type="xs:unsignedShort" use="optional" />
<xs:attribute name="NAME" type="xs:string" use="optional" />
<xs:attribute name="ICON" type="xs:string" use="optional" />
<xs:attribute name="ICONID" type="xs:unsignedByte" use="optional" />
<xs:attribute name="COLOR" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SIZE" type="xs:string" use="optional" />
<xs:attribute name="EXPERIENCE" type="xs:string" use="optional" />
<xs:attribute name="CHARACTERISTICS" type="xs:string" use="optional" />
<xs:attribute name="PROFICIENCY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="READINESS" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SUPPLY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="GOINGTOX" type="xs:unsignedByte" use="optional" />
<xs:attribute name="GOINGTOY" type="xs:unsignedShort" use="optional" />
<xs:attribute name="EMPHASIS" type="xs:string" use="optional" />
<xs:attribute name="STATUS" type="xs:unsignedByte" use="optional" />
<xs:attribute name="ENTRY" type="xs:unsignedShort" use="optional" />
<xs:attribute name="REPLACEMENTPRIORITY" type="xs:unsignedByte" use="optional" />
<xs:attribute name="SECONDARYICON" type="xs:string" use="optional" />
<xs:attribute name="X" type="xs:unsignedByte" use="optional" />
<xs:attribute name="Y" type="xs:unsignedShort" use="optional" />
<xs:attribute name="NEXT" type="xs:unsignedShort" use="optional" />
<xs:attribute name="CHARACTERISTICS2" type="xs:unsignedInt" use="optional" />
<xs:attribute name="PARENT" type="xs:unsignedShort" use="optional" />
</xs:complexType>
</xs:element>
CHARACTERISTICS - the bitpattern of the units all equipment capabilities ?
My guess, too.
What is the difference between GOINGTOX and X ?
Position of the unit x/y hex on map
NEXT seems to point to another unit in the same formation but I don't see the logic
Don't have this string in my .OOB dumps.
CHARACTERISTICS2 ???
Linked to the alternate icon, my guess.
PARENT -seems to be the same unit or if the unit are divided ?
YES
Cheers
/John
See above in
bold.
Klink, Oberst
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 6:58 pm
by John T_MatrixForum
ORIGINAL: Lobster
Why are you even using this???? [:D]
The game editor does all of this.
The User interface is as bad as ever but that seems to be by design so you have to live with it
(but it sucks)
First,
What Version of the software do you use?
For me The game editor is not stable (in plain language - does not work)
Sometimes it crashes to desktop,
Cut and paste a formation and the display of what formation a unit belongs to screws up.
I dont trust it and it is simply not in a state of a release candidate for professional software.
Secondly
I load the .gam file into A SQL Server so I can manipulate the OOB.
I working with the WeserUbung 5.2 and added Swedish units from my previous go at Weserubung 4.9
and checked the data from my original try at Weerubung 2.6
And then it is quite convenient to be able to change the unit ID Offset at one place and regenate the OOB.
And then it makes sense to understand how it is implemented.
Cheers
/John T
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 7:12 pm
by Oberst_Klink
ORIGINAL: John T_MatrixForum
ORIGINAL: Lobster
Why are you even using this???? [:D]
The game editor does all of this.
The User interface is as bad as ever but that seems to be by design so you have to live with it
(but it sucks)
First,
What Version of the software do you use?
For me The game editor is not stable (in plain language - does not work)
Sometimes it crashes to desktop,
Cut and paste a formation and the display of what formation a unit belongs to screws up.
I dont trust it and it is simply not in a state of a release candidate for professional software.
Secondly
I load the .gam file into A SQL Server so I can manipulate the OOB.
I working with the WeserUbung 5.2 and added Swedish units from my previous go at Weserubung 4.9
and checked the data from my original try at Weerubung 2.6
And then it is quite convenient to be able to change the unit ID Offset at one place and regenate the OOB.
And then it makes sense to understand how it is implemented.
Cheers
/John T
DO NOT manipulate the .GAM; that's where you sooner or later encounter parsing errors 'en mass! Dump only the .OOB as .OOB extension. Re-importing the .GAM, the OOB or the whole scenario part, I do
NOT advise at all.
Klink, Oberst
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 7:15 pm
by John T_MatrixForum
ORIGINAL: Oberst_Klink
See above in
bold.
Klink, Oberst
[/quote]
Thanks
/John
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 8:23 pm
by Lobster
ORIGINAL: John T_MatrixForum
ORIGINAL: Lobster
Why are you even using this???? [:D]
The game editor does all of this.
The User interface is as bad as ever but that seems to be by design so you have to live with it
(but it sucks)
First,
What Version of the software do you use?
For me The game editor is not stable (in plain language - does not work)
Sometimes it crashes to desktop,
Cut and paste a formation and the display of what formation a unit belongs to screws up.
I dont trust it and it is simply not in a state of a release candidate for professional software.
Secondly
I load the .gam file into A SQL Server so I can manipulate the OOB.
I working with the WeserUbung 5.2 and added Swedish units from my previous go at Weserubung 4.9
and checked the data from my original try at Weerubung 2.6
And then it is quite convenient to be able to change the unit ID Offset at one place and regenate the OOB.
And then it makes sense to understand how it is implemented.
Cheers
/John T
I see. I didn't realize the problem was with your machine. It all works fine for me and I can throw together an OOB with no problems. For me I can place a unit anyplace in an OOB no troubles. Sorry for your problems. Machine dependent bugs suck.
RE: XML Tags descriptions
Posted: Fri Jan 05, 2018 11:26 pm
by John T_MatrixForum
ORIGINAL: Oberst_Klink
DO NOT manipulate the .GAM; that's where you sooner or later encounter parsing errors 'en mass! Dump only the .OOB as .OOB extension. Re-importing the .GAM, the OOB or the whole scenario part, I do NOT advise at all.
Klink, Oberst
I see, thanks for the advice.
So far I only generated parts of a OOB - Formation - Unit - Equipment
And I have to admit it isn't always easy to get it right.
But my favorite movie quote are "I ain't go myself a name being reasonable"
[:)]
/John
RE: XML Tags descriptions
Posted: Mon May 28, 2018 7:50 pm
by 76mm
ORIGINAL: Oberst_Klink
DO NOT manipulate the .GAM; that's where you sooner or later encounter parsing errors 'en mass! Dump only the .OOB as .OOB extension. Re-importing the .GAM, the OOB or the whole scenario part, I do NOT advise at all.
Hi Oberst, just want to make sure I understand your concern with manipulating and re-importing the .gam file--you say never do it?
So far, albeit with rather simple modifications (changing some equipment quantity numbers, the dates, and adding one unit), I haven't encountered any problems with making changes to a scenario .gam file. Is it just a matter of being extremely careful, or is it more complicated than that?
Also, what does the "status" tag indicate for units? From what I've seen so far, values are typically in the 7-9 range.
<UNIT ID="3" NAME="1/2" ICON="Infantry" COLOR="20" SIZE="Regiment" EXPERIENCE="veteran" CHARACTERISTICS="E0002009" PROFICIENCY="81" READINESS="33" SUPPLY="1" X="13" Y="4" EMPHASIS="Minimize Losses" NEXT="9973"
STATUS="9" REPLACEMENTPRIORITY="0">