• Hi Guest!

    This is a notice regarding recent upgrades to the Hub. Over the last month, we have added several new features to improve your experience.
    You can check out the details in our official announcement!

Search results for query: *

  1. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Can you provide more information? If the assets are "Questionable", "PC", or "MISSING" then the author cannot give permission to release in the free category and must update their license.
  2. AshAuryn

    Feedback on proposed Paid content submission procedures.

    A couple additional bugs were discovered thanks to @Farger . A fix has already been developed and hopefully will be pushed live within the next 24 hours. The bug prevents updates to free resources without a version change, and it prevents editing of free resources if your resource is hosted...
  3. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Lets get back on topic. Thank you. Updates and fixes to Var Health Check are now live. Please post here if you run into any issues or have questions.
  4. AshAuryn

    Feedback on proposed Paid content submission procedures.

    That is the stance we are taking as well.
  5. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Bugs that will be fixed in next update: 1. Attempting to post an update without a version change for a paid resource is giving the "Please complete all required fields" notification and not allowing the form to be completed (fix completed) 2. Dependency tab initially shows "Not on hub" but gets...
  6. AshAuryn

    Feedback on proposed Paid content submission procedures.

    So, we're live. A few bugs I've noticed right off the bat, which we will fix in the coming day. 1. Auto-generated credits are including sub-dependencies when they shouldn't. EDIT: not a bug / not repeatable 2. The dependencies tab for paid resources isn't showing download links, and instead...
  7. AshAuryn

    Feedback on proposed Paid content submission procedures.

    The feature is now live on the Hub.
  8. AshAuryn

    Feedback on proposed Paid content submission procedures.

    The notification system has not been implemented yet. Once development begins I will have more answers. But I can tell you that after the user feedback we received regarding the dependency notifications, we will make the new Health Check notifications as non-intrusive as possible. Most...
  9. AshAuryn

    Feedback on proposed Paid content submission procedures.

    In response to user feedback, we will be modifying the checkbox that insists you upload a new copy of your .var anytime you make any changes. The new wording is here:
  10. AshAuryn

    Feedback on proposed Paid content submission procedures.

    One of the reasons we will not be hosting paid content now or in the future is due to liability. The Hub is not willing to be responsible for hosting commercial content due to the risks. Better to let the experts, such as Patreon, deal with the money side of things. You can rest assured we...
  11. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Here are some screenshots from the beta in a development environment which may help to clarify some things. This is the paid resource form. "Permission" in this context means either the licenses you are using give explicit consent (such as FC or CC BY) or the creator has given you explicit...
  12. AshAuryn

    Feedback on proposed Paid content submission procedures.

    The var will be required. As for the trust, there are legal protections for what you're talking about. We never could, nor would, risk legal complications by mishandling your intellectual property. Not even the moderators or admins have access to the file. It is deleted before the form is...
  13. AshAuryn

    Feedback on proposed Paid content submission procedures.

    @WolfmanVR Everlaster answered this perfectly. Thanks @everlaster ! 💕
  14. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Default VaM content is officially licensed from Daz, and as part of this standard commercial license from Daz, we have a responsibility to make sure no Daz content is distributed on our platform. If you are aware of specific Daz content being shared, please report it to our team. The purpose...
  15. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Good news. We did figure out how to display the dependencies tab on the Hub website. I am not sure how it will present in-game though.
  16. AshAuryn

    Feedback on proposed Paid content submission procedures.

    I would like to answer this officially and in more detail within the coming days. We are currently discussing this policy and will present an illustrated explanation that should help users to understand licenses, dependencies, and tiers and how they interact.
  17. AshAuryn

    Feedback on proposed Paid content submission procedures.

    We'll get you a clarified answer to this in the coming days. Rest assured, we don't want to disrupt or cause inconvenience to our valued creators. The new scan after all is aimed at protecting your content and safeguarding the effort you put into it. It shouldn't become a burden, otherwise it...
  18. AshAuryn

    Feedback on proposed Paid content submission procedures.

    1. You create a resource. For that resource, let's say you have something.1.var and something_demo.1.var on your Patreon. You must upload both files and have them scanned. 2. You update your Patreon post but do not change the files or create new versions. You do not need to update your Hub...
  19. AshAuryn

    Feedback on proposed Paid content submission procedures.

    That is correct.
  20. AshAuryn

    Feedback on proposed Paid content submission procedures.

    Retaining the file names is no problem, however I'm not sure I understand what you mean by "indexed and properly referenced". Since this is Paid Content we're talking about, it would be illegal to use these vars as dependencies in other work without the creator's permission. So, for example...
Back
Top Bottom