• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Racial Special removal - when?

wrs92103

Member
When (what phase and priority) do Alternative Racial Traits remove racial specials?

I created a Gnome character, who naturally gets Low-Light vision (raLowLight). I chose the Darkvision alternative racial trait, which replaces it with Darkvision (via RaReplace.raLowLight). I want to give this character the Blood of Dragons racial trait, and have this trait re-add low light.

My GM agrees that this should result in a character that has both Low-Light and Darkvision. Unfortunately the character sheet disagrees.

I _think_ what's going on is that the sequencing is off; both the race and bloodline trait add raLowLight, then the RaReplace comes in and blows them both away.

My thought is to make a custom version of Blood of Dragons that tries to add the raLowLight tag later, so that it's added after RaReplace happens. Anyone know when that would be?
 
Actually I think that is a known limitation of the program, it does something similar with archetypes that remove armor proficiencies, it doesn't allow you to later add them.
 
The issue is nothing to do with tags but the fact that the Low-Light vision is a Pick with a add-once uniqueness. Meaning only one exists on the hero container at a time.

The easy solution here would be to create a new version of Low-Light with a different unique ID and bootstrap it to an adjustment. Then you could add the adjustment to any character to re-add low-light vision.

I would still recommend reporting this as an error as the Archetypes issue of proficiency was fixed.
 
Back
Top