is there a way to halt further stacked pubm triggering?

[jamie3]

bind pub can be used to bind nonstackable triggers,
and bind pubm for stackable (chainable) triggers.

but i want to be able to trigger a command to halt bind pubm processing, so that i can tell eggdrop, from one of my binc pubm triggered functions, to not proceed through the rest of its chain of triggers that have been registered through bind pubm. sort of like a haltdef in mirc scripting.

[De Kus]

that might be impossible, if (and im almost sure it is) pub is proceeded before pubm. I dont know the exact order, but keep it in mind . You can usually prevent pubm beeing called, if the pub bind returns 1, but I never heard from a thing upsidedown .
suggestion: unbind the pub command and call it from the pubm proc instead and relay the arguments.

[greenbear]

a workaround using bind filt would also work.

[De Kus]

a workaround using bind filt would also work.

(28) FILT (stackable)
bind filt <flags> <mask> <proc>
procname <idx> <text>

Description: party line and file system users have their text sent
through filt before being processed. If the proc returns a blank
string, the text is considered parsed. Otherwise, the bot will use
the text returned from the proc and continue parsing that
Module: core

this sounds like a partyline only bind, doesnt it?

You probably mean a bind to RAW and return with 1 to prevent further processing.

[greenbear]

ah, i suppose i was a bit quick there, i thought it worked with all binds. its been a while since i used it.