Encourage posters to state 'why/how' their problem was solved.

[Feldschlacht IV]

This mainly applies to the Script/Engine Help subforums and similar places.

Usually, when I'm scrolling old topics for a solution, problem I'm encountering I get excited when I see an old topic of someone having the same issue, and then my heart sinks when the next to last post is "NVM GUYZ I FIGURED IT OUT" with no elaboration and the last post is the topic being locked.

I'm not saying it should be a rule, but a blurb encouraging posts to elaborate on how they solved their issue if they figured it out themselves would be a big help for very little effort.

 

[Napoleon]

One of the reasons why I proprosed the "Accepted/Assisted answer buttons". You can then also add a post at the end with your own solution and accept that one as THE answer.

 

[DoubleX]

This mainly applies to the Script/Engine Help subforums and similar places.

Usually, when I'm scrolling old topics for a solution, problem I'm encountering I get excited when I see an old topic of someone having the same issue, and then my heart sinks when the next to last post is "NVM GUYZ I FIGURED IT OUT" with no elaboration and the last post is the topic being locked.

I'm not saying it should be a rule, but a blurb encouraging posts to elaborate on how they solved their issue if they figured it out themselves would be a big help for very little effort.

In general I agree with what you said, but in some cases I can understand why they didn't explain how they solve their issues. There are at least 2 such cases I've seen before:

(Disclaimer: I've no intention to insult anyone)

1. They solved their issues, but without even knowing what they've actually done. Maybe they were just brainlessly messing with the scripts without knowing what they're doing and then they just "solved" the issues miraculously

2. They know what the root causes are and what they're doing to fix the issues, but they don't want to voice them out as those root causes are ridiculously dumb nub script user mistakes(I've helped 1 case which is exactly this)

Of course they're probably just a minority though, so if those subforums do implement your suggestions, maybe more of them will actually at least briefly state what the causes of their issues are, if no solutions are followed

 

[Shaz]

One of the reasons why I proprosed the "Accepted/Assisted answer buttons". You can then also add a post at the end with your own solution and accept that one as THE answer.

If they post saying NVM GUYZ I FIGURED IT OUT and we give them an accept/answered button, it doesn't mean they're not STILL going to just post NVM GUYZ I FIGURED IT OUT. Having a button so they can close the topic themselves is not going to encourage them to be any more elaborate with the solution.

 

[Feldschlacht IV]

In general I agree with what you said, but in some cases I can understand why they didn't explain how they solve their issues. There are at least 2 such cases I've seen before:

(Disclaimer: I've no intention to insult anyone)

1. They solved their issues, but without even knowing what they've actually done. Maybe they were just brainlessly messing with the scripts without knowing what they're doing and then they just "solved" the issues miraculously

2. They know what the root causes are and what they're doing to fix the issues, but they don't want to voice them out as those root causes are ridiculously dumb nub script user mistakes(I've helped 1 case which is exactly this)

Of course they're probably just a minority though, so if those subforums do implement your suggestions, maybe more of them will actually at least briefly state what the causes of their issues are, if no solutions are followed

Those people might be a minority and that may be the case. However I think it's just a culture thing; if people are aware that it might be an improvement of etiquette and a service to the community to explain/elaborate in a quick sentence or two how they solved their problem, it would slowly change to reflect that.

Which is why I wouldn't want to make it a hard rule or 'enforce' people to do that, that's not fair. However I do think it could benefit in an 'soft', but impactful and meaningful way to have a blurb somewhere saying 'hey, it would be rad to state how your issue was solved'.

 

[Napoleon]

If they post saying NVM GUYZ I FIGURED IT OUT and we give them an accept/answered button, it doesn't mean they're not STILL going to just post NVM GUYZ I FIGURED IT OUT. Having a button so they can close the topic themselves is not going to encourage them to be any more elaborate with the solution.

It might be if the total amount of accepted answers is recorded somewhere just like your reputation and post count. Some people like collecting useless numbers .

But indeed the close button could be a problem as they could simply close it as soon as they figure it out without any post made at all.

But anyway, I find it rude if people close their post with "NVM GUYZ I FIGURED IT OUT" without posting a solution anyway. They ask for help but don't even bother posting their solution and so personally I don't feel like helping them again.

 

[Shaz]

Yeah, I like to know what they did to get things working too (sometimes when they DO post, their solution is not a good one, so it gives a further opportunity to help).

 

[Feldschlacht IV]

Well, this seems to be a well received idea, I suppose. Is this something the administration would consider doing?

 

[Nathanial]

http://forums.rpgmakerweb.com/index.php?/topic/31428-mark-as-solved/


This will help/has been requested in the past.


But yes, some proper etiquette would be nice to stop people from just drive by "I already figured it out" with no explanation.

 

[Feldschlacht IV]

Awesome! As for encouraging people to post why, why not just make it an Announcement blurb?

 

[Shaz]

You mean asking them to be more explanatory when they solve their own problems, just like we ask people now to post in the right forum and not double-post or prematurely bump? Yeah, that'd work