Page 7 of 14

Re: Changes in what a 3.0 ruleset can do

Posted: Fri Jun 17, 2016 12:37 am
by sveinung
The regular attack is now controlled by the "Attack" action enabler. See patch #7260

This isn't as awesome as it sounds. The target requirements are evaluated against the tile, not against any unit on it. You therefore can't use stuff like unit type requirements. I have a plan that may change this in the far future.

Things you can do includes creating an almost[0] (non absolute[1]) pacifist government type by making it disable regular (and other) attacks[2].

[0] City occupation isn't action enabler controlled yet.
[1] Units will still defend them self when attacked.
[2] You can already disable bombard, capture and the violent spy actions.

Re: Changes in what a 3.0 ruleset can do

Posted: Thu Jun 23, 2016 2:10 pm
by sveinung
OnNativeTile property added to the UnitState requirement type. See patch #7267

OnLivableTile tests if the unit can exist outside of a transport at its current tile. OnNativeTile tests nativity from terrain and extras. Unlike OnLivableTile it doesn't care about cities and safe terrain.

Re: Changes in what a 3.0 ruleset can do

Posted: Fri Jun 24, 2016 4:36 am
by GriffonSpade
sveinung wrote:OnNativeTile property added to the UnitState requirement type. See patch #7267

OnLivableTile tests if the unit can exist outside of a transport at its current tile. OnNativeTile tests nativity from terrain and extras. Unlike OnLivableTile it doesn't care about cities and safe terrain.


Hmm, no way to separate out nativity of terrain from extras, though, I take it?

Sounds like great work as always though, Sveinung.

Re: Changes in what a 3.0 ruleset can do

Posted: Fri Jun 24, 2016 9:47 am
by sveinung
GriffonSpade wrote:Hmm, no way to separate out nativity of terrain from extras, though, I take it?

No shortcuts. In many cases (effect, action enablers) you can require the unit type (/unit type flag/unit class/unit class flag) + the terrain (/terrain flag).

GriffonSpade wrote:Sounds like great work as always though, Sveinung.

Thank you.

Re: Changes in what a 3.0 ruleset can do

Posted: Tue Jun 28, 2016 10:01 pm
by cazfi
Coast-restricted units flags reworked; "Trireme" flag renamed as "CoastStrict" (unit with this flag can never leave coast).
New "Coast" flag added. It's meant to be used in conjunction with unit fuel property. The effect of the flag is that unit considers coastal tiles refueling points -> if it has fuel for one turn, it must end every turn at coast; if it has fuel for two turns, it must end every other turn replenishing water and food stock at some coast.
patch #6979

Re: Changes in what a 3.0 ruleset can do

Posted: Wed Jun 29, 2016 6:35 pm
by dunnoob
sveinung wrote:This isn't as awesome as it sounds.
If it allows me to fire on hills, mountains, forests, and so on with a BIG LAND unit not permitted to move on these terrains without a road, it is awesome, because it's the one and only reason why I'm not using BIG LAND. :o

Re: Changes in what a 3.0 ruleset can do

Posted: Thu Jun 30, 2016 12:23 pm
by GriffonSpade
dunnoob wrote:
sveinung wrote:This isn't as awesome as it sounds.
If it allows me to fire on hills, mountains, forests, and so on with a BIG LAND unit not permitted to move on these terrains without a road, it is awesome, because it's the one and only reason why I'm not using BIG LAND. :o


Hmmm, can the attacker's tile also be checked? Could wipe out any use for attack non native and attack from non native both, and even allow blocking attack non native from non native only.

Re: Changes in what a 3.0 ruleset can do

Posted: Thu Jun 30, 2016 2:54 pm
by sveinung
dunnoob wrote:
sveinung wrote:This isn't as awesome as it sounds.
If it allows me to fire on hills, mountains, forests, and so on with a BIG LAND unit not permitted to move on these terrains without a road, it is awesome, because it's the one and only reason why I'm not using BIG LAND. :o

Isn't that what the AttackNonNative unit class flag is for?

GriffonSpade wrote:Hmmm, can the attacker's tile also be checked?

Yes. Put the tile requirements in the action enabler's actor requirements.

GriffonSpade wrote:Could wipe out any use for attack non native and attack from non native both, and even allow blocking attack non native from non native only.

I plan to move attack from non native (AttFromNonNative/Marines) to the ruleset. It will be easier to do with action enabler controlled city occupation. It is currently prioritized below some work I need to finish before the 2.6 network protocol freeze.
Having the "Attack" action enabler replace attack non native is more complicated. The relationship is between the actor unit and the target's tile. It could be solved by using many action enablers (attackers x terrains/extras). It could be solved by some action enabler specific test. It could also be solved by keeping it as a unit class flag.

Re: Changes in what a 3.0 ruleset can do

Posted: Sat Jul 02, 2016 3:36 am
by GriffonSpade
sveinung wrote:
GriffonSpade wrote:Could wipe out any use for attack non native and attack from non native both, and even allow blocking attack non native from non native only.

I plan to move attack from non native (AttFromNonNative/Marines) to the ruleset. It will be easier to do with action enabler controlled city occupation. It is currently prioritized below some work I need to finish before the 2.6 network protocol freeze.
Having the "Attack" action enabler replace attack non native is more complicated. The relationship is between the actor unit and the target's tile. It could be solved by using many action enablers (attackers x terrains/extras). It could be solved by some action enabler specific test. It could also be solved by keeping it as a unit class flag.


I was actually thinking along the lines of not allowing triremes and boats to attack land from within a city (technically they should be in the harbor, and unable to attack all the way across the city). There are buildings in the way and such after all. I guess it wouldn't technically be 'non-native' since cities are considered native to all units.

Re: Changes in what a 3.0 ruleset can do

Posted: Mon Jul 04, 2016 9:19 am
by cazfi
Added concept of tech class: patch #7354

They are optional feature in a ruleset, and in this initial version their only property is "name" of the class that gets shown in help of each tech.