Capturing prompt

Post Reply
fredrik
Posts: 17
Joined: Sat Apr 10, 2010 9:55 pm

Capturing prompt

Post by fredrik »

Sorry if this has been answered already. I've been going through a number of threads with examples but unable to get it right. Been playing around with Geyser.Gauge trying to create hp and gp bars displaying from my prompt.

But cant get the trigger to recognize it.

Prompt looks like this:
Hp: 10655(10655) Gp: 2275(2275) Xp: 25628780(123000000)

During fighting tracking of your opponents health are displayed with numbers:
Hp: 10655(10655) ** 5 ** Gp: 2275(2275) Xp: 25628780(123000000) Fighting: 5 2 10 7

Displaying my hp and gp in bars in bottom of the screen is my goal. Eventually I would also like to capture the health numbers of my opponents and display that value in large numbers inside another label.

fredrik
Posts: 17
Joined: Sat Apr 10, 2010 9:55 pm

Re: Capturing prompt

Post by fredrik »

Update: progress!

Managed to get it to capture with the follow code:

Code: Select all

^Hp: (\d+)\((\d+)\) Gp: (\d+)\((\d+)\) Xp: (\d+)\((\d+)\)
This captures and updates my hpbar nicely.
Problem is: when in combat there is an additional number added to the prompt displaying status of my foe. This prevents the trigger from firing. Although I can get around it with just capturing my hp.

Code: Select all

^Hp: (\d+)\((\d+)\)

Hp: 10655(10655) Gp: 2275(2275) Xp: 25628780(123000000)
and
Hp: 10655(10655) ** 5 ** Gp: 2275(2275) Xp: 25628780(123000000) Fighting: 5 2 10 7

Is the solution to do three separate perl regex triggers for hp, gp and xp or is is possible to alter my first and make it "ignore" the extra tracking number messing it up?

Jor'Mox
Posts: 1142
Joined: Wed Apr 03, 2013 2:19 am

Re: Capturing prompt

Post by Jor'Mox »

So, you can add in a bit to make it work in both circumstances:

Code: Select all

^Hp: (\d+)\((\d+)\) [\s\*\d]*Gp: (\d+)\((\d+)\) Xp: (\d+)\((\d+)\)
Basically, it just makes a group of characters, spaces, numbers and asterisks, and then says that your pattern should look for 0 or more of them right before the Gp in your pattern. This SHOULD match the ** 5 ** that I'm seeing in what you shared.

Post Reply