[crossfire] sound2 protocol and issues: sound_chance

[Nicolas Weeger]

>   Using a string for action name is probably fine, OTOH, there is
> presumably a finite (and actually quite small) set of actions.  Since
> right now, all the play_sound calls are basically hardcoded on where they
> get called, putting in an integer type would be fairly easy.

What about plugins being able to send an arbitrary sound?



>   That would mean there is the potential for the client getting an event
> type it doesn't know how to handle - but at the same time, if the client
> doesn't know how to handle that event type, it would be equally likely it
> would not have a matching sound file for that even either.

Unless it can request it from some place.





Nicolas
-- 
Mon p'tit coin du web - http://nicolas.weeger.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
Url : http://mailman.metalforge.org/pipermail/crossfire/attachments/20101002/ee9df2bd/attachment.pgp