Important note II

[GFM GToeroe]

Hi!

There is currently code in the host which that force your true allies
to start fire in a common space combat:

Example

Your unit: A
Your true ally's unit: B

True ally means that you mutually has switched off attack in ally menu
in the client.

Now a hostile unit C which has you (A) as enemy triggers a combat.

Now if C fires at A your unit informs your ally about this hostile
act. If now B and C are not mutually allied B starts fire on C.

There was an agreement that it is not a good idea to force a player's
units to fire on another player if this other player was not set as
ally.

There is already FIX waiting which changes this behavior. Then B will
start fire on C if B has set C as enemy but B is still not firing
because B is in defensive mode.

Gabor

[Black No.1]

Post by GFM GToeroe
Now if C fires at A your unit informs your ally about this hostile
act. If now B and C are not mutually allied B starts fire on C.
There was an agreement that it is not a good idea to force a player's
units to fire on another player if this other player was not set as
ally.

Do you mean "was not set as enemy" or maybe "was set as ally"?
(would make more sense imho)

Post by GFM GToeroe
There is already FIX waiting which changes this behavior. Then B will
start fire on C if B has set C as enemy but B is still not firing
because B is in defensive mode.

If I have understood it right, the current code checks for mutually alliances
when deciding to have player B open fire at C once C attacks player A.

And it should be that player C's ally settings regarding player B shouldn't
matter -
only player B's ally settings regarding player C.

Right?`

Cheers.
Jochen

[GFM GToeroe]

Post by Black No.1

Post by GFM GToeroe
Now if C fires at A your unit informs your ally about this hostile
act. If now B and C are not mutually allied B starts fire on C.
There was an agreement that it is not a good idea to force a player's
units to fire on another player if this other player was not set as
ally.

Do you mean "was not set as enemy" or maybe "was set as ally"?
(would make more sense imho)

Post by GFM GToeroe
There is already FIX waiting which changes this behavior. Then B will
start fire on C if B has set C as enemy but B is still not firing
because B is in defensive mode.

If I have understood it right, the current code checks for mutually alliances
when deciding to have player B open fire at C once C attacks player A.
And it should be that player C's ally settings regarding player B shouldn't
matter -
only player B's ally settings regarding player C.
Right?`
Cheers.
Jochen

Yes, if my unit is under attack then it sends a distress signal to the
players which are not set to attack in my client's ally menu. If these
players also haven't set me to attack in their client's ally menu then
they start fire with the player which is firing at me if they are not
mutually allied with the bad guy. Even if they have set the bad guy as
ally (not to attack).

So my unit could force another player to fire at a third player even
if the player has that the third not to attack. This is not good.

The change will then only force another player to start fire on the
bad guy which is attacking me if the other player is mutually allied
with me and if the other player has set the third bad guy to attack in
ally menu. If not the the other player has to wait till the bad guy
opens fire at him.

Gabor