Poland is the navel of the world! xd!Poland has built in many cities watermill and nilometr, how is this possible?
(July 4, 1610 – Polish victory over the Russians in the Battle of Klushino. The road to Moscow opens.)
Last edited:
Poland is the navel of the world! xd!Poland has built in many cities watermill and nilometr, how is this possible?
This is literally the point of it thoughI full agree with this, either you promise and I think it last like 50 turns, way too long or you declare war from a suboptimal position and not being able to attack first. There should be a 3rd option, not making a promise but also not attacking.
Yeah, there should be a difference between those too. Like when you promise not to attack, then they should like you and trust you more, but feel betrayed when you actually attack them. Not promising should make them more catious.This is literally the point of it though
If the third option is "don't promise and set up to attack optimally" you might as well remove the whole thing because that's the obvious best option and it's no longer a choice (choices are the entire point of civilization)
I can attest it is from building barbican, I got it recenty, I had too much culture and my tiles were producing too much food in cities with barbican, I discovered nilometer which I used IGE for VP to get rid of in my cities and had to keep IGE to remove nilometers in cities I built later after building barbicans in them.I think its probably a lua error from a modmod. Iirc if adding a building fails for some reason, it defaults to the nilometer.
I know you aren't quoting me, but initially I brought this up specifically to address when a vassal forced me to either liberate them or declare war on them, which I didn't think was a good binary choice. I conquered them and they capitulated. I shouldn't be forced with a binary choice of "Free me or DoW me", rather it should be them declaring on me if they really want that. I understand why the promise not to attack or DoW on the spot makes sense for an enemy Civ, but not your vassal.This is literally the point of it though
If the third option is "don't promise and set up to attack optimally" you might as well remove the whole thing because that's the obvious best option and it's no longer a choice (choices are the entire point of civilization)
Ah yeahI know you aren't quoting me, but initially I brought this up specifically to address when a vassal forced me to either liberate them or declare war on them, which I didn't think was a good binary choice. I conquered them and they capitulated. I shouldn't be forced with a binary choice of "Free me or DoW me", rather it should be them declaring on me if they really want that. I understand why the promise not to attack or DoW on the spot makes sense for an enemy Civ, but not your vassal.
A vassal suspending tribute isn't really an act of aggression. It's up to the master to raise an army if they want to preserve it. I think vassalage is only really meant as a temporary arrangement before autocracy, and it carries the same negative connotations as warmongering which is why it's on the master to take the diplo hit.I know you aren't quoting me, but initially I brought this up specifically to address when a vassal forced me to either liberate them or declare war on them, which I didn't think was a good binary choice. I conquered them and they capitulated. I shouldn't be forced with a binary choice of "Free me or DoW me", rather it should be them declaring on me if they really want that. I understand why the promise not to attack or DoW on the spot makes sense for an enemy Civ, but not your vassal.
That seems like a fair compromise to me.A vassal suspending tribute isn't really an act of aggression. It's up to the master to raise an army if they want to preserve it. I think vassalage is only really meant as a temporary arrangement before autocracy, and it carries the same negative connotations as warmongering which is why it's on the master to take the diplo hit.
I do think a victorious war started by this request should allow immediate capitulation. That just seems like an oversight.
Fully agree with this. Just happened in my latest game and it was annoying.I know you aren't quoting me, but initially I brought this up specifically to address when a vassal forced me to either liberate them or declare war on them, which I didn't think was a good binary choice. I conquered them and they capitulated. I shouldn't be forced with a binary choice of "Free me or DoW me", rather it should be them declaring on me if they really want that. I understand why the promise not to attack or DoW on the spot makes sense for an enemy Civ, but not your vassal.
Doesn't matter since you get no warmonger penalty for it. I removed that some versions ago.I know you aren't quoting me, but initially I brought this up specifically to address when a vassal forced me to either liberate them or declare war on them, which I didn't think was a good binary choice. I conquered them and they capitulated. I shouldn't be forced with a binary choice of "Free me or DoW me", rather it should be them declaring on me if they really want that. I understand why the promise not to attack or DoW on the spot makes sense for an enemy Civ, but not your vassal.
Warmonger penalty is the least of my concerns really. It's the fact that my vassal can unexpectedly force a war on me, likely directly on my borders, and my only other choice in the moment is to liberate them. That's extremely annoying. Especially as it's a war they can't likely win, but will cause an extreme inconvenience for me. Maybe it should be that they ask for liberation, and if I deny them, there is a % chance that they will declare war on the spot. Why is the choice "liberate me or declare war"? The choice should be "liberate me or I might rebel". The two choices as it stand don't really make sense. I obviously crushed them hard enough for them to capitulate already. The war is already won.Doesn't matter since you get no warmonger penalty for it. I removed that some versions ago.
Fair enough. That's logical. It's still super annoying though. lol. But I guess it makes sense. I just wonder why I've never really had to deal with that before. I've had them DoW before, or complain about taxes. But never offer me the choice of liberate or DoW.From the vassal's perspective, it's one of the only ways of wielding leverage over the master, and the only way of being able to break free and resume the game. It's an intended drawback of vassalizing instead of just killing them.
If it really annoys you there's always DIPLOAI_DISABLE_INDEPENDENCE_REQUESTS in DiploAIOptions.sql.Fair enough. That's logical. It's still super annoying though. lol. But I guess it makes sense. I just wonder why I've never really had to deal with that before. I've had them DoW before, or complain about taxes. But never offer me the choice of liberate or DoW.
awesome! thank you.If it really annoys you there's always DIPLOAI_DISABLE_INDEPENDENCE_REQUESTS in DiploAIOptions.sql.
Added Elon's latest technological marvel to the changelog.- Removed Elon Musk as Great Engineer His engineering merits are in doubt. See: CyberTrucks, Twitter, Tesla Diner
Learn to not stack up on the border.Same with when a civ asks for a promise not to attack them.
I don't see why I should be forced to DoW them. If I refuse a promise, it's them that should DoW me if they so choose, or just live with it and fortify their border.
I'd also love an option to disable these promises altogether.