@Veracity: Not at all -- it'll only be incovenient the first time I need to consult the data files; after that I'll know how to do it, and eliminating a cause of user self-screwage is definitely worth it. In short, we are completely on the same page about this. Plus, as proxy records get more complete, scripters have less and less cause to parse mafia's data files.
@adeyke: Ok, this is on the list to investigate once I get to aftercore (doing a 100% Hipster run atm). I suspect it's due to batround not being properly inserted into DB combos when macrofying. My KoL playing has been rather spotty of late, thanks to an intermittent internet connection and the continued lack of my laptop.
@lazy_fire: Good call. Will be in the next update.
@Galanodel: For once Bale's not quite right; SmartStasis uses a bounty.txt with a different format than that on the Map Manager -- the vestigial call to load_current_map() should actually be a regular file_to_map(). I hadn't bothered with this issue since at the time, adding bounty information to proxy records had seemed towards the top of Veracity's queue, which would allow us to dispose of that map entirely and streamline the code a good bit in the process. But new IoTM's, Valhalla revamps, spider-infested servers, et. al have conspired to push the proxy record feature requests down a ways, it seems. I suppose I should consider a "more semi-permanent" solution to this.
Also, thanks for searching the thread and finding your own answer, 40 pages back no less! You are a shining example of Good Foruming.
