Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
I'd say this is coming along nicely, I think I am getting the hang of XML. This is certainly easier to learn than C++ was. I will figure out the portals for the new Tab later, but my current plans are to include output for chapter abilities and demeanors here. Might even put the chapter trapping choice up here since it is and essential.
My group has a Black Temp Apothecary who developed a zealous fervor toward his bolt pistol after landing one headshot after another with it against genestealers. This is a player who in a normal 40K game would not roll well, but those low rolls actually mean something in Deathwatch. ------------------------------ Added a couple more progress shots. The six chapters are present now, and I have added all of the 19 Implants that a marine gets, and precluded from the specials tab the ones that give no in-game effect. Last edited by RavenX; July 6th, 2012 at 06:34 AM. Reason: Added a couple more progress shots |
#11 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
Here you can see that I have made some changes to the configuration screen. I figured I could learn a bit more about portals and positioning starting with something smaller. You will notice that there is now a Starting XP edit field to store starting XP. This is important in Deathwatch as space marines typically start with 13,000 xp as a Rank 1 character (they are actually Rank 9 compared to other Warhammer 40,000 Roleplaying characters).
I also got rid of that pesky character points mechanic. To the person who wrote the authoring kit materials, getting rid of the starting cp mechanic was more than a 'couple' changes to track down. I managed to do it but I had to think about it more than usual. I still have a lot of work to do on this data, but it is coming along. |
#12 |
Senior Member
Join Date: Jul 2010
Location: Knoxville, Tn
Posts: 126
|
Looking forward to seeing this in use!
|
#13 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
|
#14 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
Got it fixed, just have to clean up the output of the headers now.
Last edited by RavenX; July 11th, 2012 at 05:38 AM. Reason: problem solved. |
#15 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
What you need is a sortset which organizes things according to the tags associated. For example, here is the one we use for Races.
<sortset id="Race" name="Race"> <sortkey id="RaceType"/> <sortkey isfield="yes" id="rRacePoint"/> <sortkey id="_Name_"/> </sortset> Things are sorted by the criteria, from top to bottom. So all things with the same RaceType tag are sorted together, and then within those groups they are sorted according to the value of the rRacePoint field, and when that is done any ties are sorted alphabetically by name. To control the order that the racetype tag groups are listed, you set that when defining the tag group. <group id="RaceType" width="7" visible="yes" sequence="explicit"> <value id="Normal" order="10"/> <value id="Custom" name="Custom Built Race" order="13"/> <value id="Feature" name="Featured Race" order="15"/> <value id="Extra" name="Uncommon Race" order="18"/> <value id="MonstClass" name="Monster Class" order="20"/> <value id="NPC" name="NPC Race" order="20"/> <value id="Animal" name="Minion" order="20"/> <value id="Companion" name="Animal Companion" order="30"/> <value id="Eidolon" order="35"/> </group> sequence="explicit" means we intend to set the order explicitly, which we do with the "order" element for each tag. So you can see those with the RaceType.Normal are listed first at 10, then Custom races at 13, and then Featured Races at 15 and so on. Can you take it from there? |
#16 |
Senior Member
Join Date: Oct 2011
Posts: 6,793
|
One last thing, you set the sortset in the portal:
<portal id="Whatever" style="VerySilly" width="blimplike" roles="createpies"> <chooser_table component="Whatever" choosetemplate="Whatever" descwidth="Whatever" candidatepick="Whatever" candidatefield="Whatever" choosesortset="YOURSORTSETHERE" showupdate="Whatever"> choosesortset="YOURSORTSETHERE" is the important bit |
#17 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
I think I can handle this, thank you for the assistance Aaron. Much Appreciated.
|
#18 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
Thanks, Aaron, I was missing one line of code, I had the rest in place already. So now it works. I was missing the "choosesortset=" part.
I still need to clean up the headers so they only show the header name, but everything else is working good now. |
#19 |
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2011
Location: Nowhere, Virginia
Posts: 3,633
|
Another Question for you, on the image attached, I have highlighted something that I am having a hard time figuring out.
How is that the Damage Rating and Net attack values show up on the weapon after it is selected by the user, but not in the actual selection portal? |
#20 |
|
|