|
|
| Welcome to the rules page. If you're a new member or not, it's important for us and for all of the other users that you understand and apply a certain list of rules. Some of which may be obvious, but rather have said the obvious than do the inivitable. If you have never been here before, let me explain you how this works: down this page, there's a list of rules. Though, some of those rules may be hard for people to understand if it's just that one sentince. That's why n some cases, there's a plus image next to the rule. If you click this image, some additional information regarding this rule will appear. This additional information could just contain an example, but could also contain exceptions to the rule. So, please take your time to go thru this entire page. On behalf of the entire NZBs'R'US crew, thanks for your time. |
| - 1. Do not defy the moderator's expressed wishes! |
 2. The maximum age of a release (NZB) that can be uploaded to the site is fourteen (14) days.  Anything older than this will be nuked by the staff.
2a. The only exception to this is filling forum requests and any such upload must have [REQ] added to the NZB name. |
|
3. Search the site before you upload. Its always possible the NZB has already been posted, any dupe file will be deleted without and kind of notice or warning. On a side note if your post does vanish then there is a reason for that to happen chances are it was DELETED.
So instead of re-uploading it your first stop should be the Logs (left hand side of the page) to see why it was removed.
Failing that try searching the site instead you may see what you are already trying to upload, it will save us a lot of unnecessary work and you getting into trouble with the staff.
|
|
4. Site's definition of dupes: Dupes are files which match in file name and newsgroup. If the file you intend to upload have already been uploaded to the site in the last fourteen (14) days it would be considered a DUPE! and as such it will be nuked, there is one exception to this rule and that would be if they are on different groups.
IE: one on alt.binaries.b4e and the other on alt.binaries.boneless would not be dupes. |
|
Do not use abbreviations in post names To make this site as accesible for everyone as possible, please void the use of abbreviations in post names. Though, when it is part of the origional scene release name, leave it like this. This includes the scene release group name. A small list of often used abbreviations for scene release names and the full names that you will need to use:
- FLT - FAiRLiGHT
- RLD - RELOADED
- iMS - iMMERSiON
- RZR/ RZR1911 - RAZOR1911
- UNL - UNLEASHED
If a scene release name is an abbreviation, you willl have to leave it like that (so, CRN stays CRN). |
|
Use Scene Release Names where possible We promote the use of scene releases since they will get you what you want (home made's can be something else than you expect, and there's no NFO included to do proper research or comparison before downloading).
Thus, when you upload a scene release, use the proper Scene Release name. This includes the dots between the names and the release group at the end. If you don't know what the Scene Release Name is, start out by looking in the post name, the NFO or on other sites such as vcdquality.com or nfoogle.com, or searching usenet with binsearch.info or newzleech.com
for example, the correct formatting for a dvdr movie would be:
The.Matrix.Reloaded.NTSC.DVDR-Replica
and for music:
Led_Zeppelin-Latter_Days-2000-EGO
etc. |
|
Include NFOs when possible | NFOs provide a lot of valuable information to the users before they start downloading related files. Add the NFO to your post when uploading a NZB so people can make benefit of this feature. Be wary of the next couple rules regarding NFOs as well |
|
Do not post NFO in description field If you add an NFO to an nzb upload, then do not paste the contents of the NFO into the description field as well. The description field is for the uploader's own comments and information, or whatever info isnt contained within the NFO (unless no proper NFO is available)
Staff members may warn/restrict your account over this. |
|
Remove serials from NFOs before uploading | Usually regarding games and applications, sometimes an associated serial number is enclosed in the NFO. Remove these serials from the NFO before attaching to the site's nzb, otherwise you may be warned/restricted. You may replace the serial with XXXX's or simply say ; when the user downloads the nzb and then the associated files, they will get the serial in the real NFO. |
|
Do not flame any of our users | Flaming consists of any excessive or unwanted derogatory or rude comments. People don't come here to get harassed. This is a community of users, each of us would like to be treated with respect and kindness. The Staff will ban you for flaming, no questions asked. |
|
Put a [REQ] tag in the post name if it's a request This is just for the ease of all the staff members. But there are a few things you'll need to watch out for here. First off, you shouldn't post a tag if the posts are younger than 14.0 days. Even if the file has been requested by someone, no tag if it's not older than 14.0 days.
Second, please try to apply a white space between the tag and the release name (post name). This is just easier on the eyes and it looks better.
Lastly, it's [REQ] in front of the post title, not request or [REQUEST] and not in the additional title information. If you insist on it, you can repeate it there, but there MUST be a tag in the post name aswell. |
|
When a post doesnt contain par recovery files, say so | When a post doesn't include par files (should be exceptional, read other rules), please notify so by posting a 'No Pars' in the additional title information (not in the post title itself, or the description field). If you are posting a 'No Pars' nzb in order to get it on the site faster, post the pars seperately as soon as they are available. Label these posts with 'Pars Only' in the same field. It is not needed to say 'With Pars' or 'Including Pars' when you make a post including pars, because it is assumed they are included, and only not having them included is the exception. |
|
| Page coded by Battle_707 |
