I don't know if this is VTank specific issue but when I do a propertydump the LightProt returned it always 1. Which is what Nether Protection always is in the AC identification. I guess the AC client should be right on this so is this fixable?

I noticed the same issue and submitted bug report PMs to multiple people. I think someone told me it's a decal issue, not vtank.


I have armor rules looking for all 7 protects to be 0.8 or higher (excluding neither protect which is in fact always a 1 for real that I can tell). And keep looting things with "poor" on lightning. The other 6 protects seem to be working fine.

I fixed this myself.

In the messages.xml the definition is wrong for the return message that contains the protections. When Turbine changed it to include Nether they inserted the float for Nether (which is always 1) before Lightning so it got replaced in Decal. After adding the float for Nether in the definition myself everything works as expected and plugins now get the correct lightProt value (so for example loot profiles in VTank can truly work correct again).

This is a very trivial fix so I suppose Decal team can fix this when they do the memloc update for February patch?

Is there any way you could copy/paste that for us and tell us exactly where to stick it in the xml file?

AWESOME!! Thank you. I just did this and mine is working perfectly too now. =)


@ ColdAvaton,


Do a search for protAcid, it'll take you here abouts:

<field name="protAcid" type="float"></field><field name="protLightning" type="float"></field>


Copy this string for Nether:

<field name="protNether" type="float"></field>


Paste the Nether string inbetween the strings for Acid and Lightning:

<field name="protAcid" type="float"></field> **INSERT NETHER HERE** <field name="protLightning" type="float"></field>


You should end up with:

<field name="protAcid" type="float"></field><field name="protNether" type="float"></field><field name="protLightning" type="float"></field>


Now, Lightning will detect correctly, though I notice this does not make Nether show up on the PropertyDump, but who cares, it's always a 1 for real!. =)


Thank you _Blakar_ !!!


-Picaro

Excellent! Thanks!

I don't know how the file was made but it contains extremely long lines without linebreaks. As such some editors will have issues editing it. I avoided this by using vi in a cygwin terminal but that isn't exactly a common tool. I don't know either how this is parsed and whether possible format changes editors can make have any effect.

Nevertheless if you have an editor that works with the file you should search for protLightning in the file. It's in a long line and the definition looks like this:
<field name="protLightning" type="float"></field>
Before this definition you'll see the one for Acid which looks the same.

What you do is in between those definitions you paste this:
<field name="protNether" type="float"></field>

After the change Decal will also take into account the additional float that now contains the Lightning protection and as the plugins use the defined name everything works immediately as expected.

I used Win 7 Notepad and it seems to have worked.

as it turns out, Fire and Cold prots are backwards as well, you can just rearrange them in the xml.

 

-----signature-----

LoL, I never even noticed that. Thanks for the info.