• 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

FYI for data file authors - new editor "Set User Identifier" feature

Colen

Ex-Staff
Hi everyone,

For everyone writing their own data files, I'd like to flag a feature that one of our new developers added in the last Hero Lab release - "Set User Identifier" in the editor. Using this feature will reduce the number of errors people get when using your data files, and increase the chances they will continue to work properly in the future. :)

Background

When you're creating your own data files, we recommend that you add a two or three character "user identifier" to the unique ids of all your content, based on your name, forum username, or some other unique characteristic. For example, if a user named Danny Butterman adds a feat named "Smash", rather than making the unique id "fSmash", he should use "fDBSmash" instead.

If Danny's friend, Nick Angel, adds his own feat named Smash, Nick's version would have the unique id "fNASmash". That means that Nick and Danny can use each others data files without a problem. If they had both been using the id "fSmash" for their feats, Hero Lab wouldn't have been able to load both sets of data files at the same time, and would report errors if they had tried.

Using a 2 or 3 character user identifier like this also means that if we add new content to Pathfinder with the same name as something you've created, you're unlikely to have a collision. We saw this recently with the new Swashbuckler playtest class, where people with a user-created version of the class ran into problems because it used the same unique ids as the new, "official" version. Those people then couldn't load their custom data files until the files had been updated to deal with the new, official, Swashbuckler.

New Feature in Hero Lab

To help you remember to use the User Identifier in Hero Lab, the editor now allows you to set it up automatically. In the editor, go to the Tools menu and choose Set User Identifier, and enter the 2-3 character user identifier you've chosen ("DB" for Danny, "NA" for nick, or maybe "DHP" for someone creating data files for the products of a company named Doom House Publishing).

Whenever you create a new thing, Hero Lab will then automatically add the user identifier to the unique id of the thing. That means you don't have to remember to add it yourself - it'll be set up automatically for you, and all you have to do is fill in the rest of the id.


Hope this helps! Remember, using a user identifier makes it less likely your data files will run into problems in future, so we highly recommend that you use one for all the Hero Lab content you create. :)
 
I've had enough problems in the 4e and SR rules sets... coming up with enough of a unique id.... could we perhaps get HL to expand that field to 25 characters over the 10 or so we get now?
 
So should we also report bugs here? So I tried to enter the value I use for my home games which is "S2". I got this error message: "The User Identifier must be 2 or 3 uppercase letters. Please enter text other than "S2", delete the text to clear the User Identifier, or select Cancel to keep the current User Identifier."

We have others in the community that uses numbers to represent say the AP number. Any reason its not able to deal with numbers?

Second problem I just found. This is set at the "Editor" level instead of at the .user file or data folder level. So in example I have almost a dozen different packages to support with different two-letter Unique IDs. So setting this value once does not really help at all. It needs to really be at the .user file level or at least stored in the data folder so that \data\Pathfinder_CB has a different value than say \data\Pathfinder_SGG. Note this is more of an idea for future enhancement than actually a bug. :)
 
Last edited:
I've had enough problems in the 4e and SR rules sets... coming up with enough of a unique id.... could we perhaps get HL to expand that field to 25 characters over the 10 or so we get now?

Unfortunately that would mean a major rewrite of Hero Lab. :( The 10 characters we allow right now let everything be translated into a 64-bit integer that we treat as a unique id - this allows us to do some extremely fast comparisons because it's just an integer. Expanding that breaks a lot of assumptions in Hero Lab, so it would be a major chunk of work to do that we don't have time on the schedule for right now. :(
 
So should we also report bugs here? So I tried to enter the value I use for my home games which is "S2". I got this error message: "The User Identifier must be 2 or 3 uppercase letters. Please enter text other than "S2", delete the text to clear the User Identifier, or select Cancel to keep the current User Identifier."

We have others in the community that uses numbers to represent say the AP number. Any reason its not able to deal with numbers?

We prefer to keep numbers out of unique ids, unless those numbers specifically refer to a numeric value that gets used in a script or similar. I'll tweak the mechanism for the next release so that it accepts numbers, but we still recommend you use letters.


Second problem I just found. This is set at the "Editor" level instead of at the .user file or data folder level. So in example I have almost a dozen different packages to support with different two-letter Unique IDs. So setting this value once does not really help at all. It needs to really be at the .user file level or at least stored in the data folder so that \data\Pathfinder_CB has a different value than say \data\Pathfinder_SGG. Note this is more of an idea for future enhancement than actually a bug. :)

Thanks for the feedback - we'll look at incorporating this into a future version of the product!
 
Back
Top