The ability allows me to access any one of the deity's domain I choose each morning by tossing out the spell list of my #2 domain and taking the spell list of my choice. Ergo, I have access to all the deity's domain. I'm not creating a new rule, I was summarizing the ability (I'm willing to accept the critique that my summary was less clear than the ability), but my argument stands on its own merits without that summary.
You created a new rule in Domain spell lists do not exist unless they have abilities attached to them. E.g. The Sun domain spell list can't exist unless you get the abilities too and must, somehow, become the Stars domain or cease to exist. Or the Stars domain spell list is the spell list that I'm accessing through my Domain Mastery ability regardless of its actual domain. The Sun domain spell list exists on its own because it is defined in the APG. Each domain spell list exists on its own, so much so that the spell entries list them School entry. Furthermore, there are Archetypes (the paladin one in Blood of Dragons comes to mind) that give access to domain spell lists without the character having the Domain class feature or domain abilities.
Really our core disagreement appears to be this:
Me: the ability is modular, you retain your actual secondary domain's powers and stop accessing your actual secondary domain's spell list (Glory) and temporarily access a different domain's spell list (Healing).
You: the ability is transformative, you temporarily choose Healing's spell list to become Glory's spell list.
We both believe the syntax of the ability supports our view, so we can't agree on RAW, outside readers will have to make their own conclusion. However, to touch on RAI, do you believe the ability was intended to allow feats and abilities that interact with specific domains the ability to boost other domain's spells?
More amusing example: Ifrit Ecclesitheurge of Yamatsumi with Fire as a secondary domain takes Water's list today. Does his Fire Mastery now boost his Water spells? I argue, "No."
Thanks Marc. Sounds neat. However, I don't really use 3rd party stuff.The whole game is third party stuff.
No it's not. Yes there are a lot of third party products but many people and gaming groups do not use them. Especially people who play pfs.
So I'm not sure what you're getting at.
Probably that Pathfinder is third party to D&D 3.5.
Okay...but PFS for example can only use Paizo products not 3rd party products.
Many people don't allow them in their games.
If people like using 3rd party products go nuts and use them great.
I don't use them except a book with monster templates and I rarely use that.
This thread derail is pointless.
However, to touch on RAI, do you believe the ability was intended to allow feats and abilities that interact with specific domains the ability to boost other domain's spells?
More amusing example: Ifrit Ecclesitheurge of Yamatsumi with Fire as a secondary domain takes Water's list today. Does his Fire Mastery now boost...
I believe that is exactly what it does, if I were the person designing the ability I'd be looking to see all available interactions with it before I finished writing and releasing it. The nature of those interactions would determine whether or not I need to rewrite the ability with more clear language or exclude certain interactions explicitly for being too powerful. I don't see +1 caster level to a random spell list or being able to cast that list spontaneously as game breaking interactions, I see them as interesting synergies that my new ability should support.
If the designer didn't take those possibilities into consideration beforehand they either didn't know their own game well enough to find them or simply don't care.
However, to touch on RAI, do you believe the ability was intended to allow feats and abilities that interact with specific domains the ability to boost other domain's spells?
More amusing example: Ifrit Ecclesitheurge of Yamatsumi with Fire as a secondary domain takes Water's list today. Does his Fire Mastery now boost...
I believe that is exactly what it does, if I were the person designing the ability I'd be looking to see all available interactions with it before I finished writing and releasing it. The nature of those interactions would determine whether or not I need to rewrite the ability with more clear language or exclude certain interactions explicitly for being too powerful. I don't see +1 caster level to a random spell list or being able to cast that list spontaneously as game breaking interactions, I see them as interesting synergies that my new ability should support.
If the designer didn't take those possibilities into consideration beforehand they either didn't know their own game well enough to find them or simply don't care.
Or, you know, maybe you're reading the ability wrong.