Zugg Software :: View topic - EQ Ident Trigger puts wrong info into DB?

Posted: Thu Sep 29, 2005 7:12 am

Hi Guys,

I have an EQ Ident trigger that captures all the right info but is putting the wrong info into my DB.

It get's most things right.

Here's an example piece of EQ, and the Item variable echoed after that.

You determine that chitinous black armor is a corpse.
It is worn on the body.
It is evil.
It cannot be equipped by those of neutral alignment.
It weighs 5 lbs, is worth 858 copper coins and is level 76.
It modifies constitution by 4.
It modifies hit points by 70.
It modifies armor class by -20.

TypecorpseNamechitinous black armorLocationbodyEvilYesAAneutralWeight5Level76Con4HP70AC-20
Item added to Database.
Variable Item removed.

This is all 100% correct.

However, in the DB, all flags are correct except Location.

As grabbed by my triggers and put into the Item variable it states Locationbody, the DB states Location finger :(

Is this a known fault?

It seems dubious because it works fine with everything else I ID.

This is the trigger for grabbing the location.

^It is worn {on|about|around} the &Item.Location~.

and this is the contents of the trigger that fires at the end of all the ID spell information.

#T- IDFlags
#DBLOAD ItemsDB
#ECHO @Item
#NEW All @Item
#DBSAVE ItemsDB
#DBCLOSE ItemsDB
#ECHO {Item added to Database.}
#UNVAR Item

Any advice appreciated.

Cheers,
Erazmus.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Two minor changes, one for readability and the other just to be prim and proper. I don't think the change on the #NEW command will actually help.
#ECHO {%expanddb(@Item,"|","=")}
#NEW All {@Item}

How is the Location field setup? Single option list? If yes, how many options do you currently have? How many records do you already have stored?

Posted: Thu Sep 29, 2005 9:52 am

Roflmao.

Thanks for pointing out what should have been obvious!

It was the location field.

There is no option for "Body", only "onbody", or "aboutbody", so it must just default to the first option which is "finger".

Changing that location trigger will do the job.

Can't believe I've been stumped over that for the past couple of days :P

Cheers,
Erazmus