Synchronised "works with" section

[Bad Cop]

Would be nice if the Works With had some synchronisation.

For example, let's take Mevent's helpful supply. He can indicate that the plugin is compatible with the features offered by Loottable GUI plugin

I would like to see that reflected on the Loottable plugin page. If i'm buying it, it's nice to know which other plugins i could get which have been optimized to work alongside it.

 

[Death]

It's a great concept, but in reality, it'll become a huge moderation issue. We'd need to make sure these files actually work with the other, and even then, authors can easily add support for it simply to be included in the other file's dependency list. I don't think creators would be thrilled about the idea personally.

[Khan]

@Death
Then don't make it a moderation issue for codefling. 

Make it so that a dev can list works with x plugin. 
Then when that occurs that plugins dev can receive a notification indicating that a dev has marked his as works with & can manually decide to opt in to agree to also maintain 3rd party plugin support with that plugin.

( Basically what we already have now on codefling ) But with the addition / addon--being where the dev is notified of it & can manually choose to opt in for mutual agreed 3rd party support between the 2 plugins.

( And if both have it listed, then a green verified check box will appear next to it on the plugins product page as "verified" to work with each other )
( And a yellow to indicate that support was added but may not be guaranteed--for those who don't both opt in/one sided )

Edited March 16 by Khan

[Khan]

You could also further push this to be solely up to the devs to support / handle by updating the codefling policy to reflect that.
So that at the time a purchase is made if both devs have opted in with a green verified works with then both devs will be required to support it.
But if only a yellow check box is next to a works with plugin listed then support is not guaranteed upon purchase.

This will keep your 6month warranty in-tact & push the responsibility to devs who have opted in.

Also, you can make this a 6-month renew option for devs. So there only obligated to support it for 6-months at a time ( or more ) if you include 1 year option.

Edited March 16 by Khan

[Khan]

You should do a poll in discord and get developer feedback.

 

 Poll: Plugin Compatibility System on Codefling

Description:
Should Codefling introduce a "Works With" verification system that allows plugin developers to opt-in for compatibility with other plugins?

 Green Verified – Both devs agree to maintain compatibility.
 Yellow Unverified – One dev has added support, but the other hasn't opted in.
 Renewable Commitment – Devs can choose 6-month or 1-year support periods.
Would you support this system?

 Yes – Helps users find compatible plugins easily!
 No – Too much overhead for devs.
⚖ Maybe – Needs refinement before implementation.

Vote below! ⬇

 

[Death]

Not a terrible idea, but I argue that communicating with said creator would be just as effective and doesn't require an additional workflow for creators and development overhead for us to achieve a similar outcome.

[Khan]

I would argue, that it would give peace of mind to customers & would justify the slight inconvenience to the dev. There could also be auto reject options ( on by default ), etc.

But again, just an idea & requires more feedback.

A simple poll on discord would provide you with an idea if it'd be something devs would even want at the moment.

[Khan]

At the moment the main issue is that customers sometimes buy a plugin expecting the works with section to actually work.

But even if you added a yellow notification to indicate that this may not be guaranteed at least then the customer wouldn't be miss-lead in case in that moment support was broken for that listed plugin.

Currently the site having a works with section in general is miss-leading for plugins that haven't maintained support. 

[Khan]

We have verifications for frameworks but not for plugins? Seems like a wasted opportunity. 

[Death]

That's completely unnecessary. If it weren't supported, it wouldn't be listed there. If it is, it should be removed. It would completely defeat the point of that.