I'm pretty sure that wonderland does. Dont know about the others thoJust going to throw this in here as I'm curious:
If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
Feel free to list pros and cons on this.
Also I saw flux uses !fire. Does anybody know any other jb communities that use !fire?
God if we could reduce it to 1 that would be a godsend.Just going to throw this in here as I'm curious:
If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
Feel free to list pros and cons on this.
Also I saw flux uses !fire. Does anybody know any other jb communities that use !fire?
Ehhhh?If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
Feel free to list pros and cons on this.
I think wonderland (EW) and I think, sg-gaming.net uses it (Freddie tf2 server) And that's the only servers that I THINJust going to throw this in here as I'm curious:
If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
Feel free to list pros and cons on this.
Also I saw flux uses !fire. Does anybody know any other jb communities that use !fire?
Decreasing the force count is cool and ok but adding !fire with it makes it a bad apple.
If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
I can safely say like a majority of popular jailbreak communities have the fire command.Also I saw flux uses !fire. Does anybody know any other jb communities that use !fire?
This feels like a partial fix. They can still be warden via the random selection and it’s not uncommon to have these random intervals where someone gets warden randomly 2 or 3 times in a row.If the limit of forcewarden was reduced to 2 or 1, would this be a better solution than introducing !fire ?
Feel free to list pros and cons on this.
hmmm maybe we should look back at to what was said previouslyI'm changing my vote to hell yes after dakota is on the server
what Xergon said sounds exactly what freekilllord predicted, its going to be 'I don't like this person so I dont want him to be warden no matter what' unless you want to elaborate further Xergon, because it sounds like you just don't want this one person to be wardenI feel like it would lead to mob lynch mentality:
*Young person with high pitched voice gets to be warden*
"CRINGE LITTLE KID GET OFF WARDEN LMAOOO EVERYONE DO !FIRE !FIRE !FIRE !FIRE !FIRE!!!!!!!!11!!1"
And then the person next to him gives in to his words and so does the person next to that person, and they peer pressure each other until the new warden is fired without even commiting a mistake
*New warden gives an order in understandable yet foreign accented english*
"NEW WARDEN IS TALKING IN MINECRAFT ENCHANTING TABLE!!!!!111!! EVERYONE !FIRE"
and then the same happens...
"But we need to stop bad people from ruining the experience, so it would be good to be able to fire them!"
No, If they want to disrup the experience they can go sniper with machina and impale all reds, not being the warden isnt an impediment for griefers as far as they stay as guards
"It would stop annoying wardens from spamming the same minigame every single round"
It will also deter them from coming with creative ideas of minigames (it can be done without freekilling) like tag death match in mine field.
why would wardens risk innovating when people could fire them for not following expectations? (that are separated from the rules).
Instead it would break the role play of warden gives ordes - reds receive, as they could held the warden at gunpoint to please their pleads of a specific minigame, which could cause minigame spam but in a more horrible way, aka: !fire threats
It is beautiful when a warden wholesomely communicates with the reds and tries to do what is better for the majority, but if he wants to play bad guy and send them to a minefield trip he is in his right to do so.
If reds dont like bad but legal warden they can bash him over the head with their melees (not always works, this is a role-play full of possibilites)
If reds dont like bad & illegal warden they can call adam
But giving reds a tool to threat the warden out of his possition?, which is out of role, thats some cartel boss giving orders to the prison guards meant to keep him jailed kind of s***.
.....................
Also people who get !fire abused will grow bitter towards the reds.
And out of that hate new mass freekillers will be born.
I was on at the same time as Xergon when Dakota was warden. Dakota was a warden who forced three times in a row and got killed by rebellers early in the round each time he forced.what Xergon said sounds exactly what freekilllord predicted, its going to be 'I don't like this person so I dont want him to be warden no matter what' unless you want to elaborate further Xergon, because it sounds like you just don't want this one person to be warden
is he purposefully trolling as warden? or is he just bad?I was on at the same time as Xergon when Dakota was warden. Dakota was a warden who forced three times in a row and got killed by rebellers early in the round each time he forced.
It's not just some "cringe little kid" or somebody doing a bad minigame, it's a player making the game not fun by purposely forcing warden, and being bad at it. This is one of the biggest reasons people have been in support of the !fire command if you read previous comments on this thread, including those from Xergon.
Also yes this problem would also be solved by lowering the number of forcewardens to 1 or 2 per map. Go vote for that suggestion, it's probably a better solution to the same problem.
OH COME ON THATS BULL SHIT! I was there longer and the first first ever time he got fucking warden every one let him die all the blues including you. You guys said, "KILL WARDEN KILL WARDEN." @scootyman was the only person killing the reds so don't say bad warden when all of the blue team being inactive and saying he is a bad warden you and the blues DO YOUR FUCKING job and protect him OR get reds instead of holding your dicks 24/7. Or just making fun of him because he is a kid like me. Every time he fucking TALKS THE blue team says, "SHUT UP SHUT UP." Like STFU leave him alone if your gonna report people breaking rules maybe you should stop "breaking the rules."I was on at the same time as Xergon when Dakota was warden. Dakota was a warden who forced three times in a row and got killed by rebellers early in the round each time he forced.
It's not just some "cringe little kid" or somebody doing a bad minigame, it's a player making the game not fun by purposely forcing warden, and being bad at it. This is one of the biggest reasons people have been in support of the !fire command if you read previous comments on this thread, including those from Xergon.
Also yes this problem would also be solved by lowering the number of forcewardens to 1 or 2 per map. Go vote for that suggestion, it's probably a better solution to the same problem.
I feel silly arguing in a suggestions thread but I feel forced since you are accusing me of mic spamming and being an in-active guard.OH COME ON THATS BULL SHIT! I was there longer and the first first ever time he got fucking warden every one let him die all the blues including you. You guys said, "KILL WARDEN KILL WARDEN." @scootyman was the only person killing the reds so don't say bad warden when all of the blue team being inactive and saying he is a bad warden you and the blues DO YOUR FUCKING job and protect him OR get reds instead of holding your dicks 24/7. Or just making fun of him because he is a kid like me. Every time he fucking TALKS THE blue team says, "SHUT UP SHUT UP." Like STFU leave him alone if your gonna report people breaking rules maybe you should stop "breaking the rules."