Search results

The change can be applied to mirror, it's not really a defined interface that we need to not change at all

Thanks V. We could consider changing the MafiaState.ABORT to MafiaState.ERROR but I'm also heartened somewhat that the change surfaced some actual bugs that we didn't know about and has lead to them being fixed.

I think https://github.com/kolmafia/kolmafia/pull/936 may help with this one a little bit.

Thanks pya. It would help me get to fixing it if you could you drop a DEBUG log for this happening?

I defer triage to a Windows user :)

https://github.com/kolmafia/kolmafia/pull/936/files

I will fix this but I must say that not checking you have an item before using it and then not checking you're in a choice before attempting to choose that choice is silly.

https://github.com/kolmafia/kolmafia/pull/935

But why do you need html for that

I'm fine with changing mirror to more exactly copy the GCLI output but I must ask why on earth you want it

Seems like that could be refactored to be a list, or even a query on the item database sorted by +weight

It's a simple PR, please do make it!

If we were to do something like this I'd be interested in adding a new column to defaults.txt that describes when a pref is reset "r,a" could be rollover and ascension and would sit next to existing prefs with a leading underscore

I would be interested in an _ascensionsToday pref, PRs welcome. Potato alarm clock should be fixed on the mafia end - we can problably give it a _ exception to only apply on true rollover.

You can implement this yourself by maintaining a pref with the day and resetting all prefs with a certain prefix when you see that that date is old.

Ok as I flesh out the further support, I realise the ash function I added is probably not quite right - it might be nicer to have item [int] expected_cold_medicine_cabinet(); where the int key is the choice and the item is the item you'd get from that choice. That is once we have estimation in...

Basic support for this has landed, and you can run `cmc` to see what your expected pill is. I want to expand on the information in that readout when I have time. I imagine it will occasionally be wrong as we iron out combats that should be excluded.

We now track the "charge" of the vintner. The only thing left to my mind in supporting this is to keep track of the types of damage dealt in vintner combats. This is quite difficult, as the damage tracking code we have used for over a decade strips all the elemental source data as its first...

So something like this? https://github.com/kolmafia/kolmafia/pull/914/files#diff-f07b31e0b504b71dde351351f48dd71300f98c1426d582a66523936abfca2373R4389-R4406 I'll write tests imitating the example and expected outcome of what scotch posted above in due course. This also does left newest right...