League of Extraordinary Multiboxers
Posts: 4606
Joined: Sat Feb 15, 2014 11:14 am
Location: In the dining room, with the lead pipe.
Re: problem when the head dies
You need to validate the following table by logging into the game with the characters in the correct slots (this needs to be consistent each time), inviting all your toons to a group, with the party leader and the order of invite/accept the consistent order you have been/will be using for all time (for this particular character set anyway). The acceptance order of the f/ship invites is more important than the issuing of invites. You can't use broadcast to accept the invites as the order is not going to be the same every time due to lag.
n.b. I tend to have my character slot order the same as the invite order, but this is not required, but it makes the below table mostly correct.
Now this is the ideal world, and matches your ISboxer profile, which is obviously not working and needs correcting.
It is meant to be read across and up, so assuming slot 1 has character D in, and D is the party leader, and the invite and accept order (note: acceptance order of f/ship invites is also important) is D invites T, who accepts before, then A who accepts, then Q then F then S.
This results in D will press F1 to select D, F2 to select T, F3 to select A, F4 to select Q etc. If you go to each slot, press the F1 to F6 keys, and note who they target and make sure it matches the above. If it does not, then note who the Fkey does target and move the Fkey notation around (and of course that means you will have at least 2 Fkeys that need to move around for that particular row).
Usually I find that the first 3 or 4 characters in Lotro are correct according to the above table, but the last 2 tend to have the F4,F5,F6 in a different order. Once you have a corrected table, apply it to the Variable Keystrokes for each slot. Again, it is to be read across, so if you are setting Slot 6, then the Target Slot 1 will be F2, Target Slot 2 is F3, Target Slot 3 is F4 etc.
Worth noting too. If you have a party member which leaves the F/Ship and then rejoins, it will break the above table because it reorders the f/ship. So, for example, if you get client crashes and it drops you from the party when you log that slot back in (by relaunching the character set and letting Innerspace load up any missing slots) you need to disband and reform the party. Same if you drop out a character because they need to run a solo quest or something.