I was discussing this with a few of my friends that also have their own license to hero lab and we thought it would be cool if you could set load outs for the settings of what content you use for specific character or the ability to save and export a load out so you can share them with other people so they know what they have access to during character creation.
-
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
Load out for settings?
- Thread starter Nychrome
- Start date
charlieluce
Well-known member
It's easy enough to make a starting character, name it after the campaign, set the configuration you want, and save it. Then when you want to make another character with the same settings, load that portfolio, set up the character, and do a Save As.
Settings can be transferred between existing characters by loading the character with the settings you want to duplicate, using Set Defaults, loading the character you want to copy them to, then using Use Defaults.
Settings can be transferred between existing characters by loading the character with the settings you want to duplicate, using Set Defaults, loading the character you want to copy them to, then using Use Defaults.
True, but there is the point that an option to save multiple "defaults" could be useful. That way you could have a load-out for when you're creating a Pathfinder Society Character, a version for when you're making a character for a standard home-game, and a separate one for when you're the GM making whatever.
Needing to load up a specific character to "copy" the configuration, to then move that over and reset to the new default is sort of a hacked alternative to actually having the option for multiple configuration settings.
Needing to load up a specific character to "copy" the configuration, to then move that over and reset to the new default is sort of a hacked alternative to actually having the option for multiple configuration settings.
Um, that's what he suggested. You create a portfolio named "PFS" and one named "Homebrew". Create characters by loading one of those and then using Save As. Easy-peasy.
This is only if you ALREADY have a character that doesn't use the settings that you want it to use.
Try out each option and you'll see what he's talking about, I think. It's actually a very generic approach that's quite effective.
Sorry Azhrei, I disagree. I have multiple players each with a copy of HL. Several GMs run different games concurrently, we want to have ONE place for GMs/Players get a default list of sources for a specific campaign. If this settings file were on a internet that would be even better.
This way as new players join a game it's easy for them to build new PCs and join the game quickly. It would also allow them to check which sources they need to purchase to be compliant with the current set of defaults.
Passing a character file around just doesn't cut it. Especially if the defaults need to change (say if new material is added) or if someone new wants to use a feature that wasn't in the original set of sources. Every player will have to go through every PC in that game and check all their defaults. Ugh, at that point why bother to even HAVE "defaults" as they quickly get out of sync with what the "real" defaults should be.
Kizan
This way as new players join a game it's easy for them to build new PCs and join the game quickly. It would also allow them to check which sources they need to purchase to be compliant with the current set of defaults.
Passing a character file around just doesn't cut it. Especially if the defaults need to change (say if new material is added) or if someone new wants to use a feature that wasn't in the original set of sources. Every player will have to go through every PC in that game and check all their defaults. Ugh, at that point why bother to even HAVE "defaults" as they quickly get out of sync with what the "real" defaults should be.
Kizan
Last edited:
charlieluce
Well-known member
Oh, it's definitely a hack, but it's the best way I've found to deal with the issue given what we have to work with. We're only sharing players between three different games, though, so emailing the portfolio to players that are new or if it gets updated has worked for us.
We tried this for awhile but started having problems when the PCs got to be high level and more PC per .por file. Both of these had a distinct affect on the stability of the iPad app. So we had to go with one PC per .por file. Even moving to one PC per .port hitting 12th or 13th level and we noticed that the app we just crash and die (on current generation iPads).
Kizan
charlieluce
Well-known member
Ah. We're an all-laptop crew (we use MapTool as well as Hero Lab) so we don't have iPad issues.
During any given game I probably have Hero Lab, MapTool, browser, PDF reader, and possibly Skype open, along with text notes. Not a tablet situation.
During any given game I probably have Hero Lab, MapTool, browser, PDF reader, and possibly Skype open, along with text notes. Not a tablet situation.
I second this... I'm in a game where the GM only allows core and APG (and some ACG) and I run a game where I allow pretty much everything under the sun. It's a PITA when I load up Walter to level him up and I'm looking at feats that aren't allowed because the settings are defaulting to my other campaign!
If you have a specific set of campaigns that you're switching between, the "Duplicate Game System" option in the tools menu can create a new copy of a game system, and each of those copies has its own default settings (also, each copy can be given different user-created content).
CorzatTheGray
Well-known member
Another option of a "hack" is to create a new game system by copying your existing game system and then you can set separate defaults for each new "system" or campaign.
I currently run a "Vanilla Pathfinder" system (just straight Pathfinder no user files), a "General Pathfinder" sytem (that I have EVERYTHING in), "AAW Games Pathfinder" system,and a "Skull & Shackles Pathfinder" system to keep my options/user files straight for what game I'm creating/updating in.
Have the players create a new system and then the GM outputs a .hl file that the players can install to the new system that has the true default template portfolio contained in it and store that .hl file on sharable storage of choice.
Separate defaults and a "true" default template.
Not ideal for the iPad users, but it has worked wonderfully for my group(s).
edit: Ninja'd by Mathias!
I currently run a "Vanilla Pathfinder" system (just straight Pathfinder no user files), a "General Pathfinder" sytem (that I have EVERYTHING in), "AAW Games Pathfinder" system,and a "Skull & Shackles Pathfinder" system to keep my options/user files straight for what game I'm creating/updating in.
Have the players create a new system and then the GM outputs a .hl file that the players can install to the new system that has the true default template portfolio contained in it and store that .hl file on sharable storage of choice.
Separate defaults and a "true" default template.
Not ideal for the iPad users, but it has worked wonderfully for my group(s).
edit: Ninja'd by Mathias!
Ah, I see. Your issue isn't with the technique itself, but with how that technique currently has to be managed (i.e., sending files around the 'net by email). And to that I say, "hear! hear!" It is[/i] a huge PITA.
I would have suggested creating a new DropBox account for shared resources, then sharing that location with all involved players. Then players could drag/drop the files into their own DropBox folders and bingo!, they'd show up on the iPad. But we all know what's happening with the DropBox connection...