Back on the 17th of this month, my partner and I were in the process of birthing out a new set of our roos. We waited until all of our first set had hit 60 and then a week or so after for a break. We haven't had any luck at all and yet, still decided to try again. In this bath of eight, there was a nest I bought months ago included in this set. We coaxed and they all birthed... except one -- the one I bought.

The nest kept erroring, saying that maybe it couldn't rez because the parcel is full. We have a sim, there is no way the parcel is full. We couldn't figure out what was wrong. I click the nest, go to it's webpage and there's the problem. There is already a live Meeroo with the same ID number as my nest being raised by someone else, though the website thinks I own it as well and allows me the ability to copy-paste it's data.

I quickly send in a ticket as we scramble to try to find a nest to replace the one that didn't birth otherwise we'd have a roo without a match. Quickly sending in this ticket didn't matter. I waited a day, which is fine. I understood the day wait but the response I got was mind-blowing.

"Hello Verinne, The meeroo from this nest ID that you gave me shows the meeroo as already being raised by you. His name is T------ and his ID# 7-----. Can you you please double check and make sure that you gave us the correct nest ID#? Thanks "

I waited a day to be told I was given the wrong number. But fine, that could happen. I stated I do not own that Meeroo but the one I have is a nest with the same ID, I had bought it months ago.

"Verinne, I'm sorry but it looks like you purchased a duplicate nest. Because this is a secondary market issue there isn't anything we can do as the origonal meeroo is already being raised by someone. Please feel free to share your ticket information with the seller and try to negotiate a replacement or refund with them. Because it is a secondary market issue we cannot help you, but the seller may, or you have the option of filing a ticket iwth Linden Lab against the seller. sorry for the inconvenience."

Now I'm being told that there is nothing they can do about it and I'm supposed to expect the seller to refund me -- if I could even remember/find out who it was.

Me:
"Excuse me? So you're saying that a possible server error on your part that may have caused this duplicate is not able to be handled by you? I don't remember who I bought it from, seeing as I said it was months ago. Maybe if you could actually help, like tell me who owned the parents and who currently owns the duplicate then I could actually do that but you and I both know they will not give me my money back. I can't understand why I had to wait an entire day just to get told you can't do anything. It is not a secondary market issue when it's your asset server or what ever allowing duplicates to happen -- that's your problem and if you personally, feel you cannot or are unable to help then transfer my ticket to someone else because I'm not just going to sit here and be told there's nothing you can do."

CSR:
"Hello there, the transaction record on the sl.com website will tell you who you bought the nest from. Nest duplications can happen when a sim rolls back or even restarts in an abrupt manner, this is a frailty of Second Life and is currently beyond our control. You are welcome to take this message and paste it to the seller when talking to them about this issue, to see if you can get a refund. I am very sorry you have experienced this problem. "

Me:
"No. You don't seem to grasp how transaction history works when you own a store and it's been over a month since you bought the nest. Please, tell me how to dig out that specific transaction ID # when the website doesn't go back that far. Seeing as the site itself states right above the transaction history drop down tab, "These are your Linden Dollar (L$) transactions for the previous 30 days. " And nest duplications can also seem to happen when your servers shortage -- why else does it try to delete duplicates? Isn't it a failure on your servers to successfully have deleted one of these nest/meeroos anyways, due to the duplication?"

This was all on the same day. I got no response. Two days later I responded to my ticket, asking if there was anything going on about it and then still a day later is when I even got a response:

"Hello there, you can get your transaction record from secondlife beyond 30 days if you apply to the for that information :) Hope that helps you find the information you need :) "

I responded:

"No, it doesn't. Do you seem to think I remember what month or day I bought this nest? You won't even give me any information to even help narrow it down. What kind of customer support is this when your own asset servers allowed the duplicate to be around instead of deleting one or the other like the servers constantly do to non-duplicate meeroos when they crash?"

The problem? That was the 22nd, now it's the 24th, the ticket was created around the 17th/18th and I won't get any help what-so-ever. I do not feel like I am incorrect in my questioning of why this duplicate exists and why they can't help when their servers are supposed to actively stop this from happening.

The fact that the Customer Support will go out of it's way to ignore my ticket makes me just want to say fuck it. It's honestly worse than the customer service you get when you call in to Verizon and that's saying something.