[Fixed] Duplicated Deco Pets and Names

03/20/2021 15:34
Title: Duplicated Deco Pets and Names
Reproduction Rate: 1/1
Blocker? No
Details: In my basement, I have several deco pets. It seems my pet broom somehow cloned itself and acquired the name of my mini italian greyhound.
Steps to Reproduce: Observe the extra broom deco pet that was duplicated from the source "Broomba" and acquired the name of "Cannoli" from my mini Italian Greyhound.
User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz (6) System RAM: 32678
GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8088
SotA.QA.Win.64.1154.Date.03.19.21
Area: BasementSceneDungeonVillage_Arena
Area Display Name: Village Stone Arena Basement
Loc: (32.2, 8.1, 23.7)
Debug: QmFzZW1lbnRTY2VuZUR1bmdlb25WaWxsYWdlX0FyZW5hfHwoMzIuMjM1LCA4LjA4LCAyMy42NzcpfCgwLCAwLjkyNiwgMCwgMC4zNzgpfDQ5OC45MzcxfDM5LjY1Mjc3fDMuMDU1ODY3

 

@Echondas is the broom placed on a rug or paver you may have moved?

https://www.shroudoftheavatar.com/f...s/submitted-68075-pet-duplication-bug.161914/

(though that bug wouldn't explain the name change)

 

I have a similar situation in my basement. I have three npc/pets two on first level and one on the second. none on carpets or pavers. The two on first floor have duped, However, the copies are not named but have the default name. the third pet on the next floor down did not duplicate.

03/21/2021 05:15
Title:
Reproduction Rate:
Blocker?
Details:
Steps to Reproduce:
User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz (4) System RAM: 16327
GPU: NVIDIA GeForce GTX 1070 Ti GPU RAM: 8079
SotA.QA.Win.64.1154.Date.03.19.21
Area: BasementSceneMedievalTown_5Floor
Area Display Name: Town Stone & Timber 5-Story Basement
Loc: (10.5, 3.3, 17.6)
Debug: QmFzZW1lbnRTY2VuZU1lZGlldmFsVG93bl81Rmxvb3J8fCgxMC41MDcsIDMuMzIzLCAxNy41NTcpfCgwLCAwLjUzNywgMCwgLTAuODQzKXwyNzcuNTAxMXwyNS40NjM0NXwxLjI1


hope this helps

 

I'm not seeing this on live - so it may have been fixed.

@Murphy Are you seeing this on the live server after the update?

 

This seems fixed - marking as such.