Page 3 of 6

Re: Changes in what a 3.3 ruleset can do

Posted: Wed Apr 17, 2024 1:58 am
by cazfi
CanEscape as internal action, to give modders action enablers control over it. RM #391

Re: Changes in what a 3.3 ruleset can do

Posted: Fri Apr 19, 2024 12:39 pm
by cazfi
Added support for ranges Tile, CAdjacent, and Adjacent for UnitClass requirements. osdn #43704

Re: Changes in what a 3.3 ruleset can do

Posted: Tue Apr 23, 2024 2:54 am
by cazfi
Added support for ranges Tile, CAdjacent, and Adjacent for UnitClassFlag requirements. RM #401

Re: Changes in what a 3.3 ruleset can do

Posted: Mon May 06, 2024 5:43 am
by Alien Valkyrie
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.

Re: Changes in what a 3.3 ruleset can do

Posted: Thu May 09, 2024 3:50 am
by cazfi
Support added for Local range Tech requirements. RM #512

The most obvious use-case is giving science bonus for researching specific tech.

Re: Changes in what a 3.3 ruleset can do

Posted: Wed May 15, 2024 12:06 am
by cazfi
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

Posted: Tue May 21, 2024 3:08 am
by cazfi
Lua: New create_trade_route() method. osdn #46550

Re: Changes in what a 3.3 ruleset can do

Posted: Wed May 29, 2024 4:40 pm
by cazfi
New building flag Infra for converting production into infra points. RM #563

Re: Changes in what a 3.3 ruleset can do

Posted: Fri May 31, 2024 4:12 am
by cazfi
Local range supported also for TechFlag requirement. RM #573

Re: Changes in what a 3.3 ruleset can do

Posted: Tue Jun 04, 2024 10:51 am
by Alien Valkyrie
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.