[Crossfire-wiki] [Crossfire DokuWiki] page added: dev_todo:improved_player_communication

no-reply_wiki at metalforge.org no-reply_wiki at metalforge.org
Fri Jul 21 13:40:31 CDT 2006


A page in your DokuWiki was added or changed. Here are the details:



Date        : 2006/07/21 13:40

User        : 

Edit Summary: created



====== Improving Player Communcations ======

Ideas on improving the communication between players.



===== Inter-Server Chat =====

Allow players on one server to chat with another server.



==== s2s ====

Servers connect to other servers directly, and exchange messages.



Possibly have a central blacklist of abusive servers (which one can choose
 not to use).



=== Possible ways ===



== Server lists ==

Options to connect to all compatable servers on the metaserver



With a List (like ban lists, etc) of connections to make with other server
s



  * Can have a split network

  * No one single point of failure

  * more difficult to deal with abusive servers than using the "central se
rver" method



== Dynamic Private Conversations ==

  - Player1 on Server1 types "tell Player2 at Server2 SOMETEXT"

  - Server1 initiates connecton with Server2, if not already connected

    * cache the servers?

    * callback like done with xmpp to prevent spoofing?

  - Server1 sends Player1's message to Server2 with address to Player2

  - The message gets sent from Server2 to Player2's client



  * No general chat, unless combined with "Server Lists"

  * No single point of failure

  * More diffucult to deal with abusive servers than using the "central se
rver" method



==== Central Server ====

Use a central server (possibly runing on, or intergrated with the metaserv
er).



Server1 ---- Chat Server ---- Server2



  * Easier to impliment channels/general chat

  * easier to blacklist abusive servers

  * central point of failure

    * use fallback servers?

  * If an abusive admin takes over the central server, bad stuff can happe
n



==== Port the protocol to Jabber/XMPP ====

  * would have to redo the protocol, and its related code

  * added network overhead

  * interesting built in features of the jabber/xmpp protocol which could 
yeild interesting game features

  * code/standards for interconnecting servers are widely used.

  * WEIRD, but would work



===== Out of game chat <> In game chat =====



==== IRC bot ====



  * exists, in some form

    * not actively runing (code hasn't been cleaned up, no host to run it 
on)

  * A significant amount of players don't use irc, or don't know how to us
e it.

  * Simple

  * Appears hackish



==== Chat Mode Connections ====

Allowing connections to servers just for chating



  * more load on servers

  * doesn't appear to be as hackish

  * would increase the amount of users of crossfire (if not necessarily pl
ayers)

  * crossfire could end up being more of a chat protocol than a game

  * A gaim plugin, and/or jabber transport would draw attention to the gam
e.



IP-Address  : 24.55.181.141

Old Revision: none

New Revision: http://wiki.metalforge.net/doku.php/dev_todo:improved_player
_communication



-- 

This mail was generated by DokuWiki at

http://wiki.metalforge.net/





More information about the crossfire-wiki mailing list