-----------------
poster: Korthrun
subject: bleeding
date: Thu Nov 23 19:26:33 2006
someone asked me about bleeding ansi once
been feeling guilty ever since :p
but i forget your name
set the world type to LP and it will fix most of that
tf still eats some random lines now and again during vcombat,
haven't fixed that
-----------------
poster: Korthrun
subject: repeat
date: Wed Dec 13 14:38:48 2006
Soo right now I'm using the repeat command to give me a little
warning for when a vuln is going to drop.
What I'd like to do is interrupt the /repeat that is still
"sleeping" if the macro get's run a second time. This way I don't
get "Brittle Limbs is going to drop soon." echoed to my terminal 100
times if my finger twitches, or if I'm doing exp and mobs are dying
fast.
I'll ask the tf mailing list in a bit, but they tend to suck.
-----------------
poster: Zifnab
subject: >repeat
date: Wed Dec 13 16:37:56 2006
On Wed Dec 13 22:38:48 2006 Korthrun wrote post #2:
> Soo right now I'm using the repeat command to give me a little
> warning for when a vuln is going to drop.
> What I'd like to do is interrupt the /repeat that is still
> "sleeping" if the macro get's run a second time. This way I don't
> get "Brittle Limbs is going to drop soon." echoed to my terminal 100
> times if my finger twitches, or if I'm doing exp and mobs are dying
> fast.
>
> I'll ask the tf mailing list in a bit, but they tend to suck.
Can't you get the PID of the new process and effectively kill it?
-----------------
poster: Uno
subject: >>repeat
date: Thu Dec 14 08:02:15 2006
On Thu Dec 14 00:37:56 2006 Zifnab wrote post #3:
> > warning for when a vuln is going to drop.
> > What I'd like to do is interrupt the /repeat that is still
> > "sleeping" if the macro get's run a second time. This way I don't
> > get "Brittle Limbs is going to drop soon." echoed to my terminal 100
> > times if my finger twitches, or if I'm doing exp and mobs are dying
> > fast.
> >
> > I'll ask the tf mailing list in a bit, but they tend to suck.
>
> Can't you get the PID of the new process and effectively kill it?
This sounds like something traditionally that you'd use a flag
variable to track.
Is that in question? or are you unsure the method for actually
interrupting the /repeat fxn?
-----------------
poster: Korthrun
subject: >>>repeat
date: Thu Dec 14 08:05:38 2006
On Thu Dec 14 16:02:15 2006 Uno wrote post #4:
> > > fast.
> > >
> > > I'll ask the tf mailing list in a bit, but they tend to suck.
> >
> > Can't you get the PID of the new process and effectively kill it?
>
> This sounds like something traditionally that you'd use a flag
> variable to track.
> Is that in question? or are you unsure the method for actually
> interrupting the /repeat fxn?
I am unsure of the method for interrupting the repeat
From what i gather from zifs post, I can put the PID in a variable
if i use an asynchronous repeat, as it's return value is it's pid.
Now I just need to read the processes docs to figure out how to kill
it, which at a glance looks like I use *gasp* /kill.
thanks all, I'll let you know how it turns out
-----------------
poster: Korthrun
subject: >>>>repeat
date: Thu Dec 14 08:45:38 2006
On Thu Dec 14 16:05:38 2006 Korthrun wrote post #5:
> > This sounds like something traditionally that you'd use a flag
> > variable to track.
> > Is that in question? or are you unsure the method for actually
> > interrupting the /repeat fxn?
> I am unsure of the method for interrupting the repeat
> From what i gather from zifs post, I can put the PID in a variable
> if i use an asynchronous repeat, as it's return value is it's pid.
> Now I just need to read the processes docs to figure out how to kill
> it, which at a glance looks like I use *gasp* /kill.
> thanks all, I'll let you know how it turns out
fyi
/def key_f1=/kill %{vuln1PID}%;!cast %vuln1%;/set vuln1PID
$[repeat( "-50 1 /echo -aBCRed $[toupper({vuln1}, 1)] falling." )]
is what I came up with
now I'm researching a way to test for a valid PID, so that when the
/repeat runs it's command and the PID goes away, I can skip the
error message reminding me that there is no such PID.
-----------------
poster: Korthrun
subject: Orpo
date: Sun Apr 22 11:39:32 2007
Mmmmhmmm TF's multiline matching is still non existant. Unless I
missed a memo.
So here's what I have, and here's what I get.
######
/def -p2 -n1 -mregexp -t'^.*((physical|electr
c|psionic|fire|cold|poison|magical|asphyxiation|acid|
oly|unholy)).*' orpo_tmp1 = \
!korthprot %0 -- %P0 %;/undef orpo_tmp2%;\
/def -p1 -n1 -t"" orpo_tmp2 = /undef orpo_tmp1
#####
You can sense the results of the damage probe that you casted on Kitten.
The following damage types were detected:
poison
Korthrun [korthprot]: orpo_base -- The following damage types were detected:
So it looks like the scope is still stuck with the orpo_base macro :(
Any exparts out there know how I can sort this out? Ideally I'd want
the output to contain "Orpo found %P0" and have %P0 be 'physical
poison' or whatever dtypes orpo said
-----------------
poster: Korthrun
subject: >Orpo
date: Sun Apr 22 11:42:17 2007
On Sun Apr 22 20:39:32 2007 Korthrun wrote post #7 in clients.tf:
> Mmmmhmmm TF's multiline matching is still non existant. Unless I
> missed a memo.
>
> So here's what I have, and here's what I get.
>
> ######
> /def -p2 -n1 -mregexp -t'^.*((physical|electr
> c|psionic|fire|cold|poison|magical|asphyxiation|acid|
> oly|unholy)).*' orpo_tmp1 = \
> !korthprot %0 -- %P0 %;/undef orpo_tmp2%;\
> /def -p1 -n1 -t"" orpo_tmp2 = /undef orpo_tmp1
> #####
>
> You can sense the results of the damage probe that you casted on Kitten.
> The following damage types were detected:
> poison
> Korthrun [korthprot]: orpo_base -- The following damage types were detected:
>
> So it looks like the scope is still stuck with the orpo_base macro :(
> Any exparts out there know how I can sort this out? Ideally I'd want
> the output to contain "Orpo found %P0" and have %P0 be 'physical
> poison' or whatever dtypes orpo said
I see the text wrapping went wonderfully, so I'll try from the web.
/def -p1 -mregexp -t'^The following damage types were detected:$' orpo_base = \
/def -p2 -n1 -mregexp -t'^.*((physical|electric|psionic|fire|cold|poison|magical|asphyxiation|acid|holy|unholy)).*' orpo_tmp1 = \
!korthprot %0 -- %P0 %;/undef orpo_tmp2%;\
/def -p1 -n1 -t"" orpo_tmp2 = /undef orpo_tmp1
-----------------
poster: Korthrun
subject: >Orpo
date: Sun Apr 22 11:55:01 2007
On Sun Apr 22 20:39:32 2007 Korthrun wrote post #7 in clients.tf:
>
> You can sense the results of the damage probe that you casted on Kitten.
> The following damage types were detected:
> poison
> Korthrun [korthprot]: orpo_base -- The following damage types were detected:
>
> So it looks like the scope is still stuck with the orpo_base macro :(
> Any exparts out there know how I can sort this out? Ideally I'd want
> the output to contain "Orpo found %P0" and have %P0 be 'physical
> poison' or whatever dtypes orpo said
Cleaned up some of the useless shit I had in while debugging.
/def -p1 -mregexp -t'^The following damage types were detected:$' orpo_base = \
/def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|cold|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
!korthprot %0 -- %P0
-----------------
poster: Korthrun
subject: >>Orpo
date: Sun Apr 22 11:59:02 2007
On Sun Apr 22 20:55:01 2007 Korthrun wrote post #9:
> > So it looks like the scope is still stuck with the orpo_base macro :(
> > Any exparts out there know how I can sort this out? Ideally I'd want
> > the output to contain "Orpo found %P0" and have %P0 be 'physical
> > poison' or whatever dtypes orpo said
>
> Cleaned up some of the useless shit I had in while debugging.
>
> /def -p1 -mregexp -t'^The following damage types were detected:$'
orpo_base = \
> /def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|
old|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
> !korthprot %0 -- %P0
I'd like to hump beranis in teh face.
-----------------
poster: Korthrun
subject: >>>Orpo
date: Sun Apr 22 12:00:55 2007
On Sun Apr 22 20:59:02 2007 Korthrun wrote post #10 in clients.tf:
> On Sun Apr 22 20:55:01 2007 Korthrun wrote post #9:
> > > So it looks like the scope is still stuck with the orpo_base macro :(
> > > Any exparts out there know how I can sort this out? Ideally I'd want
> > > the output to contain "Orpo found %P0" and have %P0 be 'physical
> > > poison' or whatever dtypes orpo said
> >
> > Cleaned up some of the useless shit I had in while debugging.
> >
> > /def -p1 -mregexp -t'^The following damage types were detected:$'
> orpo_base = \
> > /def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|
> old|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
> > !korthprot %0 -- %P0
> I'd like to hump beranis in teh face.
/def -p1 -mregexp -t'^The following damage types were detected:$' orpo_base = \
/def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|cold|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
!korthprot %0 -- %%P0
-----------------
poster: Goroharahad
subject: >>>>Orpo
date: Mon Apr 23 05:29:43 2007
On Sun Apr 22 21:00:55 2007 Korthrun wrote post #11:
> On Sun Apr 22 20:59:02 2007 Korthrun wrote post #10 in clients.tf:
> > On Sun Apr 22 20:55:01 2007 Korthrun wrote post #9:
> > > > So it looks like the scope is still stuck with the orpo_base macro :(
> > > > Any exparts out there know how I can sort this out? Ideally I'd want
> > > > the output to contain "Orpo found %P0" and have %P0 be 'physical
> > > > poison' or whatever dtypes orpo said
> > >
> > > Cleaned up some of the useless shit I had in while debugging.
> > >
> > > /def -p1 -mregexp -t'^The following damage types were detected:$'
> > orpo_base = \
> > > /def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|
> > old|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
> > > !korthprot %0 -- %P0
> > I'd like to hump beranis in teh face.
> /def -p1 -mregexp -t'^The following damage types were detected:$'
orpo_base = \
> /def -p2 -n1 -mregexp -t'.*(physical|electric|psionic|fire|
old|poison|magical|asphyxiation|acid|holy|unholy)*' orpo_tmp1 = \
> !korthprot %0 -- %%P0
This will leave a trig in the wild if you detected nothing by the way :)
I implemented some multiline trig that are based on 3 ideas, 2 of
which appear above :
- need a basic trigger ( single word to ensure it is not split over
2 lines, or beginning )
- You can then grap as many lines as you want using a /def -F -t"",
you just need to decide how far you go ( number of lines or a
stopping match - in any case it is wise to have a max number of
lines )
- If the basic trigger is not the beginning, you can also use
/recall to get lines before.
You can even concatenate all those lines and operate a global match
etc .. What I did not figure out yet is how to apply attributes on
the lines preceding the basic trigger.
For those interested, I found that a bit nightmarish to code in tf
.. but it seems to work decently.
Goro
-----------------
poster: Goroharahad
subject: >>>>>Orpo
date: Mon Apr 23 05:53:16 2007
> This will leave a trig in the wild ...
After writing this comment, I didn't even oneshot or even name mine ...
Goro hangs his head in shame ..
-----------------
poster: Korthrun
subject: >>>>>>Orpo
date: Mon Apr 23 22:21:58 2007
On Mon Apr 23 14:53:16 2007 Goroharahad wrote post #13:
> > This will leave a trig in the wild ...
> After writing this comment, I didn't even oneshot or even name mine ...
>
> Goro hangs his head in shame ..
<3
-----------------
poster: Korthrun
subject: reincs
date: Tue Jan 1 02:22:33 2008
srsl
/quote -S !for spell in hsieb berqa nohexeqekor xeraq velenu qares
seher kiesah loghob orpo;do echo 19 study $spell;done