Yes, I originally put the sitting check so that when the actor is on a horse you would get a different selection for options. Looks like I can swap the position of the two different condition sections and still get the same effect without locking you out of giving commands if they are sitting, but not on a horse. Don't see why it wouldn't work if they are lying down though unless there is a bug in the getsitting function that reports a sleeping actor is sitting.

wups my bad. it owrks fine when they'r sleeping but not when sitting guess now i kn ow why

Ok thanks, I uploaded a new version that includes the fix for this issue.

nother thing. it see3ms the file wasn't packed right in your update. there are two Companion Master Esp's one inside and one outside the data folder. not abiug issu as far as I can tell but still owrth mentionig it can get a bit confusing

Thanks the one inside the data folder is the old one. I just dragged the update into the archive so the new one got placed outside the folder, that's what I get for not being thorough. I deleted that upload and replaced it, thanks again

happy to help. big fan of yor work. not much of a modder my self more of a bug report an d idea knda guy

Well I have about ten or so companions and I presume they are all using the same PartnerScript, not so? I figure it would work on some of them at least that happen to be using the correct slots. Ah well, I will fiddle again later, not in the mood on a sunday night just want to play as much as possible before work tomorrow



Yeah I have never ever had double face bug and I use CM partners a LOT. Disabling them though usually if not always results in a crash.



Yeah will have to untangle what script is being run, is there any way to get the console to print the script it runs? Yep it definitely crashes on a companion with locked items But I was toying with your Share function and all of your other menu items and I must say, fantastic work on all that stuff, awesome!! You might want to include a few 'Back' buttons on all those nested menus though.



Will give it a try when I'm feeling energetic. Don't think my knowledge of the Oblivion language is up to it though, but I am a programmer so what's my problem? Hehe.

Well I have just been playing for a couple of hours and testing your mod quite a bit. I installed the Horse Dreamland mod and gave three of my companions lovely new horses. Then fiddled with all the mounting and riding functionality. I notice that when I dismount, my companions don't automatically follow suit, unless its on entering combat (I think they might have dismounted once, eventually). I need to manually tell them to dismount. Is it possible you could have a look at that or am I doing something wrong? Also, is it possible to have some kind of catch-all option that would mount or dismount all companions that are on the companion list?

Wow! It was great to have all my peeps riding around with me, what a sight!

I also noticed that on mounting, companions don't always assume their riding order, and I often have to tell them each twice or three times to take their designated spot in the queue. Seems they want to assume the default CM behaviour of "follow close as possible jockeying for position" and with horses it just gets messy

Was trying out some of the other functionality as well. Picking locks seems fine. However with regard to companion training, I see that I can only train ONE companion in ANYTHING every two days. Was this by design? I was thinking it might be more reasonable/lenient to enforce the 2 days as before, but per companion and per skill (or at least per companion).

Overall this is a fantastic mod! I never thought I'd see my CM partners riding horses with me, and I experienced no related crashes other than the one you forewarned me about. You're the kind of guy who could write your own CMPartners replacement that would encompass what you have now and a whole lot more!

If you open whichever version of CM you are using in the editor, the esm and any esps that go with it, then find your companions in the object window, just see which script is attached to them.



I didn't script anything to make them dismount with the player. Reason being that I want the script to be as efficient as possible. To me that means shutting down all functions when the inventory item is not in use. CM companions already have a ton of un-necessary code running every frame and I certainly don't want to add to it.

I might be able to do some group mount/dismount stuff, just have to make room for another menu option. All the menus are basically holding all the commands they can hold at this point without creating an out to another menu, but I will look into it.



The reason they bunch up like that is that you need to give one the mount command, then wait until they are mounted before ordering another one. Reason being I add one package to get them to mount which has a very close distance to the player. This is necessary to get them moving to their horse before setting a longer follow distance. If I set a longer follow distance before they are mounted then if they are inside that follow distance they wont mount until you move far enough away that they are outside that distance. Sorry hope that makes sense to you. Anyway when the companion is moving to the horse the script keeps track of them and when they mount it sets the follow distance you selected. So if you tell one to mount, then another before the first is mounted, the script stops tracking the first, and instead tracks the second. So the first never gets his position set, and stays with the close follow I gave him to make him mount in the first place. That sounds so confusing I know but it's really not



This is something that I knew would come up. I obviously don't want to make it seem like a cheat feature where you can just click your companions to max lvl. I can keep track of positions in the companion menu and only allow each position to be trained a given number of days, but things get messy when someone removes a companion and adds a new one to the same position. I can't really track a specific companion because they are from other mods, best I can do it set a variable to them and track that variable. Of course that variable will represent a different companion once one is removed, then a new one added. So I'm not sure what is best but I'll take all opinions into consideration

Hi b3w4r3,

Thanks as always for the feedback, I was mounting my companions before mounting myself, now I will mount up first then mount each one individually in turn (your explanation wasn't confusing actually!). That last line sounds dodgy, lol!

A group mount / dismount button(s) would be fantastic!

I have other questions I noted down at home, one of which I remember: I notice that most of the time I have to cast the Companion Master spell more than once (usually 3 times) on a horse to set its owner or do whatever with it. Another thing, the spell causes a momentary "distortion of the air" type effect that usually happens for summons. Is it possible to change this effect to be more of a generic/nondescript casting motion?

Anyway I don't often post and I'm only doing so regularly in this thread because I am loving the mod and just providing constructive criticism and (optional!) suggestions

Would be interesting if you make this mod modular.
Haven't tested it yet but it will come in time.

no real point in making it modular? why seperate all the functions theres no chya nce of conflict far as I can see

It was modular. Per the description,

This is a rebuild of 5 of my other companion based support mods.

Set Essential Actors Plus
Companion Horse Support
Companion Repair and Recharge
Companion Resurrect
Companion Tracker

So if you want individual elements, just download the originals.

I know these preceding mods, but where is the new companion hotkey command and the lockpick command? so I don't think it's modular in his present form.

I'm afraid I don't understand. In other words, you want to load in one ESP and have the option to choose what commands you use? You can do that, now. You don't have to use any part of CM that you don't want to. So if you want to only resurrect a companion, you can do that, and leave everything else alone.

But if you want to run only the resurrect portion of CM, and not even see the option for other commands, it's already available as a separate module on TES Nexus.

Well I did some work last night incorporating something I am using in a Fallout 3 mod to add some of these features to that companion mod. Basically I changed this mod so that if you hold down the block key while accessing the Command Ball, it will open a new menu aimed at group commands. I've added Follow, Wait, Ride Horse, and Dismount. Testing seems to be going well now that I have worked out the bugs so this will be in my next release.

I'm also changing the way horse riding works. Instead of letting the player selecting a follow distance I'm setting that automatically depending on your companions position in the Companion list. I also added some code to track each NPC during the mount procedure so you won't have to wait until one is mounted before telling the next to mount, and they will still fall into their correct following distance.

As for making all of these features modular, I understand where you're coming from but I don't think it's necessary. When I started making these companion support mods it became apparent that having one bigger mod that allowed control of all functions from a minimum of spells/items was easier to use. You may not want or need all of these features but it's nice to have the two or three features you want not require 3 spells and 3 items. Using this mod you have a wide variety of companion controls at your fingertips without having to walk up to your companion and enter dialogue every time you need to make a small adjustment. With the new group commands coming I think I have covered enough that this can be your main companion interaction function while on the move.

Still not sure what to do about the training. Letting you train every companion once a day, or even every two days just seems a bit unfair. I can change it to one companion every day and still be confident that it is not going to be abused. Consider that in 10 days (if I change it to one day) you can train one companion's skill from 0 to 100 providing that you are lvl 100 in that skill.

Oh, and I will change the spell effect to something different. That soul trap effect lags me aging computer anyway Maybe just remove the effect completely as it's not really necessary.

What about allowing a character to a companion once every month for 1-3 points in a single skill? Or place it in an INI file, and allow the player to set it as they wish.

Version 4 is up for grabs at TesNexus with the new group commands, and other changes I noted above, and in the file description. Please understand that to access the new Group menu you will need to press and hold down the block key while activating the Command Ball inventory item, either from your hot key

Fantastic, I will be using this primarily for the easy access to horse commands. I have a mod already that allows me to hotkey the existing CMPartners commands (follow, standby, guard, etc) but obviously it doesn't include horse riding



This sounds great too. Just thinking though, if I add companions at positions 1, 2 and 3 o the list, then another at position 9, will there be a large gap between 3 and 9 or will the two be right up against each other? Just wondering. Also I have two companions (Saerileth and Viconia from SultericDrums) that have their own horses. I will leave them to mount and dismount as they normally do without interference, but how do you think your script will handle them if I have placed them in the companion list (in order to access the other features with them) and then get all my companions to mount up? Will they attempt to keep the distance stipulated in their mod code, or will your functionality overwrite that?



Yeah absolutely! The centralisation of group commands withouth having to enter dialogue is just great, and so is the reduction in ESPs, spells, items etc.



I think go with what you think is most balancing (you know the math), or you could provide an INI option if you feel particularly energetic. No worries from me though either way



Removing it would be great, then!