Difference between revisions of "Route problem guide"
Yevad Doobie (talk | contribs) (Created page with "==What to do if you discover a problem along the Protected Routes== ---- ==Accepted issues== '''Type 1''' :* Defective sim border crossing prims, which cause vehicles to pass…") |
Yevad Doobie (talk | contribs) m |
||
| Line 8: | Line 8: | ||
'''Type 1''' | '''Type 1''' | ||
:* Defective sim border crossing prims, which cause vehicles to pass through apparent phantom prims and get stuck/crash. | :* Defective sim border crossing prims, which cause vehicles to pass through apparent phantom prims and get stuck/crash. | ||
:* Non-phantom signs near sim borders. | |||
:* Incorrect permissions (zero return time, push allowed, object entry disabled, scripts disabled, flight disabled). | :* Incorrect permissions (zero return time, push allowed, object entry disabled, scripts disabled, flight disabled). | ||
:* Resident owned obstructions. | :* Resident owned obstructions. | ||
:* Requesting Linden/Mole prims/land be changed to allow better access from a resident owned parcel. | :* Requesting Linden/Mole prims/land be changed to allow better access from a resident owned parcel. | ||
:* Incorrectly named parcels. | |||
'''Type 2''' | '''Type 2''' | ||
:* Dialogue box spammers, with range set to catch route travellers (item givers, group inviters etc). | :* Dialogue box spammers, with range set to catch route travellers (item givers, group inviters etc). | ||
Revision as of 19:21, 1 July 2011
What to do if you discover a problem along the Protected Routes
Accepted issues
Type 1
- Defective sim border crossing prims, which cause vehicles to pass through apparent phantom prims and get stuck/crash.
- Non-phantom signs near sim borders.
- Incorrect permissions (zero return time, push allowed, object entry disabled, scripts disabled, flight disabled).
- Resident owned obstructions.
- Requesting Linden/Mole prims/land be changed to allow better access from a resident owned parcel.
- Incorrectly named parcels.
Type 2
- Dialogue box spammers, with range set to catch route travellers (item givers, group inviters etc).
Type 3
- Ghost prims.
Type 1
A support ticket needs to be made, there is a good guide at this blog entry: Getting Answers and Help from the DPW. It is recommended that you add "FAO DPW:" to the first text entry box, this helps filter the issue to DPW. Please explain the problem as clearly as you can, including images, edited to mark issues if required. Remember, the easier you make it for DPW, the faster the fix!
Note: tickets to DPW can also be used to request a rez-zone in areas where they are lacking, or to suggest new routes if DPW adopting abandoned land will create a useful route, or extend an existing one.
Type 2
The abuse report system is best for these. If possible, locate the spammer and right click it, choosing "Report Abuse" from the menu. If you cannot locate the spammer, use the option at the top (Help menu). Always include a screenshot! Once the abuse report window is open, if you need to find the owners name, select "mute" on the dialogue box, you mute list will open and the newest entry will show as selected. It is important that you do this only after the abuse report window is open, or else you will be unable to show it with a screenshot. Fill out a report under the "Unwanted advert spam" category.
Note: non-repeating automated chat messages triggered by avatars along the routes are generally tolerated, though if excessive it might be worth reporting.
Type 3
A sim restart is required, make a support ticket under the following headings:
Land & Region > Report and offline region
Please include the full sim details, found using the help menu > About Second Life. The details will look something like this:
You are at 256549.5, 261343.9, 133.9 in Rivata located at
sim8900.agni.lindenlab.com (216.82.41.76:13001)
Second Life RC LeTigre 11.06.28.234198
Other Information
Second Life Road Network Directory
External Links
Getting Answers and Help from the DPW (DPW blog entry)