On 09/29/10 09:40 PM, Kevin Bulgrien wrote:
I think that was one reason I was more in favor of symbolic names
(dangerous_song, port_area) - it seems in many cases the client may do some
amount of remapping for what songs it has.
OTOH, using file names does not preclude that - it can
I think that was one reason I was more in favor of symbolic names
(dangerous_song, port_area) - it seems in many cases the client may do some
amount of remapping for what songs it has.
OTOH, using file names does not preclude that - it can just make it
harder if one adds a new file name
I think that was one reason I was more in favor of symbolic names
(dangerous_song, port_area) - it seems in many cases the client may do some
amount of remapping for what songs it has.
OTOH, using file names does not preclude that - it can just make it
harder if one adds a new
Extract from the Developers/protocol:
Change background music. Server will send NONE as the string to stop any
music from playing. This song data is set in a map property. (Due to
someone forgetting to update this file when he/she implemented the
command, it is unknown
Extract from the Developers/protocol:
Change background music. Server will send NONE as the string to stop any
music from playing. This song data is set in a map property. (Due to
someone forgetting to update this file when he/she implemented the
command, it is
On 09/26/10 02:48 PM, Kevin Bulgrien wrote:
Extract from the Developers/protocol:
Change background music. Server will send NONE as the string to stop
any
music from playing. This song data is set in a map property. (Due to
someone forgetting to update this file when
6 matches
Mail list logo
