Changes in what a 3.3 ruleset can do
Re: Changes in what a 3.3 ruleset can do
CanEscape as internal action, to give modders action enablers control over it. RM #391
Re: Changes in what a 3.3 ruleset can do
Added support for ranges Tile, CAdjacent, and Adjacent for UnitClass requirements. osdn #43704
Re: Changes in what a 3.3 ruleset can do
Added support for ranges Tile, CAdjacent, and Adjacent for UnitClassFlag requirements. RM #401
-
Alien Valkyrie
- Elite
- Posts: 518
- Joined: Sun Feb 10, 2013 10:21 pm
- Location: Stuttgart, Germany
Re: Changes in what a 3.3 ruleset can do
Removed limit on requirement vector length. RM #541
Note that at some point beyond a couple hundred requirements in one place, you will run into issues transmitting ruleset data to the client as individual packets get too large. I don't expect this to ever happen in practice.
Note that at some point beyond a couple hundred requirements in one place, you will run into issues transmitting ruleset data to the client as individual packets get too large. I don't expect this to ever happen in practice.
~ AVL
Re: Changes in what a 3.3 ruleset can do
Support added for Local range Tech requirements. RM #512
The most obvious use-case is giving science bonus for researching specific tech.
The most obvious use-case is giving science bonus for researching specific tech.
Re: Changes in what a 3.3 ruleset can do
Trade Goods now have a "select_priority" controlling which good trade route will carry. osdn #48250
Re: Changes in what a 3.3 ruleset can do
Lua: New create_trade_route() method. osdn #46550
Re: Changes in what a 3.3 ruleset can do
New building flag Infra for converting production into infra points. RM #563
Re: Changes in what a 3.3 ruleset can do
Local range supported also for TechFlag requirement. RM #573
-
Alien Valkyrie
- Elite
- Posts: 518
- Joined: Sun Feb 10, 2013 10:21 pm
- Location: Stuttgart, Germany
Re: Changes in what a 3.3 ruleset can do
Added new requirement type MaxDistanceSq to check the (squared) distance between tiles. RM #616
This is only available in contexts where there are two separate relevant tiles: primarily action enablers, but also (at time of writing) the Trade_Revenue_Bonus (source and destination), Unit_Bribe_Cost_Pct (target and actor), and Heal_Unit_Pct (actor and target) effects. This mainly allows more easily expressing some things that would've otherwise required multiple distinct actions with different ranges.
This is only available in contexts where there are two separate relevant tiles: primarily action enablers, but also (at time of writing) the Trade_Revenue_Bonus (source and destination), Unit_Bribe_Cost_Pct (target and actor), and Heal_Unit_Pct (actor and target) effects. This mainly allows more easily expressing some things that would've otherwise required multiple distinct actions with different ranges.
~ AVL