thanks for your postings. I'll reply to them both in one :-)

Regarding the F1 / F2 keystrokes. Since they seem to be mapped to 
your brightness controls in your setup, they are global hotkeys that 
are filtered away before any events are being passed on to any 
application. So, in fact, they have no chance to get through to 
Remote Buddy's "keystroke field".

A simple solution to this problem would have been to just press Shift 
+ F1 and then uncheck the checkbox for the Shift modifier.

Regarding your AppleScript: I really don't know what the cause of 
this would be. Especially, since it is obviously being executed (you 
mention the bezel display for brightness).

I've thought about this already, but then abandoned the idea of 
creating a Screen Settings behaviour that exposed all the possible 
screen settings as actions since the list would be just too long - 
especially with two or more displays. But I keep thinking about an 
elegant solution to this problem. Is it just the brightness controls 
you'd like to map in a behaviour - or also resolution/refresh rate/ 
depth/.. changes?

For now, what you can do is create a custom menu and drag the "screen 
settings" elements you need from the left outline view into a place 
of your choice in the menu.

Changing the names of existing behaviours or actions can be done 
right now by modifying the respective Localizable.strings in the 
"Contents/Resources/YourLanguageHere.lproj/" subfolder of the 
respective Behaviour package. I do plan to allow editing them within 
the UI for a future release, though (although this has a low priority 
atm).

Best regards, 
Felix