e785615 - hostile defense mods were locked under 'siege mod', which requires for base to receive 8 million damage for its activation. The bases will not attack everyone by default any longer, only if they were triggered to siege mode. Defense mods continue to fulfill nodock regulation role. Their role to identify hostiles is still important during activated siege mode.
957fdd0 Chain reaction = activation of siege mode to one base, activates siege mods to nearby bases as well (within 8k range as the default value)
a759c4f nearby bases get activated siege mod in chain reaction, only if they are hostile in 'emulated siege mode' to at least one of the attacker. Basically, check for reputation.
50e15af duplicated white list IFF lists for bases to have its blacklist IFF version in order having better way, which IFFs are enemies to the current base + it regulates nodock blacklist for the base
New commands were added to the change
/base addhfac <IFF group> // adds IFF to hostile base list
/base rmhfac <IFF group> // removes IFF from hostile base list
/base clearhfac // clears IFF hostile list
2c7f351 added system-wide + logger warnings to players and admins for chain reacted siege mods activations (similar messages were added in previous commits for activation of siege mode of the targeted base, and for activation of personal self-defense against one player)
5e3d150 improved siege mode trigger condition
instead of 8 million sum of damage by all players, the damage must be made by ONE particular person
in this it will be more abuse proof and will help better to justify rule enforcing against triggering siege mods
fixes:
replaced return 1.0 to return true, in nodock regulating function, which I left by accident in a previous pull request.
SpaceObjDamaged had been activating SyncReputationForBase too often due to a previous PR, fixed to be activated only once when necessary.
API:
base.cfg
siege_mod_damage_trigger_level = 8000000
siege_mod_chain_reaction_trigger_distance = 8000
why it should be accepted:
(redacted) original discussion (heavily outdated due to super inefficiency proposed implementation)
discord votings: (lazy to insert image)
also made a survey about it among players, more than half of players wish for it. but almost half of players do not wish it.
The balance devs would make the change to remove 'PoB area domination(which shoots all hostiles)' anyway, but in a much more crude way.
notes:
After consideration that, more than half of players wish it, all developers except one voted yes, and plus I think it is a good change as well, I decided it should be made. And balance people would do something drastic like removing weapon platforms if not having this code addition, I thought it would be better to have it made in a more elegant solution in my opinion.
built dlls to test
Game masters could make a new rule, that invoking siege mod trigger without attack declaration leads to sanctions, for example:
image
This messaged is logged in playerbase_events.log
Fixes #157 , information inside the issue is outdated
