Senior Member
Join Date: Sep 2012
Location: Ottawa, Canada
Posts: 781
|
I just want to clarify if what I am doing and the error I am seeing is related to what I have dne in my user file or a bug, or what.
OK little background; I am building a custom campaign game world of my own IP using pathfinder ruleset in Realm Works and Herolab. I have created using the PF ARG 18 custom races for my world. I of course do not want any ARG or CRB races to show up as choices for players, but unlike ARG races there is no way to turn off the Core races in the hero configuration. So what I did was use the replace ID box in the editior on my races to remove a core race. So as examples, Daedrea Human removed Human, Yetica removed Gnome and Varnule Giants removed Half-Orc. Now to my issue, I am now creating adventures in my story almanac and of course building encounters in herolab. This is when I came across a weird issue, when I choose to add "Skeleton, human" to an encounter I had a ton of errors when I imported them, "Bootstrap 699" errors, all for "ra" skills associated with the core race human. So I am wondering is this an error of my own doing and is there a way around it? Did by my act of "replacing" the core race human with Daedrea human cause this issue? If it is because by replacing various core races and this is an issue for some monsters in the bestiary, is there a way to hide them otherwise? Could we have have a house rule addition "no core races" check box lik we have for featured or advanced races from ARG? That won't cause the issues with monsters from the bestiary. Thanks for any feedback. Exmortis aka "Scott" RW - Needs Rez spell HL - Game Master/Designer RPG Tools - Campaign Cartographer 3+, D20 Pro Ultimate Real Life - IT Security Hobby - Anything on water or ATV |
#1 |
|
|