Forums » Community Projects
Proximity beep
Is it possible to change the beep for a different sound? did a quick search and came up blank
I'm sure I read a post somewhere about how to change the beep sound but I haven't been able to find it again. : (
Will have a look at the lua api and see if there's anything in there that might help but no promises.
Will have a look at the lua api and see if there's anything in there that might help but no promises.
Are you thinking of the deboop plugin, Woodlander?
http://vo-wiki.com/wiki/Plug-ins#deboop
You'd have to edit it to replace the prox sound rather than the hit beep, but the concept should work.
[EDIT]
You'd want to change line 18 to:
if name == "prox.warning" then
http://vo-wiki.com/wiki/Plug-ins#deboop
You'd have to edit it to replace the prox sound rather than the hit beep, but the concept should work.
[EDIT]
You'd want to change line 18 to:
if name == "prox.warning" then
Thanks meridian, that's exactly what I was looking for. : )
TehRunner, hope this helps http://ubuntuone.com/60POsguGL0YbgGMafURDui
I'm assuming you know how to install plugins but if not look here. Replace the sound.ogg file in the /plugins/deboop_prox/sounds folder with the .ogg sound file you'd like to use, then rename it to sound.ogg
I've only had a chance to test it with npc's but there's no reason why it shouldn't work with pc's too.
TehRunner, hope this helps http://ubuntuone.com/60POsguGL0YbgGMafURDui
I'm assuming you know how to install plugins but if not look here. Replace the sound.ogg file in the /plugins/deboop_prox/sounds folder with the .ogg sound file you'd like to use, then rename it to sound.ogg
I've only had a chance to test it with npc's but there's no reason why it shouldn't work with pc's too.
You really shouldn't use the name deboop1 on lines 13 and 18 of deboop_prox, Woodlander, as that will cause a conflict with the original deboop plugin if both are installed.
There is also a conflict with the load_deboop() function, as spuck wrote it to only get called if spuck.deboop has not yet been set to true. So if both plugins are loaded, only one will end up calling its load_deboop() function... at least that would be the case if it weren't for a typo. I'm guessing spuck intended "spuck.deboop = true" instead of "spuck.doboop = true" on the last line.
There is also a conflict with the load_deboop() function, as spuck wrote it to only get called if spuck.deboop has not yet been set to true. So if both plugins are loaded, only one will end up calling its load_deboop() function... at least that would be the case if it weren't for a typo. I'm guessing spuck intended "spuck.deboop = true" instead of "spuck.doboop = true" on the last line.
Thanks meridian, I owe you a few beers!
Have altered deboop_prox so it won't conflict with deboop (the url above now points to this version) - http://ubuntuone.com/60POsguGL0YbgGMafURDui
Have altered deboop_prox so it won't conflict with deboop (the url above now points to this version) - http://ubuntuone.com/60POsguGL0YbgGMafURDui
awesome. thanks all