Nandiin 0 Report post Posted November 8, 2016 I've downloaded 1.12 client for mac from several different sources and they all crash on start on my system. I downloaded the torrent then unzipped it then I double clicked on the "WoW Classic.app" and then it simply crashed without showing up any window. The error information goes as below: Process: World of Warcraft [34276] Path: /Volumes/VOLUME/*/WoW Classic.app/Contents/MacOS/World of Warcraft Identifier: com.blizzard.worldofwarcraft Version: 1.12.1 (1.12.1) Code Type: X86 (Native) Parent Process: ??? [1] Responsible: World of Warcraft [34276] User ID: 501 Date/Time: 2016-11-08 14:01:40.384 +0800 OS Version: Mac OS X 10.12 (16A323) Report Version: 12 Anonymous UUID: 3F15645A-6AB8-FF3C-99DB-1549875F3F6E Sleep/Wake UUID: 417BCBA6-15B9-480B-B4A4-B9D3136FFCE9 Time Awake Since Boot: 87000 seconds Time Since Wake: 7600 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000024 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x24: --> __TEXT 0000000000001000-0000000000693000 [ 6728K] r-x/rwx SM=COW /var/folders/*/WoW Classic.app/Contents/MacOS/World of Warcraft I know that I've missed the step of replacing realmlist.wtf but I don't think that will cause a crash. (I tried to replace that file actually, it still crashes) Anyone can help? or this client is too old for running on a 10.12 OS X? 0 Share this post Link to post Share on other sites
Kubicek 0 Report post Posted November 8, 2016 (edited) Hey there fellow mac user! I noticed a following problem yesterday, but do not worry, it can be easily fixed. 1. Go to your WoW folder 2. Right-click WoW app and select "Show package contents" 3. Go to Contents/MacOS 4. Launch World of Warcraft executable file This will open a terminal window and consecutively launch the game You can easily create an alias for this executable file and place it on your dock for convenient access in the future. Hopefully this helps you. Edited November 8, 2016 by Kubicek 0 Share this post Link to post Share on other sites
Nandiin 0 Report post Posted November 9, 2016 Hey there fellow mac user! I noticed a following problem yesterday, but do not worry, it can be easily fixed. 1. Go to your WoW folder 2. Right-click WoW app and select "Show package contents" 3. Go to Contents/MacOS 4. Launch World of Warcraft executable file This will open a terminal window and consecutively launch the game You can easily create an alias for this executable file and place it on your dock for convenient access in the future. Hopefully this helps you. This helps! 0 Share this post Link to post Share on other sites
Jerycko 0 Report post Posted December 14, 2016 That fixed it for me too. Thank you! However, it does not seem to remember settings? Everytime I launch the games all settings are back to original. Any solution for this? Cheers! 0 Share this post Link to post Share on other sites
Jerycko 0 Report post Posted December 14, 2016 Nvm, I just needed to delete the WTF folder 0 Share this post Link to post Share on other sites
Ellipsea 36 Report post Posted December 14, 2016 (edited) I don't know if your settings would never get saved that way. If that's true, it definately isn't an ideal solution. If it never saves your settings or addons, it would be better to run the application as a root as described towards the bottom of this thread: https://forum.elysium-project.org/index.php?showtopic=23403 Edited December 14, 2016 by Ellipsea 0 Share this post Link to post Share on other sites
Jerycko 0 Report post Posted December 14, 2016 It didn't save the config because I had the WTF from the original download. As this folder was created by another user I didn't have read write access and the sudo would do the trick. But after deleting that folder, it did recreate the config files for my user without root. There probably isn't any issue running with root, but probably better to avoid it when possible, certainly when the client was downloaded unofficially. 0 Share this post Link to post Share on other sites
Ellipsea 36 Report post Posted December 14, 2016 (edited) Running it as root is totally fine, it opens up permissions between the newer OS and the client, nothing else. I said I don't know what running it from executable file would do but IF it doesn't allow for updating all your settings to go to running it as root. Edited December 14, 2016 by Ellipsea 0 Share this post Link to post Share on other sites
