fonnymunkey / RLCombat

A fork of Better Combat Rebirth for the modpack RLCraft
3 stars 1 forks source link

Sounds do not play. #6

Closed MagmaBro123 closed 1 month ago

MagmaBro123 commented 1 year ago

Title. No other mods are in use.

image

fonnymunkey commented 1 year ago

Ensure "Additional Hit Sounds" and "Additional Crit Sounds" are enabled in the config, they should be enabled by default.

I can not recreate sounds not working on a fresh install without purposefully turning off the config option, both vanilla and spartan weapons play the sounds correctly.

MagmaBro123 commented 1 year ago

Both are enabled.

fonnymunkey commented 1 year ago

Does it play any hit/crit sounds, like the default ones, or none at all? Is this with any weapon, or specific to certain weapons? On server or singleplayer, or both?

MagmaBro123 commented 1 year ago

Both, no sounds at all, any weapon.

fonnymunkey commented 1 year ago

If you're not hearing any sounds from weapons then that sounds like an issue external to the mod, either a problem in your sounds settings, or with the game/drivers itself.

MagmaBro123 commented 1 year ago

Well, all other sounds play correctly. Music, etc.

MagmaBro123 commented 1 year ago

To add, BetterCombatRebirth's new sounds work just fine. Whatever RLCombat does, apparently none of its new sounds function, or you removed BetterCombatRebirth's sounds.

fonnymunkey commented 1 year ago

I've changed nothing to do with sounds, they are still exactly the same as BetterCombatRebirth. I have been unable to replicate sounds not playing without either disabling them in the config, disabling sounds in the sounds settings, or some other mod cancelling/breaking RLCombat's attack handling entirely. Likewise, none of the hundreds of RLCraft testers have reported missing attack sounds as well so far, so I have no idea what is causing your issue.

MagmaBro123 commented 1 year ago

Me neither. The modlist above is all I have right now.

fonnymunkey commented 1 month ago

As of 2.2.0 the whole sound system has been reworked, and additionally I have never been able to reproduce this issue nor had any other instances of it happening, so Im going to assume it will be resolved with the latest version.