Changes in what a 2.6 rule set can do
Re: Changes in what a rule set can do
The spy/diplomat action "Bribe Unit" now use the action enabler frame work.
Re: Changes in what a rule set can do
Achievements are a new concept in 2.6. Here's example of current achievement definition format:
Achievements can be granted to either only to the first player fulfilling the requirements, or all players fulfilling the requirements. Granted achievement alone does not do anything, but it can be used as requirement for effects, or anything where requirement vectors are used.
Suggestions for new achievement types welcome. We currently have "Map_Known" and "Spaceship_Launched" achievement types, with patch for "Multicultural" (citizens of many different nationalities in ones cities) waiting for approval.
Code: Select all
[achievement_map_known_20p]
name = _("Map Known 20 pct")
type = "Map_Known"
value = 20
Suggestions for new achievement types welcome. We currently have "Map_Known" and "Spaceship_Launched" achievement types, with patch for "Multicultural" (citizens of many different nationalities in ones cities) waiting for approval.
Re: Changes in what a rule set can do
Added effect type Victory. When that effect gets active (when value of the effect is positive, to be exact) player wins the game. You can just give requirements for winning the game as requirements for this effect.
Note that you can do everything you can do with this effect (and more) in earlier version too, with lua scripting function Player:victory(), but this effect is probably easier for non-coder modpack authors to use.
Note that you can do everything you can do with this effect (and more) in earlier version too, with lua scripting function Player:victory(), but this effect is probably easier for non-coder modpack authors to use.
Re: Changes in what a rule set can do
City tile related requirements for effects targeting the city are now supported (bug #19874) This one will be in 2.5 already.
Re: Changes in what a rule set can do
The spy/diplomat action "Sabotage City" now use the action enabler frame work. The "Spy" unit flag is still used to decide if the action can be targeted. The plan is to split this action in two - one that is targeted and one that isn't.
Re: Changes in what a rule set can do
New terrain flag NotGenerated added for preventing map generator from ever placing the terrain. Such terrain is only available for transform results, or to be placed via lua script or editor. (patch #4158)
Terrain called Inaccessible with that flag has been added to classic, experimental, multiplayer, civ2civ3, and alien rulesets. This terrain is also native to no unit (no unit can enter) and cities can never work it. This terrain type is meant for scenario authors to place in editor to shape the map, or at least part that's accessible. (patch #4159)
These went to 2.5 too.
Terrain called Inaccessible with that flag has been added to classic, experimental, multiplayer, civ2civ3, and alien rulesets. This terrain is also native to no unit (no unit can enter) and cities can never work it. This terrain type is meant for scenario authors to place in editor to shape the map, or at least part that's accessible. (patch #4159)
These went to 2.5 too.
Re: Changes in what a rule set can do
In stead of having the presence of the "Spy" unit flag determine if the spy action "Sabotage City" can be targeted or not split it in two actions, "Sabotage City" and "Targeted Sabotage City". "Sabotage City" can't be targeted. "Targeted Sabotage City" may be targeted at the price of worse odds.
Re: Changes in what a rule set can do
Only relevant if you care about how your rule set appear in the client.
The server knows everything. The player has limited knowledge. It is possible to create rules that depend on knowledge the player don't have. This leads to situations where the player don't know if a rule applies or not. Meta knowledge helps identify those situations.
Meta knowledge is now used to evaluate action enablers in the GTK3 client. The meta knowledge isn't complete. Missing meta knowledge is assumed to be uncertain. An action that may or may not be enabled is shown but colored red in the UI.
The server knows everything. The player has limited knowledge. It is possible to create rules that depend on knowledge the player don't have. This leads to situations where the player don't know if a rule applies or not. Meta knowledge helps identify those situations.
Meta knowledge is now used to evaluate action enablers in the GTK3 client. The meta knowledge isn't complete. Missing meta knowledge is assumed to be uncertain. An action that may or may not be enabled is shown but colored red in the UI.
Re: Changes in what a rule set can do
The spy action "Incite City" now use the action enabler frame work.
Re: Changes in what a rule set can do
It used to be impossible to do spy actions against units in cities. This has now changed for the spy action "Sabotage Unit". The requirement that the unit targeted for sabotage isn't in a city now live in its action enablers. Note that it currently only is possible to see (and therefore target) a unit in a city if you are allied to its owner. This makes this change quite limited.
Edited to hopefully be more understandable. Thank you for the reminder cazfi!
Edited to hopefully be more understandable. Thank you for the reminder cazfi!
Last edited by sveinung on Thu Sep 19, 2013 2:22 pm, edited 1 time in total.