Topic: Definition of player defeated

The problem with 1) is that there are still more cornercases that will then surface. E.g. if you have no warehouses left but a functioning economy with woodcutters, sawmills, … you can still produce everything to build a new warehouse. (A builder could be kept in "storage" at a disconnected constructionsite.) So we'd also need to periodically destroy all WH csites, and there might be even more loopholes to be found…

IMHO the cleanest way would be a C++ change. Let's have a new function Player.mark_as_defeated() that irreversibly turns the player into a real spectator, rather than faking this mode with see_all, and disallowing all playercommands so the player won't be able to do anything at all ever again during that game.

Top

Quote

king_of_nowhere wrote:

i would opt for 2: leave him not defeated. in general, a defeated player can also still send attacks while he has still soldiers available. I'd just declare them not defeated.

If he is defeated, he currently can't launch an attack anymore. That should not be changed. Furthermore we need a definition of defeated for our winconditions and scenarios. So do you vote for 2 (not defeated if able to build a new warehouse / port) or do you propose a third option not defeated until alll warehousess and all militarysites lost?

Top

Quote

hessenfarmer wrote:

king_of_nowhere wrote:

i would opt for 2: leave him not defeated. in general, a defeated player can also still send attacks while he has still soldiers available. I'd just declare them not defeated.

If he is defeated, he currently can't launch an attack anymore. That should not be changed. Furthermore we need a definition of defeated for our winconditions and scenarios. So do you vote for 2 (not defeated if able to build a new warehouse / port) or do you propose a third option not defeated until alll warehousess and all militarysites lost?

not defeated until all warehouses and all military sites lost.

actually, i would support different definitions for different cases.

I would leave the current definition for AI scenarios.

change to "all warehouses and all military sites" for human vs human. actually, i can still envision a case where a ship in expedition, and some drifting ships with some wares, could restore a full economy. and if we establish trading resources, then one could still give a contribution while defeated. in fact, i'd be in favor of removing the "defeated" status entirely among humans. i mean, it's pretty clear when someone is defeated, i don't see a need for the game declaring it.

and i'd add a win condition to kill the headquarter for seafaring maps, when you cannot conquer all the islands.

Top

Quote

Nordfriese wrote:

IMHO the cleanest way would be a C++ change. Let's have a new function Player.mark_as_defeated() that irreversibly turns the player into a real spectator, rather than faking this mode with see_all, and disallowing all playercommands so the player won't be able to do anything at all ever again during that game.

I think it's the best thing to do, let the players accept themself the defeat if it's obvious.

hessenfarmer wrote:

1. if the last completed warehouse (this means HQ, Port and Warehouse) is destroyed, destroy all constructionsites of warehouses as well. Leaving the defeated player really a spectator (only thing he could do is dismantling/desztroying buildings)

And the 1) is a good option too.

Top

Quote

Sounds good to me

Top

Quote