Code Requests & Code Support Rules

[Trublu]

Please read all posts carefully before creating your thread in this board. Threads that do not adhere to these guidelines will be locked.

Requesting a Code

Code Support

Filling Requests or Answering Questions (Code Helpers)

---

Credit to Peter for the source (see here).

[Trublu]

Code Requests
Before you request a code to be made, please read this post fully.

New Code Request Limit Per Week: 3

• 1. Check the database first
  Before you request a code, check the Code Index and list of tables. The Code Database is divided into 14 categories and 3 sub-categories in order to make searching the database easier. You may also find it helpful to search the page for keywords in order to find the code that you are looking for: if you are on a PC, press "ctrl + f" to search the page; if you are on a Mac, press "Apple + f".
  
  
• 2. Check the Code Support FAQ and Requests that will be rejected threads before requesting a code.
  The FAQ describes how to create many of the most sought after effects. If your request is listed in the "Requests that Will Be Rejected" thread, we unfortunately cannot fill it.
  
  
• 3. Check the current open request threads
  If you find that the code you want is not in the code database, you now need to look through the current open request threads, it's quite possible that another member has requested the same code as you.
  
  
• 4. Make sure you are under the 3 code request limit
  Please keep tabs on how many requests you are making a week. We will only allow a certain amount of requests per person per 7 Day Period. If we spot you have gone over the request limit, then all your requests will be locked. Please note that this does not apply to code support or code modification threads, only requests for entirely new codes.
  
  
• 5. Include all relevent information in your thread
  
  a. Create a thread title that is clear and gives helpers an idea of what you are requesting. The thread title is somewhere that you can describe where you want the code to affect / what you want it to do. An example would be if you wanted a code to add the newest member to the news fader, then you would make the title of the thread "Add newest member to News Fader", not "Need Code".
  
  b. A good clear description is essential. Explain your request in as much detail as possible, this will help coders get a better understanding of what you actually want. If possible, provide images or links to help. Do not just post one sentence. It won't be enough to give us a clear idea about what you would like.
  
  
• 6. Remain patient while someone addresses your request
  After posting your request, you now just need to be patient until someone responds. Keep in mind that the coders here are all volunteers, so it may take time before anyone is available who can address your request. Not all coders are able to tackle all requests. It may also take a longer period of time for some codes to be made than others.
  
  a. What happens if no one responds to my request?
  
  Wait 24 hours. Once that time is up, your may "bump" your thread. Please note that consistently bumping early will result in a locked thread, and you will not be allowed to make the request again until the full 24 hours has gone by.
  
  
• 7. Filled Requests
  
  Once your request has been filled, please remember to thank the person who helped you! Please also edit the title of your opening post to include [RD] before the rest of your thread title. This helps coders know which requests still need attention.
  Please do not delete your first post. Other members and coders may reference your thread if something similar is requested later.
  
  a. What if there is a problem with the code?
  If there is an issue with the code, please continue to ask for support in your request thread, as its easier for responders to see what has already been done.
  
  
• 8. Rejected Requests
  If a code has been rejected, it could be for (but is not limited to) any of the following:
  
  a. Your code was on the Requests that will be rejected list.
  b. It isn't possible for anyone to create a code that can do what you're asking.
  c. What you are looking to do may be accomplished by a built-in Proboards feature.
  
  If your request has been rejected, please edit your first post to include [RR] before the thread title.
  
  
  
• 9. What if I don't need this code anymore?
  
  If, for any reason, you do not need the request to be filled any longer, and no one has responded to your thread, please delete your post. This will remove the thread and will prevent our coders from taking time to make a code that isn't needed.
  
  If someone has already responded to your post, do not delete your first post, just post stating that you no longer need assistance.
  
  

[Trublu]

Code Support

Before making a request for support with a code, please read this thread fully.

• 1. Before asking for support...
  
  a. Make sure that you are following any and all instructions that are in the thread where the code came from. Especially if the code allows you to define veriables, make sure that you have the correct syntax (format). This includes having the code in the right place; almost all codes provide instructions on where the code should be placed in order for it to work.
  
  b. If you got the code from somewhere other than our Code Index, ask for support first at the place where you got the code.
  
  c. Please note that we may not be able to make changes to codes that:
  
  • Have a copyright notice prohibiting us from doing so
    
  • Are remotely hosted
    
  
  
  
• 2. When making your support thread...
  
  Please include all relevant information, including your Forum's URL (may be PM'd if you wish to keep it private), a detailed description of the problem you are having, a link to the code, and any other relevant information. Screenshots are welcome, but should be accompanied by a description. We do not need you to post codes that you have, because we can see them on your forum.
  
  If either "Guests Must Login" or "Maintenance Mode" are set to "yes" in your General Settings portion of your admin panel, you will need to set these to "No".
  
  Create a thread title that is clear and gives helpers an idea of what you are requesting. The thread title is somewhere that you can describe where you want the code to affect / what you want it to do. An example would be if you wanted a code to add the newest member to the news fader, then you would make the title of the thread "Add newest member to News Fader", not "Need Code".
  
  A "detailed description" should include information about what happens when you try to use the code (what changes, what doesn't change, etc.). Saying that the code "doesn't work" is not specific enough for us to help you in a timely manner.
  
  
• 3. What if no one responds?
  
  Keep in mind that not all coders will know how to solve every problem, so it may take some time before someone comes along who can accurately answer your question. You may bump your thread every 24 hours. Threads bumped in excess before the time has gone by will be locked.
  
  
• 4. When you've received help...
  
  Once your issue is solved, please help us by adding [RD] before your thread title in your first post, and make sure to thank whoever has helped you.

[Trublu]

Code Helpers

If you're helping fill requests or providing support, please keep these guidelines in mind:

• 1. Does the request or support question follow all rules and guidelines?
  
  a. If the post has broken any rules, please let a moderator know instead of responding to the thread.
  
  b. If the request cannot be filled, please direct the poster to Requests that will be rejected or provide an explanation.
  
  c. Make sure the code does not already exist; check the Code Index.
  
  
• 2. Can I really fill this request or answer this question?
  
  Before you reply in a thread, make sure that the request is actually something that you know how to accomplish. Please do not respond saying that you'll make a code if you know that you won't be able to in a correct and timely manner. There are plenty of helpers who can cover the amount of requests we receieve.
  
  
• 3. Has someone else already replied?
  
  If another member has already replied to a thread, please let that member continue the interaction with the original poster. This avoids confusion and the posting of conflicting information, which allows us to remain consistent. If the original responder has either a., responded incorrectly or with inaccurate information, or b., indicates that they can no longer help, then you may step in.
  
  
• 4. Linking to codes in the Database
  
  a. If a member is looking for a code that is in the Code Index, please link to the index only, not the code itself, and provide the name of the code. Oftentimes, this helps members because they know where to look in the future for codes. If a code exists in the database already, there is no need to recreate it for a request.
  
  b. Make sure that if there is more than one code in the index that does what the member asks, try to direct them to all codes that may help them out. This way, we can avoid having everyone respond with a link to their own code.
  
  c. Exceptions may be made for codes not available in our database; in that case, you should link directly to the code in question.
  
  
  
• 5. Filling Requests
  
  a. When filling a request, make sure that you test the code before giving it to the requester. It isn't helpful to the member to give them a code that doesn't work.
  
  b. Please do not remotely host your code. While it might be more convenient, we cannot accept remotely hosted codes due to previous instances of hosts being consistently down, people switching files, etc. You can always give the member instructions on how to host the code themselves.
  

Keep in mind that you may want to submit a code that you've created to the Code Database Submission Board