Search results

From HLKitWiki
Jump to: navigation, search
  • ...le, you can use this [http://www.lonewolfdevel.com/downloads/savage-worlds-test-drive.pdf mirror link].
    9 KB (1,221 words) - 17:08, 2 May 2009
  • ...of developing your data files, there will be times where you want to fully test that everything is working properly. There will also be times when you simp ...ata files, you need to load those changes into Hero Lab so you can use and test them. The simplest way to do this is to go to the "File" menu and select "S
    5 KB (922 words) - 21:17, 17 December 2008
  • Once everything is in place, reload the data files and test everything out. The sample attribute should display as "d4" on the Basics t
    13 KB (2,202 words) - 02:54, 21 January 2009
  • ...reference a trait from a script of some sort (e.g. within a pre-requisite test), be careful to handle it properly. If the trait is a skill or something el .... For situations like this, we need to define an appropriate pre-requisite test that checks the state of the character and reports whether the pre-requisit
    8 KB (1,322 words) - 21:13, 17 December 2008
  • ...ays possess tags for each edge chosen for the character, which we can then test against. ...and pivotal NPCs in the story. We could implement a separate pre-requisite test for each of these edges, but the number is significant and it is much easie
    8 KB (1,275 words) - 21:13, 17 December 2008
  • ...tag. We use an Eval script to assign the behaviors, wrapping them within a test of the activated ability state. This edge also demonstrates the need to car ...lemented as a distinct pre-requisite instead of merging them into a single test. While this is not required, it is a highly recommended approach. The advan
    8 KB (1,295 words) - 21:13, 17 December 2008
  • ...last line of the script as shown below and our changes should be ready to test out. To test your changes, start by using Quick-Reload to reload them into HL, then disp
    6 KB (1,093 words) - 21:12, 17 December 2008
  • The final thing that we need to test on this tab is edges. Add a variety of edges and make sure that the appropr
    9 KB (1,487 words) - 00:35, 11 February 2009
  • ...Since we want to include all arcane backgrounds by default, our Candidate test needs to be designed to exclude things only when certain conditions exist. ...can exempt all edges lacking the tag from our exclusion test. Half of our test is now figured out. Just be sure to open the file "thing_edges.dat" and ass
    15 KB (2,450 words) - 19:19, 27 January 2009
  • ...hey can be managed by the user. We'll also need this new tab to adequately test the additional handling we must still implement for arcane powers.
    3 KB (475 words) - 00:59, 18 December 2008
  • .... Now that we've got the "Arcane" tab in place and working, we can add and test the remaining logic. .... That's a lot of work that we can avoid by writing a single pre-requisite test on the component that is shared by all arcane powers.
    12 KB (1,951 words) - 19:20, 27 January 2009
  • ...t to add our new code. At the end of the "if/then/else" block, we'll add a test for the "Power" component and call our new procedure. The resulting code bl
    9 KB (1,407 words) - 00:04, 23 December 2008
  • After putting the above code into place, we can test our data files. Create a portfolio with a number of different characters in We can now reload the data files and put our changes to the test. If you want to make absolutely sure that the logic is performing the way y
    21 KB (3,532 words) - 01:15, 27 January 2009
  • ...tag if it is less than the linked attribute value, so all we need to do is test against that tag. The only other details we have to make sure differ are th ...t is failed, so all the checks must be performed to ascertain whether each test is satisfied, but it's much easier for us to simply assume success and bail
    13 KB (1,972 words) - 00:08, 23 December 2008
  • ...o eliminate the reference to the usage pool. Change the script so that the test is based on the shaken state and the number of wounds and fatigue levels. T
    17 KB (2,554 words) - 15:39, 19 February 2009
  • ...we also need to convert the rank requirement used within the pre-requisite test for minimum character rank, and the Finalize script won't work for that, so
    6 KB (1,011 words) - 20:11, 29 January 2009
  • ...it's available. Otherwise, we use the the field value. We'll use the same test from earlier to determine which method to employ. The revised Validate scri
    29 KB (4,644 words) - 22:51, 17 February 2009
  • ...or pieces with the non-stacking logic we just implemented, this validation test is not appropriate for us. The validation is performed via the "valArmor" t
    14 KB (2,135 words) - 21:12, 11 February 2009
  • ~Note: The final test below ensures that we only let the user change the domain
    12 KB (1,684 words) - 04:19, 11 February 2009
  • ...uch picks always have their live state resolved immediately after the last test governing their live state - i.e. '''as early as possible'''. However, if a ...hicle. Scrolling down through the task list, we'll find a "Pick Condition" test for the "A6M Zero" pick at a timing of Setup/10000. Just below this task, w
    20 KB (3,315 words) - 21:08, 12 January 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)