More on Scoopin not taking on Commodore:
Scoopin have a small tech advantage now, but once they have built some infrastructure and fully consolidated the Nakor gains, they will have a larger and growing tech advantage over Commodore. They are Vikings with circumnav, so they have complete control of the battlefield against all naval cities, the tactical initiative mentioned a few posts up. They have berserkers, and some that are well promoted. They can continue churning out berserkers and then upgrade them to amphibious rifles and utterly wreck someone who is technologically inferior, with little risk at that point and so be able to prolong the offensive without needing to build loads of new units. At that point, I expect the list of possible (though perhaps not likely, given other meta concerns like PB8 WW and psycho-commodore) victims to include Commodore. They would have time to preposition stacks of galleys (if they invest in a buildup for this type of exercise) and hit him in multiple places at once, perhaps cutting his empire in half by taking out interior islands. Or, they could do this to someone else if they determine that there are better gains to make against that opponent.
Much of what makes Commodore's land useful to him and his economy effective is monk buildings now and coastal cities + UB soon, both of which make his cities more valuable to him than they would be to Scoopin. His land is generally cottage heavy and food poor, so any attack that would hope to see benefit for the attacker needs to happen quickly enough to prevent Commodore from whipping away loads of food-poor cities from cottages that the attacker would want to work quickly, as well as limiting the swarm of eventual defensive units.
I'm not saying that Commodore would never be attacked by Scoopin, just that there are going to be better targets available for quite some time to come. And also, as mentioned, fighting Commodore is not fun for them. Razing a couple cities off mack is probably more fun. There's something to that too.
Scoopin have a small tech advantage now, but once they have built some infrastructure and fully consolidated the Nakor gains, they will have a larger and growing tech advantage over Commodore. They are Vikings with circumnav, so they have complete control of the battlefield against all naval cities, the tactical initiative mentioned a few posts up. They have berserkers, and some that are well promoted. They can continue churning out berserkers and then upgrade them to amphibious rifles and utterly wreck someone who is technologically inferior, with little risk at that point and so be able to prolong the offensive without needing to build loads of new units. At that point, I expect the list of possible (though perhaps not likely, given other meta concerns like PB8 WW and psycho-commodore) victims to include Commodore. They would have time to preposition stacks of galleys (if they invest in a buildup for this type of exercise) and hit him in multiple places at once, perhaps cutting his empire in half by taking out interior islands. Or, they could do this to someone else if they determine that there are better gains to make against that opponent.
Much of what makes Commodore's land useful to him and his economy effective is monk buildings now and coastal cities + UB soon, both of which make his cities more valuable to him than they would be to Scoopin. His land is generally cottage heavy and food poor, so any attack that would hope to see benefit for the attacker needs to happen quickly enough to prevent Commodore from whipping away loads of food-poor cities from cottages that the attacker would want to work quickly, as well as limiting the swarm of eventual defensive units.
I'm not saying that Commodore would never be attacked by Scoopin, just that there are going to be better targets available for quite some time to come. And also, as mentioned, fighting Commodore is not fun for them. Razing a couple cities off mack is probably more fun. There's something to that too.
We've had some embarrassing rollovers in this game, but here' a new low:
