TOPIC: True Dungeon Character Generators (App)

Dave wrote: Just want to say again how much I love this app. It really is awesome!

Having said that, I was playing with my new builds this evening and noticed something. When I MEC and Sharpen a sliding spell, when it crits, it is not doubling the MEC bonus, as it should.

Did this problem exist in prior versions? Not sure. I didn't notice it before, but am playing with a build where I'm trying to squeeze out a little more damage and it became obvious. I made sure I was on the latest version 10.2.1. I'm using the ioS version on my iPad. I tested it several times and was able to recreate a crit slide 4 times. Each time it only doubled the base and bonus spell damage. It only applied the MEC bonus once.

Assuming a fix will take a little time, this is a heads up for everyone this coming weekend that you'll have to manually inform the DM of the additional damage if you notice that you slid a crit.

Also, it would be nice if the dice roller told you if you slid a crit. Currently, I can only tell because my damage is higher than it would be otherwise.

A couple things. I do appreciate your help Dave. You have provided very helpful code reports, but this topic brings up a few issues.

First. The token database or any documents I have found do not specify what gets doubled by a crit using Sharpen. Until that is specified, I will not be making any changes. I have ZERO interest in getting between TPTB and players when it comes to rules, and very tired of being stuck there.

Second. I DO NOT control the Dice Roller. Please direct any issues you have with it to True Dungeon. Acherin and I get a lot of comments over stuff we have no control over.

When we have the wrong info on tokens, those are fair game, and we need to correct those, but if you have issues with rules or how adventures happen, please direct those to True Dungeon

Thank you.

Fair enough. I don't see an official ruling on this and looking back over old posts I see other people treating it differently. I think it's going to be confusing no matter how it's ruled. In person, it was always easier to say my spell with MEC does X damage, so if I slide a crit it does 2X damage. The other version is taking MEC into consideration and calculating a crit as X + (X-MEC). I can logically think that through either way I guess. It depends upon the sequence of when Sharpen and MEC are applied.

Running the app in iOS.
I’ve noticed that when the Barbarian uses Fury, hits often do not crit as they should. Specific example is room 7. I confirmed that the creature could be critted, but even though I was getting hits, they did not crit. I also use Greater Rage with Fury. Screen shows Greater Rage above the die but not the crit. Fury description in Tokendb indicates they can be used together. Not sure if Fury is being blocked.

Thanks for all you do!

Had time to finally do a little more testing. Again, using iOS version on an iPad.

If I Fork a spell that requires a skill check, I get the following.
If I execute the spell manually, I am told the damage (including the skill check) and then get at "Target 2" message, which to me indicates I should just apply the same damage to Target 2. This is as I would expect.

If I execute the spell using Spell Sequence, the damage to Target 1 is the same, but the Forked damage is not including the skill check bonus.

Similarly, if cast the same spell using Fork and MEC, everything looks as expected if I do it manually. I'm given one total that includes the Skill Check and MEC bonus. If I cast the same combo using Spell Sequence, I am given a Fork amount that does not include the Skill Check. Also, the Skill Check is not being included in the MEC bonus.

Next.
I ran 202 tests on sliding spells using different combinations of Sharpen, Fork and MEC. I ran these tests manually and using Spell Sequence. I noticed the following.

The app is telling me die roll if I cast the spell manually. It is not if I use Spell Sequence. That's okay, just mentioning that I can specifically tell if I crit when using Spell Sequence. I can assume based on spell damage.

If my die roll is a natural 1, I'm still being given the expected damage total. This should be a critical miss and the damage is 0.

When I cast the spell manually and roll a crit (18, 19 or 20), the spell damage is not being doubled.

When I cast the spell using Spell Sequence, I saw several examples where the spell damage did double (not counting MEC, which is possibly pending a ruling from TD).

Fork is probably working okay, but if I hit a crit, the forked damage is not being doubled. That's probably because the target 1 damage is also not being doubled. The two are the same.

When I use Fork as part of a spell sequence, the target 1 and target 2 damage is identical, but again, pending a ruling, MEC is not being doubled if I also hit a crit.

I hope some of that helps. In summary.
1. Skill check bonus should be included when I Fork a spell as part of a spell sequence.
2. Rolling a natural 1 on a slidiing spell should result in 0 damage, both manual and in spell sequence.
3. Rolling a crit when executing the spell manually should result in doubling the damage.
4. (still pending) If so ruled, include MEC in the doubling of spell damage when a sliding spell crits. Ignore this, if ruled it doesn't double.

I played Bard for the first time during the last VTD and was not able to get Soundburst to register to the roller when used. Sonic Dart had no issues. I did a search first to see if this had come up before but didn't see it, and not sure where the issue might come from in my case. The app made it look like the attack was taking place and calculating damage correctly in the lower left margin where results normally show, the spell was checked off when used, but it did not appear in the roller either time I used it. I know once was room 7, the other was in a prior room.

Just in case you didn't see it, a ruling was added to MEC and summarized in this thread.

truedungeon.com/forum?view=topic&catid=572&id=256024

Version 10.3.0 has been released on Android and IOS with the following updates:
1. Updated Creature File
2. Corrected features of some tokens
3. Corrected some issues with Spell Sequences, forking and skill tests
4. Corrected Cast spells with sharpened spells and critical misses

BTW: I did look at Barbarian Rage and Fury and it appears to be working correctly. Keep in mind, Fury only applies to 1 attack roll, so any miss due to incorporeal, or AC or any other 50% miss will render it useless.

Bard Soundburst is an AoE spell, with a spell pool so must be handled manually with the GM.

Cranston wrote: Version 10.3.0 has been released on Android and IOS with the following updates:
1. Updated Creature File
2. Corrected features of some tokens
3. Corrected some issues with Spell Sequences, forking and skill tests
4. Corrected Cast spells with sharpened spells and critical misses

BTW: I did look at Barbarian Rage and Fury and it appears to be working correctly. Keep in mind, Fury only applies to 1 attack roll, so any miss due to incorporeal, or AC or any other 50% miss will render it useless.

Bard Soundburst is an AoE spell, with a spell pool so must be handled manually with the GM.

Wizards - Just get rid of 'em.

I so love your app and can't express how much I appreciate your effort. Having said that, I'm in the middle of redoing my earlier tests, but am already finding some strange things.

Test 1 - Cast a Magic Missile (manually and using spell sequence)
Base Damage = 11 (with skill check) Bonus Damage = 40 Expected Result =51
Manual Cast Damage = 51
Spell Sequence Damage = 51
All looks good

Test 2 - Cast a Magic Missile using MEC (manually and using spell sequence)
Expected Result = 62
Manual Cast Damage = 62
Spell Sequence Damage = 67 (appears like you're taking the normal damage of 51 and adding the base damage (without skill check) of 8 twice for MEC, instead of taking base + skill check.

Test 3 - Cast a Magic Missile using Fork
Expected Result = 51 Fork = 51
Manual Cast Damage = 51 Target 2 = 51
Spell Sequence Damage = 54 Fork = 48 (appears like you're adding the skill check amount in twice to the first target, but still not adding it to the forked amount.

More to come. But thought I'd give you a heads up on what I'm seeing.

Test 4 Magic Missile using MEC and Fork
Expected Result = 62 (11 base + 40 bonus + 11 MEC)
Manual Cast Damage = 62 Target 2 = 62
Spell Sequence Damage = 70 Fork = 56 (appears like the base without skill check is getting triple counted for the first target and should only be x2 including MEC) The skill check is still not getting counted at all on the Forked Target.

Things are getting a little bogged down.
Test #5 Acid Ray using Sharpen
Expected Results = 52 (normal hit); 104 (on a crit); 0 on a miss (crit miss or otherwise)

Manual Cast Damage = 52 (normal); 64 (crit); 0 (I think on a miss) Appears that only the base damage is doubling on a crit. All damage should double. On a miss, it displays "spell miss" and then shows the die roll result twice. I just assume a damage of 0 is fed to the dice roller. At least it does pick up that it was a miss. Even when my "to hit" bonus was +19, a natural 1 displayed as a miss.

Spell Sequence = 52 (normal); 104 (crit); Despite 82 attempts (even lowering my "to hit" bonus to 3), no misses were displayed.

Still want to do more testing with MEC and Fork on a slide spell, but until the above is fixed, I'm certain it's not going to work as expected.

Edit: Also, just to be sure, I assume version 10.3.0 is the most current.

When doing the Druid test, it is very difficult for me to find the choice I'm looking for.
1. Can you please put the choices in alphabetical order?
2. Can you choose colors which are easier to read? White on light gray does not have enough contrast.

Beertram wrote: When doing the Druid test, it is very difficult for me to find the choice I'm looking for.
1. Can you please put the choices in alphabetical order?
2. Can you choose colors which are easier to read? White on light gray does not have enough contrast.

Are you running the app in dark mode? I don’t have a contrast problem, but I’m running dark mode.