inherit
2671
0
May 14, 2013 14:40:03 GMT -8
Peter
🐺
10,615
February 2002
peter3
|
Post by Peter on Jun 5, 2005 4:39:39 GMT -8
In this thread there are 3 posts, the first and last one is to be read by all members who wish to request a code. Failing to read those posts will most likely end up with your thread becoming locked. The second post in this thread is for members who wish to help fill requests. |
|
inherit
2671
0
May 14, 2013 14:40:03 GMT -8
Peter
🐺
10,615
February 2002
peter3
|
Post by Peter on Nov 3, 2006 8:09:17 GMT -8
Before You Request A Code[/size][/b] - Step 1 - Check the database first
First thing to do before actually posting a request is to browse through the code database. There is a code index in the code database that lists all the codes in there. Reason for this is because it's not fair on the coders who fill your request, only to find that it was in the database already.
- Step 2 - 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.
- Step 3 - How many requests does that make?
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. Look out for any updates in this post, as the request limit could change at anytime.
- Step 4 - Create your thread
So, you are pretty sure that the code hasn't been done or requested yet?... You may now create your request thread, but before you do, here are a few things to note which will probably help you and coders have a better understanding of what you want....
1. Create a thread title that is clear. No use in creating a title called "I need a code!!!", it's more then likely coders will just ignore the thread (I know I would). Too many threads have inappropriate and unhelpful titles. Not all coders have a great deal of spare time so will just browse the threads here to see if there's anything that they fancy doing. They shouldn't have to open your thread just to get some idea about what you want.
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", it's obvious really.
In order to make this board more organised and in order to help others looking for similar requests, Threads with un-descriptive or inappropriate titles will be Locked. If your thread is locked, you may not make another for 24 hours.
2. 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.
- Step 5 - Waiting....
After posting your request, you now just need to be patient until someone responds.
What happens if no one responds to my request?
Wait roughly 24 hours. Once that time is up, you may post to your request so that it is bumped up. If you bump well before the time limit is up, then I will just lock your thread, and you will not be allowed to create another request until a further 24 hours is up.
I've bumped quite a few times now, but still, no one is filling my request, what do I do?
There are many reasons why the request might not have been filled, here are the top 3...
- It could be that there is no one good enough to fill your request.
- It could be that your request is too complicated.
- It could be that you haven't described in detail what you actually want.
Best thing you can do is let the thread drop, and then ask in couple of weeks. There might be someone around to fill it.
- Step 6 - OMG, my request is done
So, your request has been done, what do you do?
Once your request has been filled by a coder, he/she will most likely post the code into the code submission board to be reviewed before it is moved to the database. Or, they may post directly in your request thread. All that you have to do now is to simple say "Thank you" to the person that filled your request. Might be only 2 words, but they can mean a lot. Nothing worse then a coder filling a request, only to not get a simple "Thank you". Remember, that coder took his/her time to do your request, doesn't matter how small it was.
If you want to earn extra brownie points, edit your first post to include "[RD]" (Request Done) in the thread title. It will help keep the place more organized as we will know which requests are still outstanding. In the long run, it will help others get help sooner.
Under no circumstances are you to delete the first post in a thread. Someone has gone out of their way to help you, the least they deserve is some respect. Besides, we can tell who it was by looking at the 'thread starter' column in the thread listing anyway. All you end up doing is making a fool of yourself.
- Step 7 - Oh no, there is a problem with the code
There will be times where you will need something changed or fixed, but you won't be able to reply to your request thread, as it will be locked. What you do now is contact the coder directly, he/she might be kind enough to offer to make the changes to the code and release an updated version. Or, you can ask for help in the Code Support Board.
 [/ul]
|
|
inherit
2671
0
May 14, 2013 14:40:03 GMT -8
Peter
🐺
10,615
February 2002
peter3
|
Post by Peter on Nov 3, 2006 8:17:35 GMT -8
For Members Who Are Helping Fill Requests[/b] RD = Request Done RR = Request Rejected - Step 1 - Has the requester broke the rules?
Before you even consider filling a request, please check to see if the person requesting a code has broke any rules.
1. Has he/she bumped before roughly 24 hours is up?
2. Has he/she requested more then the limit set?
3. Anything else that might apply.
If yes to any of them, then please don't fill the request. Either inform one of the Moderators or politely inform the requester that they need to follow the rules.
- Step 2 - Has another coder already replied?
Before you reply to a request, make sure that there hasn't been a coder who has already replied to fill the request. If you repeat what someone has already said, delete your post.
Remember - It's not a competition to see who can fill the most requests.
- Step 3 - Does the code already exist in the database?
Quite a few people request codes that are already in the database, if that is the case, then all you need to do is direct the user to the code database. Please do not post links directly to the codes nor the codes themselves, just guide them to where it is posted, if after a few attempts they cannot find the code, then you may provide the link yourself.
- Step 4 - Can I actually do this request?
If you don't think you can do the request, then please don't reply saying that you will, leave it for a more experienced coder to fill. Otherwise the requester could be waiting days for the code, only to find out you couldn't do it, where as someone else could have it done sooner.
- Step 5 - I've done the code, now what?
Before you actually think about posting the code, ask this simple question...
Will other people use it?
If you answered yes to this, then post your code in the code submission board, this way, other people will be able to use it as well. No use in posting it in the request thread, people looking for codes won't look there. Otherwise, just post it in the request thread, there will be times when you will do this, for example....code could be extremely simple.
If you do post your code in the code submission board, reply to the request thread with a link to the code.
- Step 6 - The person who requested the code is PMing me. Why?
Since you were the person who filled the request, then that person will PM you to get help with it. It could be there is a problem with your code, or it could be anything. But it's up to you to provide the help. If you don't want people PMing you, then don't fill any requests.
Thank you [/ul]
|
|
inherit
2671
0
May 14, 2013 14:40:03 GMT -8
Peter
🐺
10,615
February 2002
peter3
|
Post by Peter on Nov 3, 2006 8:17:52 GMT -8
RD And RR In Topic Title?[/b] - These initials stand for 'Request Done' and should be added to the start of your thread title when your request has been filled. RR - These initials on the other hand stand for 'Request Rejected' and should be added to the start of the thread title in a number of circumstances. For example, if the requested code would break the TOS, if it is already (or soon will be) a built in feature or if the code is simply not possible. Why should I do this? - This system is in place to eventually help you, the person requesting the code. It gives coders at a glance information on who still needs help and who doesn't; meaning that you and others like you will get helped sooner. It will also let you see what is or isn't possible. How do I add it to my thread title? - Just go to the first post in your thread and click on  . Then, at the start of the thread title add the appropriate initials. Why does my thread already have the initials in the title? - When it seems obvious a request has been completed successfully or that it cannot be done, we will modify the thread for you so that other coders or people requesting codes do not get confused. [/ul]
|
|
