Sorry if I'm in the wrong place, What is the current Unity Asset Store Refund Policy?

I just purchased a script Asset from the store, which was released on March 2, 2016 for version 5.3.1

I tried to run just the demos included and got several errors and "application.Loadlevel has been depreciated" stuff... and the demo games have caused unity to crash 3 times already... Now, I'm not ready to toss in the towel, as there might simply be something I'm doing wrong, however, I've been looking for the refund policy....


What I did find is from 2015, and doesn't seem very good.

Needing to contact the Seller to Authorize a refund? I spent close to $1000 at Daz 3D over the course of 1 year, and bought many items, simply because I could return them if they didn't fit my needs, and of the items bought, only 3 or 4 hopelessly broken items were returned. I can pretty much say I will not be spending anything more here if I "Need to talk to the publisher first". simply too many variables, too many headaches... This is of course a shame, as I've seen some things I'd like, but simply not going to risk it. I shouldn't have to "Fix" broken code when it's less than 4 months old, especially if I paid cash for it.

But before I get wound up, I just want to make sure this is still the policy.

 

Well the text you've quoted is talking about Daz 3D... but you purchased from the Unity Asset Store. It doesn't seem to me that those are at all related.

If I were you, I would contact the publisher of that asset and ask for help. Most asset publishers are sincere and hard-working, and will want to help you be successful.

 

As specified in the Asset Store EULA all sales are final. However, you are welcome to contact the publisher of the asset for their assistance. In some cases, they may be willing to authorize a refund at their discretion.

quoted from the FAQ

 

deprecation warnings arent the end of the world... they will still work for a long time before being completely removed.

Seems weird it crashes unity... wouldnt really expect that from a plugin unless it was rubbish.

Have you tried contacting the author about your issues?

 

I think you misunderstand. I'm talking about a Unity Asset, purchased in the Unity Store, that gives errors in Unity, when loading the demo code... Daz3D has nothing to do with the error or anything else other than to convey that I'm willing to spend a lot of money in a place with a decent return policy, but not in a place that does not. On closer inspection, the Version of the script I purchased was released on 5/30/2016, so it is less than 30 days old, yet is loaded with code that Unity Obsoleted quite some time back.

Anyways none of this has anything really to do with my question, as I was asking about the return policy, which Hamshank Answered.

Thank you, I was afraid of this... It's my own fault for not verifying this before I made a purchase, but I must say this seems like a really bad way to do business... I had a couple hundred dollars worth of stuff I was considering, but If 30 day old code doesn't work, and there is a "no return" policy, I guess I'll pass..

 

What version of Unity are you using? As I recall the newer version tends to bug a lot (seeing from other threads), your alternative might be to use an earlier build to test out first, before the developer update the script to the newest version of Unity. I've privately mailed developers, and I can say most of them gives out very fast replies and are happy to help.

 

Talk to the developer. Many of them will authorize a return if the asset does not suit your needs or they might help you get it to work. I wouldn't be afraid of them. They are usually very nice people.

 

Agreed on all points. I just had to revert from 5.3.5 to 5.3.4 because of a nasty bug that breaks editor plug-ins (and I can't live — or at least, can't code — without my Script Inspector 3!). This is very unusual; Unity rarely regresses, and this is the first time I've ever had to go back to an older version. But it's certainly not the plugin developers' fault. And I'm hopeful Unity will get it fixed soon.

But more importantly, as everyone else has said: talk to the developer. I'm sure they're eager to help you out.