ares completely ignores FactoryOwners.Forbidden
Bug #1794328 reported by
FELITH
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ares |
New
|
Undecided
|
Unassigned |
Bug Description
ares v2.0
=======
[tank1]
;FactoryOwners=is not set
FactoryOwners.
;I owned USSR's factory but still able to build tank1.
=======
[tank2]
owner=USA,
FactoryOwners=
FactoryOwners.
;no USSR's factory built, owned only GER's factory. can't build tank2 even there is no GER in forbidden list.
it's not listed in "FactoryOwner=", yes. but it still does need to check forbidden list next.
but it seem to ignores the process of this function completely.
=======
To post a comment you must log in.
Did you own a single factory that was owned by USSR? Or did you own more than one, and one owned by USSR was among them? In the first case the [tank1] shouldn't be buildable, in the second case it should. Only if all factories are owned by forbidden owners should [tank1] become unavailable. I'll look into it if it's the former.
In case 2, [tank2] is not buildable by GER, because FactoryOwner= does not include GER, and thus GER factories can't build it. Because this test fails, there's no need to check FactoryOwners. Forbidden= . The result can't change: both settings have to be satisfied and the first one already fails, thus the result of the Forbidden check wouldn't change the outcome. So this is to be expected, or am I mistaken?