• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

AB docs - collected bugs

T

TMPEditor

Active member
Authoring Doc Bug: New Def File

The Getting Started article (kit_started.htm), under Creating an Initial Definition File > Game System Information, 3rd paragraph:

Instructions say to save the def file at this point. However, this gives you an error message that you haven't set the folder name yet.

Need to revise order so that folder instructions come first.
 
Authoring Doc Bug: Race Abbreviations Required

In kit_started.htm, under heading "Races," 2nd paragraph:

"When you create a race, you'll need to provide it with an appropriate unique id and name."

ADD: Abbreviation is also required.
 
Authoring Doc Bug: Entity Tag Group Not Explained

In kit_started.htm, under "Groups and Tags," there should be an explanation of the mandatory "entity" tag group (which, according to the error message, is "required for designating entities as units or items").
 
Authoring Doc: _UnitName_ in Sort Order?

In kit_started.html, under "Default Sort Order," 3rd paragraph:

"This would translate to entering the unique id "Category" for Group #1 and "_UnitName_" for Group #2."

When I use "_UnitName_" for a group in the sort window, I get error "one or more tag groups are undefined"
 
Authoring Doc Bug: Statset Required

kit_started.htm needs to mention that a statset must be defined before the def file will compile.
 
Authoring Doc Bug: Option Set Mandatory

in kit_started.htm, the "Option Categories" section should mention that a compilable def file must include at least one option set, that it must be marked default, and must be designated for leader use.
 
Authoring Doc Bug: Rule Set Requirements

In kit_started.htm, under "Rule Contexts and Rule Sets," it should mention:

1. There must be one rule set of type "user" for the def file to compile.
2. There must be a rule set marked as default, to compile.
 
Authoring Doc Bug: Premature Loading

In kit_started.htm, under "Making Sure It Works," paragraph 5, it says that you are now ready to load the files into Army Builder.

Actually, the files won't compile yet since we haven't created any data files, just the original def file.
 
Authoring Doc Bug: Data File Prompt Incorrect

In kit_started.htm, under "Save and Test," 1st paragraph, it says:

"Note that you are automatically prompted to save the new file in the same folder where your definition file resides..."

Actually, it defaults to the ArmyBuilderEX main folder.
 
Authoring Doc Bug: New Def File

I've been noting all of these issues for correction. The original tutorial was written before V3.0 was finalized, and it hasn't been revisited since. Clearly, there are a fair number of things that have changed as we've tried to tighten up the error trapping within AB. It just never occurred to me that these things were breaking the tutorial. That's a bone-headed move on my part. Sorry.

Henceforth, would it be possible to please post these issues all within the same thread? That makes it much easier for everyone, since everything is in one convenient place. :-)

Thanks, Rob

At 09:58 AM 2/15/2006, you wrote:

The Getting Started article (kit_started.htm), under Creating an Initial Definition File > Game System Information, 3rd paragraph:

Instructions say to save the def file at this point. However, this gives you an error message that you haven't set the folder name yet.

Need to revise order so that folder instructions come first.
Click to expand...
 
SUGGESTION: For kit_started.htm, "Unit Stats and Stat Sets" section.

Should mention that designer does not need to include stats for certain fields which are automatically provided by ArmyBuilderEX (such as name and cost).
 
SUGGESTION: In kit_definition.htm, under "Structure Information":

Attribute "roster" doesn't appear in ABCreator Info panel
Attribute "raceterm" doesn't appear in ABCreator Info panel
Ditto "unitterm" "itemterm" "modelterm" "ptsplural" "ptssingle" "ptsabbrev" "squadterm" "ldrname" "ldrabbrev"

Since ABCreator doesn't seem to support these attributes at this time, might mention in the doc that designers will have to edit these in manually.
 
Oh, wait, I see them - why are they in the Terms window, rather than in the Structure window with the other structure-related items? (Suggest mentioning this in kit_definition.htm)
 
Minor bug: the tooltip for the Roster grid should use the Terms from the def file. (It says "squad" even if squadterm has been defined otherwise.)
 
Authoring Doc Bug: New Def File

The "minsize" attribute is defined for "Entities". As such, it is inherited by both Units and Items. There should be a link near the top of the discussion of Units that specifies this and takes you to the Entities section. Did I accidentally delete that at some point?

-Rob

At 01:30 PM 2/17/2006, you wrote:

In kit_data.htm, under "Units," minsize is referred to but not listed in the definitions.
Click to expand...
 
You must log in or register to reply here.
Back
Top