Rules RPG MAKER MV SUPPORT RULES

[Archeia]

RPG MAKER MV SUPPORT RULES
(Last Update: November 21st, 2023)​

All General Forum Rules apply. Please review and understand these before making a post in this section.

• If your issue relates directly to a plugin, please use the JavaScript/Plugin Support section or the plugin's dedicated thread if one is available.
• If your issue relates to locating a specific kind of resource or plugin, please use the Resource Requests or JS Plugin Requests sections respectively.
• If your issue relates to the creation or implementation of a resource, please use the Resource Support section.

Resource standards, specifications, and graphical glitches can be discussed in this board, however.

Before Making a Thread​

Do not shy away from asking! But, before opening a new thread, please familiarize yourself with searching the forum.

1. Know which maker and which version of that maker you have. We offer support for multiple products. Make sure you're reading and posting in the right forum.
2. Search the support forum.There's a chance someone has already encountered the same problem. Read through any relevant threads and see how they solved it. If you find the thread has no responses, that the solution was posted a long time ago, and/or it may vary slightly from your issue— recreate the thread.
3. Browse the tutorial forum. The community is fantastic at helping and teaching others. Please take a look and you may find exactly what you’re looking for!

Requirements to Open a New Thread​

1. Create a thread title with a direct and clear topic. Ambiguous titles such as "help me now" or "I don't know what to do” are unhelpful. Use keywords that can describe your support issue. Here are some examples: “My character graphic is cutting off, what am I doing wrong?” and “I'm eventing a title screen and I am stuck on creating [function name here].”
2. Be as descriptive as possible. Explain what you're trying to achieve. Use screenshots and list any plugins that may be interfering. Link any prior threads or tutorials you are referencing. If you are trying to recreate a mechanic from a popular game, do not assume everyone knows what that means.
3. Always post screenshots of your entire event window. This helps tremendously in pinpointing the problem far more quickly than words alone. Please include the entire event command window—including the conditions, the content, and all of its event pages.
4. Be patient and polite. The people who answer threads are donating their time and energy to help you. They may not have answers to every question. Do not complain that you're being looked over. You can bump your topic after 72 hours if it has not been solved.
5. Do not take any responses as a personal attack. Thorough questioning about your debugging and researching process is necessary to save time and figure out your issue. It is not meant to undermine your abilities as a creator or your intellect.

After your Question is Answered​

1. Thank the people who helped you. Let people know when their solutions worked and thank them for their time.
2. Don't edit the thread title or main body of the first post. Keeping the thread intact makes it easier to find through the search function. Although you may not need the thread anymore, someone else could find it useful.
3. Once solved, report your thread to be closed and marked as solved by a moderator.

 

[Archeia]

Before Posting a Solution
​

Read the whole thread. You could spend a little or a lot of time writing up a solution, only to find that someone else posted it first. Or, maybe you'll find that you misunderstood the poster's question. Situations like these can be frustrating. Get as much information as possible before you spend time troubleshooting.

Understand the question. Support questions aren't always clear or simple. A poster may use different terminology or they may have trouble explaining their situation. Take the time to understand what they need. Rephrase their requests or ask them to elaborate.

When Posting a Solution​

Remember, there's no such thing as a stupid question. A lot of the questions you encounter will be easy or have been answered a hundred times. But, to the person posting them they're a big issue and a hurdle they have to overcome. It takes courage to post in a public forum. Keep this in mind and be nice to the poster. It's not their fault that the question has been asked and answered before.

Keep your explanation as simple as possible. It can be challenging to be brief when you have a lot of knowledge and experience. Some of you may be tempted, but too much information could confuse the person and it is not always necessary to solve the issue either. It's better to keep things simple and elaborate when the poster asks for more information.

Add a screenshot, a video, or a demo to illustrate your solution. Visuals can help a person learn faster. Posting a screenshot of how an event should look and highlighting important points is a good tool. The poster can try to replicate it in their own project. Promote self-learning. You're welcome (and encouraged!) to post a demo for the poster to dissect but that should not be an invitation to just make the event for them.

Link to a tutorial, plugin, or another support thread if needed. Avoid quoting threads or posting entire plugins. A link would be much more helpful and easier on the eyes.

After Posting a Solution​

Answer any follow-up questions. Try to keep track of the thread and see if the poster has any other questions.

Enjoy your thanks. Really, you deserve them!