About your example: parsing a MOTD the owner sets in the hub, only has to be done once, as long as a CHCM-version and a non-CHCM-version are stored to serve to connecting users. So I don't see a need to prevent parsing there.
How would a client that doesn't support x.lt and x.tt handle the message:
IMSG ABCD Welcome\to\the\shub,\smagnet:?x.ltclick+here&x.tt=%2Bregme+%25%5Bline%3APassword+(leave+empty+to+un-reg)%5D\sto\sregister
If it was a feature broadcast, only supporting clients would receive it and the clients that don't support can get another message. How that translates to sending a proper MOTD is up to the hubsoft.
But granted, the point is that magnets already provide similar functionality, and if it can be extended to provide clickable hubcommands in chat, then sure, why not. Started this thread because of the idea, not because of the implementation-specs. A way to send proper alternative messages to clients not supporting this magnet-extension will be needed then.
Clickable hubcommands in chat
Forum rules
If you have an account on the wiki, remember to update the ADC Proposals page for new ideas.
http://dcbase.org/wiki/ADC_Proposals_list
If you have an account on the wiki, remember to update the ADC Proposals page for new ideas.
http://dcbase.org/wiki/ADC_Proposals_list
-
FlipFlop™
- Junior Member
- Posts: 23
- Joined: Fri Apr 17, 2009 8:29 am
-
Crise
- Senior Member
- Posts: 139
- Joined: Sat Nov 10, 2007 9:34 pm
Re: Clickable hubcommands in chat
When the command originates from client then F type would be the choice and when it does from hub the choice of what is sent can be done as in F type broadcast as well.
Last edited by Crise on Thu Dec 09, 2010 10:06 am, edited 1 time in total.
Reason: typo
Reason: typo
Who is online
Users browsing this forum: Google (Crawler) and 0 guests