That might actualy be a cool idea.

Temporal storms are effectively the same as Emissions gameplay wise (minus the fact the storm itself doesn't kill you).
Having to keep an eye out for anomalies (and having them change position after a storm) would be fun.
Artifacts could occupy backpack slots.
Artifact detectors could be crafted with Jonas parts and temporal gears.

I might keep this in mind for later. >:)

yeah there is surprisingly a lot of overlap, maybe after whatever combat updates they are cooking up are ready some stalker-inspired rust creatures could be made - they did a a really good job with the shivers, imagine a whole set of stalker-like creatures, including something akin to controllers that slam you with temporal instability

Surprisingly, no.
Based on testing with some friends, sound playing from firearm animations is implemented in a very peculiar way.

I'm not exactly sure on the spesifics, and I'm not great at explaining things, but here's what I've gathered:
Basically, the client tells the server what sound other clients should hear. 
This means the client playing a sound from a firearm's animation has complete control over what other clients hear.

So take this example:
There are 2 clients, Client A and Client B
Client A has this mod installed client side, Client B does not.

Client A fires an arquebus, and tells server that other clients should play firearmsresound:sounds/Matchlock and firearmsresound:sounds/Carbine_1.
Client B doesn't have the mod installed, so those asset don't exist on it's side. So Client B hears nothing.

Client B fires an arquebus, and tells the server that other clients should play maltiezfirearms:sounds/arquebus/arquebus-fire-1.
Client A has this asset on it's side (because it has the original Firearms mod installed). So Client A will hear the old arquebus firing sound dispite having the Resound mod installed.

With all this in mind, for this mod to function properly it's best that it be installed on all clients playing together.
Having it be set to be both server and client side allows the server to force all clients to download the mod before connecting. So having the mod be for both is simply for convience.

Now technically, I can circumvent this by replacing Firearms's sound assets directly, but that:
1. is yucky
And 2. would limit how many unique sounds I can add.

As compensasion for this not being client-side only, here's a picture of my cat trying to eat my keyboard keys while typing this out:

I see, thanks for the detailed explination dispite the furry obstruction!

No, not really.

My initial thought process behind setting the range to 768 blocks was that I thought it did get quieter the further someone is.
However, after playing with this mod with some friends, this doesn't appear to be the case.
it looks like it plays the sound at full volume basically the entire range, and only lowers the volume at the last 2-4 blocks or so, rather than lowering the volume linearly.
It also appears that sounds were implemented in such a way to where it doesn't support directional audio, so you can't tell where shots are coming from.

The only way to fix this would be to reimplement how Firearms plays its sounds. Which I don't feel like doing at the moment (might screw around with that once I get around to reading the modding wiki proper).

Maybe.
I saw the mod a while ago, and it does look really cool.
I might take a crack at it once I get to playing around with it.

+1 for Gearlocks!