- 11,444
- 1,997
On the past Sora vs Goku thread (which Cross closed out of exasperation) and the Wolfgang Schrieber vs Flash thread, it became apparent to me that voters rarely read through both profiles before commenting on a VS Thread. This is not only tiresome (as the supporters of the other side have to explain why X wouldn't work for Y reasons) but it makes many debates turn circular and boring really fast.
As a result, I'd like to propose that a rule be added to alleviate this issue somewhat:
"Please remember to thoroughly read the basic statistics and powers of both profiles before posting on a versus thread. This prevents threads from becoming needlessly long and saves users the trouble of having to completely explain each character's powers and abilities for each and every thread."
Naturally, this would be virtually impossible to enforce, but it would at least encourage users to do so rather than just post biased opinions without listening to the other side.
In addition, it's come to my attention that many new users don't know how to use the Source Editor and thus stick with the Visual Editor despite our efforts to dissuade them. Thus I was thinking that it might be a good idea to write a page that provides easy-to-understand examples of each type of formatting and how to apply them in order to make the Source Editor more approachable.
Thoughts?
As a result, I'd like to propose that a rule be added to alleviate this issue somewhat:
"Please remember to thoroughly read the basic statistics and powers of both profiles before posting on a versus thread. This prevents threads from becoming needlessly long and saves users the trouble of having to completely explain each character's powers and abilities for each and every thread."
Naturally, this would be virtually impossible to enforce, but it would at least encourage users to do so rather than just post biased opinions without listening to the other side.
In addition, it's come to my attention that many new users don't know how to use the Source Editor and thus stick with the Visual Editor despite our efforts to dissuade them. Thus I was thinking that it might be a good idea to write a page that provides easy-to-understand examples of each type of formatting and how to apply them in order to make the Source Editor more approachable.
Thoughts?
