[CF-Devel] '/command and '<text to say>

Wed Mar 10 12:13:53 CST 2004

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Mercredi 10 Mars 2004 12:21, Brian Angeletti a écrit :
>

      Jochen Suckfuell wrote:

     >

      >>In order to do so, the server must handle the default as say unless it

     >

      >>sees a '/'.  If it does see a slash, it will parse it as a command,

     >

      >>unless it is not listed on the server as a command, in which case it

     >

      >>would return an invalid command error.

     >

      >

     >

      >This could be handled completely in the client. That way, it could even

     >

      >be optional.

     >

     >

      Yes that would work, but I feel that server side would pay off more in

     >

      the end.  It would make sense to make our current style as the default

     >

      if the slashed command prefix weren't *much* more common than our

     >

      command style.  For example, IRC and the overwhelming majority of other

     >

      MMOGs prefix commands with a /.  Finally, it makes more sense to err on

     >

      the side of caution and use the most commonly used command style rather

     >

      than to force people to learn a new command entry style if they haven't

     >

      used it before.  Also, if we were to add this as just a client option,

     >

      you would need to patch each of the 5 different clients.

     >

implementing on server side mean to patch all running servers. Some server 
only use the releases, some servers are still a 1.5.0 version  or and finally 
some server use the cvs.
If we change it server side, we change it only for cvs servers. This mean we 
end up with different set of commands on different sets of server. Not good

>

      Another reason is that I feel that the method of entry we use now is

     >

      highly redundant.  'say is the most commonly used command... why should

     >

      I need to type say to say something anyway?  I think we can err on the

     >

      side of caution and handle text as though users want to say something

     >

      when they don't deliberately invoke a command.

     >

And what happen if an admin want to type

dm mypassword

and mistake it, typing 

dl myspassword  ??

Yes the dmpassword will be 'said' around :/ a bad thing imo

>

      Another advantage is that if we write this into the server, if someone

     >

      didn't write the "standard command" option into the client this use

     >

      would still be default.  For many people who are new to Crossfire this

     >

      may be much easier to understand than typing commands without /.  The

     >

      client can still have an option for "Crossfire style commands",

     >

      regardless of whether we handle this server side or not, but I feel that

     >

      if we put this on the server it will be much more beneficial.

     >

Do not agree, on server is complicate, need code, need to wait for the server 
admins to upgrade. 

Concerning your 5 clients... Can you enumarate them?

I'll say directx client is deprecated and it already has 'say' and 'shout' 
buttons
The gtk linux and windows client are now insync concerning releases.
The cfclient uses the same core as gtk, so changes in gtkclient would be done 
immediatly in cfclient

Who's the 5th client? :/

>

      _______________________________________________

     >

      crossfire-devel mailing list

     >

      crossfire-devel at lists.real-time.com

     >

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

     -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAT1rnHHGOa1Q2wXwRAmMsAJ9AaiOjduEIDF/F72f+87/lXgoCxgCfZSfJ
uVKeyYgsHNQAtHz4j0eEdL8=
=hm1E
-----END PGP SIGNATURE-----

_______________________________________________
crossfire-devel mailing list

     crossfire-devel at lists.real-time.com

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