BUG... Mod and client injection error in Windows launcher #17
Description
A critical error found in the Windows launcher is related to the installation and execution of mods (DLLs). When importing a DLL for the first time, the launcher often gets stuck on the loading screen and requires a forced close. Upon re-opening, the DLL may be imported but corrupted, necessitating a re-import, though this only happens in certain cases.
The second major issue is the failure to run mods within the game. Although it is known that the DLL files are for the correct Minecraft version and have been successfully run using another type of injector like Fate injector, attempting to run two of them simultaneously through the Levi launcher for Windows causes the game to fail to launch. Even when disabling one of the DLLs and trying to run only one, the game still does not launch. Instead, the Task Manager shows that two Minecraft windows are running in the background, a process that is clearly a bug. This issue suggests that client DLLs may not be injecting correctly, although other types of mods might, and even though Fate injector was able to run both DLLs. (The Fate injector allowed the execution of LatiteClient and Better Resource Pack Manage, but the launcher Levi did not (it could not even launch any client).
The third error involves importing resource packages (mcpack). Since Minecraft Bedrock is not installed as a standard system program and must be executed only from Levi, the program cannot be found when trying to export an mcpack using a standard method. Users are thus forced to use the Levi import button, but it incorrectly reports a "Package structure error." This bug compels users to perform manual, tedious importing (unzipping and moving folders), which requires fixing.
Finally, the last bug is a minor visual error: the Minecraft Bedrock logo is not properly implemented. Consequently, the program appears in the taskbar as a generic text file icon instead of the correct game logo.