Project

Profile

Help

HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...

Feature #875465

Post activity Casus Belli

Added by Sveinung Kvilhaugsvik about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Category:
General
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

"Pillage" currently triggers the Casus_Belli_Success effect when the activity begins. Introduce Casus_Belli_Complete that it can trigger once the activity is done.

If you think Casus_Belli_Successful_Beginning on activity start and Casus_Belli_Success on activity completion makes more sense it will probably be easy to convince me to replace Casus_Belli_Complete with Casus_Belli_Successful_Beginning.

0018-Post-activity-Casus-Belli.patch (8.12 KB) 0018-Post-activity-Casus-Belli.patch Sveinung Kvilhaugsvik, 2020-05-28 08:13 PM

Related issues

Related to Freeciv - Feature #874197: Make Casus_Belli_Success support pillageClosed

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Related to Freeciv - Feature #873295: Casus_Belli_Success for all actionsNew

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by Sveinung Kvilhaugsvik about 2 years ago

#2 Updated by Sveinung Kvilhaugsvik about 2 years ago

  • Related to Feature #874197: Make Casus_Belli_Success support pillage added

#3 Updated by Sveinung Kvilhaugsvik about 2 years ago

#4 Updated by Lexxie L about 2 years ago

Hey, I like this feature in all its forms, it solves a lot. Here are some thoughts.

Both options leave a ruleset designer some more room I guess.

When the action begins, causing casus belli can make sense because it allows you to retaliate to prevent the actual pillage. BUT it makes a potential problem that a missed key would cause diplomatic chain reactions. I guess it's not going to happen often enough to worry about, or justify coding a 1 minute delay or something like this.

Thanks for this feature. Sometimes the smallest things like this end up being huge!

#5 Updated by Sveinung Kvilhaugsvik about 2 years ago

Lexxie L wrote:

Hey, I like this feature in all its forms, it solves a lot.

I'm glad to hear it.

BUT it makes a potential problem that a missed key would cause diplomatic chain reactions.

On the other hand you risk an incident against the tile's new owner with Casus_Belli_Complete if you forget to cancel a pillage after a tile owner change.

#6 Updated by Sveinung Kvilhaugsvik about 2 years ago

  • Status changed from Resolved to Closed

The version that went in allowed the post successful activity start Casus Belli to keep the name Casus_Belli_Success and gave the name Casus_Belli_Complete to when the activity is done. If you think that the post activity Casus Belli should get the Casus_Belli_Success name and the post successful activity start Casus Belli should be the one to get its own name please file a feature request (or bug report) before the 3.1 data file format freeze. The important thing about the effect naming is that it is logical from a ruleset author's point of view.

Lexxie L wrote:

I guess it's not going to happen often enough to worry about, or justify coding a 1 minute delay or something like this.

File a feature request if this becomes a big problem. I can't promise a high priority but then we know that it is a big problem.

#7 Updated by Lexxie L about 2 years ago

I agree it's low priority. It was my mind thinking of exception edge cases just by habit ;~)

Also available in: Atom PDF