Skip to content

[AAG] Fixes to Astral Elf and Wildspacer#318

Merged
aurorabuilderlegacy merged 8 commits intoAuroraLegacy:masterfrom
JarodHuber:AAG-Fixes
Apr 22, 2026
Merged

[AAG] Fixes to Astral Elf and Wildspacer#318
aurorabuilderlegacy merged 8 commits intoAuroraLegacy:masterfrom
JarodHuber:AAG-Fixes

Conversation

@JarodHuber
Copy link
Copy Markdown
Contributor

@JarodHuber JarodHuber commented Feb 11, 2026

Added TCOE proficiency replacer to Astral Elf's Keen Senses
Removed Language proficiencies from Wildspacer background

Removed grant ID_INTERNAL_GRANT_RACE_ELF as it is redundant
Moved rules around to match the order in MOTM races

Copy link
Copy Markdown
Contributor

@NickVendel NickVendel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we might've fixed Astral Elf in PHB24 PR, but it shouldn't matter for this PR.

Comment on lines 32 to +40
<select type="Ability Score Improvement" name="Ability Score Improvement Option (Astral Elf)" supports="Custom Ability Score Improvement Option" requirements="!ID_INTERNAL_GRANTS_BACKGROUND_ASI" />
<stat name="innate speed" value="30" bonus="base" />
<grant type="Size" id="ID_SIZE_MEDIUM" />
<stat name="innate speed" value="30" bonus="base" />
<grant type="Vision" id="ID_VISION_DARKVISION" />

<grant type="Language" id="ID_LANGUAGE_COMMON" requirements="!ID_WOTC_TCOE_OPTION_CUSTOMIZED_LANGUAGE" />
<select type="Language" name="Language (Astral Elf)" supports="Standard||Exotic" />
<select type="Language" name="Customized Language (Astral Elf)" supports="Custom Race Language" requirements="ID_WOTC_TCOE_OPTION_CUSTOMIZED_LANGUAGE" />
<grant type="Vision" id="ID_VISION_DARKVISION" />
<grant type="Grants" id="ID_INTERNAL_GRANT_RACE_ELF"/>
<select type="Language" name="Language (Astral Elf)" supports="Standard||Exotic" />

Copy link
Copy Markdown
Contributor

@NickVendel NickVendel Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a mess. I recommend just updating this branch's file with the one from the master, increment version of the file and then add your fix for Keen Senses. That should work much better and won't delete relevant Grant either.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can move Darkvision back down to match PHB24 and rewrite the language grant to match as well (select 2 on customized language option). But ID_INTERNAL_GRANT_RACE_ELF is redundant with ID_INTERNAL_RACIAL_TRAIT_TYPE_HUMANOID_ELF, which is at the top to coincide with PHB24 organization. I'm a bit surprised to see it's not utilized in the PHB24 races.

Copy link
Copy Markdown
Contributor

@NickVendel NickVendel Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right about the Grant, we probably missed the original TYPE_HUMANOID one. So yeah, we can remove the redundant one, but i do think everything else should be in the same format as it is now, just because it's messy either way in my opinion, so it's better not to move anything.

I can move Darkvision back down to match PHB24

You don't need to match PHB24, better would be to match AAG. Which would probably require you to move Languages above, after ASI. Then moving Creature type under it as well, above Size, and then move Darkvision below Astral Fire. But just to be clear, it's an optional thing, we technically don't need to move anything in this PR, it works as is (though redundant Grant should be removed).

I'm a bit surprised to see it's not utilized in the PHB24 races.

Which ones need it? I feel like none of them are "considered as", they're just Humanoid of their related species.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason to match the PHB24 format is to have a consistent format. Even if it's messy, having a standard, consistent way the rules are granted improves the readability and helps prevent errors like missing the TYPE_HUMANOID grant. That said, I won't harp on that point and will revert that part as it's not for me to decide something like that. As for the PHB24 races, you're right, I guess I just figured they would be used for clarity. Shall I still rewrite the customized language grant from Tasha's to override both language grants and be a 'select 2'?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if it's messy, having a standard

Our standard is a book standard. The reason why i, personally, wanted a standard for PHB24 is because 1) i assume plenty of official books afterward will use that standard or at least something fairly close to it (same goes for third-party and homebrew content) and 2) because original PHB was created by the dev, so there's lots of weird decisions that i wanted to get around in order to get closer to book format. Books before PHB24 are kinda all over the place, and while i can see how having a standard can improve readability for the coder, i still think it's much easier to compare to the book when it's all in order that is in the book, so that's kinda my go-to format with any source.

Shall I still rewrite the customized language grant from Tasha's to override both language grants and be a 'select 2'?

I think there's no reason, since that second one is already basically TCOE logic, i think only Common is fine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I see what you mean now. Yeah, I guess that makes sense. I was only considering book accuracy from the end user's PoV. In that case, shouldn't Darkvision be under Astral Fire and Speed under Size?

Copy link
Copy Markdown
Contributor

@NickVendel NickVendel Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's what i said in the comment just before previous one (in the edit)

@aurorabuilderlegacy aurorabuilderlegacy merged commit 0fa6442 into AuroraLegacy:master Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants