Home › Forums › Discussion Forums › Bug Reporting › Kaylas PC Properties curse
- This topic has 4 replies, 3 voices, and was last updated May 12, 2014 at 12:54 am by
Sarkhan.
- AuthorPosts
- September 20, 2012 at 6:55 pm #33274
We have many skins in our pack and they must be cursed cause we can not get rid of them and they stink. We pray that the gods will forgive our trespasses and remove the pc Properties curse from us.
September 21, 2012 at 3:33 am #58628@Kayla Evergreen wrote:
We have many skins in our pack and they must be cursed cause we can not get rid of them and they stink. We pray that the gods will forgive our trespasses and remove the pc Properties curse from us.
Give me a heads up as to when you can get in over the weekend and I will see about logging in to remove them.
Are you running a spell that causes them?
The PC Skin issue was a one shot from the 1.69 upgrade and shouldn’t generate more than one.
Let me know.
September 22, 2012 at 6:05 am #58629Its going to be a while before I can get in during a weekend. But as soon as i have a idea of when i can get in ill let you know if it winds up being hit and miss im good with that T.
**Edit**
I’m not sure when or how they got there when I logged in right after my last successful reinstall (I posted recently about Issues) i noticed them all over my inventory. I don’t believe they were caused by a spell I suppose it is possible that they may have come from my wildshape or elemental forms and to be honest that just now occurred to me.September 22, 2012 at 2:30 pm #58630The initial launch of an old PC in 1.69 caused the PC Skin to drop to inventory. They had made it possible for builders to script changes to the PC Skin so the old one was replaced.
I posted about it when we switched
May 12, 2014 at 12:54 am #80107Ok I’m slowly working my way back and have found a couple issues.
Kayla Still has PC Properties in her inventory.
Sar and Kyle are sharing Kyles chest and its hostile to both of them.
Other than that everything seems fine - AuthorPosts
- You must be logged in to reply to this topic.