Search results

Forgive my ignorance (and you can ignore this, I'm just trying to learn more about kolmafia), but what's the bug? Did you have 2 glacial clocks, and thus were expecting 2 to be equipped vs. the clock to be moved to the 2nd acc slot? My cursory reading of the code says it's doing what it's...

:)

You should stick that in it's own feature request, sounds like a good idea. :) Or wait for Bale to do it...

Cool, thanks!

Yeah, googling around about this got me the pack() method, but trying that out as a part of the MaximizerFrame initialization didn't seem to make a difference, I kept digging for a bit, but quickly got lost in a twisty maze of Java classes, all alike. :) If you do have any better luck with it...

By default for me (linux running openJDK 1.6), the maximizer frame is sized juuust small enough to drop off the "pullable/buyable" radio button and the "all consumables" radio button. :) I for a long time had been annoyed that the maximizer "didn't" support pulling items from your closet, and...

So, balloon monkey reminder is already a reminder. The gunpowder should be covered with breakfast (seems unnecessary to have a reminder to do breakfast), and that's not a "per ascension" thing anyways. And the loathing legion knife I assume is a convenience thing, not because you're missing out...

Ah, I see you did indeed have to make a change to get modtrace to work. nifty.

I should clarify - it would only show prices when the suggested action is "acquire", i.e., get something from the mall. So if you don't choose the "pullable/buyable" radio option, you will unsurprisingly never see prices. If you choose that option (to get stuff from hagnks) but aren't out of...

hmm. I already found a place where I missed stuff on my patch (this just gets items, not equipment). :) So, please ignore the patch for now, just let me know if the feature is worth it or not. Sorry about that.

I noticed an interesting quirk as I learned more about the maximizer setup - it would only show mall prices for items when you specified a maximum price (and of course chose pullable/buyable and can buy stuff from the mall). I would find it more useful to always show the price of the mall item...

Well, I am not a developer (java or otherwise), so take this all with large grains of salt, but in my experience when you're getting garbage responses back like that, you're reading some random section of memory rather than a properly initialized io stream. It looks like the socket is being set...

Can you/someone post a debug log of a fight where you're not getting the combo recognized? I'm happy to volunteer to poke further at this, but I'm not going to be a DB for a while still.

Ah, excellent catches, makes sense. :) I hope this has nothing to do with the bug fronobulax just reported - http://kolmafia.us/showthread.php?10823-Cannot-use-Sofa-%97-r11337

:) I will be sure to take you up on that offer...

The difference was (is) for me is that for adventures left, they're prominently displayed both in kolmafia and the relay browser. By default (or at least, how I have it configured), PvP fights left are not obvious at all - and with the pvp revamp, it's worth grinding the pvp fights even if you...

I've forgotten to use up my PvP fights a few times when ascending, so spent the brief period of time to whip up an addition to the common things to do section of the astral gash page. Patch is pretty trivial, and takes people to the "pick a fight" page in the Colosseum, as I figure that's more...

I wasn't sure how to fix the generic case, as it seems like the part of kolmafia that knows when the HP is lost doesn't have any idea if it's during the recovery process or not. Or at least, it's beyond my ability to figure out so far... so I patched the specific case, which is vastly easier...

Yup, but that "next GET" should have had be printed out to the debug log (with the corresponding "---- FROM BROWSER -----" line), no? and it didn't seem to be. Hence my recommendation for more info when this error occurs, in a prior post. Winterbay, if you can duplicate in the future, you...

You should post the debug log in a separate thread to get that looked at. I took a quick look this morning because I was curious, but didn't see a connection between the stack trace and the log to suggest a fix. Did you have debug log turned on when this happened? I assume you can't reproduce...