Forums Feature Suggestions $maxtargets?

Another paramter recieved through 005 on CONNECT and I know it already is held in mIRC because I saw the /debug output when /amsging so why can't we call it?

Because you can just get it yourself from raw 005?

Not exactly a good arguement, as the maximum number of modes (for example) is also returned in raw 005, yet mIRC has $modespl

Rather than add an identifier for each token one-by-one I'd much rather see an $isupport(<token-name>) identifier.

It's not an argument, it's a fact.



$isupport(MODES)


The other problem being that there is more than one "maxtargets" result on certain networks (this is from efnet):


It would have to be something like $maxtargets(kick), which I don't think is standardized across networks.

And if $network is $null ?
Btw, I don't see why we should not have one identifier per token.

Because then mIRC has to explicitly add support for each and every token which is just stupid and impractical. Having a single $isupport() identifier means mIRC can just parse 005 and return the values for whatever tokens it provides (or $true for tokens which have no specific value).

Ah yes, but the $issupport is good for me.

Feel free to use $cid if you use networks that don't fill $network, doesn't really change much.

I just answered about your script because I've think about the issues but I don't really care about using it.

As Russel says, mIRC has $chantypes, $chanmodes, $modespl, and $prefix all from 005. There is evidence that MAXTARGETS is also used so I'm wondering why that isn't an identifier too.

MAXTARGETS isn't supported by all networks. I like the $isupport idea and have stated so on several occasions here in the past, but unfortunately it has never come to be. I too have a $isupport custum identifier.