Search results

Actually, the limit is one, if you have over 500 hp: case SkillPool.DEEP_VISIONS: maximumCast = KoLCharacter.getMaximumHP() >= 500 ? 1 : 0; break;

I added it a while back for items of the month with daily passes which can’t otherwise be recognised

Barrel shrine is different, there is no daily access so visiting it in the browser will set the preference.

Or more likely it is in item number order, and what you are seeing is powercreep over the years.

Generally because no one cares and wouldn’t maximise for them. If you aren’t going to maximise for them, we don’t really need to support. Occasionally when one becomes important it gets added. Can certainly see an argument for adding various ways of adding passive or retribution damage, as they...

We could also use it to set the monster appearance rates in AreaCombatData.

It is because by default, at present, ALL items that match a boolean requirement are passed through to the brute force maximization, so would need pruning. Numerics already get pruned.

I definitely think we can quash, eventually, the not preferring an unhelpful item over no item. If you have no item, and it doesn’t beat a tie with an item, then stick with no item. That is a bug I’ve tried to track down several times and over many hours. I don’t see how we can ever get...

This isn't done yet, but I think I've hit the wall for today. It works, badly and slowly, for +club, as it hasn't yet got pruning. It doesn't work, yet, for +accordion, +knife or +utensil, I suspect I've missed turning an int into a long somewhere. If anyone wants to take a look, feel free...

Well, it isn't quite that simple. Most items that give a boolean exist on relatively few items, and Maximizer just passes them all through. However, there are loads of items that meet these booleans, so we need to prune the list to just the best one in these cases.

It does look like making club, utensil, knife and accordion into Boolean modifiers would make this work better (and needed as getScore considers only modifiers, not items). So I think it's converting bitmaps to longs (as this will take us over 32 booleans), adding 4 boolean modifiers, and...

If you don't want an item removed from a slot, use -slot. eg, you put on the weapon you want then use "-weapon" in the maximization. Or say you always want your accordion thief to use an accordion, you use +accordion. -tie is explicitly for saying you aren't going to use a tiebreaker.

That'll be a KOL bug, as it's KOL that tells us which skills we have. It isn't unprecedented for us to handle it until KOL does.

-tie says "I don't care what items are equipped if they don't change the maximizer result." So if you care, don't use -tie.

I have toyed with adding a comparison of outfit sets whose bonus changes with number with the best of other items, so we can prune items that only might help before the full iteration. It should be possible, and make a big difference, but is quite a big project.

I mean any time you try to prioritise two different things. So this can be boolean + maximization, or maximization with min or max supplied. Ideally one day a maths guru will totally rewrite maximizer using advanced maths!

We probably should do something like this. I’d feel keener if it weren’t for the fact that the thing Maximizer does worst is these kind or prioritisations.

And that is what the true/false means, according to https://wiki.kolmafia.us/index.php?title=Who_clan The boolean values are true if the character is in clan chat or false if just listening.

There are a few different chat versions, maybe you are using another?

> ash who_clan() Returned: aggregate boolean [string] Darzil => true Kittenbabble => false justinarms => false missfishie => true Players in this channel: missfishie, Darzil, Kittenbabble, justinarms (4 total) (and Kittenbabble and justinarms are in grey)