We’ve recently begun accepting what we call presentation-style preview videos for applicable Motion Graphics submissions. We feel that buyers tend to appeal to these kinds of preview videos since they portray real-world use scenarios.You can read the official policy and all of its details in the help center: https://help.market.envato.com/hc/en-us/articles/204063054-Presentation-style-Preview-Videos-for-Motion-Graphics
Hey guys, I thought I’d pop in here to try and explain the situation with the new plugin fields.
A little history
As many of you probably remember, we used to explain plugin usage within Projects using a single attribute titled “Requires Plugins” and the value was either Yes or No. Over the years I received many requests from both authors and buyers to expand this field to actually list out the specific plugins because up until very recently the only way to explain plugins used was through the item description.
Listing out required plugins in the description was always mandatory and it was setup that way for a reason. If you submit a project that requires Trapcode Particular, but neglect to list it in your description, buyers might find themselves unable to use the project if they do not own a Particular license. Requiring it in the description was a solution, but it was never very effective. Mainly because all we required was that the plugins were listed somewhere in the description. Each and every author has their own description style. Some would list required plugins at the top, others would bury this info below everything else. Some may include the information in a neat ordered or unordered list, and others might just type out each plugin required in sentence/paragraph form.
This inconsistency creates a very confusing experience for buyers. If it’s not easy to see which plugins are required, it could lead to a large number of refund requests and some very upset buyers.
Why we went with the new solutionWe racked our brains for quite a while about the ideal solution to this problem. There’s many possible ways we can present this attribute but we felt that this method best achieved the desired results.
- Allows authors to easily explain which plugins are utilized and can be edited if the buyer owns the plugin.
- Allows authors to easily explain which plugins are actually required.
- Will help people locate your item in the future, when these could potentially be searchable facets
- Will improve consistency and buyer confusion, removing the need to list all plugins in the item’s description (unless you select “Other”). Buyers now know all of the plugin related information is available in the item page sidebar. More importantly, it’s always going to be presented exactly the same way, for each and every item.
Regarding the concerns raised..
They way I understood it is if you provide two versions, one with prerenders, one with the plugins, you list those plugins in the “plugins used”. And if only a plugin version is included you list it in the required plugins list.
That is correct.
This is the tricky part: If you used a plugin in the creation of your item but do not provide a plugin version, only a prerendered, I think you list in in no list at all. But if buyers search for a specific look instead of a plugin to use, they might be filtering out those with only prerenders for no reason.
In the event that you used a plugin to create something, like a particle animation using Particular, but did not include the version of the project file that actually uses the plugin, you’d simply select “No Plugins” for both fields.
This is the way the rule has always been and hasn’t changed at all. If you went outside and shot a texture and included that texture image in your project, or rendered a 3D asset from another software program, or included any other footage or media assets, you wouldn’t reference plugins at all. So any media that’s included (rendered or otherwise) does not need to be referenced back to the plugin, unless of course the editable plugin version of the project has actually been included.
Keep in mind that if you use a plugin with a project file and want to provide a prerendered version, it’s in your best interest to also include the editable version for buyers who do have access to that plugin. Providing only the prerendered version here only serves to limit the appeal and usefulness of your item, so this scenario is really more of an edge case and is not recommended.
Very confusing. Why should the buyer need to know what plugins or 3D software I used to make a template? What’s the use of that option? If you ask me, we should open a thread and give suggestions, vote and that would be the best way of implementing important things in item description, and making search for buyers more efficient.
Buyers do not need to know what plugins or 3D software were generally used to create assets for the project, and we’re not asking you to provide that information. You’re only selecting plugins in either of these lists if you’ve included a project file that actually utilizes/requires these plugins. Again, we’re only asking you to provide information that’s valuable to buyers and requiring you to provide information that buyers would absolutely need to know before purchasing.
Take this scenario for example. Lets say I submit a new project that makes use of Element 3D, Optical Flares, and Particular. To make my project available to the largest audience possible, I prerender out the Optical Flares and Particular animations, and create a second prerendered project that uses the rendered videos rather than referencing the two plugins. When I go to submit, my attributes would look like this:
- Element 3D
- Optical Flares
- Element 3D
These attributes basically tell the buyer that my project makes use of all 3 plugins, so if they own the plugins, they have complete control and can customize every aspect of the project. But if they do not own OF and Particlar, they can still use the prerendered version to achieve the desired result. Aside from some basic adjustments, they will not be able to edit the results from the 2 plugins. It also tells them that regardless of the prerenders, Element 3D is required for them to use the project.
What’s nice here is that if/when this gets tied into search, buyers will have the ability to search for projects that they can use, while hiding anything they can’t, creating a better user experience. If I do not have Particular, I really wouldn’t want to see any projects that require me to own Particular. Projects that use particular, but do not require it would also show up in these results since buyers without Particular can still make use of them.
I hope that helps clear things up a bit.
It looks like your file was hard-rejected a few hours ago. You might want to check your email’s spam folder to make sure the notification email didn’t get held up there. If you cannot locate the email and need further clarification, please create a new support ticket. Our support staff will be happy to assist you and provide more information.
Just wanted to quickly clarify Jarel’s last point. Unfortunately our workflow is not setup to accept files over 1GB directly in review. If you feel you need to submit a file that’s larger than 1GB, you’ll need to submit a support ticket requesting permission. In that ticket, please include a link to a preview that we can watch and also include the total file size that you’d like permission to submit.
Please do not upload the item directly into the queue that’s over 1GB unless you’ve already been granted permission through the support process.
We’re happy to announce that we’re now officially supporting Element 3D v2.0 project files. You should all be able to see the new option that has been added to the “Requires” field. So please make sure to select the proper version when submitting any items for version 2.0.
There have been a few items that have been submitted before today’s release for 2.0 that we had to temporarily soft-reject. If you’ve had an item that’s been rejected purely for being a 2.0 project, please feel free to resubmit that project at any time.