Absorbing another civ's colonies...

[DrFell]

If you think about it though, that might be classified an act of war, as even though the people want to work for the nearby civ, it should not be their choice, as the reason they are there is due to the original civ placing the colony. One way or another they are traitors to the original civ, and the civ who accepted them could take blame too. Imagine if China had 'absorbed' Hong Kong in the days of imperialism. That is an example right there that would start a war. Same as if Spain absorbed Gibralter.

[kailhun]

Originally posted by DrFell
If you think about it though, that might be classified an act of war, as even though the people want to work for the nearby civ, it should not be their choice, as the reason they are there is due to the original civ placing the colony. One way or another they are traitors to the original civ, and the civ who accepted them could take blame too. Imagine if China had 'absorbed' Hong Kong in the days of imperialism. That is an example right there that would start a war. Same as if Spain absorbed Gibralter.

In those days looking at someone funny could be construed as an act of war. If your civ is looking for a fight, any excuse will do.

An act of war is something that causes a state of war to exist between two civs. A reason to start a war is something else. Absorbing a colony (even Hong Kong or Gibraltar) is a reason to go to war, but does not cause a state of war to exist between China and Britain respectively Spain and Britain.


Robert

[The Eliminator]

Hong Kong was a lease of Chinese territory, so you could hardly call it being "absorbed."

Gibraltar is more of what people are thinking with the colony problem in Civ. The British culture is very strong in Gibraltar, and the only way it could be "absorbed" is through force. If Spain occupied Gibraltar, I would argue that a state of war would exist between Spain and the UK.

Plopping a city beside a colony is an act of war, because the AI is forcing your colony to be destroyed. The gradual overtaking of a colony by culture expansion is not an act of war.

[Ironikinit]

I disagree that colonies are completely useless.

I may not use them every game, but they can be helpful after taking new cities and I don't want to wait for culture expansion, and they can also be helpful in mountains.

I think it would be nice if when a colony is absorbed the population of the city went up one.

[Drefsab]

Yes, I agree with Eliminator. Having your colony absorbed by another Civ's culture is fine. However, setting down a City next to a colony is claiming land that another Civ has already claimed. This is an act of war.

I noticed a comment up the page about sending workers around to all the strategic resources on the map. This cheese tactic is easily solved by the fact that a colony has to be connected by a road/harbor in order to be part of a civ.

[DrFell]

'An act of war is something that causes a state of war to exist between two civs. A reason to start a war is something else. Absorbing a colony (even Hong Kong or Gibraltar) is a reason to go to war, but does not cause a state of war to exist between China and Britain respectively Spain and Britain.'

True, but it's hard to imagine them not going to war over something like that. Taking a colony is basically stealing a reasource from the original colony owners. Perhaps absorbing a colony should be a reason to go to war without and kind of reputation hit (and make the AI likely to go to war also).

[Ironikinit]

Your argument would make sense if war broke out when cities flip. They don't, and it doesn't.

If it makes you mad, declare war.

[Libertarian]

Non sequitur. A colony is not analogous to a city.

[Grumbold]

I do not like the concept of colonies protected by military garrison being absorbable. While a unit enforces the fact that that tile is national territory it should remain so. If the unit marches out, fair enough.

A common arguement for the present conversion of cities regardless of military occupation is that the population, when roused, vastly outnumbers even a large army. Even if this were true for cities it certainly is not for colonies.

The whole cultural concept is interesting but IMO poorly implemented in Civ III. I don't expect much to change in forthcoming patches but hopefully it willl be thought through properly in any future Civ games.

[DrFell]

Originally posted by Ironikinit
Your argument would make sense if war broke out when cities flip. They don't, and it doesn't.

If it makes you mad, declare war.

So if the middle east cut off the USA's oil supply today, you're saying there wouldn't be a war? Look what happened when Japan got it's oil supplies cut off.

I don't build colonies generally so I've never had one absorbed, and I would indeed declare war if it happened. Having units in the colony should stop it being absorbed though.

[Grumbold]

What Civ III is lacking here is anything like the concept of a "Casus Belli" that is used in EU. It may well be that if Chicago revolts and wants to join Canada and Canada then accepts their appeal that war has not broken out. However the USA should have a right to declare war against Canada in the near future without the severe diplomatic penalties it would normally incur had there been no good reason for doing so. The penalties for unprovoked wars make starting them a very serious business. In Civ it is the USA that will be seen as the aggressor and treaty-breaker when Canada should be seen as at least equally guiilty.

[Ironikinit]

OK, for starters, the US doesn't have any colonies in the Middle East. Trade partners, yes, colonies, no.

The WWII Japan example: Uh, yeah, there was a war. The country that had its oil supply cut ran took the equivilent of the Civ 3 penalties because it declared war with bombs. Having it's oil supply cut was not considered an act of war. A provocation, maybe, but not an act of war.

Generally, the AI is easy enough to bait into declaring war. I don't find it so difficult to avoid doing so myself. Some AI behaviors become de facto casus belli, such as repeatedly trespassing. If the human player repeatedly tells its rival to leave, war will be declared in most cases. The casus belli rule was an interesting part of EU, tho, and could possibly adopted in another civ type game. I liked the bad boy rule, too.

[Libertarian]

Stop equivocating. Your analogy failed.

[kailhun]

Originally posted by DrFell


So if the middle east cut off the USA's oil supply today, you're saying there wouldn't be a war? Look what happened when Japan got it's oil supplies cut off.

There may or may not be a war. The US is pretty 'careful' about sending it's own soldiers into warzones.

But cutting off the US oil supplies doesn't cause a state of war. It is a reason for the US to go to war, but a declaration of war or attack is needed before a state of war exists.

So absorbing a colony is a reason to go to war, but does not cause a war by itself. I don't think there is any reason for this. If the absorbed civ decides not to do anything (for now), there is no war. I would prefer to keep this option to suddenly being at war over a colony I may not even care so much about.

It may lead to a souring of diplomatic relations. However this would have little effect in civ3 as the AI civs are generaly pissed at you anyway. And if you're pissed at them, you can effect this by ending trade agreements or denying them stuff. Of course this is not really an option as it is better to have the cash than useless luxuries lying around and if you deny the naughty civ a tech, but not the others, they will sell the tech in question to the naughty civ.
There is little else for it than to either decalre war or grin and bear it. Very realistic really.

I don't build colonies generally so I've never had one absorbed, and I would indeed declare war if it happened. Having units in the colony should stop it being absorbed though.

I think I build a colony once. It got absorbed, but a few hundred (?) years later I absorbed the empire. A fair trade, I think.

Robert

[DrFell]

'But cutting off the US oil supplies doesn't cause a state of war. It is a reason for the US to go to war, but a declaration of war or attack is needed before a state of war exists.'

Yep, but I'm not saying it should be auto-war because a colony was absorbed. It should just be considered an aggressive act by the AI and give the player some freedom to declare war without a damaged reputation.

'OK, for starters, the US doesn't have any colonies in the Middle East. Trade partners, yes, colonies, no. '

That's not the idea. The idea is that if you're going to cut off a country's supply of X, and if that item is important to them, then they are going to get pissed, and rightfully so, and possibly take action to get their supply back.