It's similar to asuka's /CHECK, and we want to display the current class on
it.
As I said though, if it's going to cause problems we can omit this
information :)
Thank you.
On 15 March 2010 22:22, Isomer wrote:
> Sirius wrote:
> > Hi Michael,
> >
> > Ah, okay. I thought there would be a simple
Sirius wrote:
> Hi Michael,
>
> Ah, okay. I thought there would be a simple way to share this data
> once a user uses /OPER, and then burst that in a netburst too.
>
> If you think this is a really bad idea I can leave it, it would just
> be great to add it to our new command.
>
> Thanks!
What d
Hi Michael,
Ah, okay. I thought there would be a simple way to share this data once a
user uses /OPER, and then burst that in a netburst too.
If you think this is a really bad idea I can leave it, it would just be
great to add it to our new command.
Thanks!
On 15 March 2010 12:33, Michael Poole
Sirius writes:
> Hi,
>
> Is there a way to use get_client_class(acptr) across servers? Locally, this
> works fine to retrieve the class of the user/oper, however, across servers it
> doesn't.
The client's connection class is not automatically published. It can be
retrieved using the TRACE comman
Hi,
Is there a way to use get_client_class(acptr) across servers? Locally, this
works fine to retrieve the class of the user/oper, however, across servers
it doesn't.
Obviously this would need to survive netsplits too. I am trying to integrate
this into a custom command, but I cannot find a way o
