Search results

Whoops, sorry about that. New version uploaded, but I didn't bother to update the version number. If you have the broken version, it won't be checking anyways.

Okay, the bad moon mcd stuff and the -ML problems are both fixed.

Do you have an outfit that slime2 is a substring of?

That means that for whatever reason, you weren't able to equip all the pieces of your slime2 outfit. I just don't understand why you would stop being able to equip something on the middle of the script running.

Use "Spell Damage Percent" modref gives you a complete list of modifiers that can be used with the x_modifier() functions

numeric_modifier(item,string) does exactly what you want. For example, ash numeric_modifier( $item[flaming crutch] , "Hot Damage" ); in the CLI returns 3.0

Indeed. Another reminder why sleep deprived coding is bad.

Bale: Simply change this: matcher s = create_matcher("(\\w+)(\\s=*\\s*(\\w+))?",$string[%%]); to this: matcher s = create_matcher("([\\w\\.]+)(\\s=*\\s*(\\w+))?",$string[%%]);

In honest confusion, what do between battle scripts have to do with recovery?

According to the wiki, your "Achievements" section of your quest log gets "You have discovered the secret of the Dungeons of Doom." put in it when you complete the greater than sign.

Oh noes, they've caught us! We're totally trying to steal your credit card info.

Update mafia.

There's a buy script out there for that, I know. Maybe that's what you were thinking of?

No, I need to know what the lastEncounter property gets set to after you have encountered Mother Slime.

It currently attempts to abort if the lastEncounter property is set to "Showdown". I'm not in a position to check, so if someone could find out what that gets set to, I should be able to fix it.

I've edited my local copy of parse_mail() to check all pages, instead of just the first one. I've gone long enough between logins a few times that I have multiple pages of notify commands. My local copy is as follows (beware the regex, zarqon!) message[int] parse_mail() { message[int]...

And I've now got a bugfixed version uploaded. All the bugs mentioned so far are fixed, but I haven't had time to add in KoL macro support, sorry. Also, I think that blank-out support is best left to moods.

I really do love how jason takes a problem, and finds a solution to it we never knew we wanted, but probably wouldn't want to live without once we have it. Thanks for all the work you've put in!

I definitely need to get a new version uploaded. I've had that fixed in my local copy for weeks >.<

Macros I can definitely work on, as soon as I have time. Is there anything that guarantees that a line will be a macro instead of a regular ccs?