Official Server rules discussion thread

[Travelsonic]

Clarification:  Is this list of rules actually official, like something you can cite in reports / telling others to cut "it" out / etc, or in the process of becoming something that can be considered finalized, official official?



Suggested idea:
TTT:

• Turning the lights off / on in clue is not a Traitorious act INHERENTLY.   Other servers have this rule, and I agree with it.  Too many times I see people nearly RDM'd, or even RDM'd because they used a function in the map ANYONE can use.  Sure, the darkness can help kill non-Ts, but at the same time, unless there are eyewitnesses and/or DNA to link a player to a killing, how can you clearly ascertain anything other than suspicion from said player's act?
  
• IF you don't fully understand how a traitor tester works, don/t threaten other players with death, especially if you are not a detective.  [and LISTEN when they are trying to explain it to you - how it works, that is]   Often in Minecraft for example, I have seen people do the "get in the tester" routine not understanding how it works.    Sometimes I was either nearly killed, or outright killed because I was refusing to go in, while trying to explain it to the guy HOW the goddammed thing ACTUALLY worked [resulting in, post-death, the spectators who know how it worked calling him a bloody moron].  It's even more annoying when we have a non-detective doing all the bloody work [AND he isn't a Traitor in the end.  When he IS a tater, it is just funny, and I laugh it as a well played charade, but when he ends up being inno, it is fucking annoying].
  
• We also, IMO, need some guidance on suspicion, what can be used to KOS some one, etc.  I mean, people KOS because of the "last seen" when it even says that the last seen is NOT necessarily the killer itself [logically true - what if that player was looked at while the person looking at said player was killed from behind, or by C4, etc?].  Also, KOsing because weapons match that somebody else was killed with, forced weapon checks by non-Ds [and even Ds] can get annoying too because, well, if somebody was killed by a shotgun, and a lot of people have shotguns, that'd either be a lot of taters, or that reasoning [matching weapon == tater] would cause a WHOLE LOT of RDMing.  Outside of obvious T weapons [silenced pistol, C4, etc] one should NOT KOS just because he has a weapon ANYONE can get, a weapon that there are plenty of in a map, and that weapon happens to be the same type that killed a non-T.
  

WS:

• Clarify / word a little better the 3/4 rule, and any rules about killing players.  Last night there was a LOT of confusion over when the speeding up of round's end needed to occur last night for example - and confusion about killing players.  Is it only allowed after that point, before, how soon after the round begins can players kill each other, etc.  Notably an argument between players that Hotgreen got involved in.
  My understanding was that you couldn't kill right as the round started, a few minutes in it was OK, and that when 3/4 or more of the people on the server were dead you had to speed it up, fight or suicide / whatever.  How far off was my understanding?
  

[Travelsonic]

n the gamemode or map is not allowed[/spoiler]

Rules of Stronghold

Spoiler (click to show/hide)

1. Spawn camping is allowed

Honestly, this is retarded, as are any justifications for it being allowed - as obviously they haven't been camped in SH before.

I mean, if there was more protection or preventive measures to keep it from being outright retarded, I'd be more inclined to be fine with it, but how it's set up now.... fuck no.

[Hotgreensoldier]

Honestly, this is retarded, as are any justifications for it being allowed - as obviously they haven't been camped in SH before.

I mean, if there was more protection or preventive measures to keep it from being outright retarded, I'd be more inclined to be fine with it, but how it's set up now.... fuck no.

He means spawn camping by custom put spawns. If you're getting spawn camped it's as easy as pressing ONE button to just go back to worldspawn.

[Shawn]

Honestly, this is retarded, as are any justifications for it being allowed - as obviously they haven't been camped in SH before.

I mean, if there was more protection or preventive measures to keep it from being outright retarded, I'd be more inclined to be fine with it, but how it's set up now.... fuck no.

Press "z" to remove your spawn, Problem solved.

[Goat]

Press "z" to remove your spawn, Problem solved.

>I place all my props AFTER the spawn point because that's how I roll
Delete base to stop spawn camp?

[jimonions]

Well if they were in your base spawn camping you wouldn't actually need it anymore right?

[Prox]

Honestly, this is retarded, as are any justifications for it being allowed - as obviously they haven't been camped in SH before.

I mean, if there was more protection or preventive measures to keep it from being outright retarded, I'd be more inclined to be fine with it, but how it's set up now.... fuck no.

>haven't been camped in SH before
Yeah, no.

Don't just go and assume that I don't know what I'm talking about, after all I'm not making this list only by myself.

[Travelsonic]

Sure, once you're on a team with a base, or hunkered down in your own area it is easy to avoid so far as personal/player spawnpoints are concerned, but I was talking about global spawn, and should have been clearer about that.   As others pointed out, there are still issues that need to be tackled - regarding stacking a spawnpoint, or even opponents building forts around the spawnpoints which while I didn't experience the latter last night, I wouldn't keep playing if that was a norm.

[also:  just so I'm not acting rashly, how fast does a player need to "snap" from one direction to another before being reasonably suspicious that said player may be aimbotting?  Just because I don't want to accuse anyone, and keep an eye out given how often SH seems to have issues with botters. ]

[Also: I was irritable last night wrestling my fucking Java programming class, assignment involving threads and deadlock while playing this]

[Shawn]

>I place all my props AFTER the spawn point because that's how I roll
Delete base to stop spawn camp?

This

Well if they were in your base spawn camping you wouldn't actually need it anymore right?

but I was talking about global spawn,

That isn't allowed call a VIP/admin to deal with people camping world spawns/ building bases on world spawns.

[Travelsonic]

The thing about the rule on page 1 of this thread, is that it doesn't seem to, to me anyways, distinguish between base / personal spawn camping, and global spawncamping.

Base/personal spawn camping I have far less of a problem with [given the mobility of said points] than global spawnpoints.

[Shawn]

The thing about the rule on page 1 of this thread, is that it doesn't seem to, to me anyways, distinguish between base / personal spawn camping, and global spawncamping.

EDIT READ WRONG

I Agree but some people disagree with me and feel world spawn is acceptable.

[Prox]

The thing about the rule on page 1 of this thread, is that it doesn't seem to, to me anyways, distinguish between base / personal spawn camping, and global spawncamping.

Base/personal spawn camping I have far less of a problem with [given the mobility of said points] than global spawnpoints.

Global spawn points are spread across and there is 5 second spawn protection so I do not think that it should be against the rules.

[Shawn]

so I do not think that it should be against the rules.

You may not but others do, some people just keep a sniper on world spawns and wait for others to spawn and theres not a dam thing they can do...

This is why i dont play SH anymore becuase as soon as i spawn i keep getting killed.

[Deacon]

Camping Global Spawns by means of entrapment or blocking: NOT Allowed.


There's my 2 cents.

[Travelsonic]

Global spawn points are spread across and there is 5 second spawn protection so I do not think that it should be against the rules.

Spread across, but the algorithm that determines where you spawn isn't rocket science to figure out by simple observation.

That and people still snipe at the spawn from before to right after the protection wears off, which means you could be running on a map where a spawnpoint is a decent enough distance away from any cade-able areas [relative to the protection time] where you can be running, not shooting, wears off, boom dead.  Unlike those who stand a the spawn, you can't just gun them down right then and there [well, exception being if you are being camped by a LOT of people on a team standing around a global spawnpoint].   In which case, I think protection time calculation should be a bit more complicated -> make it map dependent sorta -> the distance from certain types of locations is calculated into the number of seconds you are invincible, no less than 4, no more than 10, or something ALONG those lines.