Will D&DBeyond ever implement backwards compatibility for 5.5 Warlock to use 5.0 Warlock invocations? I saw a post from 2024 asking this and based on my research, I didn't find an answer. Has WOTC discussed this yet? If so please direct me where to go.
I have been playing in a campaign for almost 4 years now. We started with 5.0 characters and upgraded to 5.5 characters. We are heard WOTC advertise backwards compatibility meaning my new 5.5 warlock can use any 5.0 invocations that weren't reprinted like Eldritch Sight. So far I cannot choose that as an option in the character builder. My temporary solution was to give myself the Eldritch Adept feat and choose the old 5.0 Eldritch Sight invocation, and now it works. In the character builder, I just left open an invocation slot to account for this. I just took my 15th level in Warlock and want to use Shroud of Shadow. I cannot do the same trick because the character builder only lets me add an extra feat once of each type- so I can't choose Eldritch Adept again.
I believe they've said that isn't possible in the current system and will have to wait for the big overhaul of the character builder that they're currently working on. Though I don't think they've committed to doing it even in that case.
It's possible to create a homebrew feat that duplicates the effect of an invocation and give that to your character instead of Eldritch Adept. For invocations like Eldritch Sight and Shroud of Shadow that just grant you the ability to cast a single spell, this is fairly easy to implement and there are probably a bunch of published ones in the public homebrew that do it already.
Would like WotC to create a backwards compatible Homebrew for all the Stuff the builder cannot do by default so we can add them to our characters in the builder.
Would like WotC to create a backwards compatible Homebrew for all the Stuff the builder cannot do by default so we can add them to our characters in the builder.
That would be great, though it would obviously also depend on the new system they're building.
I try to NOT mix the 2014 PHB and the 2024 PHB. There are enough differences to convince me that the two rule sets are not compatible and trying to mix them merely creates a mess and endless arguments.
I try to NOT mix the 2014 PHB and the 2024 PHB. There are enough differences to convince me that the two rule sets are not compatible and trying to mix them merely creates a mess and endless arguments.
The rules sets are generally compatible with occasional tweaking, and 5.0 invocations that haven't been replaced all, AFAIK, would work fine in 5.5. The other way less so because of how they changed the pacts.
None of which has anything to do with the system limitations that are presumably the reason 5.5 warlocks can't use 5.0 invocations on DDB.
I try to NOT mix the 2014 PHB and the 2024 PHB. There are enough differences to convince me that the two rule sets are not compatible and trying to mix them merely creates a mess and endless arguments.
The rules sets are generally compatible with occasional tweaking, and 5.0 invocations that haven't been replaced all, AFAIK, would work fine in 5.5. The other way less so because of how they changed the pacts.
None of which has anything to do with the system limitations that are presumably the reason 5.5 warlocks can't use 5.0 invocations on DDB.
Under the 2014 rules, warlocks had the invocation Eldritch Sight, which gave the warlock a continuous Detect Magic while under the 2024 rules, Eldritch Sight has been defined out of existence, which put a crimp in my warlock character's usefulness to the party. The limitations in the DnD Beyond character app regarding the invocation Agonizing Blast is being debated endlessly in other threads and I will not drag that debate into this thread. In other threads, posters have asserted that when a warlock conjures (Out Of Thin Air) a Great Sword dealing Radiant damage, the warlock must have a minimum Strength or else be unable to wield said weapon despite the fact that Pact of the Blade clearly says that the warlock IS PROFICIENT WITH THE CONJURED WEAPON. (I have left a few scorch marks on those threads.) If the warlock, with his encounter temporary conjured weapon, has to conform to the rules that bind non-magical, non-conjured weapons, what then, is the point of having the invocation Pact of The Blade? It would be better to simply define that invocation out of existence as well.
I think you're getting the rules and D&D Beyond's implementation of the rules confused.
In terms of the actual rules, Agonizing Blast works just fine and Eldritch Sight can still be used in 5.5e. The fact that D&D Beyond's implementation of these things is incorrect doesn't mean that the rules are not compatible.
(Heavy weapons having Strength or Dexterity requirements has nothing to do with proficiency.)
I think you're getting the rules and D&D Beyond's implementation of the rules confused.
In terms of the actual rules, Agonizing Blast works just fine and Eldritch Sight can still be used in 5.5e. The fact that D&D Beyond's implementation of these things is incorrect doesn't mean that the rules are not compatible.
(Heavy weapons having Strength or Dexterity requirements has nothing to do with proficiency.)
Fine. Demanding Strength requirements on a conjured item defeats the proficiency benefit. That means the Pact of the Blade invocation can only conjure a melee weapon for which the warlock has the Strength or Dexterity. ( It would have been nice if the description of the invocation had made that point explicit.) The warlock would be better off simply stabbing with an ordinary spear or dagger and not bother with an insipid Pact of the Blade.
If the DnD Beyond character app fails to fully support the rules as written, then there is an incompatibility issue. As a software developer, I find such an issue to be intolerable.
I try to NOT mix the 2014 PHB and the 2024 PHB. There are enough differences to convince me that the two rule sets are not compatible and trying to mix them merely creates a mess and endless arguments.
The rules sets are generally compatible with occasional tweaking, and 5.0 invocations that haven't been replaced all, AFAIK, would work fine in 5.5. The other way less so because of how they changed the pacts.
None of which has anything to do with the system limitations that are presumably the reason 5.5 warlocks can't use 5.0 invocations on DDB.
Under the 2014 rules, warlocks had the invocation Eldritch Sight, which gave the warlock a continuous Detect Magic while under the 2024 rules, Eldritch Sight has been defined out of existence, which put a crimp in my warlock character's usefulness to the party.
That's a matter to discuss with your DM. If they're not allowing the use of 5.0 invocations in their game, that's their call, but the rules permit it.
The limitations in the DnD Beyond character app regarding the invocation Agonizing Blast is being debated endlessly in other threads and I will not drag that debate into this thread.
That's a non-sequitur. "The site can't implement the rules properly, but they're working on it" is not the same this as "5.0 and 5.5 are mechanically incompatible".
In other threads, posters have asserted that when a warlock conjures (Out Of Thin Air) a Great Sword dealing Radiant damage, the warlock must have a minimum Strength or else be unable to wield said weapon despite the fact that Pact of the Blade clearly says that the warlock IS PROFICIENT WITH THE CONJURED WEAPON. (I have left a few scorch marks on those threads.) If the warlock, with his encounter temporary conjured weapon, has to conform to the rules that bind non-magical, non-conjured weapons, what then, is the point of having the invocation Pact of The Blade? It would be better to simply define that invocation out of existence as well.
What's the point of being able to fight with your casting stat, summon weapons out of nowhere, gain proficiency you wouldn't otherwise have, use it as a casting focus, and replace the damage type? I dunno.
5.0 warlocks were subject to the same restriction, except in that version it was based on creature size. The weapon still has mass, even if you're proficient in it.
The two rule sets are not compatible.
Your definition of "compatible" appears to be rather idiosyncratic.
Fine. Demanding Strength requirements on a conjured item defeats the proficiency benefit. That means the Pact of the Blade invocation can only conjure a melee weapon for which the warlock has the Strength or Dexterity. ( It would have been nice if the description of the invocation had made that point explicit.) The warlock would be better off simply stabbing with an ordinary spear or dagger and not bother with an insipid Pact of the Blade.
A lot of DMs would be happy to ignore that restriction in practice, since it's ultimately kind of silly. This has nothing to do with 5e and 5.5e stuff being compatible with each other, though.
If the DnD Beyond character app fails to fully support the rules as written, then there is an incompatibility issue. As a software developer, I find such an issue to be intolerable.
Again, you're getting two things confused here. Yes, D&D Beyond's implementation of the rules isn't fully correct for either 5e or 5.5e. This has nothing to do with the question of whether content written for 5e and content written for 5.5e can be mixed when actually playing.
Rollback Post to RevisionRollBack
pronouns: he/she/they
To post a comment, please login or register a new account.
Will D&DBeyond ever implement backwards compatibility for 5.5 Warlock to use 5.0 Warlock invocations? I saw a post from 2024 asking this and based on my research, I didn't find an answer. Has WOTC discussed this yet? If so please direct me where to go.
I have been playing in a campaign for almost 4 years now. We started with 5.0 characters and upgraded to 5.5 characters. We are heard WOTC advertise backwards compatibility meaning my new 5.5 warlock can use any 5.0 invocations that weren't reprinted like Eldritch Sight. So far I cannot choose that as an option in the character builder. My temporary solution was to give myself the Eldritch Adept feat and choose the old 5.0 Eldritch Sight invocation, and now it works. In the character builder, I just left open an invocation slot to account for this. I just took my 15th level in Warlock and want to use Shroud of Shadow. I cannot do the same trick because the character builder only lets me add an extra feat once of each type- so I can't choose Eldritch Adept again.
I believe they've said that isn't possible in the current system and will have to wait for the big overhaul of the character builder that they're currently working on. Though I don't think they've committed to doing it even in that case.
It's possible to create a homebrew feat that duplicates the effect of an invocation and give that to your character instead of Eldritch Adept. For invocations like Eldritch Sight and Shroud of Shadow that just grant you the ability to cast a single spell, this is fairly easy to implement and there are probably a bunch of published ones in the public homebrew that do it already.
pronouns: he/she/they
Would like WotC to create a backwards compatible Homebrew for all the Stuff the builder cannot do by default so we can add them to our characters in the builder.
That would be great, though it would obviously also depend on the new system they're building.
pronouns: he/she/they
My two cents:
I try to NOT mix the 2014 PHB and the 2024 PHB. There are enough differences to convince me that the two rule sets are not compatible and trying to mix them merely creates a mess and endless arguments.
The rules sets are generally compatible with occasional tweaking, and 5.0 invocations that haven't been replaced all, AFAIK, would work fine in 5.5. The other way less so because of how they changed the pacts.
None of which has anything to do with the system limitations that are presumably the reason 5.5 warlocks can't use 5.0 invocations on DDB.
Under the 2014 rules, warlocks had the invocation Eldritch Sight, which gave the warlock a continuous Detect Magic while under the 2024 rules, Eldritch Sight has been defined out of existence, which put a crimp in my warlock character's usefulness to the party. The limitations in the DnD Beyond character app regarding the invocation Agonizing Blast is being debated endlessly in other threads and I will not drag that debate into this thread. In other threads, posters have asserted that when a warlock conjures (Out Of Thin Air) a Great Sword dealing Radiant damage, the warlock must have a minimum Strength or else be unable to wield said weapon despite the fact that Pact of the Blade clearly says that the warlock IS PROFICIENT WITH THE CONJURED WEAPON. (I have left a few scorch marks on those threads.) If the warlock, with his encounter temporary conjured weapon, has to conform to the rules that bind non-magical, non-conjured weapons, what then, is the point of having the invocation Pact of The Blade? It would be better to simply define that invocation out of existence as well.
The two rule sets are not compatible.
I think you're getting the rules and D&D Beyond's implementation of the rules confused.
In terms of the actual rules, Agonizing Blast works just fine and Eldritch Sight can still be used in 5.5e. The fact that D&D Beyond's implementation of these things is incorrect doesn't mean that the rules are not compatible.
(Heavy weapons having Strength or Dexterity requirements has nothing to do with proficiency.)
pronouns: he/she/they
Fine. Demanding Strength requirements on a conjured item defeats the proficiency benefit. That means the Pact of the Blade invocation can only conjure a melee weapon for which the warlock has the Strength or Dexterity. ( It would have been nice if the description of the invocation had made that point explicit.) The warlock would be better off simply stabbing with an ordinary spear or dagger and not bother with an insipid Pact of the Blade.
If the DnD Beyond character app fails to fully support the rules as written, then there is an incompatibility issue. As a software developer, I find such an issue to be intolerable.
That's a matter to discuss with your DM. If they're not allowing the use of 5.0 invocations in their game, that's their call, but the rules permit it.
That's a non-sequitur. "The site can't implement the rules properly, but they're working on it" is not the same this as "5.0 and 5.5 are mechanically incompatible".
What's the point of being able to fight with your casting stat, summon weapons out of nowhere, gain proficiency you wouldn't otherwise have, use it as a casting focus, and replace the damage type? I dunno.
5.0 warlocks were subject to the same restriction, except in that version it was based on creature size. The weapon still has mass, even if you're proficient in it.
Your definition of "compatible" appears to be rather idiosyncratic.
A lot of DMs would be happy to ignore that restriction in practice, since it's ultimately kind of silly. This has nothing to do with 5e and 5.5e stuff being compatible with each other, though.
Again, you're getting two things confused here. Yes, D&D Beyond's implementation of the rules isn't fully correct for either 5e or 5.5e. This has nothing to do with the question of whether content written for 5e and content written for 5.5e can be mixed when actually playing.
pronouns: he/she/they