Friendly Fire Messages - Githubissues

broma-arma / BromA-Framework-A3-Addon

The addon version of the BromA Framework for ArmA 3.

5 stars 9 forks source link

Friendly Fire Messages #174

Closed Royallle closed 3 years ago

Royallle commented 3 years ago

Friendly fire messages show up when blufor/indfor players kill/wound civillian players, it also shows if a blufor Zeus, for example, remote controls an ai unit and shoots one of the other blufor players

Coryf88 commented 3 years ago

Civilians are technically friendly. Could add a friendly_fire_civilians setting to override it. To override, would add friendly_fire_civilians = false; in plugin-settings.sqf

I've been hesitant on fixing the remote controlled friendly fire messages, because it helps mitigate Zeus' potentially rampaging and complaints about remote controlling.

Royallle commented 3 years ago

Civilians are technically friendly. Could add a friendly_fire_civilians setting to override it. To override, would add friendly_fire_civilians = false; in plugin-settings.sqf

Seems like a good idea, this is only an issue for a very small amount of ops, but it's still annoying since there's no way to modify it.

I've been hesitant on fixing the remote controlled friendly fire messages, because it helps mitigate Zeus' potentially rampaging and complaints about remote controlling.

This is true, maybe have the message be broadcast to the admin channel only (don't know if it's possible), that way we know someone is using it, I barely remote control units and when I do it it isn't to directly kill players, only to spook/supress them but it's still a good thing to have and it kinda ruins the immersion knowing someone took that AI when the message pops up

Coryf88 commented 3 years ago

Another issue is each "Hit" creates a separate message. E.g. A shoot B, wait 59 seconds, A shoot B, wait 1 second, "A has wounded B", wait 59 seconds, "A has wounded B".

Message after the first hit delay, ignoring hits between. E.g. A shoot B, wait 59 seconds, A shoot B, wait 1 second, "A has wounded B".
Message after the last hit delay. E.g. A shoot B, wait 59 seconds, A shoot B, wait 60 seconds, "A has wounded B".

I'm leaning towards the first option, since its closer to the way it currently works.

maybe have the message be broadcast to the admin channel only (don't know if it's possible), that way we know someone is using it

It would be possible, but would add a dependency on Rhea. Another option is log the message in the RPT either globally, clients only, or server only.

Royallle commented 3 years ago

Another issue is each "Hit" creates a separate message. E.g. A shoot B, wait 59 seconds, A shoot B, wait 1 second, "A has wounded B", wait 59 seconds, "A has wounded B".

Message after the first hit delay, ignoring hits between. E.g. A shoot B, wait 59 seconds, A shoot B, wait 1 second, "A has wounded B".

Message after the last hit delay. E.g. A shoot B, wait 59 seconds, A shoot B, wait 60 seconds, "A has wounded B".

I'm leaning towards the first option, since its closer to the way it currently works.

maybe have the message be broadcast to the admin channel only (don't know if it's possible), that way we know someone is using it

Yeah first one seems better to implement.

It would be possible, but would add a dependency on Rhea. Another option is log the message in the RPT either globally, clients only, or server only.

True, RPT server logs seems like the best idea, if we have any suspicion of some Zeus wrong doing going on then we can just check the log