Mode +u on quakenet

Fluxism · Post by **Fluxism** » Tue Jul 01, 2003 7:12 pm

Hi all,

Does anyone know how to make an egg enforce +u on quakenet? (mode +u hides quit messages when ppl err.. quit).

At the moment, it is not possible as far as I can see...

Thanks,

Flux.

kazoo · Post by **kazoo** » Tue Jul 01, 2003 7:26 pm

That sounds like a server mode.. It doesn't seem like a channel op mode..

Fluxism · Post by **Fluxism** » Tue Jul 01, 2003 7:31 pm

Tis channel specific

/mode #egg +u

Or am I missing the point of what you said?

kazoo · Post by **kazoo** » Tue Jul 01, 2003 7:59 pm

It sounds like a mode that a channel service would set that is not able to be done simply by /mode #channel +u maybe not..

Post by **user** » Tue Jul 01, 2003 8:30 pm

Add it to the init-server modes (check the .conf)

(It has to be a user mode since quits don't occur on channel level

)

Aron · Post by **Aron** » Wed Jul 02, 2003 4:28 am

Mode +u is a channelmode on quakenet, which prevents Quits/parts to be shown on the SPECIFIC channel

Try something like this:

Code: Select all

bind mode *-u* domode
bind time - "?0 * * * *" domode
bind time - "?5 * * * *" domode

proc domode {nick host hand chan mode victim} {
  set chanmode [getchanmode $chan] 
  if {[string first u $chanmode] == -1} {
      pushmode $chan +u
  }
  else { return 0 }
}

This would (hopefully) check every 5 minutes if the mode is set, and set it, if not. It will also trigger when the mode is removed.
Someone will probably come with a better solution soon, since i think my use of timers and such is kinda odd

I thought i might give helping a try too

Fluxism · Post by **Fluxism** » Wed Jul 02, 2003 11:37 am

Thanks for the replies, I shall give it a go

MD87 · Post by **MD87** » Wed Jul 02, 2003 1:16 pm

If it doesn't work (I think you'll get errors when the time binds are 'triggered'), try replacing this:

Code: Select all

proc domode {nick host hand chan mode victim} {

with this:

Code: Select all

proc domode {nick host hand chan mode args} {

Aron · Post by **Aron** » Wed Jul 02, 2003 2:16 pm

how would that make a difference?

it could be proc domode {i love to make up things } for that matter, as long as you call the same variables as mentioned in the process.

..or am i wrong now?

gumbydammit · Post by **gumbydammit** » Wed Jul 02, 2003 3:05 pm

no you are not wrong AsoAron. you can call the variables whatever( how many variables there are does matter tho of course), mind you it helps to call them something that makes sense .

Post by **caesar** » Thu Jul 03, 2003 2:33 am

Where the heck you've seen "nick host hand chan mode victim" in the proc of time? And even the "nick host hand chan mode args"? Go read the tcl-commands.doc file..

Post by **user** » Thu Jul 03, 2003 3:14 am

AsoAron wrote:Mode +u is a channelmode on quakenet, which prevents Quits/parts to be shown on the SPECIFIC channel

If you want to see someone's quit message and they happen to be in that same +u channel as you they/you will have to part for you to see it?

What a stupid hack..it should be a user mode or not exist at all imo.

What's next? The incredible channel mode "B" that makes you go entirely blind when joining a channel where it's set?

Aron · Post by **Aron** » Thu Jul 03, 2003 4:41 am

ah sorry ceasar, that was just sloppy.
I made it for the trigger first, and just added the binds for the timers.

kazoo · Post by **kazoo** » Thu Jul 03, 2003 11:43 am

hehehe