Gammon Forum : MUSHclient : Plugins : Any way to make a 'chat' plugin?

Entire forum ➜ MUSHclient ➜ Plugins ➜ Any way to make a 'chat' plugin?

Any way to make a 'chat' plugin?

It is now over 60 days since the last post. This thread is closed. Refresh page

Pages: 1 2 3 4 5 6 7

Posted by

Poromenos Greece (1,037 posts) Bio

Date

Reply #60 on Thu 10 Apr 2003 03:08 PM (UTC)

Message

I have read the entire thread. Being a programmer, i have a very important question to ask. What's zChat?

Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it!

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #61 on Thu 10 Apr 2003 03:34 PM (UTC)

Message

Zchat is an optional plugin for Zmud. It functions as a stand-alone chat client or, with the registered version of Zmud, will fully integrate. It adds chat functionality to Zmud and allows communication with MudMaster's native chat client.

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

Poromenos Greece (1,037 posts) Bio

Date

Reply #62 on Thu 10 Apr 2003 08:23 PM (UTC)

Message

So the chat text goes in the MUD window?

Vidi, Vici, Veni.
http://porocrom.poromenos.org/ Read it!

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #63 on Thu 10 Apr 2003 09:56 PM (UTC)

Message

Zchat text only appears in the MUD window if you have a registered version of Zmud. Otherwise, Zchat functions independantly as a stand-alone chat client and chat text appears in the Zchat window.

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

Nick Gammon Australia (23,165 posts) Bio Forum Administrator

Date

Reply #64 on Thu 10 Apr 2003 10:36 PM (UTC)

Message

Quote:

Nick are you adding chat to the next ver of MUSH?
E.G. Can/should I abandon the dll/plugin...

Yes I am working on that, your earlier posts prompted me to get on with it, as a chat system is obviously wanted by at least some users. :)

Because I haven't used chat in the past myself I am unsure exactly how their implementations work, as I obviously want to be compatible with zChat/MM chat, so that you can play in a mixed client environment.

NightCrawler, I will probably take up your offer of testing shortly, at least you can tell me if my system doesn't work the way you are used to.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

Posted by

Nick Gammon Australia (23,165 posts) Bio Forum Administrator

Date

Reply #65 on Fri 11 Apr 2003 12:18 AM (UTC)

Message

Can someone explain how groups work in chatting? There is a CHAT_TEXT_GROUP command which seems to indicate you send a message to a named group. But how do you get into groups?

Is it the sender's responsibility to put people into groups, and then only send to the group, or the receiver's responsibility to know if they are in that group or not?

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

Posted by

Skarsnik (11 posts) Bio

Date

Reply #66 on Fri 11 Apr 2003 12:42 AM (UTC)

Message

> Yes I am working on that, your earlier posts prompted me to get on with it, as a chat system is obviously wanted by at least some users. :)

Sweet, abandoning chat dll :). For the record I did have the basics (chat/emote/peek/request) working compiled and wrapped in an install kit ready to be shipped to testers...

> Because I haven't used chat in the past myself I am unsure exactly how their implementations work, as I obviously want to be compatible with zChat/MM chat, so that you can play in a mixed client environment.

I would personally be inclined to make it MudMaster compatible (and therefore zChat compatible). But thats mostly because I dislike zChat(zMud) in all its bloated glory...

Skars

Top

Posted by

Nick Gammon Australia (23,165 posts) Bio Forum Administrator

Date

Reply #67 on Fri 11 Apr 2003 12:51 AM (UTC)

Message

Can you tell me what you did for "request connections"?

It seems to me there are 2 IP addresses - the "reported" one from the client, which might be a private address, eg. 10.0.0.1, and the "actual" address which the client connected from, which might actually be the NAT router or somesuch.

Which one did you use? According to the zChat spec (and also the MM spec) you might not know the IP address. Why not? You must have if you made a connection. That tends to imply that it wants the reported IP address and not the actual one.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #68 on Fri 11 Apr 2003 01:34 AM (UTC)

Message

Groups:

When you have a list of connections MM, you can assign them group names using the /chatgroupset <connection> <group> command. You can then chat to a specific group using the /chatgroup <group> <message> command (which MM will let you abbreviate by typing /cg <group> <message>).

So, I can have two groups of people like Cool People and Uncool People. I can send messages to one group without the other group seeing the message (ie. /cg Cool People The other group sucks!)

The people I have placed it groups won't know that I've placed them into groups. It's simply something I set in my client to help sort my connections into sub-categories.

Requesting Connections:

I'm assuming you were directing your question at Skarsnik, but I'll answer too, since MM has this feature as well.

Imagine that A is connected to B who is connected to C...

If A wants to know who B is connected to, he can /peek B and see a list of connections (assuming B hasn't marked them as Private). This will show A the name of the person(s) B is connected to as well as their IP addresses.

If A wants to talk to C, he now has two options: Ask B to serve either A or C so they can communicate indirectly, or A can /requestconnects B and attempt to automatically establish a connection to C. Basically, /request is the same as manually calling an IP except MM does the work for you.

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #69 on Fri 11 Apr 2003 01:40 AM (UTC)

Message

You may already have this info, but I'll paste it here anyway. It reiterates some of the topics we've already discussed and may help to explain some of them further. It may also explain some of the features we haven't yet discussed. This is from the MM Help file on Chat:

=====
Part One:

Mud Master chat allows you to establish a site to site link with another MM
user. Once you have a connection you are able to talk with any or all of your
chat connections, transfers commands (actions, aliases, variables, etc...),
and transfer files. Site to site means the clients are connected directly.
Often you will experience less lag using MM to chat than you would talking to
the same person through a mud.

Before you connect to anybody you need to set your chat name. Everybody you
connect to will see this name when you talk. The command is:
/chatname {chat name}.

To start a chat with another person you use the call command and their network
address. Call will accept both IP address and named address. You can see your
IP address in MM in two ways. First, you can type /info. Second, you can use
the procedure @IP(). Example: tell arithon My address is @IP(). Once you know
another user's ip address use call to connect to them. /call 204.120.248.148

Sometimes MM will be unable to reach an IP address when you /call. This is
usually because the person you are trying to call has a firewall. A firewall
prevents remote systems from connecting to an internal network. If you cannot
connect to somebody have them try to call you instead. If you still cannot
connect to each other you may both be firewalled. You can still chat if you
can both connect to another person who is willing to be a chat server for you.

An easy way to get connected with a group of people already chatting is to use
/requestconnects {name/number}. Once you connect to a user, you can request
all of their chat connections with this command. MM will then try to connect
you with all of the other user's connections. Only public connections are
returned when somebody requests your connections. If you don't want people to
see some of your connections, flag them as private.

There are several things that can happen when a chat call comes in. You can
prevent people from connecting to you by using the DND (Do Not Disturb)
command. When a call comes in DND is checked, if it is on, the chat connection
is hung up on without interrupting you. /dnd will toggle the option on and
off. You can see the DND status by using /info. Autoaccept also affects how
incoming calls are handled. If you have autoaccept off you will be prompted to
accept the call when it comes in -- this will pause your mudding until you
press Y or N. If you leave autoaccept on chat calls get accepted without
prompting you. You can see the status of autoaccept with /info.

=====

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #70 on Fri 11 Apr 2003 01:40 AM (UTC)

Message

=====
Part Two:

/Chat will show you all the chat connections you have. It also shows you some
status flags associated with the different connections. The flags and a
description of them are listed below. If you are transferring a file thru a
chat connection, the chat name color will change. If the name is blue, you are
receiving a file, if it is green, you are sending a file.

A - You are allowing that chat connection to transfer commands to you
(aliases, actions, variables, etc...). /chatcommands {name/number} will
toggle this flag.
F - Means that chat connection is behind a firewall.
I - You are ignoring that chat connection. You will not see any chats or
name changes from that person. /chatignore {name/number} will toggle
this flag.
P - Private connection. Connections marked as private are not given out
when somebody requests your chat connections. /chatprivate
{name/number} will toggle this flag.
S - You are serving this connection. When serving, /chatalls coming from
people not being served are sent to those you are serving -- text from
those being served is sent to all of your other connections.
/chatserver {name/number} will toggle this flag.
T - Allow transfers. You are allowing file transfers from this connection.
/chattransfers {name/number} will toggle this flag.

To talk with a specific connection you use /chat. /chat {chat name/chat number}
{text}. Like with the other lists you can use either the name of the
connection, or the number you see when you list your connections with /chat. To
talk with all of your connections at the same time use /chatall {text}.

You can also group chat connections and talk just to that group. Use
/chatgroupset {name/number} {group name} and /chatgroupremove {name/number} to
set and remove group names from a chat connection. Once you have people grouped
you talk to the group with /chatgroup {group name} {text}. You can also use /cg
as a shortcut for /chatgroup.

Emoting on the chat channel works very similar to the commands used for
chatting. /emote, /emoteall, and /emotegroup. When you emote you chat name and
the text you emote is sent to the chat connection. /emoteall licks you would
send "{Chat Name} licks you." to all your connections.

To hang up on a chat connection use /unchat {name/number}.

If you want to send commands to another chat connection you have to first get
them to enable the reception of commands from you with /chatcommands. Once they
have flagged you able to send commands you can use the following to send them:
/sendaction, /sendalias, /sendarray, /sendbaritem, /sendevent, /sendgag,
/sendhighlight, /sendlist, /sendmacro and /sendvariable. If you want to send a
group of commands use /sendgroup. When you send a list or array, all the items
belonging to the list or array are transfered as well.

To send files through a chat connection you have to get the chat the other
party to flag with allow transfers. Use /sendfile to transfer files. Both
users are notified when a file transfer has been started and notified again
when the transfer is complete. You can check the status of a file transfer with
/filestatus {name/number}. The {name/number} refers to the chat connection, not
the name of the file being transferred. /Filecancel {name/number} will cancel a
file transfer in progress.

/ChatBack and /ChatFore can be used to change the default colors of the chat
text.

/ChatVersions will show you the version of MM that each of the chat connections
is using.

By default when you start up MM it will listen for chat calls on port 4050. You
can tell MM to listen to an alternate port if you want. You can only change the
listen port when you first run MM, using a command line parameter.
"mudmast L:port num" will cause MM to listen to a specific port.
"mudmast L:4000" will cause MM to listen to port 4000. You can see what port MM
is listening to with /info. /call uses port 4050 by default as well. If you
change the port that MM is listening to you will have to let people know which
port number to call

=====
End of File

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #71 on Fri 11 Apr 2003 01:50 AM (UTC)

Message

I should add, finally, that the above HELP file hasn't been updated since the original MM Console version. While all those commands are still available in the GUI release, much of it is also point'n'click now so users can use the input bar or a mouse. Also, extra commands have been added.

Finally, regarding the last paragraph of the file concerning changing ports: you can change ports on-the-fly in MM2k. You simply need to stop and restart the chat server to enable listening on the new port.

Enough spam for awhile...

NightCrawler

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

Nick Gammon Australia (23,165 posts) Bio Forum Administrator

Date

Reply #72 on Fri 11 Apr 2003 02:24 AM (UTC)

Message

When you are asked for connections (request connections) do you supply yourself?

eg. If A is connected to B and C

B asks A: request connections

Does A reply with B and C, or just C (after all B knows he has a connection, after all, that is what he just used).

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

Posted by

NightCrawler Canada (16 posts) Bio

Date

Reply #73 on Fri 11 Apr 2003 03:02 AM (UTC)

Message

You only see the other connections (that aren't marked private), you don't see yourself. This is true whether you're just peeking at the connection or whether you request them.

A computer once beat me at chess, but it was no match for me at kick-boxing...

Top

Posted by

Nick Gammon Australia (23,165 posts) Bio Forum Administrator

Date

Reply #74 on Fri 11 Apr 2003 05:42 AM (UTC)

Message

I am having trouble testing zChat - for one thing I can't work out how to change the port number from 4050, and for another it keeps crashing with an access violation. Does anyone else have better luck them that with zChat?

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

277,035 views.

This is page 5, subject is 7 pages long: 1 2 3 4 5 6 7

It is now over 60 days since the last post. This thread is closed. Refresh page

Go to topic: Search the forum

top