I found a bug with the Scan function... or at least a strange behavior... (IMG:[
invalid]
style_emoticons/default/tongue.gif)
I don't like to store monsters data when they have a "Debuff Affected"... so I refuse to use Scan on monsters that have this attribute... however when I use Scan on a monster and it got a debuff on the same turn (i.e. from a Spike Shield)... HVStat stores the "original data" from monster (i mean, without the debuff) but put a "Debuff Affected" attribute on it... (IMG:[
invalid]
style_emoticons/default/blink.gif)
I guess this happen 'cause Scan occurs before the debuff but HVStat store the data only at the end of turn... (IMG:[
invalid]
style_emoticons/default/unsure.gif)
Well, I think images explain things better... (IMG:[
invalid]
style_emoticons/default/tongue.gif)
1) Here I use Scan to get information from monster:

2) In next turn I use Scan again and the target is affected by debuff on same turn... note that the mitigation data is identical to before (cause Scan occurs first) but it got a Debuff Affected tag:

3) Here I use Scan again, target still have the debuff and now the correct data is stored:

Is there anyway to fix that? (IMG:[
invalid]
style_emoticons/default/rolleyes.gif) ...cause i think in that way it can lead to some misinformation... (IMG:[
invalid]
style_emoticons/default/smile.gif)
By the way, is possible to add new option to "Never store scan results on database if the target has a Debuff Affected status"? (IMG:[
invalid]
style_emoticons/default/rolleyes.gif)
Anyway... Thanks very much to
greentea039 and every others users involved in the development of this excellent Script... it offers a completely new experience while playing HV... (IMG:[
invalid]
style_emoticons/default/wink.gif)