Equipment optimiser for frogcomposband characters
Collapse
X
-
Character 41 had an exclusion that has an empty value. This somehow matched everything so the solver barfed when it was given 0 items to solve for.
When this happens, I have added a message in the Solution text box below about the possibility of item exclusions excluding everything.
Have also made it such that one should not be able to create an empty valued exclusion entry.
Hopefully this resolves similar issues in the future.Comment
-
The optimiser counts *Fi, *Co, *El, *Ac, etc. as different attributes from their respective Fi, Co, El, Ac attributes. Hence if you wear one *Fi item and have no other items worn that gives Fi, the attributes table will simply show:
Does that make sense? Or do you prefer if I present the attributes table as follows?Code:Fi: *0
Code:Fi: 0 *Fi: 1
Comment
-
The app did not take into account the (+2) or (+3) values for Wm. This should be fixed now.
I'm unable to replicate this. If this happens again for some other character, please can you keep a copy of the offending HTML dump file and send it to me? Thanks!Also, the first dump I uploaded that had the Dagger of Amun did not lead to that item being added to the item list. I tried putting it in my home and re-uploading, and then it was visible to the Optimiser.Comment
-
Parsing bug?
In my character's pack, I have:
a Ring of Combat (+16,+14) {Fe}
The Ring of the Future King (+11,+8) (+2) {St;Di;Si(St}
but the Optimizer recommends I use
a Ring of Combat (+16,+14) {St;Di;Si(St}
which appears to be some weird combination of the two that doesn't actually exist.
I'm excited about this optimizer! Thanks for making it
Comment
-
This is what I'm seeing in the Solution box for your character:In my character's pack, I have:
a Ring of Combat (+16,+14) {Fe}
The Ring of the Future King (+11,+8) (+2) {St;Di;Si(St}
but the Optimizer recommends I use
a Ring of Combat (+16,+14) {St;Di;Si(St}
which appears to be some weird combination of the two that doesn't actually exist.
I don't see this:ring: a Ring of Combat (+16,+14) {Fe}
ring: The Ring of the Future King (+11,+8) (+2) {St;Di;Si(St}
Please can you confirm that you are still seeing the wrong entry?a Ring of Combat (+16,+14) {St;Di;Si(St}Comment
-
Thanks for fixing the issues I was having, especially missing the /* tag on some items. This is a handy tool and we are grateful for your effort and for sharing it with us.Comment
-
I kept a copy of the offending character dump, and it still results in the error. I can send it to you if that would help. What's the best way to do that?
Thanks for your hard work!Comment
-
-
Thanks for sending me the offending HTML dump.Please send the HTML dump to optimiser@riverwaterhill.com and I will take a look. Thanks!
The problem here is that within the Inventory section of the HTML dump, similar items of the same "coloring" is wrapped in a single <font> tag.
For instance,
andCode:<font color="#c00000">a Ring of Combat (+16,+14) {Fe} The Ring of the Future King (+11,+8) (+2) {St;Di;Si(St} </font>
This is different from the other sections where each item is wrapped within its own font tag.Code:<font color="#c08040">a Fur Cloak of Aman [3,+10] (+2) {SpSl;Sh} a Large Leather Shield of Celestial Protection [6,+17] {DkSh} </font>
The parser in Optimiser had assumed that the two rings are one item and hence the strange combined attribute item you see in your character earlier.
I have done a workaround by treating the Inventory section separately so it should work properly now for your character.
Hopefully this doesn't break something else.
By the way, this might explain the problem that Bostock had earlier:
I'm suspecting that the dagger was in the inventory when he did the HTML dump. If it is worn or placed in home, it then "shows up" in the Optimiser.Also, the first dump I uploaded that had the Dagger of Amun did not lead to that item being added to the item list. I tried putting it in my home and re-uploading, and then it was visible to the Optimiser.Comment
-
Thanks, schatz. I love your Optimizer.
Idea, in case you're looking for them: allow us to assign weights to various stats for use in the Optimizer's maximization calculations. For example, we might tell the optimizer to value +dam more than +AC by assigning a weight of 1.0 to +dam but a weight of 0.4 to +AC.
Keep up the good work!Comment
-
I have a cloak with Aura of Shards and the Optimizer is counting it as both [Sh and Sh.
Sorry to pester; I love this Optimizer
Comment
-
Probably another case of the same error I reported last: gloves of slaying with the Slay Living flag get counted as having Levitation by the Optimizer (they both use Lv in their inscriptions). I think with the way the inscriptions are set up it should be possible to always determine the intention of an ambiguous string like Sh or Lv by detecting certain tag-like characters ([ and /)in the string before them.
Have a good one and thanks again!Comment
-
Fixed.Probably another case of the same error I reported last: gloves of slaying with the Slay Living flag get counted as having Levitation by the Optimizer (they both use Lv in their inscriptions). I think with the way the inscriptions are set up it should be possible to always determine the intention of an ambiguous string like Sh or Lv by detecting certain tag-like characters ([ and /)in the string before them.
Very much appreciate the bug reports. I should have written a parser for the attributes string rather than doing string comparisons. A bit too late now - something to keep in mind should I find more time on my hands.Comment
Comment