Hi Boards,
I have an indea that would squish a pain in the buttocks for me. When plyers drop out of the game, the CPU takes over. Fair enuff.
But this is sometimes annoying and can lead to one sided diplo games in particular.
Why not have the server option to DISABLE players that drop? This would make diplomatic alliance voting more meaningfull when you have 2 or more droppers, and prevent players hiding behind CPU shields...
Just a thought...
RO
Idea for Dropouts
Moderator: Defcon moderators
- Red October
- level1
- Posts: 12
- Joined: Fri Nov 10, 2006 8:40 pm
Re: Idea for Dropouts
Red October wrote:Why not have the server option to DISABLE players that drop? This would make diplomatic alliance voting more meaningfull when you have 2 or more droppers, and prevent players hiding behind CPU shields...
How would you do that? Are you going to prevent them from unplugging the physical cables? Or turning off their computer? Or unplugging the power from their computer? There is no way to keep people from dropping. The best that you can do is minimize the impact of them dropping. With that in mind, it seems that you are bringing up two issues:
1) When the host quits, the server dies, and the game ends. This, I agree, is a problem. It has been talked about quite a bit on the forums, and I think that the consensus is that one of two things should happen. Either IV should release a stand alone server, so that people can host without playing (personally, I don't much like this option) or IV should allow Defcon to pass the power of server onto another machine if the original host quits. Unless you can think of something else, I think that pretty much covers that topic.
2) In Diplo games, people can hide behind the CPUs when people quit. I agree, this is a problem. In diplo games that I play, I insist that any player that drops is immediately kicked from the alliance. However, I have been burned by teams of people allied to CPUs. I think that the solution is to automatically kick CPUs from any alliance when a player drops. This is not an ideal solution, but I think that it is better than the current situation.
xander
I had thought much the same thing, that is, how useful it would be if when a player drops and the CPU takes over it automatically withdraws from the alliance. That should be automatic, except of course if no defection is enabled.
A more interesting additional option that perhaps one could enable would be not only does the CPU player leave the alliance, but it joins that of any existing CPU players for others who dropped.
That might have a negative effect on the dynamics, I don't know. Since most players who drop do so because they are severely weakened (often misjudged because I've seen many come back at the end and/or others drop below them), it would balance out against the other players who might be forced into some uneasy cooperation in dealing with several allied CPU players while still fighting it out (or planning to fight it out) among themselves. That would certainly turn it into a different game if several people leave, but it might still be interesting - so certainly this would be an optional setting. On the other hand, as it is, games currently are much less fun after several players leave.
A more interesting additional option that perhaps one could enable would be not only does the CPU player leave the alliance, but it joins that of any existing CPU players for others who dropped.
That might have a negative effect on the dynamics, I don't know. Since most players who drop do so because they are severely weakened (often misjudged because I've seen many come back at the end and/or others drop below them), it would balance out against the other players who might be forced into some uneasy cooperation in dealing with several allied CPU players while still fighting it out (or planning to fight it out) among themselves. That would certainly turn it into a different game if several people leave, but it might still be interesting - so certainly this would be an optional setting. On the other hand, as it is, games currently are much less fun after several players leave.
- Red October
- level1
- Posts: 12
- Joined: Fri Nov 10, 2006 8:40 pm
I think that would have a lot of downsides if game assets suddenly disappear. If I'm moving my subs or bombers against target cities or even have multiple nukes on the way and suddenly the player disconnects, I would be out of luck. This is true in default scoring and especially genocide mode. I'd hate to see a player lose most of his silos and radar, then disconnect. Suddenly, the player who went to all the trouble to eliminate the defenses gets no reward if they have follow-up nukes ready to go.
If their cities remain and all their military assets disappear, then again it gives an advantage to whomever is firing at them already or their nearest opponent, who can now attack defenseless cities. If the cpu remains in 'defense only' you just have the original problem again with it acting as a shield with neighbors not having to worry about attacks.
So some sort of cpu has to remain or it just creates a negative game dynamic in some other fashion. The best solution has already been suggested, that of making the cpu withdraw from any alliances.
We don't want anyone to benefit from a cpu player, which is the current problem, so having the cpu withdraw from any alliances solves it since unless no defection is enabled, the 'alliance' would eventually break apart anyway. Having the computer break the alliance as opposed to another player keeps the normal flow (as much as possible) of the game going for the remaining players.
If their cities remain and all their military assets disappear, then again it gives an advantage to whomever is firing at them already or their nearest opponent, who can now attack defenseless cities. If the cpu remains in 'defense only' you just have the original problem again with it acting as a shield with neighbors not having to worry about attacks.
So some sort of cpu has to remain or it just creates a negative game dynamic in some other fashion. The best solution has already been suggested, that of making the cpu withdraw from any alliances.
We don't want anyone to benefit from a cpu player, which is the current problem, so having the cpu withdraw from any alliances solves it since unless no defection is enabled, the 'alliance' would eventually break apart anyway. Having the computer break the alliance as opposed to another player keeps the normal flow (as much as possible) of the game going for the remaining players.
Re: Idea for Dropouts
xander wrote:Red October wrote:Why not have the server option to DISABLE players that drop? This would make diplomatic alliance voting more meaningfull when you have 2 or more droppers, and prevent players hiding behind CPU shields...
<insert predetermined rant here>
xander
Fixed ;)
Re: Idea for Dropouts
KingAl wrote:xander wrote:Red October wrote:Why not have the server option to DISABLE players that drop? This would make diplomatic alliance voting more meaningfull when you have 2 or more droppers, and prevent players hiding behind CPU shields...
<insert predetermined rant here>
xander
Fixed ;)
Oh, come on! My second point was pertinent!
xander
Re: Idea for Dropouts
xander wrote:Oh, come on! My second point was pertinent!
xander
I suppose you're right. After all, nobody expects the Spanish Inquisition.
Re: Idea for Dropouts
KingAl wrote:xander wrote:Oh, come on! My second point was pertinent!
xander
I suppose you're right. After all, nobody expects the Spanish Inquisition.
NOBODY EXPECTS THE SPANISH INQUISITION!
xander
Who is online
Users browsing this forum: No registered users and 6 guests