Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12

Thread: maximizer silent nightlight issue

  1. #1
    Senior Member
    Join Date
    Oct 2017
    Posts
    285

    Default maximizer silent nightlight issue

    http://kol.coldfront.net/thekolwiki/...ent_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.

  2. #2
    Developer
    Join Date
    Apr 2010
    Posts
    4,758

    Default

    -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.

  3. #3
    Developer
    Join Date
    Apr 2010
    Posts
    4,758

    Default

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

  4. #4
    Senior Member
    Join Date
    Oct 2017
    Posts
    285

    Default

    So I guess the more general question is, which others of these should be ignored by -tie ?
    Originally Posted by Darzil View Post
    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?
    Last edited by taltamir; 06-21-2018 at 11:57 PM.

  5. #5
    Developer
    Join Date
    Aug 2009
    Posts
    2,796

    Default

    private static final String TIEBREAKER = "1 familiar weight, 1 familiar experience, 1 initiative, 5 exp, 1 item, 1 meat, 0.1 DA 1000 max, 1 DR, 0.5 all res, -10 mana cost, 1.0 mus, 0.5 mys, 1.0 mox, 1.5 mainstat, 1 HP, 1 MP, 1 weapon damage, 1 ranged damage, 1 spell damage, 1 cold damage, 1 hot damage, 1 sleaze damage, 1 spooky damage, 1 stench damage, 1 cold spell damage, 1 hot spell damage, 1 sleaze spell damage, 1 spooky spell damage, 1 stench spell damage, -1 fumble, 1 HP regen max, 3 MP regen max, 1 critical hit percent, 0.1 food drop, 0.1 booze drop, 0.1 hat drop, 0.1 weapon drop, 0.1 offhand drop, 0.1 shirt drop, 0.1 pants drop, 0.1 accessory drop, 1 DB combat damage, 0.1 sixgun damage";

  6. #6
    Developer
    Join Date
    Aug 2009
    Posts
    2,796

    Default

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

  7. #7
    Developer
    Join Date
    Apr 2010
    Posts
    4,758

    Default

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

  8. #8
    Developer
    Join Date
    Apr 2010
    Posts
    4,758

    Default

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

  9. #9
    Senior Member
    Join Date
    Oct 2017
    Posts
    285

    Default

    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.

  10. #10
    Developer
    Join Date
    Apr 2010
    Posts
    4,758

    Default

    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •