|
| 13 Aug 2017 07:18 PM |
Decided to type out my own, since I don't see any anywhere. >->
When asking a question, you should...
1. SPEAK ENGLISH. Don't just give code, and expect others to figure out the problem for you. You should at least tell us what's not working, what you're wanting it to do, and, if possible, give any feedback returned from the script, being errors, warnings, etc.
2. DON'T SPAM QUESTIONS. Your question/thread may be taken down for spam, as that's already a rule in the threads.
3. HAVE YOUR QUESTION REVOLVE AROUND SCRIPTING. Your thread should be around scripting, and not anything other.
4. HAVE YOUR TITLE REFLECT WHAT YOU'RE PROBLEM IS. I know, some question titles are hard to explain, but you should do the best you can to have your question title revolve around what you're doing/working on. It also gives people a bigger idea, and highers the chances of them going to take a look at your question.
5. TAKE THE PROPER PROCEDURES WHEN ASKING TO HIRE. Thane_1 did a wonderful job of explaining this, but I'm going to add onto what he's said.
When hiring a script, you have to:
1a. Say what you're wanting, and the amount you'll pay. Don't be vague, as that'll detract people from helping you, rather than them wanting to help you.
1b. Give proof if you're a fellow scriptor, and builder when you claim you're one of the two (or both) categories. It more-so attracts people to help you, ez they'll feel you'll know what you're talking about, and that you're legit.
1c. You should be descriptive of what you're wanting. Simply saying "I want a GUI to [BLANK]," or "My script isn't working please help" isn't enough. You should explain in more detail about what you're trying to do/wanting to do. That'll better equip people to help out, and you'll have more people who're more towards what you're trying to do.
1d. Have the scriptor(s) show proof of their work: You don't want a "false" scriptor tricking you into thinking that she/he is a scriptor.
1e. When working with a scriptor, again, you should prepare pay. When you further the agreement, and the requirements are met, you shouldn't pay flat out, otherwise it may be a hit-and-run. You should only be so much the first time, then when the scriptor has finished and presented his work, and if it turns out to be what you wanted, you should pay them the rest, as that's apart of the original agreement.
6. BEWARE OF "TROLLS." There're people who'll post bait to try and lure you in, so be very careful when you reply to a thread, or plan to make one yourself!
7. DON'T BAIT PEOPLE! No one wants to help/work with someone who baits them, or other people. That'll greatly detract people from wanting to help you, and the only thing you'll gain is negative feedback from them. You might also receive a bad reputation if you keep it up, and people wont want to help, or even read your questions anymore.
8. IF AT ALL POSSIBLE, MAKE IT SHORT AND SWEET! Make sure you have enough information, while keeping it short, and organized. Really attracts people!
9. IF YOU'RE HAVING SCRIPT TROUBLE, PROVIDE THE SCRIPT! It's good to speak English, but you should also provide the code that's having the problem. Helps make things go quicker, and people'll be more equipped to help you the best they can!
10. BE RESPECTFUL! No one wants a poster to be a big meanie! You should be nice the best you can when talking to others. Boosts rep too!
11. NOT BRING UP RELIGION OR POLITICS! You're asking for trouble when you do this. Not everyone has the same views as you, and may attack for it, so don't bring them up the best you can! Try to avoid conversation with it!
Now, onto answers. When answering a question, you should...
1. MAKE SURE THAT A HIRE REQUEST IS LEGIT. People who hire may seem that they're request is a small thing, but in turns it may get more complicated, and more overwhelming where you just can't work with them. Be sure to reread and ask questions before agreeing to the job request.
2. NOT TARGET/ATTACK SOMEONE. The only time you can get after someone is when you criticize them. Don't go off and start cursing/attacking at them "just cause." There needs to be a reason, rather than just that person not helping you with your English homework.
3. MAKE YOURSELF PRESENTABLE AND PROFESSIONAL. People who ask questions expect that those who reply will be able to fully answer their question. Similar to #1, you should be sure to ask questions, and try your best to see if you can help you. If you're no longer within the reaches of help, just say that you're not able to help anymore, as you're not within that category.
4. BE SURE OF WHAT YOU'RE TALKING ABOUT. As scriptors, we need to be able to be ready for questions that come up. When a question appears that you find interesting, you may want to research up on it. You may come across something new, and handy in the future!
5. Read #6, #8, #10, and #11 in the Questions section.
6. BE EQUIPPED. You want to be ready for any challenge! Even if it means going up against the almighty NOOB SCRIPTORS!
7. NOT COME ON TOO STRONG. You don't want to pull super complicated stuff at the start, unless if it seems the thread owner seems to know about what they're trying to do. If you just do it strong from the start, it'll only confuse and overwhelm the thread owner. Be careful!
8. NOT DISCOURAGE OTHERS, AT LEAST NOT TOO GREATLY. It only shows that you're a big meanie. >:c And you may get a bad rep too.
9. GIVE SOURCES WHEN NEED AND POSSIBLE! You should give the thread owner some sources to look at and take notes from, and they may greatly appreciate you for that! That'll also show off how classy you are. c;
10. NOT FIGHT WITH FELLOW SCRIPTORS. ...FIGHT FIGHT FIGHT!... I mean, try not fight with your fellow scriptors. c: Unless if they're wrong on something, or if they're being ignorant.
Please let me know if I missed anything, and thank you for reading! |
|
|
| Report Abuse |
|
|
iiNemo
|
  |
| Joined: 22 Jul 2013 |
| Total Posts: 2380 |
|
| |
|
| |
|
|
| 13 Aug 2017 07:26 PM |
| @BunnyBoy26 Np. I hope this aids everyone in the future. :) |
|
|
| Report Abuse |
|
|
|
| 13 Aug 2017 09:05 PM |
@TheeDeathCaster Forgot to add one thing to the Questions list.
12. MAKE AN ATTEMPT. You shouldn't just be flat out making a thread when you haven't tried hard enough! Make sure you debug your script, and try and see what the problems are! If you don't see any problems, but are receiving feedback from the script, be sure to give us that information, with the script provided: It'll help us to further to help you with your problem.
On the other hand though, if you're just expecting someone to make a full script for you, without pay, and are just hoping people will do it, it likely wont happen. However, if you were to make an attempt to do what you're trying to do, and gave your attempt, then we'll be more happy to help you. :) And if you came with feedback with your attempt, and give it, then your chances of successful answers highers greatly! :D |
|
|
| Report Abuse |
|
|
|
| 13 Aug 2017 09:39 PM |
calm down its annoying i know, ive seen the people like that but damn this is essay material |
|
|
| Report Abuse |
|
|
|
| 14 Aug 2017 09:24 PM |
Stop trying to be someone your not.. You are legit spam posting on posts to bump this trash.
Take your own words for it and stop spamming trash like this and help users who need help... Fool
|
|
|
| Report Abuse |
|
|
|
| 14 Aug 2017 09:27 PM |
^^^^^^
Google is handy, give it a try. |
|
|
| Report Abuse |
|
|
|
| 14 Aug 2017 09:35 PM |
e.e
Sorry for my bad English at 3:30 in the morning.. ---
At the end of the day he is going into threads and spam posting this post...
A post on "Posting Good Questions and " Answers " on The Scripters Subforum
He used the word answer in this post lol yet he Answers in peoples threads
with ( LINK TO THIS POST ) No help.. talk about contradicting your post lol idiot
|
|
|
| Report Abuse |
|
|
|
| 14 Aug 2017 10:37 PM |
an improved guide
when asking a question on the scripters subforum... 1.do not post the script or its description you do not want to overcomplicate the post after all 2.flame those peasants who ask for more info if they cannot fix it with the info at hand, they are just stupid 3.ask everyone to make you things everyone is obligated to do everything for you, do not let anyone tell you otherwise 4.insult everyone else you want a real tough user helping you, not someone who gets annoyed by your insults, so that the help received is just a tough 5.bump every minute you need to get your thread noticed
when writing answers on the scripters subforum... 1.measure how good your answer script is by complexity and size you want to show everyone you are an expert with your knowledge of complex solutions, and the bigger the better 2.insult the op and other posters you are doing the people a favor by hardening them against the internet and the insults are a joke really, plus that one guy insulted you with his "correcting" 3.derail the thread introduce new topics to keep the thread exciting and exciting, bring your political views and petty rivalries with other players there 4.start a flamewar the post activity will help the thread get more help 5.show deprecated methods when possible if it is not broken then do not fix it, there is probably a good reason why that person you learned from years ago used the method 6.do not explain anything the op just needs the script, do not overcomplicate your post since nobody will be finding the thread in the future anyway 7.fight those who are against your great deprecated methods do not let these people with their new ways are kill your superior deprecated culture 8.tell the person to google it or fix it themselves strong and independent people do not need any help, anyone else is lazy and you should spread this news
when hiring a scripter on the scripters subforum... 1.write all your requests into a single paragraph with no grammar you want to compact all the information for readability 2.display that you do not know what even print is the more the specialisation you expect the better scripter you get 3.offer to pay in FUN, EXPERIENCE and EXPOSURE all scripting is supposed to be always done free and everyone who tells you otherwise is corrupted by greed - only the genius who comes up with the game idea needs the money 3.specify very specific guidelines on what the scripter can use and do it will make it easier for you to understand the script if no functions, modules or arrays are used, and each scripts only contains 1 thing for modularity 4.request the scripter to be active 24/7 and not sleep anyone less devoted is going to destroy the project 5.have your worst free modeled place on display that way more scripters will want to help you move away from it 6.use a trendy game idea if case clicker got popular, then making a practical clone of it will get popular too and everyone will flock to the opportunity of making it
when scripting for someone... 1.use wait loops instead of events whenever possible events are a thing of the devil and you join have a wait loop repeat until input happens instead 2.use the most complicated and memory intensive way to do something the players should get a better computer if lagging 3.keep all checks client sided you do not want to waste extra servers resources on things like currency systems and admin commands 4.avoid testing for bugs it just shows you are a unconfident coward 5.avoid checks against unloaded objects those waste precious space and the script should never break anyway since you are good at scripting 6.do not be afraid to use depreciated ways who are people to tell you what you can or cannot use 7.read a guide on writing unmaintainable code those new tricks will prevent you from being replaced without your permission 8.put the entire script in a call statement you do not want ugly errors showing up in your output
now you will do great here and with scripting |
|
|
| Report Abuse |
|
|
|
| 14 Aug 2017 10:39 PM |
^ Amazing, and improved.
Google is handy, give it a try. |
|
|
| Report Abuse |
|
|
|
| 15 Aug 2017 07:47 PM |
I admit, it wasn't smart of me to do what I had done. I wont make any excuses. However, I understand that I shouldn't have just post the link, but instead add the name of the thread along with it, since it's been pointed out; I didn't realize the problem with what I was doing.
"Why didn't you do this before?" I'm not going to make any excuses. It was for one reason alone: I wanted to see this thread in action, and see if it would actually help anyone. That's the reason why I kept posting this thread: I didn't think to add the name of the thread when I posted it; I got too excited to see it in action. <->
"That's a stupid reason." Ok, I'll accept that. "That's an excuse, hypocrite/idiot." It may sound like an excuse, but it's the truth.
"Why should I believe you?" It's your choice, the reader, if you wish to believe me or not. I will respect your opinion if you don't.
"I'm not going to use your thread." That's fine. I'm ok with people not using this. "You anonymously posted this thread." I admit to that. I'll add the name of the thread when I post it in the future. It may not be enough, but it'll hopefully let people know of the thread before they enter the link, so that they're not "baited." I didn't think of that.
"You didn't even follow the rules you set up." True. I'm not going to make any excuses on that, as I clearly did not follow the "rules" within this thread.
"You're an idiot." Well, I wont argue there. >.>
"Why're you typing those things within the quotes?" Think of them like Q&As. I typed out the most probable predictions for what a user might reply with. TL;DR They're counterarguments, to put short. >->
I'll try and be more careful with how I handle this thread. Again, I admit, it wasn't smart of me to have done what I did, but that's why there's criticism. I accept criticism, as it helps for a user to grow, and conform. Just like any other criticism, I'll take it into note, and (try) to conform into what I should have been doing, as well as (try to) not repeat the same mistake(s).
Thank you, reader, for reading, and thank you all for your feedback; I'll take it all into note, and try to conform into it. :) Have a good day, everyone. :) |
|
|
| Report Abuse |
|
|
|
| 06 Sep 2017 06:20 PM |
Sorry if I read over this (I do not think its in there though):
For asking scripting questions, after thoroughly testing code and trying to resolve the issue by yourself, be sure to post related OUTPUT with the code block you need help with. Copy and pasted output is perhaps the best way to tell another scriptor exactly what is wrong with your code block. |
|
|
| Report Abuse |
|
|
|
| 06 Sep 2017 10:00 PM |
| ^ It's alrdy there-ish, but you made the 3 ones on the original post into one (#'s 1,8,9 in the questions/asking section). XD Nice job. :) |
|
|
| Report Abuse |
|
|
|
| 06 Sep 2017 10:05 PM |
^^ Actually 4. >-> (#12 in the questions/asking section, in another reply box) Makes it even btr though. XD 4-in-1 package deal! |
|
|
| Report Abuse |
|
|
| |
|
|
| 04 Nov 2017 02:59 AM |
Hey people
could you try to make me a script in where example you have come in contact with Brick/Part, it would give you a random item which i will put in ServerStorage and after you have got the item the brick/part would Be gone/Destroyed.
anyone? |
|
|
| Report Abuse |
|
|
| |
|