Validity Check bug?

[Fitz]

Whenever I open a character (all characters so far) I get a validity check warning saying that "Missile Deflection is not a valid modifier for Killing Attack - Ranged because it can already be Missile Deflected", and it goes on to say that the modifier will be removed.

All well and good, except that none of the characters I've opened so far have that modifier on their RKA, and one character doesn't even *have* an RKA.

On the plus side, it did spot a real bogus modifier on one character -- he had "Beam Attack" on a HA :)

[Simon]

OK...that's weird.

I can't get that to happen at all. Admittedly, I'm a bit lost for things to try (I've opened plenty of characters, many with RKAs and none of them have given me that warning).

The Modifier warning is correct...that Modifier is not valid on an RKA....but you shouldn't be getting it unless it is assigned to one of the characters that you have open.

Can you do me a favor and post all characters that you have open in the app when you get that warning? I want to load them all on my end and see what I can get.

Thanks!

[Fitz]

Further weirdness ensues on reopening: it now tells me that Armor Piercings is invalid for RKA because AP can only be applied to powers which act apon a target's defences.

Wuh???

Anyway, I've attached a zip file containing the three characters affected thus far.

[Simon]

Actually, those seem to be working fine for me.

The Immaculate Po loads without a problem.

Sir Fnord loads without a problem.

Hildegard loads with several messages:
1. The template specified cannot be found (obviously....you used a custom template which I do not have). HD used the Superheroic template instead.

2. Range Based on Strength is not a valid modifier on Killing Attack - Hand to Hand. Reason: you need to select the appropriate variation of the Ranged Advantage (there is an option for Range Based on Strength), you can't take Ranged and Range Based on Strength on the same Power.

3. Can be Missile Deflected cannot be taken on Killing Attack - Hand to Hand (this is on the same Power that has the Ranged Advantage). Reason: it can already be Missile Deflected. This is correct...the Limitation is invalid.

4. Can be Missile Deflected cannot be taken on Killing Attack - Ranged. Reason: it can already be Missile Deflected. Again, this is correct....

After that, the character loads in. You won't see those modifiers on the abilities, because they have been removed by the app's modifier checking. If you want for them to stay on the abilities until you remove them yourself, you need to change the appropriate option under your app prefs.

I get no message about AP on an RKA....was that on one of the characters that you posted?

[JTesla]

I might have encountered something that is similar. I have a prefab with Regeneration that is Inherent.

1) A warning comes up that states Inherent can only be applied to powers that are Persistent so it is removed.

2) I go in and add Persistent, for test purposes I click OK then edit again, no problems.

3) I go in and add Inherent and get the error: Persistent is not a legal modifier, Healing is already Inherent, Persistent will be removed. It adds Inherent to the list and removes Persistent

4) I hit OK and then go to edit and I go back up to #1. I went through the circle three times and keep coming up with the same results.

It appears that the Persistent is being removed because Inherent is being added, which is fine but then it is looking to have Persistent in order to verify that it can be Inherent.

Warning: I am still wading through the rules so I could have missed something simple, if so simply bonk me on the head.

[Simon]

Originally posted by JTesla
I might have encountered something that is similar. I have a prefab with Regeneration that is Inherent.

1) A warning comes up that states Inherent can only be applied to powers that are Persistent so it is removed.

2) I go in and add Persistent, for test purposes I click OK then edit again, no problems.

3) I go in and add Inherent and get the error: Persistent is not a legal modifier, Healing is already Inherent, Persistent will be removed. It adds Inherent to the list and removes Persistent

4) I hit OK and then go to edit and I go back up to #1. I went through the circle three times and keep coming up with the same results.

It appears that the Persistent is being removed because Inherent is being added, which is fine but then it is looking to have Persistent in order to verify that it can be Inherent.

Warning: I am still wading through the rules so I could have missed something simple, if so simply bonk me on the head.
Fixed. The problem was in the modifier intelligence check for Persistent.

We'll likely have a number of these to ferret out....this whole process for validating the modifiers on powers is a bit of a different way to go about things, as far as the app is concerned. It's definitely do-able, but there's going to need to be some adjustments (obviously).

Thanks!

[Fitz]

Originally posted by dsimon
4. Can be Missile Deflected cannot be taken on Killing Attack - Ranged. Reason: it can already be Missile Deflected. Again, this is correct....
[snipped]
I get no message about AP on an RKA....was that on one of the characters that you posted?

The Missile Deflection message came up when I loaded the Immaculate Po -- who doesn't have any RKA of any sort at all (though he does have MIssile Deflection).

The "No AP on RKA" message came up on loading Hildegard.

Possibly related: When starting that same session of HDv2, a message came up saying that an error had arisen loading prefabs that had been previously loaded -- however, no prefabs had been loaded at all during the previous three or four sessions (i.e. all prefabs had been unloaded and no new ones loaded).

[Simon]

Originally posted by Fitz
The Missile Deflection message came up when I loaded the Immaculate Po -- who doesn't have any RKA of any sort at all (though he does have MIssile Deflection).

The "No AP on RKA" message came up on loading Hildegard.

Possibly related: When starting that same session of HDv2, a message came up saying that an error had arisen loading prefabs that had been previously loaded -- however, no prefabs had been loaded at all during the previous three or four sessions (i.e. all prefabs had been unloaded and no new ones loaded).
I think you might be mistaken about some of the timings and what's going on with your system.

The prefabs message is extremely specific -- it will only occur during the loading of a prefab. There is an app prefs setting which specifies whether to reload prefabs during program launch or not.

It doesn't matter what order or in what way (manually or during application launch) I load in the three characters that you posted....Hildegard is the only one that generates any errors, and all errors that are generated are legit.

[Simon]

Using the current build, I get the following errors when validating each of the three characters (all of them are correct):

Sir Fnord: No errors.

The Immaculate Po: <ul>
<li><blockquote>No Knockback is not a legal modifier on Ch'i Strike: Hand-To-Hand Attack. Reason:

No Knockback can only be applied to abilities which do Knockback.</blockquote>

This error is absolutely correct...you've applied NND to the HTH Attack, which automatically makes it no KB.</li>
</ul>

Hildegard:<ul>
<li>Template load error (because I don't have the template that you used to create the character)</li>
<li><blockquote>Range Based On Strength is not a legal modifier on Magical Returning Dagger: Killing Attack - Hand-To-Hand. Reason:

Range Based On Strength cannot be applied to Powers that have taken the Ranged Advantage. Use the options on the Ranged Advantage instead.</blockquote>
This is correct. The Ranged Advantage has been changed to allow certain variations during its purchase....this gives you the correct Active and Real Costs for the Power.</li>
<li><blockquote>Can Be Missile Deflected is not a legal modifier on Magical Returning Dagger: Killing Attack - Hant-To-Hand. Reason:

Killing Attack - Hand-To-Hand can already be Missile Deflected.</blockquote>
This is correct. A ranged attack which targets an opponent's DCV and does not act against "unusual" defenses can be Missile Deflected by default.</li>
<li><blockquote>Can Be Missile Deflected is not a legal modifier on Heavy Recurved Bow: Killing Attack - Ranged. Reason:

Killing Attack - Ranged can already be Missile Deflected.</blockquote>
This is correct (see above).</li></ul>

All of these errors are correct, according to the rules. The Modifiers should not be applied to the mentioned Powers.

[Mastermind]

I liked the Validation Check.

I received a Warning on using AOE with Telportation that said,

"Cannot use AOE advantage if power is not usable on others"

However, when I wanted to add the usable on others advantage and then re-add the AOE, I could not find it.

What am I missing?

[Simon]

Originally posted by Mastermind
I liked the Validation Check.

I received a Warning on using AOE with Telportation that said,

"Cannot use AOE advantage if power is not usable on others"

However, when I wanted to add the usable on others advantage and then re-add the AOE, I could not find it.

What am I missing?
Could be a number of things....it depends mainly on what you have your app prefs set to.

If your app prefs are set to just warn you about any validation errors (and not remove the offending modifiers), then AOE is still on the Power, which is why it's not appearing in the list.

If you check and AOE has been removed from the Power and it's still not appearing in the list after you apply Usable On Others (in some form or another), then I'll need to know what other Mods you ahve assigned to tell you what's wrong (or you can check the reason AOE is not available by selecting it in the Unavailable Advantages list and clicking on "View Reason").

Basically, AOE should be in 1 of 3 places:

1. In the Advantages list, ready to be selected.

2. In the Unavailable Advantages list, with a reason why it is not available.

3. Already assigned to the Power.

I just created Teleportation with UBO and AOE immediately became available, so the app's logic seems to be working fine in that regard.

[Mastermind]

Figured it out!

Bottom line: Validation helped me to better define the powers that I wanted and within the rules.

[Simon]

Originally posted by Mastermind
Figured it out!

Bottom line: Validation helped me to better define the powers that I wanted and within the rules.
Glad to hear it ;)