• Your Wine should be at least version 10. (Certain 9.x versions may also work but there's no harm in updating.) You can check your current Wine version by executing "wine --version" in a terminal. If it's not at least version 10, search around online for how to update Wine on your specific distro.
  
• Winetricks. Many distros come with this pre-installed, and all good software centers & package managers have it regardless.
  
• The most recent version of the BYOND installer. Note that you must specifically get the Windows version, not the Linux one - as mentioned on the website, the Linux release of BYOND is only useful for server hosting, not playing games.
  
• The WebView2 evergreen bootstrapper. At time of writing the BYOND download page contains a link to it, but just in case: here. Make sure you get the 'evergreen bootstrapper' specifically.
  

• If BYOND fails to launch at all, either after your first setup or just in general... yeah it does that sometimes. You might have some luck with using your task manager to kill byond.exe, otherwise a system reboot will usually do it. (From experience, though: after a fresh system startup, wait a minute or so before trying to launch BYOND.)
  
• You'll probably suffer from a severely flickering chatbox. My hope is that the eventual TGUI-ification of chat will fix this, but in the meantime you can click on the 'Text' button at the top of the area to close the commands window, and this does fix it. It also prevents you from accessing commands. Tradeoffs.
  
• Item & ability tooltips are at war with euclidean geometry. More news at 7. (I have found no fix for this.)
  
• It has trouble reconnecting automatically after a round restart. SOMETIMES it does. Usually it doesn't. Closing Goonstation and re-launching is your friend.
  
• Sometimes, after rebooting while in a round, Wine will immediately crash upon trying to load back in. This will go away on its own once the round ends, but don't despair: you can fix this immediately by opening up your BYOND pager (the BYOND application itself), clicking on the gear icon in the top right, 'Preferences', 'Games', then click 'Clear Cache'. You should then be able to reconnect (albeit it'll take a good 10-30 seconds to redownload all the assets that you just cleared.)
  
• LINUX MINT USERS SPECIFICALLY: By default, Mint will consume any alt-clicks, which prevents you from using Goon's alt-click to examine feature. You can fix this by opening up Mint's 'Windows' settings menu (literally just search 'Windows'), going into the 'Behaviour' tab, then setting the 'special key to move and resize windows' option to disabled. Voila - you can now examine again.
  
• One time I must have cast some voodoo spell or some shit because I wound up having a considerably more stable chatbox at the cost of crashing almost every time I entered or exited a pod, or whenever the round reconnected, or whenever trying to resize the chat window. I don't know how to reproduce this, I don't even know what I did differently to begin with. It went away after a reinstall.
  
• The respawn timer/button's text, the one you see as a ghost, is all fucked up. I assume it's trying to use some special font that corefonts doesn't cover, but I don't care enough to trawl through them to find out if this is the case. Luckily the actual functionality of the button is fine all the same.
  
• You may have a bunch of black windows (such as viewport, camera terminal, chatboxes) upon booting up Goonstation. The chatboxes can be dismissed by using the 'Fix chatbox' command, but the others are stubborn - as far as I know, the only way to be rid of them is to reboot Goon until you get lucky and they're not there.
  
• Upon tabbing back into the game, you'll probably have to click in order for the game to be re-focused and BYOND to start reading your inputs. Keep in mind that the click itself will be registered by the game so don't accidentally harmbaton someone or something. (I've misfired a Lawbringer before because of this.)
  
• No, I don't know how to clear your IE cache if you're running Goonstation via this method.
  
• When playing as the AI, exiting out of your shell can take a hot minute.
  
• TGUI works great, but sometimes it really doesn't like trying to have multiple TGUI windows open at once. Your mileage may vary.
  
• Sometimes, certain non-TGUI UI windows (such as the PDA, latejoin job selection, and character setup occupation selection) will blank after a good 10-ish minutes of playing. Rebooting Goonstation fixes this. (This might just be some kind of cache issue, I don't know.)
  
• When closing out of Goonstation and even BYOND as a whole, the WebView2 process might not end properly - leading to a lingering, dead process consuming memory just laying about in your system after every close. It also seems to make the game respond slower and slower with each one accrued. I advise going through your task manager regularly to kick these vagrants out.
  
• The BYOND pager's offer to update BYOND for you if there's a new version is a bold-faced lie.
  

1.     Install BYOND as per the instructions above.
   
2.     On, say, "Loading game information", press [Ctrl]+[p]. Also works from the hub.
   
3.     Navigate to "Games" tab.
   
4.     Uncheck the "Login to games as Guest..." box
   
5.     Locate your verified-to-work install's .key
          - For me, on both Windows and Linux, it was located at [your-user]/Documents/BYOND/key.txt
            Notably Linux-side it was not on the weird Wine simulated disk, it was in your actual Linux user's Documents.
   
6.     On the working side copy BEGIN KEY ... END KEY block of text that contains your ckey.
   
7.    Plonk it down in the non-working side's key.txt file. I wrote mine before the preexisting guest KEY's block, not sure if order matters.
   

Quote:You'll probably suffer from a severely flickering chatbox. My hope is that the eventual TGUI-ification of chat will fix this, but in the meantime you can click on the 'Text' button at the top of the area to close the commands window, and this does fix it. It also prevents you from accessing commands. Tradeoffs.