As you may or may not know, you cannot put in JMC actions NemBot commands like /load bayeast. Reason is because it's not keyboard input, and jmc doesn't interperate that. So as of v2.0 of NemBot, i made it fairly simple for JMC actions to trigger NemBot events.

To load a nembot script use the command:
#scr {nembot_load("fen1");}
Replace fen1 with the name of the script you want to load, that's just an example.

To start a nembot script use this command:
#scr {nembot_begin();}

To stop a nembot script use this command:
#scr {nembot_end();}

To pause a nembot script use this command:
#scr {nembot_pause();}

To change the current move or shortcut, use this command:
#scr {nembot_setmove(id);}
id can either be an integer, or a shortcut string.

To change the attack you're currently using:
#scr {nembot_vars['config']['attack'] = "kill";}

Here is a list of nembot variables for the config that you can use in the same way above.

Example implimentation of this:
#act {^The fluttering of wings and a loon's shrill cackle pierce the tranquil marsh.}{#scr {nembot_end();};c 'red mark teleportation';#scr {nembot_load("fen1");#scr {nembot_setmove("west");};#scr {nembot_begin();}}
The small script above basically, when repop occurs in fens, it stops the current script, teleports to the intersection of fens and sets the shortcut to west and begins.

These should be the basics of what you need to make your scripts automated.