Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Crossbows are providing half STR bonus to damage when wielded in the off-hand. I reproduced this with both the heavy and light xbows.
Thanks for the bug report!Crossbows are providing half STR bonus to damage when wielded in the off-hand. I reproduced this with both the heavy and light xbows.
I have a hefty file of well detailed 3.5 "Living Greyhawk" Deities that I did for Pathfinder. With some tweaks (once I see how its done in the new d20 tab) it should be set to add to community files.Well, that looks especially awesome. Guess I'll have some deities to add.![]()
Only its location. It will ONLY display on the Race tab no where else (not on the cleric tab or the Personal tab). I assume you have been comparing "Strings" of the deity text field on the background Pick? All of that is still present on a character.has the functionality of how dieities are selected fundamentally changed?
FIRST and Most important.. thanks for your efforts Shadow.... and now for the questions....Just thought I would share a few pics of what is coming in the next update. The two big new pieces is Custom Wands which will work like Custom Scrolls allowing you to make a wand of any spell in the game.
I realize the SRD limits what you "Can do", and again any efforts on your part are greatly appreciated.... I for one would make use of this (as discussed in older threads) I was curious if this would bare some of the similarities (in end user interface) as the Herolab 5e piece? Such as being able to separate pantheons of differing cultures? And if it would be possible to restrict those selections within the code? Meaning it would be "unlikely an elf would select from a dwarven pantheon.. so that "group would not be "on the list" so to speak... And lastly, a wish list item from this... would be to be able to create available spell lists based on the domain that the deity oversees..... speaking of domains... is that listed or would be just in a descriptor within the text?On "custom wands", will this be able to be cannibalized for use in other item types, such as if there were items that "stored spells"? ie Rings or rods or staffs, etc?
View attachment 4520
The next one is Deities have finally come to d20! A new editor tab is available to enter your deity with information and layout that matches to Complete Divine. The below shows a few test deities but because of the SRD d20 will only come with the first three listed options (None, Atheist, Other / Philosophy).
Since you have moved the racial and alignment to this tab as well for cohesiveness (good call IMHO) It would seem logical to capture a few other things there as well.View attachment 4517
Because of this I have reworked where you select your race and alignment to be on its "own" tab. This allows for a central place to also choose your Deity. Plus your racial abilities will display on the same tab.
Thumbs UP to this!View attachment 4518
The top part of the d20 software now shows your selected race and all classes and levels you have:
Me TOO!!! great News can't wait!Well, that looks especially awesome. Guess I'll have some deities to add.
@Dami> Die-hard Greyhawk myself... would love to see this .. happy to help if needed.I have a hefty file of well detailed 3.5 "Living Greyhawk" Deities that I did for Pathfinder. With some tweaks (once I see how its done in the new d20 tab) it should be set to add to community files.![]()
Only its location. It will ONLY display on the Race tab no where else (not on the cleric tab or the Personal tab). I assume you have been comparing "Strings" of the deity text field on the background Pick? All of that is still present on a character.
When you select a deity the Deity Text Box and Alignment chooser will be hidden and the new HasDeity.? tag will be assigned to the hero. In addition the new #hasdeity[] macro can be used to test for a deity.
Thanks for working on the update!
Only its location. It will ONLY display on the Race tab no where else (not on the cleric tab or the Personal tab). I assume you have been comparing "Strings" of the deity text field on the background Pick? All of that is still present on a character.
When you select a deity the Deity Text Box and Alignment chooser will be hidden and the new HasDeity.? tag will be assigned to the hero. In addition the new #hasdeity[] macro can be used to test for a deity.
The answer here is no actually. You have to remember 5e was forked from the Pathfinder code that had these advanced UI features in place already. The d20 base code does NOT have these features to build upon yet. Its in the to-do list but I honestly have it marked sort of a low priority. Getting "functional" features into peoples hands I think is more important.I realize the SRD limits what you "Can do", and again any efforts on your part are greatly appreciated.... I for one would make use of this (as discussed in older threads) I was curious if this would bare some of the similarities (in end user interface) as the Herolab 5e piece? Such as being able to separate pantheons of differing cultures?
This is possible using the normal HL feature called Pre-Req scripts. For example in the pictures above you can see that the "A New Deity" is grayed out because I put a simple pre-req logic of:And if it would be possible to restrict those selections within the code? Meaning it would be "unlikely an elf would select from a dwarven pantheon.. so that "group would not be "on the list" so to speak...
#hasrace[rElf] <> 0
The gods have a place to list which "domains" they offer (ie by tags). I have not added validation checking automatically to the domain component yet. I would like to get that added before release but "may" not happen. We shall see..And lastly, a wish list item from this... would be to be able to create available spell lists based on the domain that the deity oversees..... speaking of domains... is that listed or would be just in a descriptor within the text?
To me Domains are class features and should not appear on the Race tab actually. They will continue to appear on the Class tab where you select them from.Since you have moved the racial and alignment to this tab as well for cohesiveness (good call IMHO) It would seem logical to capture a few other things there as well.
>domains, there for the religious aspects.
> Sub-races, similar again to the pathfinder / 5e setups (see graphic)
This should work just fine in the new system. On the Deity you would setup access to the Lightbearer, Law, Good, Sun and Protection domain.For example, if there is a deity called Lightbearer, that has a forced choice of a Lightbearer Domain (available only to that deity), and the choice of one other domain from Law, Good, Sun, and Protection. Hopefully nothing breaks, but if it does, I'll just deal with it, so no worries.
hope so.I'm interested in the new tags, could open some doors for how I'm doing things at the moment.
That's cool. I was not sure at what stage of transition you were at... and getting some functionality is miles ahead of the "oldway"...The answer here is no actually. You have to remember 5e was forked from the Pathfinder code that had these advanced UI features in place already. The d20 base code does NOT have these features to build upon yet. Its in the to-do list but I honestly have it marked sort of a low priority. Getting "functional" features into peoples hands I think is more important.
That works...What I would recommend doing is making sure that the new Gods are "Source" marked correctly so that if you are playing in Forgotten Realms and you turn on FR Gods "Source" you only see the FR gods.
That works...The gods have a place to list which "domains" they offer (ie by tags). I have not added validation checking automatically to the domain component yet. I would like to get that added before release but "may" not happen. We shall see..
Your workaround will do.. there are not many.... Domains, but some spells are "homebrew" and Deity specific.Not sure what you mean by Available Spell Lists based on a Domain? Domains already get specific "Domain" spells. I guess what your asking is for each Deity to support different Domain Spells? DLG>YES
If that is what your asking its a Houserule and not part of the SRD. DLG>YES, but only in some cases. There were additional domains added after the SRD and there are also domains that are campaign specific (Greyhawk in this case)
Meaning you won't see me add direct support for this feature. What you could do to accomplish this is setup the domain spells with bootstrap conditions that look at the HasDeity.? tag. Then based on the selected Deity you would get different Domain Spells.
I agree, and to clarify a couple points, I was referring to a list of domains that, through the editor, could be bootlegged to that deity. And when the Player is perusing the Deities list, that those domains would show with that deity... for now a text box works for domains "ruled over"...and toggling back to the class to set the domain spell choice for the class.To me Domains are class features and should not appear on the Race tab actually. They will continue to appear on the Class tab where you select them from.
Agreed, and in the interim I have already created "sub-races" with their abilities...Stuff like Sub-races, Creature Types, Sub-Types, alternate racial abilities and etc etc are "eventually" going to go to this new "Race" tab. Its the main reason it was worth taking the time to move the Deity, Alignments and Race choosers now. But those other changes are still coming in "future" updates. Not currently.![]()
This should work just fine in the new system. On the Deity you would setup access to the Lightbearer, Law, Good, Sun and Protection domain.
Then what I would do is setup a Pre-Eval rule that only fires when the Deity selected becomes a Pick (do this by checking the @pick variable). You would also maybe want to say you are valid if not a Cleric or other "Domain" choosing class. Then make the deity valid if it can specifically find the Lightbearer domain on the character. This way your players would get a nice message after selecting the god to add the Lightbearer domain. Once lightbearer was added the error message goes away.
If there is a 3.5 book that needs to support this feature please point me to it. Its easier for me to add features if I can show that a specific "book" needs it.Not sure what you mean by Available Spell Lists based on a Domain? Domains already get specific "Domain" spells. I guess what your asking is for each Deity to support different Domain Spells? DLG>YES
If that is what your asking its a Houserule and not part of the SRD. DLG>YES, but only in some cases. There were additional domains added after the SRD and there are also domains that are campaign specific (Greyhawk in this case)
I think its a little different. Kendall-DM was in need of forcing a gamer to select a specific domain for a specific god. If I get time I will create an example Domain that has different spells per deity.Your workaround will do.. there are not many.... Domains, but some spells are "homebrew" and Deity specific.
IF I understand your response to Kendall-DM I think that partly answers this?
Oh I get yeah. That is a good point. I wrote the display script logic many weeks ago so I don't remember if it shows the domains.And when the Player is perusing the Deities list, that those domains would show with that deity... for now a text box works for domains "ruled over"...and toggling back to the class to set the domain spell choice for the class.
The best method going forward is to make these a new component. Meaning they will get there own special Tab in the editor for setup. It makes it SO much easier to keep the logic separate then trying to make use of the generic "Special" that is in the system. The fact that Special can be on a race or a class is really making some changes very difficult.Agreed, and in the interim I have already created "sub-races" with their abilities... Would there be a preferred methodology to anticipate supporting the newer format to come? or will, when those features come to fruition, have to be rebuilt? I am presuming the latter?
I have made this part easier as its now a selection on the Deity editor tab. You can simply select the race or races that the deity is restricted too.This is possible using the normal HL feature called Pre-Req scripts. For example in the pictures above you can see that the "A New Deity" is grayed out because I put a simple pre-req logic of:
as a Pre-Req so that the god is only valid for Elvin characters. You can add any other "Pre-Req" logic you wish including requiring special feats or ability scores or even only valid for Male characters. Anything you could accomplish with normal HL Pre-Req scripts will work.Code:#hasrace[rElf] <> 0
Domain validation based on your chosen deity is finished. Yeah! Though this got me looking at the Domains that are included and saw that many are lacking information, features, and a good domain spell mechanics.The gods have a place to list which "domains" they offer (ie by tags). I have not added validation checking automatically to the domain component yet. I would like to get that added before release but "may" not happen. We shall see..
So I misspoke about how domain spells work as its VERY different than Pathfinder. I will be re-working the way you associate a Spell to a Domain. This will make it much easier to setup new domains and will allow for an easy method to define different spells per deity (I hope).Not sure what you mean by Available Spell Lists based on a Domain? Domains already get specific "Domain" spells. I guess what your asking is for each Deity to support different Domain Spells?
What you could do to accomplish this is setup the domain spells with bootstrap conditions that look at the HasDeity.? tag. Then based on the selected Deity you would get different Domain Spells.
This is done. What this looks like now is you have a "Domain Spells" button and you just select the spells you want to be allowed for your domain. This moves the control from the Spell to the Domain making setup of new domains much easier.So I misspoke about how domain spells work as its VERY different than Pathfinder. I will be re-working the way you associate a Spell to a Domain. This will make it much easier to setup new domains and will allow for an easy method to define different spells per deity (I hope).![]()
[B] <eval phase="PreLevel" priority="5000"><![CDATA[[/B]
[B][COLOR="SeaGreen"]~ Set focus to the war domain if present on hero[/COLOR][/B]
perform hero.findchild[BaseClrDom,"AllowDom.cdWar"].setfocus
[B][COLOR="SeaGreen"]~ Change out the War Domain's 3rd level spell with Prayer[/COLOR][/B]
if (state.isfocus <> 0) then
perform focus.delete[ClsScAllSp.sClr30019]
perform focus.assign[ClsScAllSp.sClr30022]
endif
perform state.clearfocus
[B][COLOR="SeaGreen"]~ Set focus to the Air domain if present on hero[/COLOR][/B]
perform hero.findchild[BaseClrDom,"AllowDom.cdAir"].setfocus
[B][COLOR="SeaGreen"]~ Change out all the Air Domain's spells[/COLOR][/B]
if (state.isfocus <> 0) then
perform focus.delete[ClsScAllSp.?]
perform focus.assign[ClsScAllSp.sDWat10000]
perform focus.assign[ClsScAllSp.sDWat20000]
perform focus.assign[ClsScAllSp.sDWat30000]
perform focus.assign[ClsScAllSp.spConWat4]
perform focus.assign[ClsScAllSp.sDWat50000]
perform focus.assign[ClsScAllSp.spCoCold6]
perform focus.assign[ClsScAllSp.spAcidFog7]
perform focus.assign[ClsScAllSp.sDWat80000]
perform focus.assign[ClsScAllSp.sDWat90000]
endif
[B] ]]><before name="Domain Secondary Spells"/>
</eval>
[/B]