some days ago my SL Dad passed me 3 of his nests so I could set them out for sale in our market stand.

2 of them rezzed the 3rd one poofed on rezzing.

it didnt return to inventory, so next day I filed a ticket with nest ID and today a very nice CSR contacted me and told me, that the nest with that certain ID isnt shown as being owned by me in their database.

so: even that I had the nest passed to me and had it in my inventory at least 3 days ago the meeroos database still shows it as the nest of my SL Dad - and they have to restore it to one of his stumps.

its no issue for us at all. its family and I had it to sell it for him, so really dont care to which stump it will be restored.

but the question is:

what if ppl p u r c h a s e a nest or a roo in a market or auction, take it into inventory .. go home - and it poofs with the well known SL message *attempt to rezz an object failed* when they rezzing it? and what if it does NOT re-appear in inventory after relog and clearing cache (sometimes poofed items come back, most of the time they wont)

the new owner of the nest/roo paid money for it, but when they file a ticket they will hear that they arent shown as owner in the meeroos database and the nest will be restored to the previous owner.

then what? the new owner who paid perhaps perhaps lots of lindens for that nest/roo and then they have to trust in the seller's honesty, hope that the seller isnt off for vacation or due other reasons to get it back at all. if this happens with a real high priced nest/roo it will cause drama.

I've been into breedables for 2 years now and when I had bunnies I used to have that *attempt to rezz an object failed* issue at least once a week. either I myself or one of my customers.

But it was never an issue to get the nest/bunny back directly to their new owners as either I had the ID# or the owner took the ID# after purchase before taking it into inventory. They just filed a ticket to Ozi support with ID and got it back without needing the person they purchased from.

Ok Meeroos are different but this might (will) get an issue sooner or later so I really hope the Meeroos Team will find a solution soon.