Additional way of aggroing with sound

[WoutProvost]

• New getter and setter for this range
• Use OnPlayerWeaponShot and FCNPC_OnWeaponShot
• New function that allows users to let NPCs interpret other 'sounds' that are not weapon shots
• Consider if a new behaviour has to be made for this, or if it can be merged with an existing one

[WoutProvost]

Will be implemented with the following two requirements in mind:

• Sound loudness: can be achieved by accompanying the sound with a range at which NPCs with 100% hearing can hear that sound
• NPC hearing loss/enhancement: can be achieved by giving the NPC a hearing percentage (normal=100%, subnormal<100%, supernormal>100%, deaf=0%, unlimited<0%)

[WoutProvost]

Some things I considered but decided not to implement. The reason for this is that the library is already occupying about 160MB. Using the weapon and vehicle categories below, this would bump it to about 200MB:

x = MAX_PLAYER independent fields
y = MAX_PLAYER dependent fields (except for HEARING fields)
z = HEARING fields (except for WEAPON and VEHICLE fields)
w = WEAPON fields
v = VEHICLE fields
MAX_PLAYERS = 1000
MAX_NPCS = MAX_PLAYERS = 1000
CELL_SIZE = Pawn uses 4 Bytes

memory = MAX_NPCS * (x + y * MAX_PLAYERS + z * MAX_PLAYERS + w * MAX_PLAYERS + v * MAX_PLAYERS) * CELL_SIZE
memory = 1000 * (5 + 33 * 1000 + 5 * 1000 + 6 * 1000 + 7 * 1000) * 4 Bytes
memory = 204.02 MB

Movement:

• Just because the movement keys are pressed doesn't mean that the player actually moves (e.g. when stunned when being hit)
• Player jumping
• Jetpack thrusters

Weapons:

• Differentiating between weapon (types) can be done much more effectively by the scripter instead of the library, to allow for finetuning + show debug ranges for each
• Grenades detonate 3 seconds after first pressing the button, which is not influenced by long pressing
• Molotovs detonates on impact, which is influenced by long pressing
• Rocket launchers could be simulated by doing a raycast to see if the rocket will collide with anything. If not, then it will detonate after a fixed range and thus a fixed time. Otherwise, the detonation on impact can be calculated
• I wouldn't allow each weapon to have its own range, but would assign a range to weapon categories, e.g.:
  • 22-24 handgun (slot 2)
  • 25-27 shotgun (slot 3)
  • 28-29 & 32 SMG (slot 4)
  • 30-31 MG (slot 5)
  • 33-34 rifle (slot 6)
  • 38 minigun (slot 7)
  • 00-21 & 35-37 & 39-46 (non-bullet weapons)

Vehicles:

• Differentiating between vehicle (types) can be done much more effectively by the scripter instead of the library, to allow for finetuning + show debug ranges for each
• Horn, but not every vehicle has a horn
• Siren, but not every vehicle has a siren
• Vehicle weapons, but some are silent (e.g. flare)
• Bikes and bicycles are silent when going backwards
• Cars are much less loud when going backwards
• I wouldn't allow each vehicle to have its own range, but would assign a range to vehicle categories, e.g.:
  • airplane + hovercraft
  • helicopter
  • boat
  • bike
  • car
  • heavy
  • train
  • trailer & bicycle & RC (non-engine vehicles)