A Request to help with Monster Creation

[huntercc]

As a programmer who attempted to do something like what you guys are describing... I can say it is nowhere near as easy as you are suggesting. The problem is there is so much variety in what feats can do, what special abilities can do, what classes can do, etc. that to simplify it all down to "Feat XXX gives +4 bonus to Y" is just not enough to cover even half of what's out there in print.

That said... maybe adding a supplemental editor would feasible... call one a Simple Editor and the other an Advanced Editor. That way you have the best of both worlds, you would be able to satisfy the needs of those folks who for one reason or another are not able to use the Advanced Editor to its full extent, but those who can would still have that option.

Also, I agree that maybe adding a few short videos describing some of the more common tasks within the editor would help get more people using it. I know the folks at d20pro have done so, and I felt they really helped me understand some of the more confusing aspects of their software.

[Mathias]

Actually, bodrin, in Pathfinder, that feat is:

 
~If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0
 
#resmax[resSkill] += 5

Admittedly, most of that simplification comes because Pathfinder puts all the skill points into a single pool, as opposed to d20's method of keeping a separate pool for each class, so there's no need to determine which class was selected, and then figure out which pool that class has.

Competence, Profane and Enhancement bonuses are added with the #applybonus macro:

 
#applybonus[BonComp, hero.child[skSwim], 4]

(+4 Competence bonus to swim)
(The list of possible bonus types is in the Reference Information page in the editor manual)

When you say you want to add a reference to an ability, are you asking for the attribute's final value? The base value (for a pre-req of INT 13+)? Or the attribute bonus? There are so many things a person could be trying to look up.

If you can't remember what Intelligence's Id is, press the "Find Thing" button at the top right of most of the forms, set the filter to "Attribute", and then select intelligence from that list, and HL will enter INT's Id for you. Is that sort of thing helpful for the sort of "selection list" you're looking for?

[rdevelyn]

My two problems with the editor are:

1) not enough documentation,
2) forward compatibility (especially with HL changing so much right now).

But back to my original post.

Adding some built in classes, feats and one adjustment *cannot* be difficult, surely, for the HL deveopers, and it would save us going down the editor route at all in most cases.

That doesn't stop people defining proper races if they like, for things like race-dependent feats, but it does give those of us who want a quick way to define, say, that Formorian Giant, just using the HL front end.

Richard

[bodrin]

Originally Posted by Mathias

Actually, bodrin, in Pathfinder, that feat is:

 
~If we're disabled, do nothing
doneif (tagis[Helper.FtDisable] <> 0
 
#resmax[resSkill] += 5

I was just using the code example from a dataset that i have in the D20 System as an example, however taking the code above which is much simpler

The ~ comment line is easily read and understandable.
But "doneif (tagis[Helper.FtDisable] <> 0" isn't to a user that doesn't program or understand the mathematical symbols or even what FTDisable is!

The macro command #resmax[resSkill] += 5 to a non programmer is confusing.

Broken down into the component parts from a non programmers point of view :- What does resmax mean? What does resSkill mean? What does +=5 mean? What is Helper.FTDisable?

To you guys that have developed the editor and Hero Lab its second nature because you use it every day.

To a gamer that just wants to add that cool new stuff from a book that isn't supported it isn't second nature.

Competence, Profane and Enhancement bonuses are added with the #applybonus macro:

 
#applybonus[BonComp, hero.child[skSwim], 4]

(+4 Competence bonus to swim)
(The list of possible bonus types is in the Reference Information page in the editor manual)

Again this is an easiliy applied macro but the only understandable parts to a non programmer is the ApplyBonus and the skSwim statement.

Again broken down What is BonComp? What is Hero.Child?

I know that BonComp is a Competence Bonus, and i'm almost certain that Hero.Child refers to the character and a tag or pick on that character but from a non programmers point of view it isn't that obvious.

When you say you want to add a reference to an ability, are you asking for the attribute's final value? The base value (for a pre-req of INT 13+)? Or the attribute bonus? There are so many things a person could be trying to look up.

If you can't remember what Intelligence's Id is, press the "Find Thing" button at the top right of most of the forms, set the filter to "Attribute", and then select intelligence from that list, and HL will enter INT's Id for you. Is that sort of thing helpful for the sort of "selection list" you're looking for?

I was just using the ability modifiers as an example of something that could be theoretically implemented and made easier to the end user that isn't a programmer.

A suggested sequence of events to add an ability modifier using buttons that write the correct code for you instead of typing it into the Eval Script, Pre req Script fields.

Enter the Custom Data name and description in the proper fields Manually.

Click a button that generates a unique ID name for the Custom Data parsing it and checking for any duplicates already in the data files.

Click the Bonus Button, which then asks what type of bonus or custom modifier the user requires.
Click the What type of bonus button, which then asks what does the bonus apply too.
Click the applicable stat, ability, feat, skill or other thing button and enter the modifier into a value field.

The editor behind the scenes writes the code with each button press.
So for your Pathfinder example at the top

Apply a +4 Competence bonus to the swim skill, requires three button presses, one tick box and typing 4 into a value field.

Bonus, Bonus type, Applies to Skill, Tick Swim, Enter 4 in a Value field.

Code produced "#applybonus[BonComp, hero.child[skSwim], 4]"
Simpler and quicker.

The button driven menu can be expanded to enter home brew custom stuff too.
After all the diverse range of feat descriptors that grew from the original SRD source was huge Tactical, Divine, Teamwork Feats.
Skill Tricks, Energy Focus and a whole smorgasbord of crunchy custom stuff that needed to be coded long hand, tested and verified, bootstrapped, gizomoed.

Quite daunting to new users, A simpler method of entering data would be beneficial to all, and anybody that wants to study the code also has the long hand option too!

Just my thoughts on an improvement to the editor, and only offered as constructive criticism.

The Hero Lab Program is amazing and you guys at Lone Wolf have provided us gamers with a great product that goes from strength to strength.

[chiefweasel]

I agree, while i love the HL product, I would like to have a simpler way to enter content, or some of it anyways. and i am sure some of this will come with the evenlution of the product, but we all know that us gamers hate to read the rules, lol.

I get emails all the time from users asking how to input information. Even the idea of videos came up, so there are user in the community that would love to contribyte information but feel they cant.

I would like to see a simpler process for entering basic information.

For instance: To check if a new feat has any pre-requ feats, I would like to see a drop down menu and be able to slect all the other feats that are required.

The same for skills, or when set amount, like +2 is added to a skill for a feat.

I guess where i am going is to ask; is there maybe a panel driven way of inputting information instead of having to code for it?

Thanks.

[bodrin]

Originally Posted by chiefweasel

I guess where i am going is to ask; is there maybe a panel driven way of inputting information instead of having to code for it?

My thoughts are in the prior posts but I concur with chiefweasels summary!

[ShadowChemosh]

I just wanted to add my voice to this thread as I am also still a customer that uses HL allot. I wanted to simply say that I would hope that if the suggestions above get put in that maybe the idea of a simple editor or an advanced editor is kept as I would actually prefer the editor to NOT get easier as it would make it harder for myself to use.

I am not saying DO NOT make it easier for others, but hope that a way of using the editor as it is now is kept also. As I am a full time programmer for 15+ years so I find the current editor just right. It helps me along nicely without getting in my way when I just want to do stuff and slap in some code. Though lately I have found myself editing the XML files directly more and more.

I do agree that videos can be VERY helpful for learning and I always look for those for new tools I have to use myself on a job site. It's much easier to simply watch a video with information then read pages of information. So that is I think a easy to implement solution to using the editor even as it is now.

In example to this one my players wanted to learn to use the Editor in HL. He spent three hours reading the help and trying to poke around and enter a single Trait. He was not able to do it and gave up. I told him to come over one Saturday afternoon and I will do a quick tutorial with him. After that single hour of going over the basics of the editor he not only got it but was able to enter the whole Dwarves of Golarion book himself (he still had questions here and their, but he did the coding). That book is on the d20 website for download.

My point being that I do agree with the videos as those can be VERY helpful to get people over the initial confusion of the editor. Once over that little hurtle they seem to do very well actually with the editor as is. Though the suggestions of having the editor able to put in some of the basic Macro's through a little wizard could also be very helpful to those that are new to coding (ie scripting) that HL uses.

So as I am probably in that very small percentage that likes the editor as is I just wanted to add my 2 cents. To me the power of the editor is the REAL scripting language and is what brought me to actual purchase HL. I had been looking for a Character Editor payed or free that was worth it for 10 years. Before I found HL I actually told my players that they should just use MS Word to do a character as at least it would be correct, but now I am pushing them all to HL. So thanks.

[Nikmal]

I personally would not want to see the editor change much either. What I would like though is for the question marks to divulge more information then they do and explain what the buttons do then the current information given. Even hovering the mouse over the buttons like bootstrap, thing and so on, could produce a little pop up window giving information out on what the button does.

Putting out some videos would be a good thing too. I have brought this up earlier in the thread and even PM'd a few people about it too. Going through the editor tab by tab and explaining what each button and field is available and what it does for each tab.

It would be nice if Mathias or Lonewolf Rob could address a few of the things I bring up too

Thanks in advance!

[Colen]

Hi guys,

Firstly, thanks for everyone's feedback in this thread. We definitely appreciate it, regardless of whether it's good or bad for us.

Since we released Hero Lab, we've spent a lot of time thinking about the editor. We've made some big improvements since v1.0, but there are definitely further strides that could be made. This thread has seen the whole spectrum of requests, from "Make it easy for me to do X specific thing" to "Please don't 'dumb things down' too much" and "You should add an 'easy mode' editor".

A comparison to the "RPGXplorer" tool is actually pretty instructive. From what I remember of RPGXplorer, it was tailored specifically to the d20 system, and its editor was very highly structured. That meant that if you wanted to add something that fit neatly into the way they did things, it was as easy as checking a box. However, if you wanted to do anything outside those lines, there was just no way to accomplish it.

Now look at Hero Lab. Instead of one game system, we now support 9 (!), with a 10th on the way. Those game systems aren't simply variants of each other, they're all incredibly different - compare Call of Cthulhu to Pathfinder to World of Darkness. So we can't simply take the easy way out and create checkboxes for the 10 common things that d20 system feats do.

We need to support every foible of each of those games, which means we need a lot of flexibility in how we do things. Not only that, we try to give users the tools to create (almost) anything they want, including things that work differently from anything in the "official" game content. That requires even more flexibility on our part.

We've tried to accomplish that while still striking a balance with ease of use. For example, go to the Hero Lab editor, and look at the controls on the "Race" tab. Without even touching the "advanced" buttons, you can configure types, subtypes, hit dice, ability score modifiers, movement types, natural attacks, and much much more - all without writing a single line of code. Once you get over the initial learning curve where you learn how the editor works (which we think the tutorials help with), you can get a lot accomplished with almost no "programming" required.

So, we've tried to do what we could to keep things simple enough for users. Could we make it simpler and easier to use than it is now? Absolutely. However, we're a tiny company, and our resources are already spread very thin. To make something that's significantly better than the current editor, it would take us many months of work. That means that we have to spend those months working on the Hero Lab editor instead of something else.

At that point it's a trade-off. If we spend months improving the editor, it means we're not working on other things - other improvements to Hero Lab, adding new game systems, bug fixes, new content for games like Pathfinder. So we've created an editor which we think works reasonably well for most people, and spent that other time working on the other aspects of Hero Lab that almost everyone uses.

For example - let's say we had spent a few months working on making the Pathfinder editor easier to use. That means we wouldn't have had time to work on a major chunk of Pathfinder features, like the Bestiary or the Advanced Player's Guide, or maybe PDF output, or perhaps the Tactical Console, or maybe even a whole new game system.

We're absolutely interested in improving the editor's capabilities in future releases of Hero Lab. But unfortunately, making major strides in that direction will take us months of work, which is time we don't get to spend on adding new cool stuff to the rest of the product. It's a balancing act.

Hopefully this helps explain the current situation. If you're curious about how to accomplish something specific in the editor, I recommend you read the editor tutorials, then post here if you still have questions. We're happy to help anyone who wants to learn how to use Hero Lab in more advanced ways.

Thanks for reading!

[risner]

I must add that having owned RPGxplorer, I found it impossible to create any of my characters in RPGx. I eventually gave up trying. I have also tried eTools, and a number of excel sheets.

HL is the first to be easy to use and allow me to build actual characters I play with a reasonably complete version.

I'm happy with the Editor, if I had one complaint is that I had trouble with two things despite reading the tutorial:

1) Understanding the meaning of and correct use of Bootstraps. (I now seem to have a handle of them, but mostly from looking at when and how they are used instead of reading something in the tutorial that make them clear.)

2) Timing is somewhat complicated. It is sometimes difficult to understand when you should add a script in the timing. The only way to help this would be to have a decent list of all "events" that happened with a description of what they do so you can place timings properly. Like after all mods to STR are added but before Encumbrance is calculated for instance. The best way I got now is trial and error.