Paid content - var.depend

trety

Well-known member
Messages
130
Reactions
1,120
Points
93
After seeing another 'paid look', with the only thing which I was actually interested were clothes... I came up with some wild idea.
It would help a lot if posting 'paid' resources would REQUIRE '.var.depend.txt' file attached to the page, like not allowing to post it at all in paid scenes\looks section without these.
It would be super cool if Hub could read them too [right now it reads deps from the vars itself, skipping txt files completely].

Some people might went rage right now. But let me explain it.

1. Creators wouldn't need to spam all the deps in the resource description, it would be all in dependieces tab with links to necessary packages. So it would be faster for them to start a page. I know people most likely just copy-paste them from theirs patreon pages, but still...
2. Users could easily see if the var they're interested is packed properly, if there isn't like 100+ deps for a look ...
3. It would reduce A LOT of breaking NC licenses. Right now a person must actually buy an 'item' and then report it on hub.

So, how do U think? Requiring attached depend file, for paid content, is good or bad idea?
 
I think this (or something similar) has been suggested few times.

Problem is, this is just plain .txt file that everyone can edit before uploading (by either removing NC refs or reducing dependencies).
Even now NC content is used, creators can't properly credit others or let alone create optimized package without dupes.
Generally speaking (when compared to free content) paid content is hot mess (not moderated the same way).

I guess it would be nice to check dependencies while "window shopping", but if depend file was manipulated than what is the point?
Some creators are editing free packages by removing dependencies inside meta, same thing...

How about different approach:
-request creators to upload a copy of paid package on separate channel and only mods can see it (within resource page)
-read all info from that package (vs depend.txt)

This way it would be:
1) easier to moderate (mods can inspect package)
2) actual dependencies, less bs (aside from meta editing)
3) less meaningless update bumps such as: "updated", "cleanup" or "fixed XYZ" (if new package version is required)

Or maybe make it optional to upload package and use less reliable depend file as alternative.
But include verified/featured/hub-hosted like approach for uploaded paid content.
 
Back
Top Bottom