Forum Etiquette
From Rigs of Rods Wiki
Contents |
This is a simple guide explaining the etiquette of the forums, yes I know there's the "written" rules...but did you know there are also some "unwritten" rules? Well, this guide is aimed to try and cover the basic ones while allowing you, the reader, to better understand where people come from on many points of interest...
Part 1
There are some things you can and can't do (well you still can but its not advisable) they are...
DOs:
Talk and have a good time.
Post comments and suggestions.
Behave in a manner that's mature.
Ask questions.
Make a Truck/Load/Terrain/Other modification.
Contribute your knowledge, thoughts, ideas, or experience to help another author who is making a truck.
Provide constructive (respectful & helpful) criticism.
Don'ts:
(these are some of the things that are considered "no no's" around here).
Beg for a release of a truck.
Beg for a release of a building.
Beg, in general, for anything.
Beg to beta test a truck and/or other project.
Disrespect others (this would be a big no no and could get you into some serious trouble...its not worth the risk).
Bash, flame, insult others or their work in some way or form.
Post any illegal or "questionable" content on wiki/forums (This includes but is not limited to the following: porn, warez, pirated software, "stolen" meshes, ect.)
Part 2
Now you may be thinking, "Ok...You said I can ask questions but then you say don't beg for a release...?"
Yes you can ask questions...and there's a few ways you can ask about a release of a truck that are generally acceptable (although it depends on the person who is making the truck but most of the time its found to be universally acceptable)
You can be reading a post like the following PLEASE NOTE THE FOLLOWING MAY USE NAMES OF PEOPLE OR TRUCKS OR PEOPLES PROJECTS WHICH IS COINCIDENTAL IF YOU PREFER NOT TO HAVE YOUR PROJECT/NAME USED PLEASE PM A MODERATOR OR ADMIN PRIVATELY ABOUT IT.
Person A: "I am making a new truck called a sterling".
Now there are a few ways you can ask with out blatantly begging for it like "Hey, nice truck, any idea when it may be ready for use in game?".
Or, "I noticed you're making a new truck, is there a download link up, or is it still a WIP (work in progress)? Anyways, I still think its looking nice and I think if you <insert suggestions/comments here>... It may make it look a bit better".
Now you must be reading that and thinking, "that's still begging."
True it could possibly be taken that way BUT your asking in a nicer way then saying, "HEY CAN I BETA TEST THAT TRUCK PLEASE PLEASE PLEASE?!?!?!?!?1!?!1!11!"
Part 3
Also another unwritten rule is don't "steal" others work.
It's acceptable to modify their work and give credit to the original person and then take credit for the mods YOU added.
Example:
The Sterling truck
The original was made by another person and you went and added Light bar, some new flares and fixed a problem with the back up lights (lets say they were red instead of white).
It's recommended to ask the original author(s) for permission before you release any mods of it to repo or in the forum. If you want your creations be free to mod by others, just add a "feel free to release your own mods" or similar to your repo release descriptive text. Just show respect to others people work by asking for permission and don't erase any author infos, just add yours and your contribution info. If a repo release is tagged with a "Need permission to mod" or "Not permitted to mod," please just respect this. He made it, its his baby, bottom line.
Don't overwrite any others users repo releases by using the same UID. Get a new one for your own mod. UID-Doubles can and will be removed from repo without further notice.
As declared by admin "Pricorde", all his repo contributions are "free to mod" for anyone.
You could go about this one of two ways (although I suggest you use the latter of the two).
ONE: You could make the modifications and release it to the repo stating you are giving credit where credit is due
TWO: In the Sterling thread, you first ask the original creator if he/she would be ok with you adding a few things and fixing a minor issue with the back up lights. Then, make your modifications (this assumes they have already posted a reply and given you their "OK") in the same thread. Wait a bit (preferably a day) then you can nicely ask "would you be ok with me uploading this to the repo?" Again if they say yes or ok then go right ahead and upload it (state in description of the file your giving credit where its due for original work and any other comments you wish to add).
Now, go grab a cup of coffee or other liquid and take a quick break.
Part 4
Ok had your nice cold or hot drink? Good, lets continue.
Now on for a few more...
Another unwritten rule is no excessive posting, this means don't make two or more posts right in a row, give others a time to respond!
Its a BIG NO NO to use twenty smilies in a post, this will be frowned upon and make you look younger & immature in the community's eyes.
Now you are probably thinking, "What if I wish to ask about the truck and maybe offer help to fix a problem that I already know a way to fix or have a simpler solution to?".
Well then offer... If you offer the assistance then if the author wants it they will let you know.
Another thing you may see from time to time is the author post up some screenshots of a [WIP] (tag used for work in progress) and then they will state their problem and ask if anyone could help them.
This isn't considered begging but I suggest you respond to the similar...
"Hey! Nice truck, you mind letting me check the truck out and see if I can help you fix it?" (If you had a similar issue then let them know you may have a solution to help fix their truck).
Now you're probably wondering about the "hit N' runs" well that's a chance some of us take. But rarely will that happen. Most people here will offer their help and give the help they said they would give.
Do you like the truck but see something that could use improvement, or better yet did you think of another variant that would be neat to have?
Well again ask nicely in the topic of what ever truck your wanting a new variant for. The author may make it when they got the time, who knows? If you know how to make a truck then you can ask the original author (like in other instances) if you can use their truck and mod it and make what ever variant you are interested in, and more then 90% of the time the original author will be oka with this and let you (provided you give proper credit where its due).
"What about a case when I make a truck or some type of mesh that's similar or really close to a mesh or truck someone else has made?"
Good question, in these cases (which are rare but some times happen) you don't have to ask the other person however its considered a courtesy to ask them or at least talk to them and let them know, you can also post in your topic that some parts of your truck are similar to parts of another truck but most of the time if you made the part and you post in your truck topic (usually in the first post with the other info about the truck) that some parts of your truck could potentially be similar to another truck and usually this is ok, This DOES NOT give you the right to out right steal others work, this only lets other know that parts of your truck could look or have some similarities with another truck!
Part 5
"What if I posted but got no reply to my question of when it maybe released?"
Well that's still technically "begging" but if you asked once and only once usually the author will let you know what work needs to be done on the project and will be more willing to post some updates as time progresses to keep others informed about progress.
"Ok, I thought there was supposed to be a release, where is it?! I'm PM'ing the author."
This, well to be honest is a very BIG NO NO!! You do this AT all (even once) your asking for some serious trouble, why? For one thing its begging to the lowest level, it shows your a very immature person. You can't act your age and more than likely the author will either report you to an admin (resulting in a possible suspension all the way up to and/or including a ban). The author could most likely pull the work and not release it and be very offended.
"Hey I like the truck but one issue it **** in handling, it texture are rubbish, and it just looks like a piece of rubbish!!! oh and I hate the truck hahahahahaha..."
Now what do you see wrong here? Every thing. This is another way to make authors suddenly decide to pull their work (it has happened on more than one occasion) and your definitely asking for a ban, especially if you make more than one post like this. Plus, its also bordering on the thing we all hate, spam. Another big NO NO here. As stated before, if you want to add something constructive go for it, but refrain from blatant hating of their work and saying mean things.
Part 6
Write in clear, grammatical, correctly-spelled language
We've found by experience that people who are careless and sloppy writers are usually also careless and sloppy at thinking and coding (often enough to bet on, anyway). Answering questions for careless and sloppy thinkers is not rewarding; we'd rather spend our time elsewhere.
So expressing your question clearly and well is important. If you can't be bothered to do that, we can't be bothered to pay attention. Spend the extra effort to polish your language. It doesn't have to be stiff or formal. In fact, hacker culture values informal, slangy and humorous language used with precision. But it has to be precise; there has to be some indication that you're thinking and paying attention.
Spell, punctuate, and capitalize correctly. Don't confuse its with it's, loose with lose, or discrete with discreet. Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only slightly less annoying, as it's difficult to read. Alan Cox can get away with it, but you can't.)
More generally, if you write like a semi-literate boob, you will very likely be ignored. So don't use instant-messaging shortcuts. Spelling "you" as "u" makes you look like an semi-literate boob to save two entire keystrokes. Worse: writing like a l33t script kiddie hax0r is the absolute kiss of death and guarantees you will receive nothing but stony silence (or, at best, a heaping helping of scorn and sarcasm) in return.
If you are asking questions in a forum that does not use your native language, you will get a limited amount of slack for spelling and grammar errors but no extra slack at all for laziness (and yes, we can usually spot that difference). Also, unless you know what your respondent's languages are, write in English. Busy hackers tend to simply flush questions in languages they don't understand, and English is the working language of the Internet. By writing in English you minimize your chances that your question will be discarded unread.
Part 7
I hope this simple guide helps you and the rest of this community. This was written by a member who knows what its like to be pestered and begged at by "noobish" people. So I have taken the time in hopes of helping more people understand the unwritten rules of the boards and try and at least educate them. I hope this doesn't offend anyone and if you wish to add to this helpful guide please don't hesitate to add to it. It's to try and help better the community!
This guide is subject to being changed or modified with out any notice, please check here often for additions, changes, ect.
Written by James and wikified by Seggons.


Gold
Silver
Bronze