Companion Trait Broken

Summary:
The companion trait does not work properly. I changed the name of the heartling with the trait, and it did spawn the animal. But it was not the animal that the trait described, and the animal says that it is befriended with the old heartling (before I changed its name.)
Steps to reproduce:

  1. Create new game.
  2. Get a heartling with the Companion Trait.
  3. Change the heartling’s name.
  4. Create Game.
  5. Click the animal companion and read it’s description.

Expected Results:
The right animal, befriended to the right person/name.

Actual Results:
Wrong animal, Wrong person.

Notes:

Attachments:

Version Number and Mods in use:
Alpha 21, No Mods.
System Information:
Not Needed.

3 Likes

I’ve had this issue too, though it was remedied shorty thereafter by my poor squirrel Twigs starving to death because he refused to eat berries. I was really sad, and my poor carpenter was devastated. Then I realized being walled in with carnivorous squirrels probably isn’t the best idea…

3 Likes

RIP Twigs. may he always be remembered.

1 Like

The owner’s name of the pet is shown in the unit frame.
But when I modify the owner’s name, the name in the pet’s unit frame still remain the same.
I suppose it’s a bug?

I will look into this. Thank you for reporting it!

3 Likes

No problem. It’s something small but I’d do anything to help Stonehearth progress. Good luck!

1 Like

Summary:
When you start a game with a character who has an Animal Companion and change the character name in citizen window during creation the animal will report their old name when the game is running.

Steps to reproduce:

  1. Start a new game and get a character with animal companion.
  2. Change that character’s name
  3. Select the animal in the world and look at the description. It will report their original name.

Expected Results:
Would show the correct owner’s name.

Actual Results:
Shows the old name.

Notes:

Attachments:

Version Number and Mods in use:
Release-707 (x64)

System Information:
Windows 10

4 Likes

Thanks for the report! This has been fixed for the next alpha.

6 Likes