Free and Paid Products - new Rule Request for Improve

[@alisha]

I want to ask about limiting or more advance logic for this new rule:
BosslandGmbH:Getting Products Accepted to the Buddy Store - The Buddy Wiki
"No free editions of paid products are allowed."



As if it stay as it is, it in the end will come with less number of Free projects available to HB Community.

For my case i create Free and Paid projects and they can have similar Categories, because my interest of WoW.

Free version which wasn't took to many of my time i want to provide to Community for free. As my contribution to the community.

But paid which cause all my day work time every day - i can't provide as free, because if i do so, i won't have money to live (for me HB now is main work and income for my family), so i have to just leave HB and find another work in that case.



Also, i understand reason for this rule and agree with it, but it should be reasonable and adequate and not just "NO".

First Example:
Product "A [Free Edition]" have goal "Walk" and functionality go right only <-- which is limitation for same goal - Walk
Product "A [Paid Edition]" have goal "Walk" and functionality go right and left <---which is full functionality for goal Walk

Yes its bad and such products shouldn't exists, cause free version player cant fully walk.

Second Example: (This example for KittyDru)
Product "B [Free Edition]" is Druid Feral CR and have goal "Fight" <-- which have Combat Rotation only works fully - you can kill enemies.
Product "B [Paid Edition]" is Druid Feral CR and have goals "Fight,Heal,Survive,Movement etc"<-- which have Combat Rotation but maybe more complicated - you can kill enemies, also it for example have more additional functionality - for healling for example, or auto movement, use additional skills etc.


So users that have Free version can fully use it without limitation - it do it goal - kill enemies.
And Paid Edition for this case is different project but yes in same category - Feral Druid.
So both projects are good to publish.


Third Example: (This example for RaiderHelper)
Product "C [Free Edition]" have goal "Invites" and functionality for Invites only <-- which works fully without any restictions
Product "C [Paid Edition]" have goal "Invites,Timers etc" and functionality for Invites + Timers + BodyGuard etc . Invites module is same without more functions for it (so its not limiting free version)

So this products are different, paid include free version but provide different functionality, which is not limiting free version.
Users that have Free version can fully use it without limitation - it do it goal - invites.
So both projects are good to publish.

Existing Problem:

For now the only reason why those "B" and "C" products can be consider as "same" is name with Edition addition - so we should rename Free version to other name - so users wont associate them as Edition of Paid version.


Also for me, as for many developers is easy to support one project by code (in my case RaiderHelper) - have one code, But have like if statements in it - so for users it will be for end view different products.
Than have 2 projects (by code) instead and support them both (in this case if i found bug in same module i need to fix it in 2 separate places).
So, having one code, we can provide improvements to both end projects with short time and can support as free as paid projects.


My Request:

Totaling, i want to request to edit this rule to more individual (reasonable and adequate) reasons for allow or not such products, depending on what they do:

• If Developer have Free product with goal of project "Walk" and it can walk only left. But he also have Paid project with same goal walk but can walk both left and right - it shouldn't be OK - Disallowed
• If free product have same module as Paid product [Paid product can have other separate modules that do not influence on first one], and Free product goal this module only, so free product are not limited in its goal (you do not describe it as more functionality as it is). But Paid product have also other modules (so basically it inludes free module as others for more cosy use of users, to do not force them have 2 interface "to check options in GUI") - it should be OK - Allowed
• If Developer have Products with same Category, for example: Druid Feral CR. Paid and Free product. Free product goal - Kill enemies, works fully as it intended. And Paid Product is different product (have other logic or other additional functions etc - have other goal) - it should be OK - Allowed

Also to exclude products influences all Developers Products should have Different not Corresponding names without Edition mentioning So user wont be force to buy something.

For example for my case, to follow new rules i have to rename products to:

• CR:
  • Free Product: "Alisha's Feral"
  • Paid Product: "KittyDru"
• Plugin:
  • Free Product: "Invite Helper"
  • Paid Product: "Raider Helper"

Sorry for my bad English , i hope its will be understandable what i mean. I just want to Bossland to allow us provide free content for HB if we have time, not limiting us if its in same section. But also to exclude Free Products that are reasonable and do not provide full functionality for their goal. Also to avoid potential advertisement as Bossland want - all products will have to have different names.

 

[patto92]

I agree with Alisha on this. I'm sure when approving a new product you can tell if the product is blatant advertising or gimping the user. Things like her free version of her combat routines are fully functional for raiding. A lot of people only need that function. Why should they not be allowed to have that for free and if they choose, grab her full version with afk support etc. It doesn't hurt the end user at all that way, it only helps them!