Due to popular request, I've created a set of zMud settings that will read the output of an identify spell or auction list and parse it into a one-line RoD Database compatible line. The line is then echoed to the local screen so you can see it, and then added to the end of a file called RoD_Item-FromTriggers.txt in your zMud directory.

Click here to download the zMud script file itemgathertriggers-zmud705.zsc (9 KB)

Here is a explanation of how this 2-trigger and 2-alias zMud trigger set work:

Overview

There are two settings classes, named ITEMGATHER and ITEMPROCESS. ITEMGATHER is enabled when a incoming line from the mud starts with "Object '". ITEMGATHER then reads and stores every line from the mud for 4 seconds, after which it is disabled again. The ITEMPROCESS settings, which are always enabled, control monitoring for the "Object '" line, turning on and off the ITEMGATHER class, and then processing the captured mud text to attempt to build a RoD Database line from the data gathered. Once the data has been parsed, the resulting item database input line is written to a text file called RoD_Item-FromTriggers.txt in the zmud directory on the local machine. Part of the purpose of setting up the triggers in this manner is so that any Identify command, or any monitoring of the Auction channel will automatically result in the storing of RoD Database item lines for all items that cross the screen.

Logic Flow:

1. ITEMGATHER starts disabled, and ITEMPROCESS starts enabled.
2. The trigger in ITEMPROCESS waits for a line starting with "Object '" to come from the mud.
3. The itemlist is emptied, and then the first line (starting with "Object'") is stored in it.
4. The ITEMGATHER class is enabled, which turns on every-line capture.
5. A four-second temporary alarm is started, to call the ITEMPROCESSOR alias in four seconds.
6. The ITEMGATHER trigger captures each line, and puts it in the itemlist text list variable.
7. After four seconds expires, the ITEMPROCESSOR alias runs, which turns off the ITEMGATHER class.
8. Then it goes through the captured lines, one at a time, and parses what it finds into RoD Database Format.
9. Once parsed, the ITEMWRITE alias is called to write the itemdb database line to the RoD_Item-FromTriggers.txt file.

Expected Input / Output

The expected input is an item from Realms of Despair, from either Auction or Identify. For example, here is the input and output when a Sword of Legend comes across the mud:

Input:

Object 'Sword of Legend'...
It is a level 50 slashing weapon, weight 1.
Locations it can be worn: wield
Special properties: hum loyal magic metal
Alignments allowed: good
This weapon has a gold value of 200000.
Damage is 14 to 44 (average 29).
Affects hit roll by 13.
Affects damage roll by 13.
Affects hp by 75.
Affects mana by 125.
Affects affected_by by detect_evil protect
Affects luck by 2.
Affects dexterity by 2.
Affects strength by 2.
Affects constitution by 2.
Affects armor class by -20.

Output:

* | Sword of Legend | 50 | 0 | -20 | 14 | 44 | 13 | 13 | 75 | 125 | 2 | 2 | 2 | 0 | 0 | 2 | 0 | 0 | 1 | 200000 | hum loyal magic metal anti-neutral anti-evil | good affected_by detect_evil protect [L]

Errors:

You'll get the following error if you have square brackets set to evaluate:

ERROR!
The square brackets were stripped from the weapon types!
To fix this, please click VIEW, PREFERENCES, GENERAL, and under SCRIPT PARSER click on GENERAL PARSING
Then, on the right, uncheck "Allow [] for eval"

As the error indicates, the square braces are critical to the database, and the "Allow [] for eval" needs to be unchecked so that it is turned off for whatever character is going to be using this trigger set.

Code (in easy to read format):