Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you: No adverts like this in the forums anymore. Times and dates in your local timezone. Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance. Email notifications for threads you want to watch closely. Being a part of the oldest wargaming community on the net. If you are already a member then feel free to login now.

Space Marines have a relic, the Burning Blade, which replaces a power sword. My Primaris Librarian has a force sword. I'm assuming that a Force Sword does NOT count as a Power Sword, but I figured I should check.

that is correct. A force sword is not a power sword.

Absolutely correct. They're not the same stat line nor name

Thanks. BattleScribe had allowed me to do it, but then i was re-reading the relic description and realized it was probably an error.

Darn, you're right. I was going to take that relic for my Terminator Librarian too

Okay then, Tome of Malcador it is

 Vilificus wrote:
Thanks. BattleScribe had allowed me to do it, but then i was re-reading the relic description and realized it was probably an error.

Battlescribe is notorious for being wrong in many respects, especially Relic Validation.

 BaconCatBug wrote:

 Vilificus wrote:
Thanks. BattleScribe had allowed me to do it, but then i was re-reading the relic description and realized it was probably an error.

Battlescribe is notorious for being wrong in many respects, especially Relic Validation.

if more people submitted bug reports for these kinds of things without being snippy and combative, more of them might get fixed. Also relic validation is notoriously tricky because of some lingering issues with the application itself and multiple hide conditionals.

 WindstormSCR wrote:

 BaconCatBug wrote:

 Vilificus wrote:
Thanks. BattleScribe had allowed me to do it, but then i was re-reading the relic description and realized it was probably an error.

Battlescribe is notorious for being wrong in many respects, especially Relic Validation.

if more people submitted bug reports for these kinds of things without being snippy and combative, more of them might get fixed. Also relic validation is notoriously tricky because of some lingering issues with the application itself and multiple hide conditionals.

I actually tried to figure out how to report this bug, but since it seems like it is a data bug and not a battlescribe bug I couldn't figure out how to reach the community.

Probably somewhere here: https://github.com/BSData/wh40k

 Vilificus wrote:

 WindstormSCR wrote:

 BaconCatBug wrote:

 Vilificus wrote:
Thanks. BattleScribe had allowed me to do it, but then i was re-reading the relic description and realized it was probably an error.

Battlescribe is notorious for being wrong in many respects, especially Relic Validation.

if more people submitted bug reports for these kinds of things without being snippy and combative, more of them might get fixed. Also relic validation is notoriously tricky because of some lingering issues with the application itself and multiple hide conditionals.

I actually tried to figure out how to report this bug, but since it seems like it is a data bug and not a battlescribe bug I couldn't figure out how to reach the community.

post a bugrep for the relevant catalog here: http://battlescribedata.appspot.com/#/repo/wh40k

it doesn't require a github account, and shows up as anonymous