Sell multiple variations/versions of a resource at once

[1337]

Hello,

I had an idea for the resources section. Essentially, if this were to be implemented, it'd allow for resource authors to sell multiple versions or variations of their resource at once. For example, let's say there's a lite and a "full" version of a resources that cost 2 different amounts, instead of manually managing and upgrading licenses and payments, this can be automated with the client choosing which version they would like to buy/download. Another potential application would be with resources (such as scripts, pterodactyl eggs, etc) that have different versions i,e: nginx or apache, nodejs v8 or v10, java 8 or 9, full or partial, etc.

All opinions/thoughts/comments/improvements are welcomed.

 

[1337]

While I think it is a fair idea for different versions to be provided I don't think that they should be able to charge more or less depending on that and certainly they shouldn't have users pay for separate versions as that would just be stupid, you pay for a resource for continuous updates for it, not simply for a one and done deal.

I'm not saying it's a one and done, I mean for different editions that are all still supported and maintained i,e:
version with node8 support
version with node10 support
lite version
premium version

 

[1337]

No still, I think versions should be listed under the same product, not separately.

That's my point haha, that's what I'm suggesting. Multiple versions/editions of the same product being available for sale/download.

 

[Justis]

If you have minor changes that simply adjust the compatible server versions, then you can include them all within your resource download.

If you have major changes that result in different prices then what you essentially have is two separate resources.
Just create a "lite" resource and a "full" resource, if that's what you're looking for. You can easily link between them in your description page.
Confusing what is essentially two different resources as a single resource and trying to manage a tree of different versions within one little resource page isn't very intuitive nor organized. Keep that for your GitHub pages. Our resource system needs to be buyer friendly too.

 

[MarkElf]

Just sticking another example in, similar to lite and full, you can pay X for the main portion and on the same resource page you can pay an additional amount via some button to unlock additional features. Something like token enchants, which has a million freaking resource pages on spigot for each enchantment for those who don't know, comes to mind. I like the idea and wouldn't mind it added but I do agree, for something of a smaller scale (not a million different enchantment resources) just make an additional resource or include everything in the single resource page/download.

 

[Mick]

If you have minor changes that simply adjust the compatible server versions, then you can include them all within your resource download.

If you have major changes that result in different prices then what you essentially have is two separate resources.
Just create a "lite" resource and a "full" resource, if that's what you're looking for. You can easily link between them in your description page.
Confusing what is essentially two different resources as a single resource and trying to manage a tree of different versions within one little resource page isn't very intuitive nor organized. Keep that for your GitHub pages. Our resource system needs to be buyer friendly too.

Denied, thanks for the suggestion.