Search results

Thanks, r12027. EDIT: Actually, I forgot the black glass, but that will go in my next commit.

If I understand correctly, the steps to reproduce this are: 1) Autoadventure until you meet an unknown Choice Adv and use the gCLI to choose an option and go through it. 2) Adventure via the Relay Browser. Next time a Choice Adv is encountered, pressing a choice button will display the other...

Each steps correspond to a Quest Log entry. See the Quest Log KoLWiki page for a complete breakdown. EDIT: wooo, way to open a thread, wait 2 hours, and answer to a question that has already been addressed.

KoL is revamping the way most shops work, and the Vending Machine is one of them. See this New Content thread for more info.

I usually use http://gskinner.com/RegExr/ too, but it has a few small issues, like not recognizing that escaped parenthesis don't need to be closed.

The _raveStealCount preferences added in r12021 should take care of everything.

release 12021. Last palindrome release for a little while. Maybe not such a long while, we seem to go through them so fast...

Nice (and kinky...)! I'm guessing this can be equipped on any familiar?

Oh, I hadn't noticed. That makes you go through a series of hoops to get what you want, but at least it's possible :)

> ash $item[ amphibious tophat ].string_modifier( "Equips On" ).to_familiar(); Returned: Dancing Frog combat => false hatchling => perfectly ordinary frog image => dancfrog.gif name => charges => 0 EDIT: You can also check whether a familiar item can be used by every familiar: > ash...

Limited Monster banishers like poppers and crystal skulls aren't tracked currently.

Then Lost was right about using getEffectiveWeight(). Thanks for confirming this is fixed.

I merged the shop revamp threads. Here is what I gathered up to now: // Crackpot Mystic // forestvillage.php?action=mystic 26 white pixel 27 red pixel potion 28 blue pixel potion 29 green pixel potion 30 purple pixel pie 31 monster bait 32 pixel shield 33 pixel hat 34 pixel pants 35 pixel...

The new JarlsbergRequest.parseResponse() already proved useful! It turns out that staves don't follow the simple itemId -> row rule I used for other items.

{crafting method, row number}-> itemId is probably unique though. I don't know anything about Java data structures... I always just copy existing code when I change or add something. But I see two ways to do store the row information from concoction.txt: in separate row -> itemId maps, one...

For reference: row item itemId 26 white pixel 459 27 red pixel potion 464 28 blue pixel potion 465 29 green pixel potion 466 30 purple pixel pie 467 31 monster bait 1300 32 pixel shield 1630 33 pixel hat 688 34 pixel pants 689 35 pixel sword 690 36 digital key 691 37 pixel boomerang 3854...

It was a quick and dirty commit, but r12002 fixes JarlsbergRequest.registerRequest() and adds JarlsbergRequest.parseResponse().

I keep getting distracted lately and most of my commits only deal with half the problem I'm addressing. I'll have a look at this later on, if the baby lets me :D

r12001.

Jick isn't that cruel, is he? EDIT: Wouldn't it make more sense to have Jarlsberg be a coinmaster? It's too late now, and not worth changing, but I can't really think of a good way to determine whether this kind of new content should be implemented one way or the other. EDIT2: I wasn't...