World of Warships

[Coffee]

I like this...
I have 80% of the code done to extract the data.
I'm in the process of writing the code to figure what folder each part points in to.
There are a fiew I dont understand..
these are German items form GSB002_Tirpiz_1942_MidFront_ports.visual but it all relates.
HP_Deck <- no idea
HP_GD <-- think this is Gun Director
HP_GF <- not sure

I think I will create one xml for each ship. Im going to try to create them so I can load them back in as a dataset.
This whay, I can write a tool to edit them very easy.

Code: Select all

<ship name>
  <sections>
     <bow>
          <bow_nodes>
          <\bow_nodes>
     <\bow>
     <midfornt>
          <midfront_nodes>
          <\midfront_nodes>
     <\midfront>
   <\sections>
< ship name>

I think this will work ok because I can read them back in as sub tables from the sections node. May take a little tweeking..

[Wobble]

[out]

[Coffee]

Not sure about the tech tree.. Ill look in a bit.
Hey.. thanks for working with me on this
I getting very close to dumping/creating all the XML files.
There are some issues with name mapping I'm sorting out.
Here is the format I have.. If you think it can be improved.. chime in.
Edit: the files will be fairly large but it will be faster in the long run to edit and parse I think than breaking this in to 4 files per ship.

Code: Select all

<ASA002_Bogue_1942>
  <sections>
    <content/gameplay/usa/ship/aircarrier/ASA002_Bogue_1942/ASA002_Bogue_1942_bow_ports.visual>
      <node>
        <name>HP_AD_2<\name>
        <model>content/gameplay/usa/director/UNKNOWN_ITEM<\model>
      <\node>
      <node>
        <name>HP_AD_1<\name>
        <model>content/gameplay/usa/director/UNKNOWN_ITEM<\model>
      <\node>
      <node>
        <name>HP_AGA_4<\name>
        <model>content/gameplay/usa/UNKNOWN_ITEM<\model>
      <\node>
      <node>
        <name>HP_AGA_3<\name>
        <model>content/gameplay/usa/UNKNOWN_ITEM<\model>

[Wobble]

[out]

[Coffee]

Thanks.. I will change it to look like this.

There are so many odd things.. this may all be a waste of time.
As soon as I get this app done, Ill figure out a way to get it to you than
Im going to work on the model editor to place dummy objects every where there is one base on the port/compound files.
This should help figure out what a lot of these strange named items are.

[Coffee]

Well.. that worked and it passed validation in Dreamweaver

Code: Select all

<ASA003_Bogue_1943.xml>
  <sections>
    <bow>
      <model>usa\ship\aircarrier\ASA003_Bogue_1943\ASA003_Bogue_1943_bow_ports.visual</model>
        <node>
           <name>HP_AD_2</name>
           <model>usa\director\UNKNOWN_ITEM</model>
        </node>
        <node>
           <name>HP_AD_1</name>
           <model>usa\director\UNKNOWN_ITEM</model>
        </node>
        <node>
           <name>HP_AGA_4</name>
           <model>usa\gun\aaircraft\UNKNOWN_ITEM</model>
        </node>
        <node>
           <name>HP_AGA_3</name>
           <model>usa\gun\aaircraft\UNKNOWN_ITEM</model>
        </node>
        <node>
           <name>HP_AGA_1</name>
           <model>usa\gun\aaircraft\UNKNOWN_ITEM</model>
        </node>
        <node>
           <name>HP_AGA_2</name>
           <model>usa\gun\aaircraft\UNKNOWN_ITEM</model>
        </node>
        <node>

Is there some why I could add something to this to lock the file so to speak. or could this be done using subversion?
This is a huge amount of work here and the files need to be safe once they are finished..
Maybe Im thinking to far ahead but these things need to be handled some way.

[Wobble]

[out]

[Coffee]

Yes.. totally open.. But some way to let someone know this file has been worked on.. Was just an idea.
Anyway.. I have this done.. but will fix anything that dosn't work right.
And.. the names .visual or .model doesn't really matter. I never read anything from the .models usually.
Here is a link to get the installer for the app. http://209.159.152.184:8080/WoW/
PLEASE SCAN before running.. I had a bug a few weeks ago but I'm 99.9999999% sure its gone.
I will make the name changes or anything else once I get more feed back.
You have been great at helping!
We need a home for this project.. github or something just so the files can be worked on by anyone that wants too.
Ill look around after I get some coffee made and in my system

[Coffee]

crap. left a file out of the install.. one sec
OK.. that should work ok.. for got to include the damn HELP file lol

[Coffee]

you know.. with a little work, I could make that in to a kick ass editor.
Add a few things like:
A mode setting: EDIT or Create Initial XML
Syntax highlighting.
Load the entire folder back in to the buttons. (I like that kind of UI) Or a single file.
Add some other tools I haven't thought of yet.

Note to self.. Add Save Progress bar!

[Andrakann]

Filled up JSB018_Yamato_1944.xml, also make log with file readings by game for this ship.
Maybe you can use this log in some way (reading sequence can match with nodes sequence).
Log in CSV-format, so can be imported into excel or open office calc - for better readability.

And don't forget about gun upgradeability of most ships in game, guys ;)

PS: Some exclusions:
HP_Fire_Burn - mount point for fire animation.
HP_NoseWave_Speed - same for water waves from ship (?).
HP_Smoke - smoke source point.

[Andrakann]

RSC001_Avrora_1917.xml is done. For other ships is good to have ability to visual comparison with ingame models.
Some mismatch found:
<name>HP_RGM_1</name>
<model>\russia\gun\secondary\RGS001_6in45\RGS001_6in45.primitives</model>
(RGS used as RGM here)

[Andrakann]

Logs for three premium ships (because they not upgradeable) to mess with.
And filter settings, just in case...

[Wobble]

[out]

[Andrakann]

.primitives should only be referenced in .visual files because this is where string name identifiers are located to match up trigs with indices.

Who cares? Game uses server database (most likely), and those xmls never be used in game anyway.
It's only purpose - making database for editor, and format must be comfortable enough to fill by hand and extract within editor.