Merge pull request #41 from AdriaandeJongh/notarization-update

Major rewrite of the mac export tutorial

docs/tutorials/mac_export.md

@@ -1,51 +1,49 @@
 # Tutorials - Mac Exporting
 
-This comes up sometimes so I figured I would cover it. However, as you can notice by scanning the page, it is short and sweet. When exporting for macOS, there are a few minor modifications you must make to the app's ZIP file.
+When exporting for macOS, there are a few additional things to consider.
 
 {==
-## Beware Codesign
+## Entitlements
 ==}
 
-For Godot 3.x users, one option you need to make sure is disabled is Codesign. For some users, it makes the game unable to talk to Steam and results in the "Steam not running" error. Just check for this during export:
+Valve says that the `disable library validation` and `allow Dyld environment variables` export settings should only be needed on Catalina 10.15, but users report needing to check these boxes anyway to allow Steamworks to load and the overlay to work properly.
 
-![Codesign Fail](../assets/images/mac-caveats1.png){ loading=lazy }
+=== "Godot 4.x"
+	![Disable Validation / Allow Dyld Environment Variables](../assets/images/mac-caveats-entitlements-godot4.png){ loading=lazy }
 
-Apparently, for Godot 4.x users, codesign is fine but you may want to keep the notarizing stuff empty.
+=== "Godot 3.x"
+	![Disable Validation / Allow Dyld Environment Variables](../assets/images/mac-caveats-entitlements-godot3.png){ loading=lazy }
 
 {==
-## Entitlements
+## Codesigning and Notarization
 ==}
 
-This one is apparently still valid though Valve says it is only needed on Catalina 10.15, but you will want to `disable library validation` and `allow Dyld environment variables` to allow Steamworks to load and the overlay to work properly.
+Codesigning and notarization are Apple's way to verify which executables are build by who. Because Valve runs the game if a user presses the Play button in Steam, both codesigning and notarization are not strictly necessary as Steam essentially takes responsibility for the app it runs. However, this may change in the future, so it may be wise to explore codesigning and notarization anyway. Besides: should you release your game on other platforms, codesigning and notarization may be required for the user to run your game on their Mac at all.
 
-=== "Godot 3.x"
-	![Disable Validation / Allow Dyld Environment Variables](../assets/images/mac-caveats-entitlements-godot3.png){ loading=lazy }
+**For Godot 3.x users, codesigning unfortunately makes the game unable to communicate with Steam for some users**, resulting in a generic "Steam not running" error. This will consequently fail notarization as well. If you're on Godot 3.x, make sure to disable codesign in the export settings.
 
-=== "Godot 4.x"
-	![Disable Validation / Allow Dyld Environment Variables](../assets/images/mac-caveats-entitlements-godot4.png){ loading=lazy }
+For Godot 4.x users wanting to codesign their game, first make sure you have a paid Apple Developer account. The easiest way to set up your Mac to codesign and notarize your app is to download Xcode and add your developer account in its settings as well as create the signing certificates you need through that same developer account settings window in Xcode.
 
-{==
-## App Icon
-==}
+To be able to notarize your game's `.app`, you'll need to codesign the `libgodotsteam.macos.template_release.framework` file in the `addons/godotsteam/osx/` folder of your project every time you download or update the GodotSteam GDExtension. Use the following terminal command, replacing the whole 'Developer ID' string with the full name of the signing certificate on your Mac. If you can't find this certificate in the Keychain app, go back to the developer account settings in Xcode and create a Developer ID certificate there.
 
-There is, by default, a Godot Engine icon already inside the `{your game}.app/Contents/Resources` folder. You will most likely want to replace it with a fancy version of your game's icon. All you have to do is export your icon and save it as `icon.icns` then replace it in the same folder, overwriting the original.
+```
+codesign --deep -fvs "Developer ID Application: <team name> (<team ID>)" libgodotsteam.macos.template_release.framework
+```
 
-You should be able to create it online or with a Photoshop plug-in. Unfortunately I don't have any great resources or links for this at the time of writing, but a quick DuckDuckGo search should sort you out.
+After codesigning the framework, simply fill in all the codesign and notarization export settings and let the Godot export to macOS handle the rest of the codesigning and notarization!
 
 {==
 ## Steamworks Components
 ==}
 
-Second, you need to add the following files to your app Contents:
+If you're using the GDExtension version of GodotSteam, you can skip this step – the right Steamworks binaries are already included.
+
+If you're using another version of GodotSteam, you will need to add the following files to your app Contents folder after each export for Steamworks to work:
 
 - `libsteam_api.dylib` to `{your game}.app/Contents/MacOS` folder
 - `libgodotsteam.framework` to `{your game}.app/Contents/Frameworks` folder
 
-The `libsteam_api.dylib` should be in the `redistributable_bin/osx` folder inside the Steamworks SDK. Make sure it matches the Steamworks API version you are using to compile the editor/template or it will crash.
-
-Alternatively, if you are using the pre-compiled one from GodotSteam's GitHub release section, you can thank **SapphireMH** for already including this file for you!
-
-Here is a handy shell script you can run after you export your mac build to zip file.
+The `libsteam_api.dylib` file should be in the `redistributable_bin/osx` folder inside the Steamworks SDK. Make sure it matches the Steamworks API version you are using to compile the editor/template or it will crash. Here is a handy shell script you can run after you export your mac build to a zip file.
 
 ```shell
 #!/bin/bash