Ladle 36 Voting Discussion

[PokeMaster]

I considered that durka, but I think it's too dangerous that some random spectator will join and cause too many problems. Teammates can be slow to join (the create new team), as I've seen in the past doing tourneys/organized matches.

This could work though, with something like access_level_play 8, and have all members of a team oped by their team captain. This would eliminate the possibility of a random spectator joining. The only potential problem would be somebody from the opposite team joining your team (most likely by accident, if the two teams unlock at the same time).

[apparition]

As for fast team switching, this is how you do it!
...

What is the real solution from the developers' point of view?

Durka's isn't a solution at all. It's a workaround that is counterintuitive and damages the flow of the game (especially by losing the recording of a player's points). The only pro it has is that it might work. I don't know, I haven't tried it. Are there other options we could pursue? Another work around I thought of is to give each team an extra slot for subbing people in and out through. Obviously making sure 7 people aren't on the grid might be a challenge at first, but as long as one player specs and one joins, it shouldn't be a problem.

And unless there's a confounding variable I'm missing, I'm not sure the subbing issue is consistent between servers. In G5's server I had the option to "Join CTa" and in CT USA I could only "Create a new team", which in itself is a pointless and confusing option for the system to have when there's only 2 teams - a flaw in the program if you ask me. At all times I was invited because I was chatting in /team with CTa.

Everyone knows about the subbing issue I take it, right? Does this issue warrant its own discussion to come up with some options to how to solve it? I'd like to see a vote to solve this issue with multiple solutions though: 7 slots, durka's method, a developer's solution, etc.

[DDMJ]

It's worked every time I've executed it. You just have to make sure your teammate is paying attention and not AFK .

[epsy]

Well this would have worked since forever O_O
1/ Sub selects team
2/ Player on the team types /teamleave (but NEVER does so before seeing "sub wants to play for Team gold on the next respawn.")
3/ Players swap cleanly

The shuffle issue is indeed a problem. For the moment I think it could be solved by having teamswitches done after grid is destroyed, have a one second pause after, then have a chat break, then have the players spawn.

[DDMJ]

Yes, that works epsy, but the only current way that, potentially, barring any intruders, allows players to join AND shuffle is the roundabout method I mentioned above.

[apparition]

What about the 7th slot? And what if you or your mate don't have the option to join the team? Like I said, I could only "Create new team".

[Z-Man]

Well, the most comfortable solution would probably be a /sub chat command the invited substitute can invoke to immediately take the place of someone without affecting the positions of the other players.

Needless to say, the 'create new team' option shouldn't be there. What were the client and server versions?

[Word]

it would be cool if there was a possibility to freeze the scores (or even the players) and to spawn a new player on the position the person who just left had. then we could take breaks whenever someone gets disconnected

[noob_saibot]

Disciplinary action? What is this kindergarten?? Admins should get their shit together, and team leaders need to wake up. If they don't realize or know they have an "imposter" on their team, then they are probably not in any position to "lead" that team. That is just mad dummy. And some "imposter." The person admitted it but a few days later, its a joke. That is not an "imposter," it's just plain "stupidity" on the teams part.

[Z-Man]

Word: taking breaks during the action is sort of possible, the FULLSCREEN_MESSAGEs do just that. But you know how confusing it can get. Sure, we could add a countdown to the restart, but there would still be complaints by the other team that wahwahwah, the break killed one of them and it's unfair, and actually transfering cycle control to a new player would be difficult, and all that to solve a relatively rare technical problem.

Disciplinary action? What is this kindergarten??

Sometimes, it appears to be.

Appa: authentication solves the impostor problem, or at least the blame problem. If you give me your login data and I imposter you, then it's your fault. If I manage to enter a team any other way, it's the fault of the player who let me in. Against playing in two teams, nothing can ultimately be done: smurf accounts and IP changes can hide your true identity. But have you ever play with an anomymizer active? You don't want to in a competition. And you need to convince a team to take you with your new forged identity in the first place. But again, the blame problem is solved: if one player is on two teams with the same ID, it's the team captains' job (IF the global ID is part of the registration on the Wiki) to find out, and if I actually make the effort to create that second ID with a second good enough reputation to get on a team, then I'm clearly the stupid kind of evil and need to be banned to the deepest level of hell.

[apparition]

Okay, I see how it solves the impostor problem. I was just thinking ahead to the dastardly deeds I wouldn't be surprised someone would do...

Well, the most comfortable solution would probably be a /sub chat command the invited substitute can invoke to immediately take the place of someone without affecting the positions of the other players.

Needless to say, the 'create new team' option shouldn't be there. What were the client and server versions?

Server I believe this happened in was CT USA (but it may have been G5's Ladle server) - not sure what versions they're running. Client was 0.2.8.3

[PokeMaster]

Fullscreen_message in the middle of a round sounds like a terrible idea. That could kill people in tight spots, because they don't know when the round will be unpaused.

[Cody <3]

As for fast team switching, this is how you do it!

I thought you could do this?

/lock (when u get 6 players)
/invite player 7(ur sub?) he cant join cause you got a full team.

player 7 clicks "join home team"

"player 7 cannot currently join home team(get this for about 5 rounds blah blah)

okay player 2 has got to go do sumthing "exits tron after round)

player 7 now joins the team

EH?

[sinewav]

The shuffle issue is indeed a problem. For the moment I think it could be solved by having teamswitches done after grid is destroyed, have a one second pause after, then have a chat break, then have the players spawn.

So, a combination of using EXTRA_ROUND_TIME and PLAYER_CHAT_WAIT can create a window for players to sub in/out and shuffle? It looks like it would take some coordination and attentiveness from the switching team, but perhaps this is a type of "Fortress skill," much like grinding and ganking.

I'm all for making a system for players to substitute effectively. Can it be solved and worded in a way we can vote on it using our current methodology?

[DDMJ]

Fullscreen_message in the middle of a round sounds like a terrible idea. That could kill people in tight spots, because they don't know when the round will be unpaused.

It would be used before the round starts. I hate it though. It always makes me think my client crashed.

As for fast team switching, this is how you do it!

I thought you could do this?

/lock (when u get 6 players)
/invite player 7(ur sub?) he cant join cause you got a full team.

player 7 clicks "join home team"

"player 7 cannot currently join home team(get this for about 5 rounds blah blah)

okay player 2 has got to go do sumthing "exits tron after round)

player 7 now joins the team

EH?

Nope, that doesn't work because they won't be able to shuffle before the next round starts.