搜索结果: *

I can confirm this is a work around. However Even this seems very buggy. It will improperly report who is actually assigned a role and seems to think that 1 person has all the roles if you try to assign multiple roles to other people during the same session. this seems to just be a UI error however as going back to world map and hitting the clan tab shows the correctly assigned people.

But the long and short of it is that if a companion is assigned a certain role and then either dies, kicked out, or forms a party that role isn't there to reassign because the person is no longer available to "unassign"

Running into an issue of entire armies wasteing away. Just started watching their number slowly plumit for no reason. . And right before that it was a big group of them running around trying to raid downs with 5-12 people each party. after following them around for a few minutes they were all 0s almost like they were starving to death.

Using zero mods on a new save file started with the new beta 1.4.1 patch

Hmm....Theres something else thats making me scratch my head.  IT also involves Donavan.  I could have sworn he got pissed off and left my party.  But I didn't pay attention for a while and was just reorganizing my unit orders, and he's still there.  Not sure if its because I reloaded a save and don't remember.  or He's really screwed up.

nope.  Only changes I have made are using ingame settings. 

I have sent off my companions many times using the companion connections talk options.

I have yet to need to ransom a companion like I experienced problem with in the last patch.

I only had the script glitch when Donavan came back to me on his own after i lent him to the count.  Also, even though Donavan had come back to me, I still had the quest in my quest log.

Using the latest versions of Warband and PoP.

I ran into that Script error again when my companion came back.  This time however it was on a New game

I had lent Donavan to Count Raban for a week.  And typically i have to hunt down the lord to get him back.  Apparently he got restless and decided to come back on his own.  Shortly before that I had seen that he was "Attempting to rejoin" but thought that was just what it said when a lord had him for a quest

SCRIPT ERROR ON OPCODE 101: Invalid Party ID: 357; LINE NO: 134:
At Game Triggers trigger no:23 consequences
At Game Triggers trigger no:23 consequences

Ahh.  Wasn't aware there was a patch.

Edit.  Applied the patch.  And Still had 1 companion on the way.  I still got the script error message scroll. 

Not really sure if that's because I had already paid ransom and were on the way.

I searched the board and didn't see any entries for this.  There are some scripting errors when it comes to ransoming companions.  I still recieve the companions when I'm traveling around, and as far as i can tell they have the right stats/equipment 

I get this error.

SCRIPT ERROR ON OPCODE 101: Invalid Party ID: 344; Line NO: 134:
At Game Triggers trigger no: 23 consequences
At Game Triggers trigger no: 23 consequences

For the different companions it seems the party id changes
but everything else stays the same




There was also another bug that I encountered which may or may not be due to the mod.  When I was trying to break my companions out of the fortress, they just stood there once they got outside the dungeon.  I had to run out and engage someone and have them get close before the companions reacted at all.

This was at Whitestag castle and there were 3 companions that I broke out.  This is what lead me to try and ransom them because obviously the breakout didn't go so well.