What you specify in the "Default Mapping" tab will be the defaults to 
be used in Prefs > Mapping > YourBehaviourName > YourRemote. If you 
manually made changes to your settings there, though, these will 
override what you previously defined in "Default Mapping" in the BCK.

To return your remote's mapping to what you have listed in "Default 
Mapping" in BCK, go to Prefs > Mapping > YourBehaviourName, select 
your remote control in the mapping table list, then click on "Reset to 
defaults".

Please note that, when you add your own Behaviour for an app that's 
already supported by a Behaviour that ships with Remote Buddy itself, 
which of the Behaviours will be picked to control the app is undefined.

You'll definately want to make sure that:

- you uncheck the checkbox in front of Remote Buddy's *own* Behaviour 
in Remote Buddy > Prefs > Behaviour (so it's no longer used by Remote 
Buddy).

- you do have only one copy of your Behaviour lying around in ~/ 
Library/Application Support/Remote Buddy/Behaviours

- your Behaviours do have different identifiers (=> see the forum 
topic "2 behaviour sets" for more info)

- you do select "Compile, testdrive and permanently install" at BCK > 
Behaviour Factory for your Behaviour. Just exporting a Behaviour will 
really just export it and have no effect at all until Remote Buddy is 
restarted - even if you replace an older copy. By using the formerly 
mentioned option instead of just exporting, your Behaviour is 
compiled, exported and loaded into Remote Buddy in one go.

Best regards, 
Felix Schwarz