[CF-Devel] Re: [CF-Devel] New comunication commands. 'me and 'set_reply

Mon Sep 29 10:02:55 CDT 2003

Nicolas Weeger wrote:
>

      <snipped some parts away>

     >

     >>

      Perhaps the solution is to allow one player to only create/have one 

     >>

      active channel at a time.  If the player wants to create another one, 

     >>

      they get a message saying they have to close the one they currently have.

     >

sure or even don't allow players to create channels at all...  If it is 
too much of a pain.  Even just having a couple dozen or so DM or admin 
setup channels to use would be a great feature.

>

      Sounds fair to me, again. But I'd add an option for DMs to make channels 

     >

      permanent. Like 'newbie' channel, that could exist even without an owner...

     >

      Also possibility to transfer ownership to another player, provided s/he 

     >

      didn't create a channel either. And of course channel disband :)

     >

     >>

      If done in a simple enough fashion, perhaps not terrible.  I'd just 

     >>

      really don't want to see it become a huge mess of code to implement 

     >>

      communication in crossfire.  Of course, one could argue from a realism 

     >>

      standpoint (the R word again) that this isn't especially realistic, 

     >>

      eg, how can someone on a map far away tell the player next to you 

     >>

      something and you not be able to hear it.  But we'll ignore that point.

     >

Ya it shouldn't need a manual to run channels - they should be prettyy 
simple.  There are already a lot of good communication commands 
available, but channel shouting would be nice to allow people to use 
shout in a responsi9ble manner since it is the most popular form of 
messaging it appears.  As  I mentioned above  - even if only DMs or 
admins could create a number of regular channels on a server it would be 
good enough in my books.  Maybe players making channels is too much of a 
pain.  This way you can have a channel file with say 10 or so channels 
(newbie, chat1, chat2, chat3, DMs, one for each guild...) you can 
subscribe to and then remind people to use thes rather than abusing the 
shout command.

>>

       Perhaps combine/clean up the current gsay type commands, and just 

     >>

      implement them as a channel also?  Eg, you create a party, and it 

     >>

      creates a channel for that party where people likewise use the same 

     >>

      commands to communicate. 

     >

     That would be ok.  Gsay type channels should be a higer listen level 
than normal channels however.

>

     >

      In this case, maybe we could reimplement the 'shout' like a general 

     >

      channel everyone is subscribed to?

     >

      This way, even if shout still exists, it's still managed the same way as 

     >

      other channels.

     >

     I thought about that but didn't want to do it that way - shout is listen 
level 1 and should be a higher priority than these channels.  How I see 
the priorities are game messages 0, shout 1, tell/reply/gsay 2, channels 
3, player joins and stuff 5...
This lets you control at any time the amount of crap you are seeing in 
messages so when you are busy then you do listen 2 or listen 1 or in 
rare cases when the shout command is being overused and the DM isn't 
muzzling shouters listen 0.  The reason is that shout should be rare, 
you should be able to ignore tell if someone is bothering you but still 
hear shouts and you should be able to ignore subscribed chitchat when 
you are busy but still hear party communication.  We have listen levels 
and it is real easy to use them when sending messages so why not use them?

_______________________________________________
crossfire-devel mailing list

     crossfire-devel at lists.real-time.com

     https://mailman.real-time.com/mailman/listinfo/crossfire-devel