Bug maximizer silent nightlight issue

http://kol.coldfront.net/thekolwiki/index.php/Silent_nightlight
Gives +5 to stats, and a 50 turn buff of +10 to stats if worn overnight.
It seems to that -tie does not exclude it like it does other items.

Using
+meat, -tie
+combat -tie
ML -tie
and probably many other things all result in maximizer trying to equip the silent nightlight, even though it has no effect on any of those things.

-Tiebreaker means that it doesn't use the tiebreaker expression to compare items.
Ties are still broken by:
Lower B count (in Bees hate you)
Preferring item droppers
Preferring meat droppers
Preferring rollover effects
Preferring unbreakables
Preferring worn
Preferring items you don't have to buy
Preferring fewer B's (in Bees Hate You)
Prefer items you have

So working as intended, but perhaps not as expected.

So I guess the more general question is, which others of these should be ignored by -tie ?

Darzil said:

So I guess the more general question is, which others of these should be ignored by -tie ?

Click to expand...

Thank you.
That is a pretty long list of tie breakers that are hardcoded outside of the tiebreaker function. I have a question... if you do not use -tie, what additional things are used to break ties beyond the list you gave?

This is particularly noticeable for bodyparts where the score is 0. That is, if you are doing "cold res, -tie", and you do not own a pair of pants that gives cold res, it might still use the above tiebreakers and swap out your already worn pants (which you are probably wearing for a reason).

I can see the usefulness of most of those tiebreakers, but that is what the tiebreaker function is for after all. -tie is specifically informing the program that you do not want it to break ties. I can see how changing it might be a problem with people preferring things as is...
Is there perhaps a function that is a more strict version of -tie that prefers worn items over all items which have a score of 0?

I think there's "+current" that you can use. I don't remember if it ignores all these other tiebreakers.

+current just makes sure that current equipment is always considered, and is the default in hardcore or ronin

I suspect we should avoid all those tiebreakers using -tie for logical sense.

Thanks heeheehee and drazil. That was very informative. Also, logical sense! that is such a succinct phrase.

Drazil, what do you mean by "current makes equipment always considered"? I don't quite understand what always considered means here.

Ok, the way maximizer works (which could be improved by a maths wiz who understands KoL, probably), is it makes a list of equipment that meets your request, then sorts that list from best to worst scores, then considers the best N items on that list, where N depends on a few factors (number you can use, how many are only conditionally best), plus any that as part of a set might be best. It then brute forces the remainder, which is what takes most of the time.

+current forces current equipment to be considered and go to the brute force part. By default Maxmizer sends current equipment in Ronin/Hardcore to the brute force section, where number of item combinations is probably low. By default in Aftercore it doesn't send current equipment, as it assumes you are likely to have something good for every slot and considering current also could make the brute force section take several times longer.

I think this may be related. If little bitty bathysphere (-20 lbs) happens to be your only available generic familiar equipment, maximizer tends to want fill that slot with it. In most cases, that are not the sea, it's actually more beneficial to leave the slot empty. Not sure if/how "-tie" may/may not apply in this situation.

Hopefully r18833 prefers nothing over items that are worse, which might fix your (possibly) unrelated issue, AlbinoRhino.