Senior Member
Join Date: Jul 2008
Posts: 106
|
Over on the Paizo boards I was involved with a discussion that included Rob.
I started out by saying that I loved HeroLab, but found the Editor to be frustrating. He asked me to elaborate, for the sake of understanding and product improvement. I replied at great length, but I'm going to trim it all down to the basic points. PLEASE NOTE: This isn't intended to be product bashing, or critical of the level of support that has been provided by Mathias in any way whatsoever. In fact, Rob even proposed a possible solution. That is what I am posting about, because I think the more that average users hear about it, the more they might be interested in Rob's idea as well. My issues with the Editor are/were: 1.) The tutorials are very simple, and thoroughly explained. However, it doesn't take long for a user seeking to build something to go beyond the scope of what the tutorial actually teaches. For example, the Storm Elf tutorial won't teach you everything you need to take a creature from the Bestiary and reproduce it in HeroLab. The Storm Elf gets you started with the basic concepts, but there's a lot more to it. 2.) One has to understand something about Paizo Design 101. They love to add PC levels, Prc's, and templates to everything. Not only with their own material, but they will very commonly use 3rd Party OGL material as well (Necromancer's Tome of Horrors and a lot of material from Green Ronin). They make a more creative and versatile encounter that way, and they do it a lot. When updating Runelords, Crimson Throne, Second Darkness, and Legacy of Fire (which were all written under 3.5) to the new Pathfinder Rules, HeroLabs could be invaluable to show how creatures come out under the new revised rules. Except that you have to input the basic race to start with. 3.) Full use of the Tactical Console lies in having your monsters in HeroLabs. That is when the true potential of the TacCon is realized. Rob addressed some of those issues: Quote:
Speaking for myself.. I'd love to import all the Bestiary Creatures into HeroLab, in my own spare time of course (and that might be a pipe dream, but I would at least like to do the handful that I'm actively working with). However, I don't want to author my own rule system. That would be too much, at least in the foreseeable future. In fact, I love M&M, but I see no need to tinker with what Lone Wolf has already done with it. I want something in between. I wish I was a programmer, but for the time being I'm not. Quote:
Quote:
And that is the purpose of this post.. so that other people can read this and hopefully post if this would be something useful to them as well. So how about it community? Is this something you would like to see as well? |
|||
#1 |
Senior Member
Join Date: Jul 2007
Location: Syracuse, NY (USA)
Posts: 213
|
I think that would be an excellent way to get people up to speed on what needs to be done to enter their favorite new race / monster / class / etc.
I agree that the tutorials are a little too basic for what most people would want, but on the other hand the Authoring Kit is more than a little intimidating (although very powerful!). Something in the middle would be perfect. I've been able to learn things on my own or with assistance from the forums, but others may not be as quick to learn. I like the idea of a set of "intermediate" documentation, as long as you provide links to the more basic documentation where appropriate. |
#2 |
Senior Member
Join Date: Aug 2008
Location: Miamisburg, OH
Posts: 1,322
|
There is a community of files already being created. they can be found at www.cheeseweasel.net. i control that website and would love to see more people in the HL community provide more files for all users.
we even ave a small team of 3 people working on D20 3.5 books. the complete champion, our first one is almost done. but we could use all the help we can get. |
#3 |
Member
Join Date: Aug 2009
Posts: 65
|
I'm all for a set of intermediate instructions! I'm not experienced enough yet to need them... but I hope to reach that point!
|
#4 |
|
|