- Sep 16, 2023
- 847
- 259
- 61
What does this suggestion change/add/remove:
This would update the current spawn camping rule (1.18) to be in line with how it is actually enforced, and has been for years. The current version is poorly worded and doesn't cover some key things that SL have had to essentially rule on instead.
The current rule is worded like so:
I am suggesting that the wording be changed to the following:
Has something similar been suggested before? If so, why is your suggestion different?:
Not as far as I'm aware.
Possible Positives of the suggestion (At least 2):
Possible Negatives of the suggestion:
Based on the Positives & Negatives, why should this suggestion be accepted:
The way the spawn camping rule is already enforced is very different to how it is and has been worded. This mainly just updates the wording so that it both actually makes sense, and so that it is in line with the existing enforcement. It also explicitly adds spawn AFK protection, which is only sometimes enforced by staff, but is generally a good idea.
This would update the current spawn camping rule (1.18) to be in line with how it is actually enforced, and has been for years. The current version is poorly worded and doesn't cover some key things that SL have had to essentially rule on instead.
The current rule is worded like so:
1.18 Spawn Camping - You may not kill someone directly outside their spawn or base, or within their compound, unless they interact with you in combat or roleplay. If you are actively raiding, you may only kill someone directly outside their compound or base, and not their spawn (unless attacked first).
I am suggesting that the wording be changed to the following:
1.18 Spawn Camping - You may not perform a hostile action upon - or take the disguise of - someone who is inside or immediately outside of their spawn or compound.
The only exceptions to this are:
- If they have already left and returned to this area during their current life, and they aren't AFK.
- If they are or have been interacting with you or others in combat or RP during their current life, and they aren't AFK.
- If you are actively raiding their base, and they are in/near their compound. Other spawn camping restrictions still apply.
Has something similar been suggested before? If so, why is your suggestion different?:
Not as far as I'm aware.
Possible Positives of the suggestion (At least 2):
- The wording doesn't imply the following clearly unintentional things:
- That the restrictions only apply to outside of spawns, and not inside them.
- The restrictions don't include things like kidnapping, harming, injecting, taking disguises, etc., and only include killing, specifically.
- If you are raiding, you aren't allowed to kill people that are inside a base, and can only kill people that are outside the base.
- You can't kill someone that is in/near their spawn that is shooting at other people, you can only do so if they are shooting you. Same with RP.
- The wording now explicitly includes the following consistently enforced non-rulings, which the current wording doesn't support:
- Leaving and returning to your spawn removes your spawn camping protection.
- The new wording explicitly states that you are still protected if you return to your spawn and go AFK.
- This is inconsistently sometimes enforced, but sometimes not. It seems like a good idea for this to be explicitly stated, so that everyone has a safe place to go AFK.
- Clearer wording and consistency with actual enforcement means it will be more understandable for newer players.
- Should ideally lead to more consistent enforcement.
Possible Negatives of the suggestion:
- Wording is slightly longer than the old one.
Based on the Positives & Negatives, why should this suggestion be accepted:
The way the spawn camping rule is already enforced is very different to how it is and has been worded. This mainly just updates the wording so that it both actually makes sense, and so that it is in line with the existing enforcement. It also explicitly adds spawn AFK protection, which is only sometimes enforced by staff, but is generally a good idea.
Last edited: