Status
Not open for further replies.

Archeia

Level 99 Demi-fiend
Staff member
Developer
Joined
Mar 1, 2012
Messages
15,324
Reaction score
15,802
First Language
Filipino
Primarily Uses
RMMZ
RPG MAKER MV SUPPORT RULES
(Last Update: June 6, 2020)
1) Plugin-related issues.
Please use the Plugin Support forum or the plugin's thread.

2) Resource requests.
Please use the Resource Requests forum. However, Resource Standards/Specifics can be discussed in this board.


Before Making a Thread

Before opening a new thread in this forum, please familiarise yourself with these rules:

1) Know which maker and version 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's already encountered the same problem as you. Read through their thread and see how they solved it.


3) Browse the tutorial forum.


Requirements to Open a New Thread

1) Identify which maker you're using.
You may add it to your title (ex. [RMMV] Thread Title) or in a topic tag.


2) Use a pertinent title.
Please refrain from ambiguous titles such as "help me now" or "I don't know what to do". Include information and keywords that can describe your thread better.

3) Be as descriptive as possible.
Briefly explain what you're trying to achieve. Please try to use proper spelling and grammar, and post in English only. You may also wish to post screenshots as well as a list of scripts you're currently using.
Large and/or multiple images and lists should be posted in a spoiler. Use the following code for spoilers:

Please note that each product has its own tutorial sub-forum and that there's a non-specific tutorial forum located
here.


Image or Post Goes here!
4) Always post screenshots of your entire event window.
Instead of describing us what you were trying to do, and what has gone wrong, show us what you've done instead. This helps us tremendously in pin-pointing the problem and helping you solve it. Please include the entire event command window, including the conditions, the content and all of its event pages.

5) Be patient and polite.
Remember that the people who answer threads aren't paid to do so. They're donating their time and energy to help you. They may not have answers to every question, either. Don't bump your thread or complain that you're being looked over. You can only update your topic until 72 hours have passed.

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.


* Exceptions to this rule will be accepted on a per thread basis. Contact Archeia for any other inquiries.
 
Last edited:

Archeia

Level 99 Demi-fiend
Staff member
Developer
Joined
Mar 1, 2012
Messages
15,324
Reaction score
15,802
First Language
Filipino
Primarily Uses
RMMZ
Before posting a solution:

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

2) 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:

1) Remember, there's no such thing as a stupid question.
A lot of the questions you may encounter will be easy. Maybe they'll even be things that you have answered a hundred times before. To the person posting, however, 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.

2) Keep your explanation as simple as possible.
It can be challenging to keep things brief when you have a lot of knowledge and experience in a subject. Some of you might be tempted to include a lot of extra information, but you need to be careful. Too much information could confuse the person. It's better to keep things brief and elaborate things when the poster asks for more information.

3) Add a screenshot, a video or a demo to illustrate your solution.
Seeing how something is done 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. One thing that should be noted is that we encourage and promote self-learning. So, while you're welcome (and encouraged!) to post a demo for the poster to dissect, it's not an invitation to just make the event for them.

4) Link to a tutorial, script or another support thread if needed.
Please try to avoid quoting threads as well as posting entire scripts and tutorials in a support thread. Just a link would be much more helpful and easier on the eyes.

After posting a solution:

1) Answer any follow-up questions.
Try to keep track of the threads you've posted in and see if the poster has any other questions.

2) Enjoy your thanks.
Really, you deserve them! 
smile.png
 
Status
Not open for further replies.

Latest Threads

Latest Posts

Latest Profile Posts

Time for my daily walk/jog ''Literally starts raining while I open the door''
I just discovered there's a giant jellyfish in the Ace RTP. My day is made.
I'm pretty sure I submitted a username change like 4 months ago.
...
No offense but uh, still waiting for my name to be updated :/
Boss #1 - All 3 phases.
w5fSXys.gif

Forum statistics

Threads
112,393
Messages
1,068,005
Members
146,045
Latest member
Paul_code
Top