I'm moving the discussion of this potential new feature here so that it's not buried in the other thread.
To summarize what has gone before:
I'm considering a new feature in HDv2 that will streamline the creation/use of package deals within HD.
The issue, as far as I understand it, is that the proper implementation if a package deal within HD is a combination of up to three different items:
1. A .hdc character file that defines the "starting point" for the character. All "fixed" abilities are defined in this file; things like starting characteristic values, Skills, talents, etc.
2. One or more prefab files. These define the optional abilities for the package. Typically things like "select 1 of the following 3 Skills" or "characters may have the following...", etc.
3. A custom template. This is only necessary if you want to have custom rules for your package. Things like different NCM limits seem to be common.
Given these three concepts, you can accomplish pretty much whatever you need for a given package deal.
Now the issues:
1. It's a bit cumbersome having to send so many files to your players. You'd potentially need to send them the character file, template, and prefabs. To use them, the player would need to load the character file (which would automatically take care of the template) and then load in any prefabs that are applicable, and remember to "save as..." so they don't overwrite the character file starting point.
2. On that last note, the possibility for someone to accidentally (and fairly easily) overwrite that character starting point file is a bit of an issue.
I was thinking of creating a new type of "package file" which would take care of all of this....it would contain the character file, prefabs, and template and would handle loading them all in and would ensure that the .hdc file starting point was never overwritten.
The problem with this really comes into play with the prefabs and with the internal mechanisms in the app for using this new file type.
What I'm thinking may be a better idea is to take a similar concept, but trim it down a bit so that the flexibility of the prefabs in the app is unaffected and the benefits of the packaged file are maintained. To wit:
What I'm currently thinking is a new function that would work similarly to Word's .dot template files (this was suggested by someone else).
A package template would essentially merge the character file and the template into a single file. When a character was started with this package template, it would automatically start out with all the abilities defined in the character file and the template would be loaded in. All that the user would have to do at that point would be to load in the prefabs that they want to use.
The advantage to this approach (IMO) is the simplicity of it. The package template would really just be an extension of the existing template functionality. The file extension would still be .hdt and it would function in all ways like a normal template. There would be two new menu items created to implement this:
File -> New Character from Template...
This would prompt the user to select a .hdt file on their system. If the .hdt file contained a character definition as well as the template definition, the starting values from that character definition would be loaded in. Otherwise, a blank character would be created.
File -> Save as Package Template...
This would take the current template and the currently active character and bundle them together into a new .hdt file.
This structure is something that I can implement in very short order and has the benefit of not conflicting with any existing functionality.
Thoughts?



Bookmarks