Minty23185Fresh
September 22nd, 2017, 16:37
I received this error when adding a spell to the Actions tab on the player's Character Sheet.
In my opinion, under the circumstances presented below, there really is no error. The error is that Fantasy Grounds is reporting one when there really isn't one.
There are four screen shots presented, in each one a portion of the Chat window is captured on the left side and a portion of the Character Sheet is presented on the right. The first two screenshots present nice FG behavior, the second two present the questionable behavior by Fantasy Grounds (again in my opinion).
In this screenshot I am getting ready to add a spell to a new character a sorcerer. During the character creation process a "default" Spell Group is created. It is circled in red here. The main reason for this pic is to contrast with the third screen shot.
20627
In this one I dragged a Burning Hands spell from the Spell Library on to the Actions tab. Everything goes as expected. This is presented to contrast it to screenshot four.
20628
In this screenshot similar to the first, except that the "default" power group is not present. I deleted it. For a non caster character or a home brew or experimental character FG (most likely) will not create a "default" group. The nonexistent group is circled in red. (Compare to the first screenshot.)
20629
And finally the questionable condition. Again, as in the third screen shot, I dragged Burning Hands on to the Action tab. Note the reported errors in the Chat.
20630
First, I suspect there are so many errors reported because the spell itself causes an error to be thrown, plus the Cast, plus the Dmg sub items as they are added by FG's code.
But, the reason I am arguing that this is not an error condition is because FG's code handles everything just fine. A new power group is created and properly populated (screenshot four, Character Sheet). True the code couldn't find a group, but the code acted resourcefully and created one. All these flags come up and one might get nervous. But nothing really went wrong. So, where's the error? All sorts of unexpected conditions may happen during code execution, but it is the ones that aren't handled robustly by the code that approach errors. That is not the case here, I believe.
In my opinion, under the circumstances presented below, there really is no error. The error is that Fantasy Grounds is reporting one when there really isn't one.
There are four screen shots presented, in each one a portion of the Chat window is captured on the left side and a portion of the Character Sheet is presented on the right. The first two screenshots present nice FG behavior, the second two present the questionable behavior by Fantasy Grounds (again in my opinion).
In this screenshot I am getting ready to add a spell to a new character a sorcerer. During the character creation process a "default" Spell Group is created. It is circled in red here. The main reason for this pic is to contrast with the third screen shot.
20627
In this one I dragged a Burning Hands spell from the Spell Library on to the Actions tab. Everything goes as expected. This is presented to contrast it to screenshot four.
20628
In this screenshot similar to the first, except that the "default" power group is not present. I deleted it. For a non caster character or a home brew or experimental character FG (most likely) will not create a "default" group. The nonexistent group is circled in red. (Compare to the first screenshot.)
20629
And finally the questionable condition. Again, as in the third screen shot, I dragged Burning Hands on to the Action tab. Note the reported errors in the Chat.
20630
First, I suspect there are so many errors reported because the spell itself causes an error to be thrown, plus the Cast, plus the Dmg sub items as they are added by FG's code.
But, the reason I am arguing that this is not an error condition is because FG's code handles everything just fine. A new power group is created and properly populated (screenshot four, Character Sheet). True the code couldn't find a group, but the code acted resourcefully and created one. All these flags come up and one might get nervous. But nothing really went wrong. So, where's the error? All sorts of unexpected conditions may happen during code execution, but it is the ones that aren't handled robustly by the code that approach errors. That is not the case here, I believe.