Simon
Apr 1st, '03, 05:33 AM
Update 1.25 is now available for download.
The only changes in this update are formatting enhancements to bring the output from the app closer to the Writer's Guidelines.
Of particular note are some changes to the Disadvantages. These should not affect any existing character files....but when creating new Disads, the formatting is going to be a bit different.
For the most part, the changes to the Disads are pretty minimal and shouldn't confuse anyone. However, there are a couple of things that have been changed which bear noting:
1. Parentheses. There are numerous disads which require parentheses to surround some of the "adders". In many cases, there are "optional" adders which, if present, should be placed inside of the parentheses.
The only way to accomplish this was to work in a little bit of "intelligence" into the Disadvantage object in the app. Specifically, it will check to see if an Adder begins with a parentheses. If it does, then it will not place a comma or a semicolon before it. It will also increment the "count" of parentheses that have been started. It will only decrement the count if the adder also ends with a closing parentheses.
Once all the adders have been accounted for, the app will insert as many closing parentheses as it thinks are necessary.
This sounds a lot more complex than it is....play with it a bit and it should make some sense. The main reason I mention it is that you will see numerous Disadvantages with Adders that begin with a parentheses but don't close them out. For ex: "(Occasionally".
2. Modifiers on Disads. There is (currently) only one Disad which has a Modifier: Vulnerability. Modifiers on Disads will not display the Modifier "name". They will display any user input, selected options, etc....but not the name. In the case of Vulnerability, this means that you will see simply "2 x STUN" rather than "Vulnerability Multiplier: 2 x STUN"
3. Commas and Semicolons. The WG is very inconsistent in whether it wants items separated by commas or by semicolons. I've come as close as I can to it while still keeping the Disads as generalized as possible. There are some Disads which the WG states should have comma separators inside of the parentheses, however....these Disads all have semicolon separators in HD as the majority of the Disads are formatted this way in the WG.
-----------------------------
There are other changes throughout the app based on the feedback that Durnin has provided. As you find more discrepancies with the WG, let me know and I'll see if anything can be done to address them.
The only changes in this update are formatting enhancements to bring the output from the app closer to the Writer's Guidelines.
Of particular note are some changes to the Disadvantages. These should not affect any existing character files....but when creating new Disads, the formatting is going to be a bit different.
For the most part, the changes to the Disads are pretty minimal and shouldn't confuse anyone. However, there are a couple of things that have been changed which bear noting:
1. Parentheses. There are numerous disads which require parentheses to surround some of the "adders". In many cases, there are "optional" adders which, if present, should be placed inside of the parentheses.
The only way to accomplish this was to work in a little bit of "intelligence" into the Disadvantage object in the app. Specifically, it will check to see if an Adder begins with a parentheses. If it does, then it will not place a comma or a semicolon before it. It will also increment the "count" of parentheses that have been started. It will only decrement the count if the adder also ends with a closing parentheses.
Once all the adders have been accounted for, the app will insert as many closing parentheses as it thinks are necessary.
This sounds a lot more complex than it is....play with it a bit and it should make some sense. The main reason I mention it is that you will see numerous Disadvantages with Adders that begin with a parentheses but don't close them out. For ex: "(Occasionally".
2. Modifiers on Disads. There is (currently) only one Disad which has a Modifier: Vulnerability. Modifiers on Disads will not display the Modifier "name". They will display any user input, selected options, etc....but not the name. In the case of Vulnerability, this means that you will see simply "2 x STUN" rather than "Vulnerability Multiplier: 2 x STUN"
3. Commas and Semicolons. The WG is very inconsistent in whether it wants items separated by commas or by semicolons. I've come as close as I can to it while still keeping the Disads as generalized as possible. There are some Disads which the WG states should have comma separators inside of the parentheses, however....these Disads all have semicolon separators in HD as the majority of the Disads are formatted this way in the WG.
-----------------------------
There are other changes throughout the app based on the feedback that Durnin has provided. As you find more discrepancies with the WG, let me know and I'll see if anything can be done to address them.