#Mutiny Vote

1 messages · Page 1 of 1 (latest)

raw flare
#

Most commanders do a solid job but every now and then team's need an option to replace the current commander. There should be a yes/no vote where teammates vote on whether or not to mutiny against the commander. When a mutiny vote succeeds then the commander would return to FPS mode for the rest of that round. If a mutiny vote fails then it can't be called for some time.

barren marlin
#

I'm not sure if making the newly mutiny'ed captain a FPS would be a good idea. But kicking them wouldn't be good either? Maybe it forces them to the enemy team?

north eagle
marble moon
#

Alongside the other kick options maybe

barren marlin
#

Yeah but can they really be trusted?

oblique kernel
#

This sounds like something that would get griefed to no end if not implemented carefully and would lead to several issues as every player wants a different thing for the com to do, so everyone could have the justification to keep spamming the votes.

If it's essential to get a good com, have a vote for who the com should be before the round starts. Let people volunteer as coms with a short message and have the team vote during the 60-120 seconds before start.

#

Also, why would you want to kick/change team for the old com if they got changed just for playing bad?

thorn fable
#

Instead of kicking the commander out, vote to have him exchanged with another player on the team. Or create a poll of the current team members.
There should be a downtime for players that joined in recently, not allowing the rush of newcomers or opponent team griefing to take over.

marble moon
#

Concept of "Time in session" modifier for vote weight?

thorn fable
oak juniper
#

Surrender needs to be a team vote too.

marble moon
#

Psychological, no surrender vote, however a restart vote maybe. With also note of score will not be recorded on vote restart, for the maybe eventual toggleable server-side score keeper files/system.

obtuse yoke
north eagle
obtuse yoke
#

I don't like the idea of commanders getting kicked because they don't have a high rank or something.

Give the guy a chance to go to the other team possibly convince them to let him command and clap those traitors cheeks 😂

#

Give some story to the action and a con

north eagle
#

I don't like the idea of them being kicked for not following the super meta strat either but the FPS players need to be able to make up for some of that gap. there will be Aholes either way though.

tidal rivet
#

server option for this too, else new commanders will never get a chance

#

let alone if u host, only to get forced into fps mode

obtuse yoke
#

That's why I think a con would be good. Like we think this guy is bad but is he bad enough to justify giving Intel to the other team.

Alot of the time no

north eagle
#

some servers will be nice others not, new players can either find the nice one or start their own

north eagle
obtuse yoke
#

There should be a negative. You should only kick people who grief which likely won't be the commander

north eagle
#

but the whole ability would be a griefer move. actually kicking would be the less bad option. the point of this is to provide an alternative to kicking

obtuse yoke
#

The day I get kicked for a streamer to play commander is the last day I play.

north eagle
#

its not the game's fault streamers are Ducks.

frigid spade
#

plus if they start a nonsense vote to eject you, you sabotage them

#

fair's fair

#

vote ejection is an option in ns2, and most games it doesn't get touched

obtuse yoke
#

Anything but demoting and then kick if they grief or forcing team switch is just bad.. Nobody should get kicked just for playing the game in a way some other people don't like.

frigid spade
#

typically it's only brought up if the commander is straight up afk

#

presumably a vote to eject the commander would work like ns2

#

the commander is just no longer commander, but still on their team

#

and it was rare to see happen in ns2

obtuse yoke
#

That's better then just seeing all your work gone after 30 mins

frigid spade
#

even if a commander is bad most teams will just suck it up and play through if the commander is trying

#

for awhile at least

north eagle
obtuse yoke
#

I would be happy to tear down my own work as long as I can see it

north eagle
#

idk man seems like your cure is worse than the disease

obtuse yoke
#

If the commander is afk sending him to the otherside does nothing. If he is incompetent all your going to get is base location and a bad strategy that was changed five seconds later. If he was good just disliked then it was a team decision to give that asset to the other team.

north eagle
#

in all cases kick instead

obtuse yoke
#

No a good commander should never be kicked. A average commander should never be kicked

north eagle
obtuse yoke
#

No players game should be cut short for just playing the game

north eagle
#

if they at least get to be on the same team i think they would prefer that option

north eagle
obtuse yoke
#

Same team and a seperate vote to kick can be issued if he is butt hurt. Is the best option but anything is better then getting kicked for anything other then bad conduct

raw flare
#

What if the commander just had 40000 resources and was having difficulties managing everything? Not sure I would vote yes to kick them for that but if it just meant they were no longer commanding then I'd vote differently

north eagle
obtuse yoke
#

Exile them lol. If they get to the other team they join it.

Puts a pc bounty on there head like Gta 😂

No respawn can use any vehicle. Only other players can target him.

north eagle
#

also sub commanders are probably going to be a thing

inland plume
#

Mutiny sounds cool but is bad for morale in a team game.
Vote to "Relieve" Commander X with Player Y would be a more appropriate.

blissful kayak
#

This seems like a really low benefit for the amount of effort it would take to implement. There are so much the game needs and this is not one of them.

How often would vote kicks even occur? Why implement something for a problem that does not exist currently? Or at least, not exists in a substantial way?

I’ve played with new commanders that people grief at for playing sub-optimally. I’ve not played with a griefing commander, I bet most have not either.

This is like a post early access feature. If a problem occurs then, I’m sure people will make a feature request at that time.

frigid spade
#

in ns2 it was typically only used on a commander who was either actively griefing their team or who was demonstrably afk

#

a commander who wasn't playing perfectly was not considered a valid ejection candidate by anyone who wasn't a total dork

#

even if the other commander was running rings around them, being less skilled was not a valid reason to eject

blissful kayak
#

I’m not saying this feature request is bad as an idea, I’m just saying this should probably be reprioritized to the backlog.

Unless the Silica community ends up being filled with commander griefers that would necessitate this feature lol.

I’m gunna be upset if this comes out before, say, other core features like com QOL, keybinds, etc.

frigid spade
#

I don't disagree with that

#

commanders desperately need the QoL improvements that rts games have implemented

grand dawn
#

if you can kick the comm youll end up with an elitest group of tryhards even more than whats going to naturally develop, who will always kick their comms

#

ns2 for reference

frigid spade
#

that's only in the sweatiest of sweaty games and even then it has to be a serious comm diff in ns2

#

if it's a rando pub server then you have to be pretty much afk to warrant an ejection

#

and if it's a mega sweaty game then you should know what to expect going in

#

and what will be expected of you

candid falcon
#

Reviving this threat for an upvote -- after playing Silica for months I can say the community is fairly sensitive to commander skill and prefers not to have complete newbie commanders. Most folks are OK with coms that are learning as long as they've figured out the basics on their own beforehand.

It just wastes everybody's time to have your COM make 2x research facilities at the start, or spam crabs from the lesser spawners without making any shrimps for 25 minutes. With commanders that don't know the basics, half the players on the server are quickly subjected to getting stomped on by the other side with no tools to be able to fight back, which is not fun gameplay

pale wyvern
#

Mutiny Vote is a good idea. Maybe you only get 1 Mutiny Vote every 30 min, or give the vote a 30 min cool down. If the team is upset they cant just mutiny whenever they like. They have to be smart about who replaces the current COM. Biggest reason why I agree with this is because of COMs sometimes going AFK for 10 min while the team struggles to keep fighting. Absent COMs should be removed quickly and team shouldnt lose because COM is gone

scarlet latch
#

I think this is a good Idea for maybe ranked and afk coms but force removing a com just because hes new to the game or not good is bad for learning the game

pale wyvern
frigid spade
#

the answer is to treat commander ejection like a typical NS2 server

#

the option is always there, but it took active griefing or being afk to warrant it.

#

being inexperienced was never a valid excuse unless it was a high skill game with a new player sneaking into the chair.

half walrus
#

nah would make people not play

#

and by time u vote game over anyways cuz other team is ahead so no point

pale wyvern
#

maybe if COM goes through a period of inactivity there is an auto-demote feature. So if 5 minutes go by and no units were moved or selected, no buildings selected or built, basically nothing gets any interaction, then the COM gets auto-demoted to infantry. The feature can be selected or deselected by the Host when setting up the server. That way you can join a game with people who demand an active COM and people can join a more relaxed game.