Page 7 of 7 FirstFirst ... 34567
Results 241 to 269 of 269
  1. #241
    Annihilator
    Join Date
    Apr 2008
    Location
    Wherever the hilarity is
    Posts
    904

    Default

    It's been a while since the last update. Is this program still being worked on?
    Quote Originally Posted by Brandubh View Post
    For Captain Orboros, heart isn't an element...it's dinner.

  2. #242

    Default

    I was just wondering about this myself, I can't access his links at all.

  3. #243
    Warrior
    Join Date
    Oct 2004
    Location
    Dayton, OH
    Posts
    40

    Default

    Quote Originally Posted by LifeshifterX View Post
    I was just wondering about this myself, I can't access his links at all.
    Links all work for me.

  4. #244
    Annihilator Sebi's Avatar
    Join Date
    Apr 2012
    Location
    Bayreuth, Germany
    Posts
    729

    Default

    Will there be an update for SR13 or is this project/programm discontinued?

  5. #245
    Conqueror Sycak's Avatar
    Join Date
    Feb 2012
    Location
    Joliet, IL
    Posts
    275

    Default

    Think I am understanding how to create the Theme Force Lists. What is the proper coding when referencing a Immune:Electricity model?
    __________________________________________________ _________
    Tony
    Trollbloods/Cygnar/Skorne/Convergence of Cyriss

  6. #246
    Conqueror Sycak's Avatar
    Join Date
    Feb 2012
    Location
    Joliet, IL
    Posts
    275

    Default

    Got it figured out....

    Nevermind...
    Last edited by Sycak; 01-30-2013 at 08:49 AM.
    __________________________________________________ _________
    Tony
    Trollbloods/Cygnar/Skorne/Convergence of Cyriss

  7. #247
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Sorry all.

    I've been away from the forums awhile dealing with work.
    It seems I missed an NQ and the new SR document.
    I'll try to get a hold of a copy of the NQ and read the SR document asap and get the program up to date.

  8. #248
    Annihilator
    Join Date
    Apr 2008
    Location
    Wherever the hilarity is
    Posts
    904

    Default

    Quote Originally Posted by LostBlue View Post
    Sorry all.

    I've been away from the forums awhile dealing with work.
    It seems I missed an NQ and the new SR document.
    I'll try to get a hold of a copy of the NQ and read the SR document asap and get the program up to date.
    Thanks, man. Glad to see this is still going strong.

    For reference, you've missed NQ 45 and 46. If you can't find NQ 45, I can shoot you a PM with what's in there.
    Quote Originally Posted by Brandubh View Post
    For Captain Orboros, heart isn't an element...it's dinner.

  9. #249
    Annihilator
    Join Date
    Jun 2011
    Location
    Wollongong, Australia
    Posts
    826

    Default

    through the magic of war-room I can send you any details you need from either. Also HURRAY!

  10. #250
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    I finally got both NQs.
    I should have the models from these NQs in by Monday.

    The next update will include these models plus the league models and 3rd Jack Marshal limit for the Coven's tier (since the code already exists in the program but the logic isn't ported to the script engine yet).

    SR 2013 support will come at a later date. After reading the PDF, there are both a specialist and a reinforcement variant. The restrictions on reinforcement are slightly different from SR 2012. To properly support both Specialist and Reinforcement SR 2013 style in a way it's compatible with past and future versions, I'm going to do a major overhaul in the logic.

    BTW Question: How many models that cannot start the game in play? This is relevant to SR2013 version of Reinforcements.
    The ones I can think off top of my head are:
    • Thrall Warriors (Alexia/Mercenary)
    • Incubus (Legion)
    • Lightning Pods (Stormwall/Cygnar) - except technically in Artificer General Nemo's Theme Army: Lightning War/T2 can

    Are there any other models?


    Quote Originally Posted by tort View Post
    through the magic of war-room I can send you any details you need from either. Also HURRAY!
    Sorry, I didn't see this until now.
    I also have the full version of War Room, but I still do not consider it a reliable source of information. While it has gotten much better since its initial release, I still feel it needs a long ways to go. There are still far too many errors for my tastes to accept the data at face value with models I can't check with another official medium.
    Last edited by LostBlue; 02-22-2013 at 10:57 AM.

  11. #251
    Annihilator
    Join Date
    Apr 2008
    Location
    Wherever the hilarity is
    Posts
    904

    Default

    Quote Originally Posted by LostBlue View Post
    • Thrall Warriors (Alexia/Mercenary)
    • Incubus (Legion)
    • Lightning Pods (Stormwall/Cygnar) - except technically in Artificer General Nemo's Theme Army: Lightning War/T2 can

    Are there any other models?
    Skorne's Kovaas, I believe.
    Quote Originally Posted by Brandubh View Post
    For Captain Orboros, heart isn't an element...it's dinner.

  12. #252
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    A new build is up today.

    This can be downloaded from my SkyDrive:
    http://cid-f4e58cf9dec68c8e.office.l...eation%20Tools

    Here is a troubleshoot FAQ for any who are having trouble installing the program:
    http://lostblueskies.comze.com/FCU/TroubleShoot.html

    SR2012 Character Checker for mk II- fcu (Directions)
    https://skydrive.live.com/?cid=f4e58...9DEC68C8E!1209

    Web Tutorial: "How to make Contracts in mk II - FCU" (updated: 2013-02-25)
    http://lostblueskies.comze.com/FCU/T.../tutorial.html

    Temp User Manual for mk II - FCU
    http://lostblueskies.comze.com/FCU/UserManual.html

    Overview of changes:

    ---------------
    v2.3 Beta, Build 20130225
    ---------------
    * Bugs and Typo fixes

    * Added Models from NQ45
    - Warpborn Alpha (Circle Unit Attachment)
    - Archangel (Legion Gargantuan)
    - Rask (Minion Bog Trog Warlock)
    - Valent Thrace (Scenario Model: Defenders of Thrace)
    - Ancient Satyr (Scenario Model: Defenders of Thrace)
    - Molgur Shaman Unit (Scenario Model: Defenders of Thrace)
    - Molgur Savages (Scenario Model: Defenders of Thrace)
    - Tharcian Militia (Scenario Model: Defenders of Thrace)

    * Added Models from NQ46
    - Mammoth (Skorne Gargantuan)
    - Mortitheurge Willbreaker (Skorne Solo)
    - Afflictor (Legion Light Warbeast)
    - Warspear Chieftain (Legion Blighted Ogrun Unit Attachment)
    - Razor Boar (Minion Farrow Lesser Warbeast)
    - Vayne Di Brascio (Scenario Model: Patriot's Crucible)
    - Iron Fang Honor Guard (Scenario Model: Patriot's Crucible)
    - Colonel Killian D'Glaeys (Scenario Model: Patriot's Crucible)
    - Llaelese Militia (Scenario Model: Patriot's Crucible)
    - Lord Benoir D'Elyse (Scenario Model: Patriot's Crucible)
    - Kovnik Fedor Grishka (Scenario Model: Patriot's Crucible)

    * Added Models from Machinations Umbra
    - The Enigmatic Artifact (Machinations Objective)
    – Battle-Tainted Centurion (Cygnar Heavy Warjack)
    - Possessed Sanctifier (Protectorate Heavy Warjack)
    - Ruptured Berserker (Khador Heavy Warjack)
    - Crimson Harrower (Cryx Helljack)
    - Experimental Manticore (Retribution Heavy Warjack)
    - Ghost Ship Mariner (Mercenary Heavy Warjack)
    - Emaciated Dire Troll Mauler (Trollbloods Heavy Warbeast)
    - Nightmare Shadowhorn Satyr (Circle Heavy Warbeast)
    - Infectious Titan Gladiator (Skorne Heavy Warbeast)
    - Scythean Duskstalker (Legion Heavy Warbeast)
    - Nightshade Swamp Horror (Minions Heavy Warbeast)

    * New Feature: If a model is a scenario or league model, the TYPE column for that model will now be highlighted light brown and have a ! in front of the type

    Sample Image


    * New Feature: Theme List can now modify the 'Jack Marshal limit of models as a Theme Force Benefit
    HTML Code:
    Change the 'Jack Marshal Limit
    
        Usage:
        <Benefit special="Edit">JackMarshalLimit:[search item]:Replace:[value]</Benefit>
    
    This command replaces the 'Jack Marshal limit with the new value.
    For [search item], input the criteria of which models this should apply to.
    For [value], input a integer number greater or equal to zero.
    
        Example: Witch Coven of Garlghast's Theme Army: Machine Minds, Tier 1
        Iron Lich Overseers can 'Jack Marshal up to 3 warjacks instead of just 2.
        <Benefit special="Edit">JackMarshalLimit:Iron Lich Overseer + Solo:Replace:3</Benefit> 

    Enjoy!

  13. #253
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    I think I'm caught up model wise and FCU should be able to cover all current theme forces and league/scenario combinations.
    If there is something missing please let me know.

    If there are any questions with theme force creation, please ask.
    I will help you within the limits of this forum.

    I know there are a few items (such as support for SR2013 specialists and new reinforcements rules) and a few from PMs I've received. I'll get to those as soon as possible.


    Quote Originally Posted by vagabondaeon View Post
    Skorne's Kovaas, I believe.
    Thanks!

  14. #254
    Conqueror Mogote's Avatar
    Join Date
    Sep 2012
    Location
    On top of a lonely mountain, in the middle of a frozen desert, dreaming of a beach.
    Posts
    150

    Default

    I have to say I use this utility weekly and appreciate you updating it (and PP for letting it exist). I've been modifying the XML code myself to keep up with releases for my faction but your changes are much cleaner This is seriously a GREAT tool.

    Edit: Looks like the Warspear Chieftain cannot be added to the unit? Also he's listed as a solo instead of being a UA.

    Edit Edit: Yup, I switched <Type requires="Blighted Ogrun Warspears">Solo</Type> to <Type requires="Blighted Ogrun Warspears">UA</Type> and it works again.
    Last edited by Mogote; 03-13-2013 at 04:21 PM.

  15. #255
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Quote Originally Posted by Mogote View Post
    Edit: Looks like the Warspear Chieftain cannot be added to the unit? Also he's listed as a solo instead of being a UA.
    Ah, my bad. I'll change this with the next update.

  16. #256
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    A new build is up today.

    This can be downloaded from my SkyDrive:
    http://cid-f4e58cf9dec68c8e.office.l...eation%20Tools

    Here is a troubleshoot FAQ for any who are having trouble installing the program:
    http://lostblueskies.comze.com/FCU/TroubleShoot.html

    SR2012 Character Checker for mk II- fcu (Directions)
    https://skydrive.live.com/?cid=f4e58...9DEC68C8E!1209

    Web Tutorial: "How to make Contracts in mk II - FCU" (updated: 2013-02-25)
    http://lostblueskies.comze.com/FCU/T.../tutorial.html

    Temp User Manual for mk II - FCU
    http://lostblueskies.comze.com/FCU/UserManual.html

    Overview of changes:

    ---------------
    v2.3 Beta, Build 20130318
    ---------------
    Fixed: Improved Tooltip logic
    Fixed: Warspear Chieftain (Legion Unit Attachment) was marked as a solo
    - Thank you, Mogote!
    Fixed: Typos
    Added: Models from HORDES: Gargantuans
    Added: Tempest Blazers (Cygnar Light Cavalry Unit)


    Enjoy!

  17. #257
    Annihilator
    Join Date
    Apr 2008
    Location
    Wherever the hilarity is
    Posts
    904

    Default

    Still awesome. Thanks once again for keeping this program alive, LostBlue.
    Quote Originally Posted by Brandubh View Post
    For Captain Orboros, heart isn't an element...it's dinner.

  18. #258
    Annihilator Ogrob's Avatar
    Join Date
    Nov 2009
    Location
    Gothenburg, Sweden
    Posts
    863

    Default

    Hey, thanks for the continued work on this!

    I noticed in the new build that Gun Mages don't seem to work in Highborn Coveneant. They are simply listed as FA0 and I can't add them to my forces. Long Gunners work. Just to be clear, I'm not trying to add Gun Mages to a list that has Long Gunners, they don't seem to be addable to empty lists or lists with just the caster selected.

  19. #259
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Quote Originally Posted by Ogrob View Post
    Hey, thanks for the continued work on this!

    I noticed in the new build that Gun Mages don't seem to work in Highborn Coveneant. They are simply listed as FA0 and I can't add them to my forces. Long Gunners work. Just to be clear, I'm not trying to add Gun Mages to a list that has Long Gunners, they don't seem to be addable to empty lists or lists with just the caster selected.
    Shoot. I know what the problem is. I updated the nick value for the Gun Mages to fit the scheme I'm using for other models.


    IMPORTANT UPDATE for Mercenary Players!
    If Gun Mages cannot be added to your Highborn lists...
    Goto the Mercenaries.xml file in your contract folder.

    Replace the Highborn Contract with the following:
    HTML Code:
      <Contract> <!-- Highborn Covenant -->
        <Name>Highborn Covenant</Name>
    	<ID>Highborn Covenant</ID>
        <Notes>Mercenary Contract: An army constructed under the Highborn Covenant contract can include any mercenary models/units that will work for Cygnar. The army can also include one Arcane Tempest Gun Mage unit or Long Gunner unit. This unit is considered to be a friendly Mercenary unit instead of a Cygnar unit and can include attachments.
    	
    Special Rules:
    * Solos in this army gain Advance Deployment. </Notes>
        <IconFile>highborn.gif</IconFile>
        <Restriction>
            <Faction>Cygnar, Minion</Faction>
            <Only></Only>
            <Include></Include>
            <Exclude></Exclude>
            <Extra special="FieldOfficer">Arcane.Tempest.GunMage, LongGunner:Contract</Extra>
    	<Extra special="FieldOfficer">Arcane.Tempest.GunMage_UA, LongGunner_UA:Contract</Extra>
    	<Extra special="FieldOfficer">Arcane.Tempest.GunMage_WA, LongGunner_WA:Contract</Extra>
    	<Extra special="Contracted">Long Gunner Infantry + Unit + Unnamed:0</Extra>
    	<Extra special="Contracted">Arcane Tempest Gun Mage + Unit + Unnamed:0</Extra>
        </Restriction>
      </Contract>
    Sorry for the inconvenience. Because I believe most people using the custom contract options, I can't make a universal change with an update to correct this.

  20. #260
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Quote Originally Posted by Paladin1127 View Post
    Is there any thing I could do to help, I would love to see theme armies able to be made. I'm not able to create theme specific armies like pCain's sons of the tempest
    All current theme forces can be created in FCU.

    To create theme forces, you will need to read this:
    Web Tutorial: "How to make Contracts in mk II - FCU" (updated: 2013-02-25)
    http://lostblueskies.comze.com/FCU/T.../tutorial.html

    Unfortunately since Privateer Press specifically asked me to remove all theme lists from FCU, I cannot post the code for all theme lists.

    To help people better understand Theme Force creation, I'll use "Caine's Sons of the Tempest" Contract as an example.

    • The first thing you need to do is find your Faction in the Contract folder.
      In this case it will be the Cygnar.xml. Open this file with a text editor and place this blank contract template.
      HTML Code:
        <Contract> 
      	<Name></Name>
      	<ID></ID>
      	<Notes></Notes>
      	<IconFile></IconFile>
      	<Details></Details>    
      	<Restriction>
      		<Faction></Faction>
      		<Only></Only>
      		<Include></Include>
      		<Exclude></Exclude>
      		<Extra></Extra>
      	</Restriction>
        </Contract>
      This structure tells FCU the basic list structure and model list expected for the Contract.
    • Let's fill this Contract.
      I placed some comments (those things in the <!-- -->). You can ignore these for the actual list creation. These are only there to help you understand what each tag is doing.

      HTML Code:
        <Contract> 
      	<Name>Sons of the Tempest (Lieutenant Allister Caine)</Name>  <!-- (1) -->
      	<ID>Sons of the Tempest (Lieutenant Allister Caine)</ID> <!-- (2) -->
      	<Notes> <!-- Enter some notes --> </Notes>
      	<IconFile>cygnar.gif</IconFile>
      	<Details> <!-- Optional Notes. Not too important --> </Details>    
      	<Restriction>
      		<Faction></Faction> <!-- (3) -->
      		<Only> <!-- (4) -->
      		Lieutenant Allister Caine, 
      		Cygnar + FactionWarjack + y[Gun] + Unnamed, Lancer + FactionWarjack, 
      		Arcane Tempest + Unit,
      		Arcane Tempest + Solo
      		</Only>
      		<Include></Include> <!-- (5)  -->
      		<Exclude></Exclude> <!-- (6) -->
      		<Extra></Extra> <!-- (7) -->
      	</Restriction>
        </Contract>
      1. <Name> - This is the name of the list that is displayed in FCU
      2. <ID> - This is the ID used by save files to identify what rules to use. You don't want to change this after you decide on the ID because when you load an army, if FCU can't find corresponding ID then it can't load your army.
      3. <Faction> - Tells FCU to look up additional model databases. Since this theme list is only using Cygnar models, there is no need to add any more factions here. Leave this blank for this theme list.
      4. <Only> - This narrows down the choice of models by using the Text Filter function in FCU. We want to narrow down the options so FCU does not load all the models in the Cygnar model database. See the tutorial for more info.
      5. <Include> - This forces additional models into the list that will override the conditions set in <Only>. For this theme list, there aren't any exceptions so we can leave this blank.
      6. <Exclude> - This forces any models that 100% must be excluded from the list. The only time we need to fill this if there is an exceptional case that the <Only> or <Include> could not filter like with the case with Cephalyx Cryx Allies. There are no models like this in this theme list so we can leave this blank. This tag is only used for rare exceptions. For the most part this tag is usually left blank.
      7. <Extra> - Last we have the extra rule tag.
        For the most part this tag should only be filled for these two cases:
        1) Special rules that need to be applied outside of Theme Forces requirements
        2) Reset universal values modified by FCU such as universal FA/PC when a higher tier are achieved. Resets are necessary for these cases if for some reason the list goes back to a lower tier. (ie drops from T4 -> T2)

        For this particular theme list...
        1) There isn't any special rules we need to load that isn't theme force related.
        2) This theme list doesn't have values which need to be reset by achieving higher tiers.

        Thus we can leave <Extra> blank.


    This is the basic Contract setup. When this is properly filled, it will load all the necessary models you have instructed FCU to do.
    But we're not done yet. We need to set the rules for checking the Tier requirements.
    I'll continue explaining the Theme List bonuses in the next post.
    Last edited by LostBlue; 03-19-2013 at 09:52 AM.

  21. #261
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Applying Theme Force benefits (continuing from the Caine's Sons of the Tempest example above).

    • To apply Theme Force benefits we need to add the <Tier> tag to the existing list after the </Restriction> closing tag.
      The <Tier> tag tells FCU how to check for Theme Force requirements and what special rules to apply when these requirements are met.

      1. Under the <Tier> tag, we need to add the four <Level> tags with a class attributes. Each class should have a numeric value corresponding to the tier level.
      2. Under each <Level> tag, we need a <Requirement>, <Benefit>, and <Text> tags.

        <Requirement> tells FCU what to check for.
        <Benefit> tells FCU what special rules to apply if all <Requirement> tags are met for this <Level> is met.
        What you write within the <Text> tag displays in FCU. This is useful to display benefits that don't modify list building rules, such has giving units stealth for a limited time.


      Once you enter all the tags mentioned, you should end up with this:
      HTML Code:
        <Contract> 
      	<Name>Sons of the Tempest (Lieutenant Allister Caine)</Name>
      	<ID>Sons of the Tempest (Lieutenant Allister Caine)</ID>
      	<Notes> <!-- Enter some notes --> </Notes>
      	<IconFile>cygnar.gif</IconFile>
      	<Details> <!-- Optional Notes --> </Details>    
      	<Restriction>
      		<Faction></Faction>
      		<Only>
      		Lieutenant Allister Caine, 
      		Cygnar + FactionWarjack + y[Gun] + Unnamed, Lancer + FactionWarjack, 
      		Arcane Tempest + Unit,
      		Arcane Tempest + Solo
      		</Only>
      		<Include></Include>
      		<Exclude></Exclude>
      		<Extra></Extra>
      	</Restriction>
      	<Tier>
      		<Level class="1">
      			<Requirement></Requirement>
      			<Benefit></Benefit>
      			<Text></Text>
      		</Level>
      		<Level class="2">
      			<Requirement></Requirement>
      			<Benefit></Benefit>
      			<Text></Text>
      		</Level>
      		<Level class="3">
      			<Requirement></Requirement>
      			<Benefit></Benefit>
      			<Text></Text>
      		</Level>
      		<Level class="4">
      			<Requirement></Requirement>
      			<Benefit></Benefit>
      			<Text></Text>
      		</Level>
      	</Tier>
        </Contract>
    • Let's fill out <Tier>.
      Note: I will not be filling out the <Text> tag.

      1. Let's look at T1 for "Sons of the Tempest"
        HTML Code:
        		<Level class="1">
        			<Requirement></Requirement>
        			<Benefit special="FA:#">U:Arcane Tempest Gun Mages + FactionUnit + Unnamed</Benefit>
        			<Benefit special="PC">-:1:Arcane Tempest Gun Mages + FactionUnit:Contract</Benefit>
        			<Text> <!-- Text description of the benefits omitted --> </Text>
        		</Level>
        1. <Requirement>
          For most theme forces, we do not need to fill out the requirement for T1 as the basic contract setup should already limit the model choices.

          We can leave this blank.
        2. <Benefit>
          There are two benefits for Tier 1. Making a unit FA:U and reducing the PC value of a unit.
          Each benefit should be listed in its own tag. The details of each command in <Benefit>/<Extra> are explained in the tutorial.

          To change the FA we use <Benefit special="FA:#">.
          "FA:#" takes in the two parameters. The first parameter takes in the new FA value of "U". The second parameter tells FCU what models have this new FA value. The second parameter works as if you are entering a search term in the Text Filter function.

          To change the PC we use <Benefit special="PC">.
          "PC" has four parameters.
          1. The 1st parameter is the operator. This tells FCU to subtract the value by entering "-".
          2. The 2nd parameter is the numeric value. This tells FCU how much to value is reduced by.
          3. The 3rd parameter is the search term. This tells FCU which models this reduction is applied to. The parameter works as if you are entering a search term in the Text Filter function.
          4. The last parameter is required model which triggers this reduction. The parameter works as if you are entering a search term in the Text Filter function.

          The last parameter might be a bit confusing as "Contract" is entered. Let me explain the last parameter in more detail. The last parameter checks how many triggering models are in the list. This tells FCU to repeat the reduction for each model that satisfy the condition. For example, instead of "Contract" we inputted "Solo", then for each Solo FCU finds in the list FCU will reduce the PC of the models that satisfy the 3rd parameter. If there are 2 solos in the list, then the 3rd parameter models will have (-1x2) reduction in cost.

          Most theme forces, there isn't a model that is check for this condition. This is the case with Sons of the Tempest theme force. Since there is no applicable model to put in the 4th parameter, we enter Contract instead.

          Contract is a "fake" model that is automatically generated in the background of FCU.
          There is always a single fake contract model for whenever a list is created. Since there is only 1 Contract model, the PC here is only reduced once. The fake contract model is useful to apply special rules that can only be applied once in the Contract regardless of other conditions.

      2. Let's look at T2 for "Sons of the Tempest"

        To achieve this tier we need to check some requirements.
        All requirements have 3 parameters:

        1. The first parameter is the search item criteria. This works the exactly as the Text Filter tool.
        2. The second parameter is the command which tells FCU what to do with the filtered text.
        3. The last parameter is the requirement which FCU uses to exam the data.


        Each requirement that needs to be checked should be in its own <Requirement> tag. This is listed in detail in the tutorial.

        T2 for Sons of the Tempest only has 1 requirement: Minimum of 2 Arcane Tempest Gun Mages units.
        When this is satisfied a free model can be added.

        To do this, we enter the following:
        HTML Code:
        		<Level class="2">
        			<Requirement>Arcane Tempest Gun Mages + FactionUnit:Min:2</Requirement>
        			<Benefit special="Free">Arcane Tempest Gun Mage + FactionUA</Benefit>
        			<Text> <!-- Text omitted --> </Text>
        		</Level>
      3. T3 and T4 of Sons of the Tempest do not have benefits that modify any army construction rules.
        For these cases, the <Benefit> tag should be left blank since FCU doen't apply rules that are not related to army construction. You can write the details of these benefits in the <Text> for your reference.

        To check the requirements:

        T3 requires a minimum number of warjacks
        HTML Code:
        <Requirement>FactionWarjack:Min:3</Requirement>
        T4 requires a certain unit.
        HTML Code:
        <Requirement>Black 13th Gun Mage Strike Team:Min:1</Requirement>
      4. The final result should look like this:
        HTML Code:
          <Contract> 
        	<Name>Sons of the Tempest (Lieutenant Allister Caine)</Name>
        	<ID>Sons of the Tempest (Lieutenant Allister Caine)</ID>
        	<Notes> <!-- Enter some notes --> </Notes>
        	<IconFile>cygnar.gif</IconFile>
        	<Details> <!-- Optional Notes. Not too important --> </Details>    
        	<Restriction>
        		<Faction></Faction>
        		<Only>
        		Lieutenant Allister Caine, 
        		Cygnar + FactionWarjack + y[Gun] + Unnamed, Lancer + FactionWarjack, 
        		Arcane Tempest + Unit,
        		Arcane Tempest + Solo
        		</Only>
        		<Include></Include>
        		<Exclude></Exclude>
        		<Extra></Extra>
        	</Restriction>
        	<Tier>
        		<Level class="1">
        			<Requirement></Requirement>
        			<Benefit special="FA:#">U:Arcane Tempest Gun Mages + FactionUnit + Unnamed</Benefit>
        			<Benefit special="PC">-:1:Arcane Tempest Gun Mages + FactionUnit:Contract</Benefit>
        			<Text> <!-- Text omitted --> </Text>
        		</Level>
        		<Level class="2">
        			<Requirement>Arcane Tempest Gun Mages + FactionUnit:Min:2</Requirement>
        			<Benefit special="Free">Arcane Tempest Gun Mage + FactionUA</Benefit>
        			<Text> <!-- Text omitted --> </Text>
        		</Level>
        		<Level class="3">
        			<Requirement>FactionWarjack:Min:3</Requirement>
        			<Benefit></Benefit>
        			<Text> <!-- Text omitted --> </Text>
        		</Level>
        		<Level class="4">
        			<Requirement>Black 13th Gun Mage Strike Team:Min:1</Requirement>
        			<Benefit></Benefit>
        			<Text> <!-- Text omitted --> </Text>
        		</Level>
        	</Tier>
          </Contract>


    I hope people will find this example useful when creating theme forces in FCU.
    If there is any specific questions please ask.
    Last edited by LostBlue; 03-19-2013 at 11:25 AM.

  22. #262
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    A new build is up today.

    This can be downloaded from my SkyDrive:
    http://cid-f4e58cf9dec68c8e.office.l...eation%20Tools



    This build fixes the Gun Mage issue in Highborn Coveneant.
    This fix is only for default contract included with FCU.

    This will NOT fix the issue if you are using custom contracts.
    To fix the issue with your custom contract...
    • Goto the Mercenaries.xml file in your contract folder.
    • Replace the Highborn Contract with the following:
      HTML Code:
        <Contract> <!-- Highborn Covenant -->
          <Name>Highborn Covenant</Name>
      	<ID>Highborn Covenant</ID>
          <Notes>Mercenary Contract: An army constructed under the Highborn Covenant contract can include any mercenary models/units that will work for Cygnar. The army can also include one Arcane Tempest Gun Mage unit or Long Gunner unit. This unit is considered to be a friendly Mercenary unit instead of a Cygnar unit and can include attachments.
      	
      Special Rules:
      * Solos in this army gain Advance Deployment. </Notes>
          <IconFile>highborn.gif</IconFile>
          <Restriction>
              <Faction>Cygnar, Minion</Faction>
              <Only></Only>
              <Include></Include>
              <Exclude></Exclude>
              <Extra special="FieldOfficer">Arcane.Tempest.GunMage, LongGunner:Contract</Extra>
      	<Extra special="FieldOfficer">Arcane.Tempest.GunMage_UA, LongGunner_UA:Contract</Extra>
      	<Extra special="FieldOfficer">Arcane.Tempest.GunMage_WA, LongGunner_WA:Contract</Extra>
      	<Extra special="Contracted">Long Gunner Infantry + Unit + Unnamed:0</Extra>
      	<Extra special="Contracted">Arcane Tempest Gun Mage + Unit + Unnamed:0</Extra>
          </Restriction>
        </Contract>


    I'm really sorry for this bug.

  23. #263

    Default

    This is great. Thank you for this project.

  24. #264
    Annihilator Sebi's Avatar
    Join Date
    Apr 2012
    Location
    Bayreuth, Germany
    Posts
    729

    Default

    Thanks a lot.

  25. #265
    Annihilator
    Join Date
    Jun 2011
    Location
    Wollongong, Australia
    Posts
    826

    Default

    Question about the Midas theme force - how do you get him to take boneswarms? - also is there a way to choose the free warbeast? It makes a difference since it starts the game destroyed. So far I'm just using reinforcements and that works for me but if there is a better solution I'll do that.

  26. #266
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Quote Originally Posted by tort View Post
    Question about the Midas theme force - how do you get him to take boneswarms? - also is there a way to choose the free warbeast? It makes a difference since it starts the game destroyed. So far I'm just using reinforcements and that works for me but if there is a better solution I'll do that.
    Currently, there is no way for the user to choose which model gets the free bonus. I'll add this feature.

    I was going to post a solution to adding Boneswarms in Midas' battlegroup, but after re-reading the rules for Midas theme force, I realize a flaw in my logic. The solution I was going to post is similar to the solution used for Vanguards in Zerkova's theme list which used the Edit command to solve this situation. However, rereading Midas theme list, this will have a problem at t4 as Boneswarms can't be one of the free warbeasts choices since Boneswarms are not Farrow Warbeasts. I will need to write some code to cover this situation.

    If you don't mind an incomplete way to do this:
    HTML Code:
    <Benefit special="Edit">Subtitle:Boneswarms + FactionWarbeast:Gatorman:Gatorman Farrow</Benefit>
    <Benefit special="Edit">BaseUnit:Boneswarms + FactionWarbeast::Midas</Benefit>
    This will allow Midas to add Boneswarms in her battlegroup.
    We need that second line to prevent Rorsh from adding Boneswarms to his battlegroup.
    But again, this will also allow at t4 to make Boneswarms an eligible free model. - I will add code to prevent this.


    Neither of these are difficult to add so I'll probably add them in by the next update.
    Last edited by LostBlue; 03-26-2013 at 08:46 PM.

  27. #267
    Annihilator
    Join Date
    Jun 2011
    Location
    Wollongong, Australia
    Posts
    826

    Default

    Something weird is happening with the Lylyth theme force so I'm going to bug you about it. Specifically the tier 4 benefit. When I use
    <Benefit special="Free">-:0:Lesser + FactionWarbeast:Archangel + FactionWarbeast</Benefit>
    I get three free lessers for every archangel. And when I use:
    <Benefit special="Free">-:0:Lesser + FactionWarbeast(Lylyth, Reckoning Of Everblight):Archangel + FactionWarbeast</Benefit>
    or
    <Benefit special="Free">-:0:Lesser + FactionWarbeast(Lylyth):Archangel + FactionWarbeast</Benefit>
    I get no free lessers.

  28. #268
    Destroyer of Worlds LostBlue's Avatar
    Join Date
    Jan 2005
    Location
    SoCal
    Posts
    3,054

    Default

    Quote Originally Posted by tort View Post
    Something weird is happening with the Lylyth theme force so I'm going to bug you about it. Specifically the tier 4 benefit. When I use

    I get three free lessers for every archangel. And when I use:
    <Benefit special="Free">-:0:Lesser + FactionWarbeast(Lylyth, Reckoning Of Everblight):Archangel + FactionWarbeast</Benefit>
    or
    <Benefit special="Free">-:0:Lesser + FactionWarbeast(Lylyth):Archangel + FactionWarbeast</Benefit>
    I get no free lessers.
    Bug confirmed.
    I'll get this fixed with the next update.

  29. #269
    Annihilator
    Join Date
    Jun 2011
    Location
    Wollongong, Australia
    Posts
    826

    Default

    Something you might not be aware of that is easier to fix, Spell Martyrs have been errata'ed so now they are FA 3 and you only buy one (instead of FA 1 and you buy up to 3).

Page 7 of 7 FirstFirst ... 34567

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •