Trouble with scripting...

[Mental Mouse]

OK, I'm starting to get into scripting, and I've been finding some major lacks. In particular, there are several things the client itself can do fine, that scripts apparently can't do. Has this been addressed in the trunk line of development? (And when are you guys going to release what you've got there as a new version?)

1) Finding out whether there's an open container -- and if you "request items cont" when there isn't one, the client drops dead of a segfault! Nor can we close an open bag on the floor!

2) Dropping, picking up, or applying items by ID. Via the GUI, you can drop, pick up, or apply items by clicking on the particular item. Pickup or drop yields "move" commands as reported by "monitor", but the script itself apparently isn't allowed to issue "move" commands. Even if we could, those reference an ID for the main inventory, which a script can't get except by observing the "monitor" results.

The "take" and "drop" commands that we can "issue" don't accept item IDs, and using item "names" commonly yields ambiguous results. Notably, it's impossible to drop (only) plain water if you've got any other waters in your inventory, or to drop only one pile of identically-named items. Similarly, we can't "apply" a specific item that's not in the inventory, only the top item on the floor.

3) Several important pieces of information seem inaccessible to scripts: The character name and their god, bowmode, and probably others.

4) There really should be a "watch draw" option, to monitor server output to the client. For example, scripts can't effectively "examine" stuff, or see the results of many commands.

[Leaf]

It would seem you have a confirmed bug report or feature request, please see this posting:

http://forum.metalforge.net/viewtopic.php?t=40

[Mental Mouse]

The mailing-list link in the "Bugs" forum yields the following:
------
Secure Connection Failed

mailman.real-time.com uses an invalid security certificate.

The certificate is not trusted because it is self signed.

(Error code: sec_error_ca_cert_invalid)