I've been pretty much quiet on this matter ever since it occurred due to a loss in my life that has been difficult to accept. While my character's soul tree was indeed a part of it as well, I had fellow ST help me through this entire ordeal given my personal situation irl to deal with. I first wish to thank those that helped me during this time, offering to roleplay my soul tree, getting ones to help, and getting an outcome done while I've been gone. For what I'm about to write, it will be in two parts. First is the side of the Treelords. The Second of Management/Mods. I hope this gives context in the end for both sides to find understanding.
We all know how it started. An attack on Illivia with some evil droods and abunch of inferi. The target was dragonoftater's soul tree. Which was in a grotto with abunch of other soul trees there. This in and of itself treelords would already understand that there is pros and cons to doing such. Which a con then happened. With Tater's soul tree attacked and destroyed, the raid wanted to go after all trees in the grove. Soul trees, regular trees, it didn't matter but players were tired and wanted to log(from my understanding). So it ended up being CRP locked. The Treelords all involved were placed in a group chat with Raiderblue, Trinn, later Pallo(ST manager). To schedule interactions. Hopefully with all those involved there at the same time. Now at that point, none of the other soul trees were ever interacted with or begun an attack upon. Most of us were asleep or not around and were surprised with the sudden statement. Which first drew some confusion and frustration. Lore was double checked and protocol was indeed being followed in regards to how soul tree interaction works. The main frustration being the trees never interacted with at all first with getting attacked, they were just in the area itself. Which was deemed CRP locked. So a froze occurred that lasted til the next weekend, which was 1 OOC week. During that time, Tater's posted the pk post and many of us were left with not being sure on if we could RP our characters or how to RP the characters. As reactions were going on in real time for all the other druids, but for those frozen, we couldn't acknowledge or react correctly because it was still happening for us. Trinn tried helping with offering solutions to this, but in the end. It was difficult to roleplay what to do. During this time as well, while of course the usual grumblings of a freeze and that the treelords should be allowed to get a rally or something because lore wise, made sense of a treelord dropping like a fly, people want to check on their tree. At the end of the day, the redlines were clear in that regard.
Now before I left the chats given my irl situation, there was back and forth on the touchy subject of unattunement and murdering soul trees and stuff. It was stated someone might get unattuned since the one for tater's didn't go off. So ontop of the freeze of the unknown, out of the four of us, one would get unattuned. Which unfortunately being told on a maybe didn't help the matter nor calm. Even if trying to explain and be honest. There wasn't ill will on the statement, but the stress grew with that unknown of who it would be. The rest would just be destroyed and stated if you had a sapling, you will be fine. I personally didn't care on the matter by that point. As I explained I was fine with whatever happens. I had Werewolf on standby to RP my tree and later Raiderblue helped find someone else to do it because Werewolf couldn't be there that day when the unfreeze happened. (Thank you again guys). Shortly after, I had to leave the chats as I was dealing with irl. So I don't know what else was said.
So fast forward to the day of. Soul trees were roleplayed, destroyed. No one was unattuned. Everything finally finished. Saplings were used to plant elsewhere and so everything continued on. So like Feb 7th this happened, then on Feb 10th(from what I can tell with the messaging), suddenly the soul tree users were messaged by Squak that an audit happened after an enquiry from the opposing side on the saplings and determined they didn't count so the treelords got PK'd. Now, the treelords are absolutely confused and hurt. As seen here. Because they thought it was over. They thought they were also following how Saplings worked because while everyone here saw the redline in regards to what is needed to do to keep a sapling alive, every single treelord had done the sapling in chest thing at one point or another. Because the lore was so vague in that regard, it was never seen as an issue and allowed. As well as saplings always accepted and used. The treelords in the end, didn't do anything wrong as they thought they WERE following lore given the redline wasn't specified and all the soul trees did such at one point or another.
On the side of ST Management and Moderation. This would be a pretty huge CRP situation and given the number of CAs effected, would need calls made and people on standby. The Opposing side of evil droods and inferi had a mod and an ST oversee the events and during that CRP, calls had to be made where the lore was vague. Tater's soul tree, for example, in regards to how many emotes would malflame destroy a soul tree. A call had to be made and determined for 3 emotes. Which was one short of the unattunement emote. Yet because the tree succumbed to the malflames an emote early, it was deemed a pk given all that was happening to it. Later on, Mod and Management had to deal with explaining to the treelords on the redlines of soul tree lore and trying to defuse the situation. Again, Trinn offering alternatives and trying to make the freeze situation fair for both sides. Especially in regards to how to roleplay and proceed. Pallo coming in later and explaining that management did talk over how to do the CRP because at the end of the day, this was a very unique and tricky situation. And it would be a huge task to make an individual CRP lock freeze for every single soul tree user there when its from the exact same CRP encounter.
Now, as stated above on the treelord side, I left the chats given irl situation. The attack proceeded on Feb 7th, things wrapped up and all said and done. However, Raiderblue then realized there was a clause in soul tree lore regarding Saplings and keeping them alive and healthy. Now, this does happen of something missed or not thought about and it brought up to management. Management told this because well, this was already a huge task and several ST were part of this encounter soul tree side. This is standard protocol. So given the situation, Management looked into it. There wasn't a duration or specifics on how a sapling is stored or frequent hugging requirement. This was written back then with the mindset of a Druid knowing what it means. Which back then, it actually followed how awakening worked with staves. If a druid isn't feeding energies for an OOC week (or something), it would fall dormant. But Management of course didn't know that nor could even rule on that factor because nothing was stated. Squak instead gave a HUGE leeway 30 day omni log to see if saplings were interacted with or at least in druid player inventories. And as people can see the results, Management had to think on a decision here. Because while the CRP was said and done, they were also faced with what is fair for the opposing side and what is fair in the lore itself. Of following the rules of what you agreed to play. Thus it was decided, even after giving a massive leeway chance, of the saplings not counting.
Now at the end of all this. My personal opinion on the matter is that while things could've definitely been handled better on both sides. No one is at fault or did anything wrong. The evil drood players weren't conspiring with ST to force take down so many people. The treelords weren't dodging creature mechanics or breaking lore, they were following what redlines were given and how all current and previous treelords did. It is a very unfortunate and frustrating situation. But, it should be noted that none of the sides were bad or out to get the other or avoiding mechanics. I think the PKs shouldn't have happened and an immediate amendment should've been made to fix that glaring sapling issue, but that option is one of a few. And its fair that it wasn't chosen by Management to uphold.