Search results

ASH scripts now support 'var' for local variable type inference, where the compiler will infer the type of a newly initialised variable. This should make dealing with records easier, as you can now do: var kit=black_and_white_apron_kit_contents(); print(`Main: {kit.main_ingredient} ->...

This will also have knock-on effects for available_amount, which should return the gems you can unequip as available.

We pick the ID if there's a comment telling us what the ID is, and the name if we can't do that. So the ID is better and preferred, but in many cases we only get the name, and because names are ambiguous we can't safely convert it to an ID.

This bug was solely the change in the image server; your bug sounds more serious. I assume https://www.kingdomofloathing.com itself works fine? I know there have been PHP changes (they upgraded from 5 to 8), but I haven't heard anyone else having such serious issues. Also, as normal scripts...

Thanks, I've stuck this on loathers and updated autoscend's dependencies to use it.

We should just set the max at the same time as the min to keep previous functionality (default max if the user doesn't set one).

KoL seem to be changing the encoding on their side, with HTML characters, latin-1 and utf-8 all being involved. Give it a few days to settle down and we'll see where we end up.

Yeah, I didn't wire anything up, and this is the first noncombat skill that requires having a particular familiar equipped to cast it, to my knowledge.

Some scripts check floristFriarChecked, that's why it was added back, for backwards compat. Intended behaviour: eh if it only happens once it's not a priority fix for me, but sure if isRefreshing avoids it you could do that.

Might be fallout from r29199.

My inclination is #1, similar to monster parts. Though, given there's only three options, #2 or #3 is also viable. Probably I feel like separating it just because it's only relevant in one specific case: you're in BvR and want to look up the team of a monster you might be fighting (and we're...

We also want prefs for "XUses" for the liquid, intangible, toxic assets. And possibly soybean futures. And how many of the inflationary pricing things you've bought. And limits for the other stuff.

`lastEncounter` is the entity-decoded actual monster name. So I would need to check whether e.g. Legstrong bicycle and the monster modifier-added monsters still go through correctly.

So there are two issues here, one Mafia and one garbage-collector. The Mafia issue is that can_adventure is returning true for the Middle Chamber when it shouldn't be. But we do actually have code for that so I'm not sure what is going on: if (this.zone.equals("Pyramid")) { if...

There's a link on the right hand side of the Valhalla decorator.

We do already use custom modifiers (Generated:_spec, Generated:_userMods, Generated:fightMods) for various things, generally maximizer-related, so you could jam it in there if we guarantee it'll be populated appropriately. I know that autoscend uses Generated:_spec for extracting modifiers.

Yeah, I agree with irrat that backing up the journal file isn't necessary, because writes are append-only so we should see the same corruption we see with the preference file, which is completely rewritten. I would prefer to keep the journal file separate to the preferences file for...

Brief comments. Periodic savings: opposed; we use the file to write daily flags we can't necessarily recover from the game easily (e.g. how many habitat fights you have left), and this makes it worse for people. Journal: support, this looks great tbh, and I think it makes it even easier to...

Yeah, modes aren't items, so $item[Jurassic Parka (spikolodon mode)] isn't a thing. I guess the way to do it would be equip(item, string) and equip(slot, item, string).

If you report this to the garbo devs they may be able to blacklist the Nemesis' Lair: https://github.com/loathers/garbage-collector/issues On our side I don't know why garbo is trying to adventure in the Lair, but we could set can_adventure to false after the quest is completed.