Hmmm you mean like having a comment section on people who have say "a viewable draft" so people can discuss, theory craft etc? If so I believe that would be a great idea.
JHOIJHOI IS THE BESTEST PERSON IN THE WHOLE WORLD AND THIS SIG IS AMAZING TY <3
In order to combat the theme of "idea theft", make it so that drafts have a "date of draft creation".
You would, however, still have to take risks with people who would go so far as to create a bunch of blank drafts beforehand just for the sake of saying that their idea came first.
This is unlikely, but I'm just warning you that it may be a possible downside of this system.
You would, however, still have to take risks with people who would go so far as to create a bunch of blank drafts beforehand just for the sake of saying that their idea came first.
This is unlikely, but I'm just warning you that it may be a possible downside of this system.
What if we added the build reset feature? Wouldn't that essentially be the same thing. You publish your build while you're working, get feedback and ignore your score (or disable it if we add that option) and then when you're done you reset it.
The thing is we don't want to make it overcomplicated. Having the unpublished drafts visible only to the author is what 99% of users will want and expect. Trying to add some in-between state is just kind of awkward and confusing?
The thing is we don't want to make it overcomplicated. Having the unpublished drafts visible only to the author is what 99% of users will want and expect. Trying to add some in-between state is just kind of awkward and confusing?
Tbh I think that the idea of a visible draft is meant to encourage feedback. If that's the case, I suggest that one could just use the option to disable voting completely on the guide (when said option comes out) and enable voting whenever wanted. Also, we've got the build and guide discussion thread for that purpose as well.
I just don't feel like enough people will do that to warrant making the system even more complicated than it already is. If you want feedback, just publish your guide. Even without a build reset, you can always archive/copy/publish a new version.
You need to log in before commenting.
The only problems I forsee (besides actually making the code and all... ) is that there could be debate over idea theft if people see ideas in the "in progress" phase and it would be hard to tell who came first. I don't know. I still think it would be worthwhile and would help us make our builds great before we publish them.
Thank you for reading!