jonpas

> No additional context, but I'd like to know why this "feature" was implemented in the first place. There was a issue that said this was by design which baffles...

> We should investigate whether we can figure out whether the host system is 32bit or 64bit and then only install the appropriate plugin on its own. Should we? Why...

> Note also that Mumble would never install such a plugin into this directory in the first place and the manually placing the libs in there is not the intended...

I do believe that was possible. Was there even a user-space plugin directory before the plugin system rework? > Therefore: Having multiple versions of Mumble installed at the same time...

> Switching architecture would probably make this possible since then one version installs into Program Files whereas the other installs into Program Files (x86) :thinking: And we come back to...

> Or accepting the error message that occurs for blindly copying both architectures into the plugin dir. Does this break anything? As far as I know, it is more of...

> gets saved into the ACRE settings so that on next start ACRE already knows what to use/check for? Don't even have to save anything, could check which plugin already...

Yes, current plan: - Update Plugin Auto-Copy to avoid warnings in Mumble about mismatched bitness. - Release as a dev-build for testing. Just need to find time for it.

Plugin auto-copy will now only copy to `AppData/Roaming/Mumble/Plugins` and only use Mumble installation itself to determine which architecture of plugin to copy (based on Program Files folder it is installed...

See pinned items in ACE3 Discord `#acre2` channel. It is an entirely separate build and the plugin will not work with stable release.