Unable to load armor data

graspee / polutils

Automatically exported from code.google.com/p/polutils

Apache License 2.0

0 stars 0 forks source link

Unable to load armor data #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
Attempting to load the armor data. 

What is the expected output? What do you see instead?
Expecting listing of armor data.  Got a message that said something like "Could 
not read file type."

What version of the product are you using? On what operating system?
0.9.7 x64 Windows 7 Pro 64

Original issue reported on code.google.com by scr...@gmail.com on 9 Sep 2010 at 4:57

GoogleCodeExporter commented 9 years ago

Fix available, need Project Committer to respond.
Current Armor.xml available online, see my Google Docs specifically.

Original comment by doomer18 on 9 Sep 2010 at 2:38

GoogleCodeExporter commented 9 years ago

Hey doomer, I've been trying to contact Tim without any luck. I hope all is 
well with him.  Do you have a build with your patch available anywhere?  I'm 
trying to get my DB updated, kind of stuck with the armor (and it's icons).  
Any assistance will be appreciated!  Email: scragg@ffxiah.com

Original comment by scr...@gmail.com on 9 Sep 2010 at 5:06

GoogleCodeExporter commented 9 years ago

Sent it via attachment.

Original comment by doomer18 on 9 Sep 2010 at 5:14

GoogleCodeExporter commented 9 years ago

I don't think my domain liked the attachment.  Try scragg@gmail.com instead.  
Thanks!

Original comment by scr...@gmail.com on 9 Sep 2010 at 5:20

GoogleCodeExporter commented 9 years ago

Sent via Gmail that time.

Original comment by doomer18 on 9 Sep 2010 at 5:31

GoogleCodeExporter commented 9 years ago

Fix seems easy enough; I'll have a build made this weekend.

Original comment by tim.vanholder@gmail.com on 10 Sep 2010 at 8:30

Changed state: Fixed
Added labels: Component-Logic

GoogleCodeExporter commented 9 years ago

I see an associated problem is that the item data comparison utility does not 
cope with a case where the exported DATs cover a different range of IDs (it 
tries to compare 0x2C00 with 0x2800, 0x2C01 with 0x2801, and so on).
I'll try to implement handling for that as well, so that exports of the new 
item DATs can still be properly compared with old exports.

Original comment by tim.vanholder@gmail.com on 11 Sep 2010 at 10:44

GoogleCodeExporter commented 9 years ago

0.9.8 released.
Similar changes could be needed in the future if the decide to expand any other 
DATs.

Original comment by tim.vanholder@gmail.com on 11 Sep 2010 at 12:43