Skip to content

#12303 Selection state of familiars should not be removed when loading a save

argent77argent77 Member Posts: 3,478
edited April 2015 in BGII:EE Bugs (v1.3.2064)
As the title says, selection states of familiars or familiar-like creatures are stored in saved games, but not restored when you load them. As a result you have to manually select the creature(s) after each reload.
It becomes especially annoying if you want to leave an area but get the infamous "You must gather your party before venturing forth" message instead because your familiar has been left behind somewhere on the map.

Actually I'm not sure if this is a bug report or a feature request. Can one of the people involved tell me more? ( @Avenger_teambg @Gate70 )
Post edited by Gate70 on

Comments

  • Avenger_teambgAvenger_teambg Member, Developer Posts: 5,862
    I didn't know it is saved, where would it be saved?
  • argent77argent77 Member Posts: 3,478
    @Avenger_teambg Summoned familiars are stored in the "Non-party character" structures in GAM files. These structures provide a "Selection state" field which is correctly set for familiars. Loading the save seems to discard this state however.

    Example of the GAM structure for the ToB Ferret after saving while the creature was still selected:
    image
  • ItomonItomon Member Posts: 187
    edited April 2015
    I am having another issue with familiars (http://forum.baldursgate.com/discussion/40887/dead-familiar-counting-as-already-summoned) but what I wanted to say is: before that, in this same game run, I had a problem with the familiar. I cant say what exactly happened but, after a battle my familiar became unselectable. It was there, as an NPC, and I could talk to him back to backpack. If I release it again, it would still not controllable, standing where he spawned.

    The problem is, I couldnt "renew" the Familiar, nor cast a new one ("Familiar already summoned" warning). So I had to kill it myself (and endure a Con loss) to have him selectable and playable again...

    Any clues what caused this?

    P.S.: I sometimes talk to him in the middle of the battle to save him in dangerous situations; maybe this must have messed with familiar in any way...
  • Gate70Gate70 Member, Developer Posts: 3,883
    edited April 2015
    Save/load
    I would say it is a bug, the state is known but ignored. Raised it on that basis.

    Unselectable. Probably what Argent77 has mentioned about dire charm at http://forum.baldursgate.com/discussion/40890/12304-familiars-should-not-lose-their-familiar-status-after-being-dire-charmed
    Thanks
Sign In or Register to comment.