This pcall was added to avoid the crash: 57643f2
So simply removing it will just return us back to the old problem.

We need to figure out why #151 causes mpvacious to crash.

At first glance, this might be why:

    if not ok then
        error(
                string.format(
                        "Failed to load module '%s' from '%s'. Error: %s",
                        module_name,
                        module_path,
                        tostring(loaded_module)
                )
        )
    end

@NamelessAssassin any ideas how to fix?

@NamelessAssassin any ideas how to fix?

It works on my machine :<

Perhaps using mp.msg.error instead of error is better?

My OS is windows 11, is this related?

If we use mp.msg.error instead of error, loaded_module should be assign to nil when the module fails to load

I think we could try that and see if this issue occurs again.

My OS is windows 11, is this related?

This is not related to the issue, but mpvacious does not recommend using any versions of Windows or macOS.