This is still in issue... Please fix I'm begging you
This has been addressed by the DDB team. The fix will be in the v2.0 DDB engine. Along with many other fixes. Apparently the old/current system just cannot handle some of the new 5.5e functions.
This is still in issue... Please fix I'm begging youl
This has been addressed by the DDB team. The fix will be in the v2.0 DDB engine. Along with many other fixes. Apparently the old/current system just cannot handle some of the new 5.5e functions.
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
No, this is primarily because D&D Beyond is badly coded. If someone had tried to come up with an eldritch invocation in 2014 that added your ability bonus to cantrips other than eldritch blast, exactly the same problem would have appeared.
This is still in issue... Please fix I'm begging youl
This has been addressed by the DDB team. The fix will be in the v2.0 DDB engine. Along with many other fixes. Apparently the old/current system just cannot handle some of the new 5.5e functions.
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
This has nothing to do with 2014-2024 compatibility
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
No, this is primarily because D&D Beyond is badly coded. If someone had tried to come up with an eldritch invocation in 2014 that added your ability bonus to cantrips other than eldritch blast, exactly the same problem would have appeared.
Ah, yes, the most common lament of every programmer (or, grey hat hacker, if you prefer) who has ever been hired to update and/or maintain a previous employee's source code. (Naturally, I, the new hire, will always write perfect source code.)
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
No, this is primarily because D&D Beyond is badly coded. If someone had tried to come up with an eldritch invocation in 2014 that added your ability bonus to cantrips other than eldritch blast, exactly the same problem would have appeared.
Ah, yes, the most common lament of every programmer (or, grey hat hacker, if you prefer) who has ever been hired to update and/or maintain a previous employee's source code. (Naturally, I, the new hire, will always write perfect source code.)
It isn't about perfect. DDB's back end code was written to support only what existed at the time of its creation and each new modifier was patched in separately. Now there's so many independent operators the entire system is unstable for changes.
The new system is said to be designed to be more flexible in the types of modifiers, supported dynamic abilities, etc.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This has been addressed by the DDB team. The fix will be in the v2.0 DDB engine. Along with many other fixes. Apparently the old/current system just cannot handle some of the new 5.5e functions.
And.......this is primarily because the 2014 rules are incompatible with the 2024 rules, despite all the official protestations to the contrary.
No, this is primarily because D&D Beyond is badly coded. If someone had tried to come up with an eldritch invocation in 2014 that added your ability bonus to cantrips other than eldritch blast, exactly the same problem would have appeared.
This has nothing to do with 2014-2024 compatibility
Find my D&D Beyond articles here
Ah, yes, the most common lament of every programmer (or, grey hat hacker, if you prefer) who has ever been hired to update and/or maintain a previous employee's source code. (Naturally, I, the new hire, will always write perfect source code.)
It isn't about perfect. DDB's back end code was written to support only what existed at the time of its creation and each new modifier was patched in separately. Now there's so many independent operators the entire system is unstable for changes.
The new system is said to be designed to be more flexible in the types of modifiers, supported dynamic abilities, etc.