From 3eccc3c3aa8a07219f9993e07ab36f4d04482e30 Mon Sep 17 00:00:00 2001
From: Gernot Zacharias <42998799+GERZAC1002@users.noreply.github.com>
Date: Mon, 10 Apr 2023 15:34:12 +0100
Subject: [PATCH] Changed Windows Build Instructions

* Changed Windows Build instructions to address version changes of libcrypto and libssl
---
 src/wiki/development/build-instructions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/wiki/development/build-instructions.md b/src/wiki/development/build-instructions.md
index 03104571f..12d30f4cd 100644
--- a/src/wiki/development/build-instructions.md
+++ b/src/wiki/development/build-instructions.md
@@ -188,7 +188,7 @@ We recommend using a build workflow based on MSYS2, as it's the easiest way to g
 4. Now, wait for it to compile. This could take some time, so hopefully it compiles properly.
 5. Run the command `cmake --install build`, and it should install PolyMC to whatever the `-DCMAKE_INSTALL_PREFIX` was.
 6. If you don't want PolyMC to store its data in `%APPDATA%`, run `cmake --install build --component portable` after the install process
-7. In most cases, whenever compiling, the OpenSSL DLLs aren't put into the directory to where PolyMC installs, meaning that you cannot log in. The best way to fix this, is just to do `cp /mingw32/bin/libcrypto-1_1.dll /mingw32/bin/libssl-1_1.dll install`. This should copy the required OpenSSL DLLs to log in.
+7. In most cases, whenever compiling, the OpenSSL DLLs aren't put into the directory to where PolyMC installs, meaning that you cannot log in. The best way to fix this, is just to do `cp /mingw32/bin/libcrypto-*.dll /mingw32/bin/libssl-*.dll install`. This should copy the required OpenSSL DLLs to log in.
 
 ## macOS