Recent content by Ryo_Sangnoir

I also use IntelliJ, and it works fine for me. So yes, try a reimport? Or git clean?

Should be fixed in r29326. A bit late, but there in the end.

Due to recent work, we can add fields to the record and keep old scripts working, so we could add a "types" field that returns all types, while keeping "type" returning whichever is first, for example.

Probably we should just add that one, and any other ones people were using in the wild.

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...