Search results

Heh, as a web dev by trade, it wasn't anywhere near as bad as some of the code I have to work with. If you have web-y features you want added (better selector boxes for stuff like outfits and familiars?) just let me know and I can poke it.

The map totally makes sense, it would just be nice if there were some comments documenting the process of adding new settings (though I'm guessing it wouldn't matter much, the number of people would would be editing it either way are minimal).

It really wasn't that hard, the worst part was how the zebra striping on the rows is handled. That could definitely do with some poking. Also it wasn't totally obvious at the start that I had to add the new settings to the map file.

Hah, the gist I posted has the relay script fully updated for the familiar scripts actually, so not a big deal either way :-)

Seems reasonable :-) You want to put together the patch or should I?

I mean that there are settings within Harvest that will affect the final computed set of equipment. This logic could be duplicated in a BBS but just shoving stuff in temp preference means that the final computed data is just available. Its really a minor thing though.

You could, but it would make the script more sensitive to the internals of Harvest (thinking of things like the sugar sheets setting and such).

That seems like it would address the same needs, so consider me +1 on the BBS to work the same way as CCS! About the only addition I would request is storing the per-task equip settings in something like _har_current_familiar just to reduce code duplication if the BBS wants to use those se

So another option I toyed with is having a single hook script that gets passed the stage name (and probably the familiar settings from Harvest) as arguments. That would reduce the impact of it from the UX side, and could be lumped in alongside the eatdrink script hook, etc. As for the idea that...

I asked about this a while ago, finally wrote the patch and been using it for a few weeks now. https://gist.github.com/4012381aa0b3c6b28e42 that adds the idea of a familiar_script for each mode, which if set overrides the normal familiar/familiar equipment logic. I can share my test script which...

That is a very good point, will update.

That is, indeed, exactly how it works :-) I just mean that Mafia doesn't have that kind of tracking internally and there isn't anything in-game to check do if, for example, you manually use the fangs it gets out of sync.

Each of the three sub-sections can be visited once per day, however because there is no way to cancel the choice adventure once started the script just has to track which areas it has visited. It does print out messages about already visiting a location, it just does it at verbosity level 6

If you have already vamp'd then future attempts would be no-ops for the same area. If you mean you ran it yesterday and are not getting anything today then please run "zlib verbose = 9" to get debugging output and run it again (and post any output you get).

Ahh yep, you are right. Right now vamp_masq_stat=main will just always give you Malkovitch. Fix is in for the next version, thanky!

A script to automate this adventure is now available http://kolmafia.us/showthread.php?8291 A daily deeds version is on my to-do list.

vampout 0.4 Automatically equip your Plastic Vampire Fangs and run the choice adventures in Vamp Out. To Use: Install zlib. Download vampout.ash and place it in your scripts/ folder. Run vampout.ash either from the scripts menu or via run vampout in the CLI window. Settings: vamp_do_vlads...

Two questions: 1. Is it possible to automate rotating familiars for daily drops and/or running Boots stomps? 2. Is it possible to run other ad-hoc daily tasks (first one that comes to mind is getting a Black Heart each day)? It seems like the answer to both is probably not currently, but if...

Schweet! Going to try and port the little zlib settings manager I made to this as an example.

Yep, and you can also pull in the KoL CSS (what little there is) and use their styles.