I wrote a haggling script for WeaponM that currently has the various factors hard-wired in. I'd like to use some persistent state so I could auto-detect the most aggressive settings permissible at each port (be more aggressive if they accept my offers, dial it back if they kick me out).

I'm assuming there's no documentation on this stuff yet, but where in the app sources should I be looking for examples of how to manage persistent state in the database?

There is documentation: http://chalcodes.com/maven/com/chalcode ... avadoc.jar

Check out Sector#setNote(String, String) and Sector#getNote(String). Sectors can have an unlimited number of notes, each identified by their unique name. The Database class has similar methods for global notes.

The database does not record MCICs yet. If you know how to calculate them, I'd welcome your help.

ah, cool, I'll check that out. thanks.



the only MCIC calculation info I've found doesn't produce working results for me, so I can't help there. that's why I'm planning on simple trial and error - start with a baseline set of offer/counteroffer factors and tune them for each commodity at each port based on what does and doesn't get accepted. this means that I'll waste a handful of turns when first trading at each port, but should (I expect) stabilise at a good set of values before too long.