Indie Dev
Hello Guest!. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, sell your games, upload content, as well as connect with other members through your own private inbox!
Locking threads
- Thread starter MistyDay
- Start date
- Status
Every user has a different game, a group of different plugins, a different graphics card, etc, when people help the main topic they are helping that person according to their equipment & conditions of their setup, now if it worked for them it's because we knew what the problem is according to their situation, technically this is their question, they own it.
Now the problems are going to occur when someone decides to ask on a week old thread, but they have a different game, a different set of plugins in their plugin list, not only can it be a brand new plugin causing the issue but maybe this specific person edited the plugin in a different way, maybe it's an event causing the exact same issue and not a plugin at all, now we will have two different questions with two different answers in 1 thread that already has an answer provided, they may seem like the exact same issue but they more than likely they won't be the exact same.
Now don't get me wrong all your reasons are valid and you're correct it would be easier for a member to quickly post and declare that it's not working for them but when it comes down to it they're going to have to do the exact same thing as the OP and provide us the same information as the OP, which will be screenshots of their plugin list/event page, the error they receive, it's going to be exactly as if they started a brand new topic but in the exact same thread. Why not go the extra mile and instead of posting in a thread which as been answered just start a new thread because let's face it if the answer does not work for you, either you're doing something wrong or it's something else causing the conflict.
Now I'm going to give you another scenario and this is my main reason for locking all support topics when finally answered. A user decided to revive a question that is 6months old and within that time period, the specific plugins, have been updated, RPG Maker has been updated as well as many other things, now all of a sudden this old topic is literally useless for anyone now and will be the exact reason why the best answer won't work for them. What they need to start a new thread with the updated plugins list and the version of RM they're using.
Basically, in the end if the best answer is not working for you it's because either time has passed and plugins/software have been updated and the problem they are having is, in fact, a brand new issue arising according to a brand new set of circumstances.
I hope this helps you understand aa bit behind the reasoning of locking support topics, now if you have other concerns like maybe us staff members are closing the topics too soon, then please let us know and we can extend the time at which we lock them, we don't want to make any members feel like we are trying to get rid of their topic and move on as quickly as possible. I personally like to wait for the question to have been answered for at least a week and the OP is no longer being active in thier topic, it's kind of my cue to know that they are satisfied and all is well.
Now the problems are going to occur when someone decides to ask on a week old thread, but they have a different game, a different set of plugins in their plugin list, not only can it be a brand new plugin causing the issue but maybe this specific person edited the plugin in a different way, maybe it's an event causing the exact same issue and not a plugin at all, now we will have two different questions with two different answers in 1 thread that already has an answer provided, they may seem like the exact same issue but they more than likely they won't be the exact same.
Now don't get me wrong all your reasons are valid and you're correct it would be easier for a member to quickly post and declare that it's not working for them but when it comes down to it they're going to have to do the exact same thing as the OP and provide us the same information as the OP, which will be screenshots of their plugin list/event page, the error they receive, it's going to be exactly as if they started a brand new topic but in the exact same thread. Why not go the extra mile and instead of posting in a thread which as been answered just start a new thread because let's face it if the answer does not work for you, either you're doing something wrong or it's something else causing the conflict.
Now I'm going to give you another scenario and this is my main reason for locking all support topics when finally answered. A user decided to revive a question that is 6months old and within that time period, the specific plugins, have been updated, RPG Maker has been updated as well as many other things, now all of a sudden this old topic is literally useless for anyone now and will be the exact reason why the best answer won't work for them. What they need to start a new thread with the updated plugins list and the version of RM they're using.
Basically, in the end if the best answer is not working for you it's because either time has passed and plugins/software have been updated and the problem they are having is, in fact, a brand new issue arising according to a brand new set of circumstances.
I hope this helps you understand aa bit behind the reasoning of locking support topics, now if you have other concerns like maybe us staff members are closing the topics too soon, then please let us know and we can extend the time at which we lock them, we don't want to make any members feel like we are trying to get rid of their topic and move on as quickly as possible. I personally like to wait for the question to have been answered for at least a week and the OP is no longer being active in thier topic, it's kind of my cue to know that they are satisfied and all is well.
- Status