Multiple PC FTL Help Leader change

[Erron]

I have a 5 PC setup running Innerspace and ISBoxer on each. I am using Input Director as my KVM software. PC's are running Windows 7.

With this setup
Each of the other PC's can communicate with the main PC - they receive key maps, repeater keys etc.
So the slaves assist/follow the main without issue.
And the main can assist/follow any of the slaves without issue.
But none of the slaves will assist/follow the other slaves.

My initial multiple PC setup was completed from the Paladin's PC as the main. using this ISBoxer guide.
The FTL macros where edited using these steps from the Lavish forums.

Here's my ISBoxer toolkit profile from the main. http://pastebin.com/xXFdKkLA


So what happens:
Log in all 5 accounts 1 per PC (Paladin, Priest, 3x Mages)

Hit (Shift + Alt + I ) setup the group from the Main (Paladin)
Group is formed, Jamba team is created with the Paladin as the Master

!if ("slot 1" and character is not "slot 1") /invite {SLOT1}
!if ("slot 2" and character is not "slot 2") /invite {SLOT2}
!if ("slot 3" and character is not "slot 3") /invite {SLOT3}
!if ("slot 4" and character is not "slot 4") /invite {SLOT4}
!if ("slot 5" and character is not "slot 5") /invite {SLOT5}
/invite Priest
/invite Mage1
/invite Mage2
/invite Mage3

Hit (Alt +F) the 4 slaves /follow the Main (Paladin)

/follow  [nomod]player;[nomod:alt,mod:lshift,nomod:ctrl]Paladin;[nomod:alt,mod:lshift,mod:lctrl]Priest;[mod:lalt,mod:lshift,nomod:ctrl]Mage1;[nomod:alt,nomod:shift,mod:lctrl]Mage2;[mod:lalt,nomod:shift,nomod:ctrl]Mage3

Now everything works while driving and attacking (DPS 1 to = keys) with the Main (Paladin) all slaves /assist the main.

/assist [nomod]player;[nomod:alt,mod:lshift,nomod:ctrl]Paladin;[nomod:alt,mod:lshift,mod:lctrl]Priest;[mod:lalt,mod:lshift,nomod:ctrl]Mage1;[nomod:alt,nomod:shift,mod:lctrl]Mage2;[mod:lalt,nomod:shift,nomod:ctrl]Mage3

Switching to a Slave (Assuming the Main is down for example and the Priest needs to take control)

I slide the mouse up to the Priest's Computer screen (Using Input Director)
Hit (Ctrl+Shift+F12) to set priest as Jamba Master

/jamba-team iammaster all

The Jamba Team display pops up on the Priest and closes out on the Paladin.
Within Jamba, the Priest is set to Master and all others are set to Slave.

Hit (Alt+F) to set all the other PC's to Follow the new Master (Priest)

/follow  [nomod]player;[nomod:alt,mod:lshift,nomod:ctrl]Paladin;[nomod:alt,mod:lshift,mod:lctrl]Priest;[mod:lalt,mod:lshift,nomod:ctrl]Mage1;[nomod:alt,nomod:shift,mod:lctrl]Mage2;[mod:lalt,nomod:shift,nomod:ctrl]Mage3

Problem - only the Main(Paladin) now functions as a slave, assisting, following the new main (Priest) the other slaves (The Mages) do not follow/assist the Priest, but rather continue to follow the Paladin.

I get this same outcome if I had switch to any of the Mages as the new main versus the Priest.

How can I determine why only the Paladin seems to be working with FTL and leader changes? The Paladin will follow any of the slaves, but none of the slaves will follow another former slave.

[Erron]

Lax jumped into IrC chat with me and provided the missing piece.

Each of the slaves need to uplink to each other for them to communicate.

I created an Uplink startup command on each slave using

remoteuplink -connect NAMEOFPCTOCONNECTTO

PC2 connects to PC3, PC4 and PC5
PC3 connects to PC2, PC4 and PC5
PC4 connects to PC2, PC3, and PC5
PC5 connects to PC2, PC3, and PC4

From Innerspace icon in the system tray, when to configuration, Startup Sequence, Uplink, Startup

From there I inserted the three connections on each slave PC.

FTL is WORKING on each slave now!! This has to be the easiest setup I've ever had now.

Lax indicated that he is working on putting functionality like this into a future release.

Thanks so MUCH Lax!

[Lax]

All connections are two way, so you don't really need to have PC3 connect back to 2, PC4 doesn't have to connect back to 2 or 3, and PC5 doesn't need to connect back to any of them. But, unless it crashes for some reason, this should be fine

[Erron]

I see in the console where the clients are rejecting the duplicate connections. Will have to tweak that.