Zugg Software :: View topic

Newbie Joined: 22 Jun 2003 Posts: 3 Location: USA

I recently upgraded from 5.55 to 6.62. I had a script to capture screen info for identified items and store them in a command line searchable database. Since upgrading, something is screwy.

This is how it starts:

Pattern:
~[Identified:~]

Commands:
#WA
#T+ IDItem1
#T+ IDterminator

IDitem1 then looks like this:
Pattern:
(*)

Commands:
#T- IDitem1
#VAR ID1 {%1}
#WA
#T+ IDitem2

Class:
IDitem1

This continues up till IDitem12 so I can get multiple lines of text.

IDTerminator then looks like this:
Pattern:
$

Commands:
#T- IDterminator
#T- IDItem1
#T- IDItem2
#T- IDItem3
#T- IDItem4
#T- IDItem5
#T- IDItem6
#T- IDItem7
#T- IDItem8
#T- IDItem9
#T- IDItem10
#T- IDItem11
#T- IDItem12
#FILE 2 ZombieIDlog.txt
#WRITE 2 {@ID1 @ID2 @ID3 @ID4 @ID5 @ID6 @ID7 @ID8 @ID9 @ID10 @ID11 @ID12}
#CLOSE 2
#VAR ID1 @blank
#VAR ID2 @blank
#VAR ID3 @blank
#VAR ID4 @blank
#VAR ID5 @blank
#VAR ID6 @blank
#VAR ID7 @blank
#VAR ID8 @blank
#VAR ID9 @blank
#VAR ID10 @blank
#VAR ID11 @blank
#VAR ID12 @blank

Class:
IDterminator

I can then search with this with some aliases I have set up. The search and on-screen display still seems to work fine.

This is how it was written in 5.55. Now after upgrading to 6.62, all I can seem to capture is my prompt. :-(

This is what I get from the MUD:
You recite a scroll of information which dissolves.
[Identified:]
[Name:] 'a shield of dark crystal' [Type:] Armor
[Item Flags:] Magic, Anti-order, No Priest
[Weight:] 5 pounds [Value:] 95099 [Rent:] 0
[MinLevel:] 95 [MaxLevel:] 100
[Armor Class Apply:] Bonus of 14
[Applied Affect:]
- Hitroll by 5
- Damroll by 4
- Auspex vs Spell by -2

Any help is greatly appreciated.

Newbie Joined: 22 Jun 2003 Posts: 3 Location: USA

This used to work just fine until I upgraded from 5.55 to 6.62. What would cause it not to work in the newer version?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Probably because of the #WAIT's. Try reading this article for more information and this article for some other alternatives.

Newbie Joined: 22 Jun 2003 Posts: 3 Location: USA

Ok, I understand my #WA may be a problem, but what can I use in it's place to wait until the next line of text is received from the mud? I don't see how I could use #ALARM, or a timer because it is not based on time. Can I use #COND to continue the trigger on the next line of text received from the mud? I was really hoping not to have to re-write the whole thing cause it took me so long the first time. :-) I want to capture everything after the [Identified:] line, and I get a blank line at the end to which triggers to stop capturing. All is then writen to my ZombieIDlog.txt file.

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Yes, #COND would be ideal. Use * to have it match anything.