Terran Stellar Navy › Forums › (OOC) Division Development › vesselData.xml
- This topic has 11 replies, 5 voices, and was last updated 8 years, 2 months ago by Matsiyan.
-
AuthorPosts
-
24/10/2016 at 05:54 #17141MatsiyanParticipant
I have been rifling through the vesselData.xml
In addition to a few mis-spellings like Hegmony instead of Hegemony and Skarren instead of Skaraan I noticed some vessel entries have apparently damaged entries
The Interceptor class has damage and playerdamage
<vessel uniqueID=”17″ side=”0″ classname=”Interceptor” broadType=”player”>
<beam_port x=”-55.4″ y=”8.3″ z=”215.74″ damage=”0.6″ playerdamage=”6″ arcwidth=”0.4″ cycletime=”4.0″ range=”800″ />
<beam_port x=”55.4″ y=”8.3″ z=”215.74″ damage=”0.6″ playerdamage=”6″ arcwidth=”0.4″ cycletime=”4.0″ range=”800″ />
<beam_port x=”-35.764229″ y=”8.3″ z=”255.250519″ damage=”1″ playerdamage=”10″ arcwidth=”0.1″ cycletime=”4.0″ range=”1100″ />
<beam_port x=” 35.764229″ y=”8.3″ z=”255.250519″ damage=”1″ playerdamage=”10″ arcwidth=”0.1″ cycletime=”4.0″ range=”1100″ />but the IX Lancer (should that be ICX Lancer?) does not (and has the header in a different order than every other vessel which is just a readability issue)
<vessel uniqueID=”25″ broadType=”player” classname=”IX Lancer” side=”0″>
<beam_port x=”-55.4″ y=”8.3″ z=”215.74″ damage=”1″ playerdamage=”6″ arcwidth=”0.4″ cycletime=”4.25″ range=”800″ />
<beam_port x=”55.4″ y=”8.3″ z=”215.74″ damage=”1″ playerdamage=”6″ arcwidth=”0.4″ cycletime=”4.25″ range=”800″ />
<beam_port x=”-35.764229″ y=”8.3″ z=”255.250519″ damage=”10″ arcwidth=”0.1″ cycletime=”4.0″ range=”1100″ />
<beam_port x=” 35.764229″ y=”8.3″ z=”255.250519″ damage=”10″ arcwidth=”0.1″ cycletime=”4.0″ range=”1100″ />Does this mean that Lancer’s range 1100 beams do ten times the damage of other division vessels or does the missing variable inherit its value rom the class type? Is that also why the Lancer never overheats its torpedo tube – because the Interceptor class does not have one?
Also the Escort has her vessel name misspelled
<vessel uniqueID=”29″ broadType=”player” classname=”ES Vengence” side=”0″>
should be
<vessel uniqueID=”29″ broadType=”player” classname=”ES Vengeance” side=”0″>
It is spelled correctly further down.The privateer has missing comments on the torpedo storage types.
Some vessels have a useful comment in the second line of the Classname or vesselname, but many do not.I have an updated version of the file with these readability/consistency issues corrected.
Is the uniqueID used in the sandbox script? If not, it would be helpful to put specific ships immediately after the class definition, or if it affects the order in which they appear for ship customization, then our most frequently used vessels should appear at the end to make selection easier (by using the left arrow).
I would be glad to help out with formatting etc.
I would also love to learn how to run the sandbox. It keeps shutting down on me.
Is there a more appropriate forum for this topic?
Cheers24/10/2016 at 15:51 #17178XavierKeymasterIt is best not to alter unique ids at that will impact the sandbox. Corrections on spellings, descriptions and general formatting is more thab welcome though. Make sure Fish is aware, then he can add it to the next update.
As for running the sandbox, I would be happy to guide you through. It probably shuts down because of the ships you have spawned. If at least one ship with our ship names doesn’t exist, then the Sandbox assumes everything was destroyed and shuts down.
I am almost done re-writing the GM menus now. I just have the AI menu to sort and some testing to do.
Finally, this is the ideal place to post as it is developing the division.
24/10/2016 at 16:21 #17185Jemel EahainModeratorthe damage and player damage are things that changed in the base game in the last update, each ship used to have a damage value for each weapon and thom found that in some simulations when things were cranked up escorts and destroyers had there damage output cranked up with all the enemy and become a bit on the over powered side, so he brought in damage for npc ships and player damage for player side ships, lancer second beams doesn’t look like has been converted properly
24/10/2016 at 18:34 #17215MatsiyanParticipantThank you for explaining the function of damage and playerDamage. That makes sense now. I will carry on tidying up and pass the file on to Fish.
For the sandbox, I did try to get one of the division’s named ships connected, but for some reason it would not take. Does it require more than a main screen and/or Helm?
24/10/2016 at 18:47 #17217XiphParticipantMatsiyan, do you have the correct sandbox version? That was the issue I had. I can’t tell you the current version number however!
24/10/2016 at 18:51 #17221MatsiyanParticipantThanks, Xiph. I thought it was the latest at the time. I will try a fresh download and install.
24/10/2016 at 19:07 #17225XiphParticipantThere’s a link? o.O
I went straight to the horse’s mouth. Or Xavier, as he’s also known.
24/10/2016 at 19:23 #17228MatsiyanParticipantIf I don’t have it on speed dial in my home browser, then there is a link to it in Xavier’s Artemis forum sig 🙂
And now back to lunchtime in the office…
24/10/2016 at 21:43 #17239XiphParticipantAh maybe that doesn’t show on mobile.
24/10/2016 at 21:50 #1724325/10/2016 at 04:01 #17257MatsiyanParticipantThat one seems to be the link from his forum signature which is the waaaay out of date version 3 🙂
Here is the latest one I could find on the forum for TSN Sandbox 4.1
http://artemis.forumchitchat.com/post/tsn-sandbox-v4-1-8276964?highlight=sandbox&pid=129368569125/10/2016 at 05:17 #17262MatsiyanParticipantI have been compiling a condensed reference to current crew assignments (has been useful to Duty Oficers) and vessel capabilities: link to TSN 4LD Vessel Profiles
-
AuthorPosts
- You must be logged in to reply to this topic.