Freeciv-3.1 gets branched to a stable branch S3_1 in a couple of hours. Development of freeciv-3.2 begins in master.
This thread is about changes that has been made to the development version of Freeciv that changes what a ruleset can do.
Please keep wishlist items and such away from this thread. This is about listing things that have been implemented already.
Include only changes relative to 3.1 - if feature gets implemented also to stable branch, it does not belong here, but maybe to similar thread about the oldest branch where the feature gets implemented.
Changes in what a 3.2 ruleset can do
Re: Changes in what a 3.2 ruleset can do
3 new user unit class flags See Feature #919098
This brings us up to 15. (The number of user unit class flags could still increase in 3.1. It's ruleset format isn't frozen yet.)
This brings us up to 15. (The number of user unit class flags could still increase in 3.1. It's ruleset format isn't frozen yet.)
Re: Changes in what a 3.2 ruleset can do
Configurable nuclear blast radius. See Feature #854166
You can now set the blast radius of the nuclear explosion for the nuke actions. This allows you to set the blast radius of briefcase nukes to only the target tile, of tactical nukes to the target tile and cardinally adjacent tiles, of normal nukes to the target tile and all adjacent tiles and to something bigger for huge nukes.
You can now set the blast radius of the nuclear explosion for the nuke actions. This allows you to set the blast radius of briefcase nukes to only the target tile, of tactical nukes to the target tile and cardinally adjacent tiles, of normal nukes to the target tile and all adjacent tiles and to something bigger for huge nukes.
Re: Changes in what a 3.2 ruleset can do
Made it possible to check in requirements if city starved last turn Feature #922788
Implemented as CityStatus type "Starved"
Implemented as CityStatus type "Starved"
Re: Changes in what a 3.2 ruleset can do
Added support for new achievement type "Killer" Feature #823396
It's granted when one has killed enough enemy units.
It's granted when one has killed enough enemy units.
Re: Changes in what a 3.2 ruleset can do
Support for "Wipe Units" action (action enablers) added. Feature #864356
Wipe Units kills entire unit stack even in situations where that would not occur for an regular Attack, such as in cities. Wipe Units can be done only when entire stack of defenders has 0 defense power. There's further change in review, that Wipe Units would also occupy the tile after it has killed the defenders.
That way stack of Diplomats (with zero defense value) would be unable to postpone city capture.
Wipe Units kills entire unit stack even in situations where that would not occur for an regular Attack, such as in cities. Wipe Units can be done only when entire stack of defenders has 0 defense power. There's further change in review, that Wipe Units would also occupy the tile after it has killed the defenders.
That way stack of Diplomats (with zero defense value) would be unable to postpone city capture.
Re: Changes in what a 3.2 ruleset can do
Added support for CityStatus values "Disorder" and "Celebration" for the requirements system Feature #870141
Re: Changes in what a 3.2 ruleset can do
Recently 3.1 format got on/off setting for visibility of Small Wonders to opponents. Now 3.2 format supports third value "Embassy", i.e., Small Wonders are visible to opponents (and their team) who have an embassy with you. OSDN #42051
Re: Changes in what a 3.2 ruleset can do
Extra flag NoAggressive with associated hardcoded maximum distance of 3 to nearest friendly city replaced by a per-extra field that tells the maximum distance for the extra to provide No-aggressive bonus for units inside. osdn #42199
Re: Changes in what a 3.2 ruleset can do
TerrainAlter requirement type now supports value CanBase osdn #42849