Script Submission Rules Options

[kaz]

Guide to Posting in the Script Submissions

General Rules

The same general rules apply to this forum. No spamming, trolling, flaming, or double posting. If you are unfamiliar with the forum rules, please take a moment to review them.

Bumping

Please wait 36 hours before bumping a topic. Only bump support topics, and please do not bump your own scrip submission if you feel it's not getting enough attention.

If you want to add more to your post, please use the edit button. It wont bite.

Unsolicited Spam

Do not spam other topics with requests or questions that are unrelated. Also, do not PM scripters asking for scripts or support. If a scripter wants to help, they will be looking in the request/support threads.

Search, Search, Search

Try using the search tool before asking a question. Also, please read the entire script topic before requesting support. Odds are that your question has been asked, and maybe even answered before.
A useful tip; most scripters will leave detailed explanations of how how how to sue their scripts at the start of the code. If you're struggling to understand their explanation, try looking at the comments left at the start of their code.

Illegal Activity and Plagiarism

Copyright infringement (Posting or distributing a script without the permission of the author, or editing a script without giving credit) and plagiarism (posting a script that does not belong to you, and claiming it as your own) are frowned upon and may result in a ban.

And as always, linking to warez such as cracked versions of RPG Maker XP or VX will result in an automatic warn, at the very least.

Topic-Specific Rules and Guidelines

[Show/Hide] Requesting Scripts

0. This should go without saying, but please always search for a script already exists that already fulfils your requirements. You're a lot more likely to get help if you're simply asking to edit an already existing script than if you were to ask for a completely new one.
We do provide a RGSS Scripting List that contains every script submission, so if you need help finding script, that's a fantastic place to start.

1. Be clear and concise. Please refrain from using chat-speak in your request. Scripters will be more likely to take requests from people who sound "serious," because a serious developer is more likely to finish the game they're requesting for.

2. Include all the information that the scripter might need to create the script. How it will work, what it should look like. Include images and mock-ups if at all possible (preferably to scale). If you're referring to a system used in a commercial game, please include screenshots and details about how the system works. Not every scripter has played every game made. Even if they have, they probably wont remember every detail about it.

3. If someone tries to help you, be polite and say thank you, even if their help doesn't work for you. If you're being rude to the people who are trying to help, others wont see any reason to try and help.

4. If you're requesting a battle system that isn't already created, or isn't an easy modification of an already existing CBS, be prepared to be disappointed. Battle systems are the most complicated scripts to make, and you're unlikely to find someone who is willing to donate countless hours of their life out of want. But that doesn't mean you cant try, you might get lucky. You may be more likely to find a scripter for this task if you offer a trade of services. But don't hinge your game on getting that custom battle system you've spent weeks designing.

[Show/Hide] Asking for Support

When asking for support with an existing script(s), include all relevant information. If you received an error message, post the exact text of the error and the line of code it appeared on. If it occurred in an event, please include a screenshot of the event code or a demo of the problem. If using other scripts, specify which ones and either link them in the topic, or (best of all) include a demo with all the scripts that were being used. If you're not posting a demo, please include any resources (graphics, sounds, etc.) that the script(s) might require. Make it as easy as possible for the scripter to see what's going wrong and you're more likely to get help.

Be as clear and concise as possible. Avoid chat-speak and grammar and spelling errors. Not every forum member speaks English as a first language, and no one speaks chat-speak as a first language. The first step to getting reliable help is by making it as easy as possible for someone else to help you.

[Show/Hide] Posting a Script

When posting a script that you did not write, make sure the author is okay with you doing so. Also, include the author's name somewhere early in your post. It is very important to direct credit (or blame) for the script in the correct direction to avoid the appearance of plagiarism.

When posting a script, please follow the guidelines stickied in this forum. It is encouraged that when posting moderately complicated scripts to include a demo illustrating how the script may be set up. We also encourage you to post screenshots when possible, and detailed instructions.

If you're not going to support a script or have stopped actively developing it (fixing bugs, etc), we'd appreciate it if you said so in your first post.

When posting a script, please use the following template, or something similar:


<Title>
<Version>
<Author(s)>

Information:

<Information about the script. what it does/does not do.>

Screenshots:

For screenshots, please use minimize or spoiler tags!
[ minimize ] image url [ / minimize ]
[ spoiler ] image url [ / spoiler ]

Instructions:

<Detailed instructions informing how to set up and use the script.>

Demo Link:

<http://yourdemolink> We encourage the use of demos when providing moderately complex scripts, especially those requiring database or graphical setup. We provide script/script-demo hosting here.

Compatibility:

<Any compatibility problems you know of.>

Author's Notes:

<Anything you want to say about the script or about changes from version to version.>

Concerning Necroposting

The rules of necroposting have always been obvious, but in the scripting forums (RGSS/RGSS2), those rules are different.

If a script topic is 3 or more months old, and is replied to with something like

"Help! I'm getting E error on line 123! what am I doing wrong?" or "the download link is dead, does anyone have a copy of this?" These are not considered to be necroposting. However, irrelevant posts - such as "nice script." or "thanks" - that are in topics 3 or more months old (that isnt a bump by the topic poster) are considering necroposting. This also applies to the script support and script request threads.

If we (moderators of RGSS/RGSS2 sub-forums) get a necropost report and it isn't a necropost by these standards, we will reply to you with a link to this topic.


When reporting a topic

You should only need to report a topic when it does not follow the rules stated above. Reporting a topic that conforms to rules may result in a warning.

When you report a topic, be sure to include necessary information. "Wrong section" isn't very helpful, and wastes time; instead, use something along the lines of: "belongs in 'RGSS script support'" or "this needs to be moved to 'RMVX.'"