Declined [JB] So about these LR chains (1 Viewer)

[Musisphaera]

the best course of action is for a group of REDs to form a team and attempt to take down the LR winner to end the chain.

*cries in "hg no teaming"*

Anyways, I was initially against it, but I've become a bit burned out because of the same lr's being done over and over again. I don't mind having a chain for a few rounds, but at a point you just become bored and just wish to do different other minigames. IMO it takes the uniqueness of the LR away too.
As crubf already said, as those are my thoughts exactly:

chaining LRs kills the vibe of the server and makes me just want to go do anything else besides JB.

Having it be decided by the warden/majority vote though would be the most helpful (and with votes: more democratic way) to decide the chain.

 

[SirKrookodile]

sureeeeee

Bugs please refrain from toxicity on the forums.

Anyways, it's a bit of a decisive thing. Like sure, you can always cause a fail round or just win lr to end a chain. But there are select cases where that's virtually impossible. Where certain bad actors have the sole goal of killing the servers vibe just by making an LR that's impossible for everyone except themselves are able to win. Sometimes being able to step in and just put an end to it is the best course of action.

 

[Madact]

If you all are going to go down this route, at least make the rule not as complicated as what calassic has proposed. It's too much in my opinion. Even the voting version.

Something along the line of what crabf stated; no repeat last round LRs or no repeat last round with FF LRs. Then you get your variety of FF and non FF rounds.

 

[Walter Black]

Me when I'm just too good at the game so I keep winning LR and I get punished by having my LR denied

 

[_Black]

Cellwars chains are bothering me way more, but thats for another time.

 

[Bananawastaken]

In my opinion there is no point to getting rid of LR chains, if a red earns it they earn it. You're effectively punishing good players, why curb bad actors thats not the point of the rules.

Thing is it’s always been abused by annoying people, nobody said anything when old groups of regulars would spam HG chains or speedrun all day!!! This suggestion just screams reactionary, either suggest to reduce the plugin cap on custom LRs, or suck it up.

Weird conditional rules like this are the antithesis to panda jb, I want to preserve panda as something that is clean and free of the headaches of other communities.

 

[Eagle_attack]

Instead of complaining about LR chains why don't you find a way to stop the person from winning the LR and strategize with your fellow RED teammates and find a way to kill the RED constantly getting the LR? (Honestly sounds like a skill issue)

Couldnt explain this better. and with the Others LR's ( hns , meatgrinder...) just kill the warden lol
I do get bored after the 4-5th hg,

 

[Cowboy]

Original idea seems a little convoluted for my tastes, I agree with madacts simplification.

Pretty unfortunate it even has to come to this.

 

[SirKrookodile]

another alternative I think could work would be limiting restrictions on lrs to like a max of two restrictions chosen by the lr recipient. Which hardly affects most lrs, just prevents certain bad apples from chaining stuff like "HG in main cell, reds must be crouching teaming allowed no medic room" which just heavily favours a soldier(whip)/demoman(skullcutter) + medic combo. But at least allows for the average lr choser to still go for things like hg no teaming no medic room. It doesn't prevent chaining entirely it just prevents certain bad apples from chaining lrs that just completely remove the chance of any other player winning.

 

[ItsNotCalassic]

View attachment 32701

Well, I got messaged by a bunch of individuals and spoke with a lot of people, it seemed to be an issue.

In the context of *that* suggestion, it was to completely restrict HG to have a specific LR option, which ruins any chance for custom rulesets and such.

My suggestion is in regards to ALL custom LRs. I believe now it is selfish or inconsiderate to assume everyone can play the gamemode as well as we all here like to think. There are people who have played this gamemode for years that still suck at getting LR but still play the gamemode because they’re having fun. What isn’t fun is potentially 40min map rotations of HG, or HnS, or do obby backwards.

Each map has so much to offer as well as there being so many other LR options included that get ignored.

I do have an idea to suggest at least a hard limit on Custom LRs per map rotation. We already have hard limits on other types of LRs, if anything it would be a high number, perhaps 4 max per map? I’m not sure what the reception would be given this suggestion.

And to point out because nergal didnt copy the last message when he edited this. I’m 100% aware this was gonna be a suggestion that will fail, but I sorta wanted it to be a place where people can point out their frustration in a easier to see matter unlike that of a discord channel.

 

[Fairbee]

Be honest, LR CHAIN is most boring thing

doing HG in 5 rows is the most boring
mostly people will leave the server just bc of that

 

[baby]

the decision to start the vote by the current warden can be easily abused or not even known at all. groups of people can choose to never start a vote in the first place to deny the chosen LR bypassing this rule completely while still being “technically allowed”.

 

[Plot Twist]

I don't see why it would matter if Jose.Barnacle.2015 didn't know about the warden vote, it's more about 5 people in discord healing one demoman for 3 rounds in a row in HG until someone goes blue, forces warden, and starts a /wvote and asks "you guys still wanna do HG?" I don't see how this became so complicated

 

[BritishMafia]

Instead of this, custom lr option needs a limit, it would stop chains. Everyone was practically begging for a limit to be added while I was playing just now, we were stuck in a cargo spinner chain.

 

[Eagle_attack]

Instead of this, custom lr option needs a limit, it would stop chains. Everyone was practically begging for a limit to be added while I was playing just now, we were stuck in a cargo spinner chain.

I kinda agree with this

 

[zevs]

pros
democracy now added to jailbreak
haters can now hate with valid reasoning

cons
if this was added, 50% of the playerbase would drop (probably)
most people pick custom LR for THIS reason
no karts first to finish chain
no hg chain

 

[Fairbee]

Instead of this, custom lr option needs a limit, it would stop chains. Everyone was practically begging for a limit to be added while I was playing just now, we were stuck in a cargo spinner chain.

it's someone who did 2 times comb by guy "warden [more sweeper please!]" most times he does do these chains

 

[zevs]

we were stuck in a cargo spinner chain.

is this possibly, a skin tissue? brother just jump

 

[scootyman]

I was a little confused at the earlier replies, but now I see that the edit to the og post was to change it from a warden decision to a server decision through a warden vote. Yet after giving it some thought, I still would rather not introduce another "exception" type rule (a rule based around modifying another rule in certain situations).

The least fun state of jailbreak is not when a troll is deliberately breaking the rules, or super unbalanced teams, or waiting the whole round for the blus to find the 1 fugitive red preventing hopjb prophunt from starting, or hg chains. It's server-wide quarrels over the rules, at least in my eyes. A new rule should stay true to panda jailbreak's unique simplicity compared to other servers. For example, I think the freelooking rule change was the best outcome of the "change the afk rule" revolution. Wardens still give the exact same orders, but now reds are ALWAYS allowed to freelook. It's super simple to follow. I'm pretty uneasy about adding more LR-related rules, since they seem to be the most common source of arguments. Some examples:

• myth that you MUST redo a denied lr
• myth that you CAN'T redo an attempted lr even if it's not lr only
• what does it even mean to "attempt" an lr?
• are a "denied lr" and an "unattempted lr" the same thing?
• does doing climb first to finish satisfies a "climb all day" lr?
• nobody agrees on what classifies a "rule" versus a "restriction"
• to what level can the lr recipient alter the lr after the next round starts? (approving/vetoing warden's added rules, adding their own rules, defining what their gibberish lr like "facebook day" actually means)

and many more. And I can already see how this rule could cause arguments:

• If hg is denied and then redone the next round, does that reset the chain and allow for a guaranteed 3rd hg without warden vote intervention?
• If warden is killed after giving lr, are guards allowed to rewarden to initiate a warden vote for the lr chain?
• If the lr recipient was the last red, could they not just continue the custom lr chain and immediately slay to end the round before the warden could start a vote?
• Suppose the lr chain is just a difficult minigame that 1 red keeps chaining because they're good at it, the warden of this round calls a vote and the majority votes to choose a new lr. The red slays as mentioned above, starting a new round with the same chained lr. The warden on this new round could STILL continue the lr chain since it's not an lr-only minigame.

Hg chains are easy enough to break that I think this rule would introduce more chaos than order.

 

[Cowboy]

I think it's fairly certain that we as a community aren't really fans of a vote procedure but I think we got some solid ideas on how to combat this sort of behavior.

Scootys mention about ensuring that the rules are simple is the exact reminder that we needed. With classics permission, I think we should reformat the poll to some of the ideas suggested and see where as a community we stand.

Personally I think the easy solution to this problem is to simply not allow custom lrs to be the same two rounds in a row and call it a day. Incredibly easy to remember and doesn't punish players who want to do interesting custom lrs by restricting the amount per map.