Search the Community
Showing results for tags 'Quality Guide'.
Found 1 result
-
It's been obvious that these days, users asking support for the same question a million times, and complaining they are being ignored. "No, you are not ignored", it's just that your topic literally doesn't make any sense, so that anyone could ever try to help you sort the issue. Below is a basic guideline structuring your support thread so that it's informative, and helpful to the users who are wishing to help you sort things out! 1. Support Topic Title The topic title is a very important part of your support thread. It filters out users who can help you and who can't. A topic must be short and informative. You must be able to convey to the viewers about the help you really need support for. It must contain a prefix or suffix that states the type of media-server it runs with - AS2 or AS3, Server source or Emulator it's powered by - Kitsune or Luna or Nitro or RBSE or Times or Sweater or etc., It must convey the very exact problem with your issue. Below is an example. Take for example, you need support with your server (say for example Kitsune) being crashed when you try to buy an item, and suppose for example you use AS2 Media-server (Logically taking it that you use kitsune as2). Below is an example of such topic title The above title is what users who support you actually need, but what most users post is The above title literally explains nothing. And users will be annoyed to even look at your spport topic to get you any help. Also, it's very good if you post a small crunchy part of the error you get in the title, for example 2. Support Topic Body Here's what the crutial part is. You've set up the title so apt that users have an idea on what to help you with. So all you have to do in the body part is, give more details of your error. Usually for server sided support it's good to embeded your console error, error lines in a spoiler. Alternatively pasting a good quality (visible) picture or screenshot of your error is worth a lot. Below is an example for the same scenario with the title. There is literally no more explanation needed regarding that, but there's yet one more thing to do. It's good if you post few lines before and after that line where the error occurs. Like Now, you might follow a person who's trying to help you with it. Nothing is more necessary than the above for anyone knowledged about it to help you with. Thanks! I request this topic to be locked!
