cool you sorted this
the "chmod" tip is only to make a kinda shortcut with a second txt file that contains the stuff you need to type in terminal to launch the 1st txt file (your config).
For this BIG misunderstanding, it is my fault, I thought the default_settings.txt was always loaded with farmpad, as a file that would be read when lauching farmpad, but this default_settings.txt seems to be just a copy of whats written in the farmpad program itself...
I thought you could just change stuff in this default txt, and then just type farmpad to have this config loaded...
My bad...

(I don't know what happened to me, I'm quite sure I did something like this one day... but I'm using personal config files since ages... dunno... but you can see I tried something because all midi channels are set on 2 in the default_settings.txt I provided, and it is normally 1, so I HAVE done this change once... and I'm sure I didn't have to type the command to load it, as it was automatically loaded with farmpad, as a default stuff should be...

)
Anyway, you got it.
The chmod stuff is easy to manage, once you understand you need 2 files:
- the "benjamin_live_farmpad_config.txt"
- a little .txt with the command 'farmpad -c .../.../benjamin_live_farmpad_config.txt"
this 2nd "command txt" you can "chmod", and then replace the extension .txt with .command (and even replace the icon with a png file of your choice (don't ask me how, I can't remember, just visit the korg forums, threads about "farmpad", the tip is there).
then you'll just have to click on this icon / command to load terminal/farmpad/your config.
For your X/Y problem I don't know, I'm using it with the 3 buttons on the right to ON/OFF the fxs that are tweaked with the X & Y values...
Now you ARE using a personal config for farmpad, and you can spend time reading the manual and examples configgurations, and I'm pretty sure you'll be creating complex stuff in a few weeks !
Have good times
cheers