Update links to Unreal Engine documentation

hach-que · hach-que · commit 4a06ea0680b7 · 2025-09-11T10:25:37.000+10:00
diff --git a/docs/dedis/preparing_your_game_server.mdx b/docs/dedis/preparing_your_game_server.mdx
@@ -16,7 +16,7 @@ To package a dedicated server for Linux, you'll need:
 
 ### Install the Linux cross-compilation tools
 
-Follow the [installation guide](https://docs.unrealengine.com/4.27/en-US/SharingAndReleasing/Linux/GettingStarted/) on how to install the Linux cross-compilation tools for the engine version you are targeting.
+Follow the [installation guide](https://dev.epicgames.com/documentation/en-us/unreal-engine/linux-development-requirements-for-unreal-engine) on how to install the Linux cross-compilation tools for the engine version you are targeting.
 
 ### Targeting a source build of the engine
 
diff --git a/docs/setup/platforms/google.mdx b/docs/setup/platforms/google.mdx
@@ -14,15 +14,13 @@ Open your project's `.uproject` file, and add `OnlineSubsystemGooglePlay` with "
 
 ```json
 {
-    "Plugins": [
-        {
-			"Name": "OnlineSubsystemGooglePlay",
-			"Enabled": false,
-			"SupportedTargetPlatforms": [
-				"Android"
-			]
-		}
-    ]
+  "Plugins": [
+    {
+      "Name": "OnlineSubsystemGooglePlay",
+      "Enabled": false,
+      "SupportedTargetPlatforms": ["Android"]
+    }
+  ]
 }
 ```
 
@@ -72,7 +70,7 @@ You should now see a screen that looks like this:
 15. Scroll down and click **Save and Continue**.
 16. Scroll down and click **Back to Dashboard**.
 17. On the OAuth consent screen page, click **Publish App**.
-  	- If you have configured everything correctly, it should say "You do not need to submit your app for verification."
+    - If you have configured everything correctly, it should say "You do not need to submit your app for verification."
 18. Click **Confirm**.
 
 If you have configured the OAuth consent screen correctly, you should now see something similar to this:
@@ -109,7 +107,7 @@ In your Unreal Engine project settings, you should have a distribution keystore
 
 ![Search for "Distribution Signing" under Project Settings to find this option](google/project_settings.png)
 
-If you do not have a keystore set up for your Android application already, please follow the [Unreal Engine documentation on Signing Projects for Release](https://docs.unrealengine.com/5.1/en-US/signing-android-projects-for-release-on-the-google-play-store-with-unreal-engine/) which will guide you through the process of creating this keystore.
+If you do not have a keystore set up for your Android application already, please follow the [Unreal Engine documentation on Signing Projects for Release](https://dev.epicgames.com/documentation/en-us/unreal-engine/signing-android-projects-for-release-on-the-google-play-store-with-unreal-engine/) which will guide you through the process of creating this keystore.
 
 :::note
 If you ever regenerate the distribution certificate, you must click **Request upload key reset** under "Setup" -> "App integrity" -> "App signing" tab -> "Request upload key reset". After re-generating a keystore, you'd have to configure fingerprints again. Therefore you should check in your keystore file to source control so you don't lose it.
@@ -132,7 +130,7 @@ Make a note of these fingerprints for later.
 
 #### Get the Google Play app signing key fingerprint
 
-These days, Google Play automatically re-signs your application with a key that they manage when your application is deployed to the Google Play Store. Therefore you *also* need to get the fingerprint that the application will have when published to the Google Play Store.
+These days, Google Play automatically re-signs your application with a key that they manage when your application is deployed to the Google Play Store. Therefore you _also_ need to get the fingerprint that the application will have when published to the Google Play Store.
 
 1. Open the [Google Play Console](https://play.google.com/console/).
 2. Locate your application in the application list and click **View app ->**.
@@ -175,8 +173,8 @@ Now for **each fingerprint**, you need to perform the following steps:
 2. Select **Android** as the application type from the dropdown.
 3. Set the name to be `<game name> - <fingerprint>` so that you can identify the client later.
 4. Set the package name to match what is configured in the Unreal Engine Project Settings.
-  	- If you need to find it, search for "Android Package Name" in the Unreal Engine Project Settings.
-	- Make sure you replace `[PROJECT]` with the project name before you put it into this form.
+   - If you need to find it, search for "Android Package Name" in the Unreal Engine Project Settings.
+   - Make sure you replace `[PROJECT]` with the project name before you put it into this form.
 5. Copy the fingerprint into the SHA-1 certificate fingerprint field.
 6. Click **Create**.
 7. You will be shown a pop-up that displays the client ID. Copy this client ID and store it for later steps.
@@ -212,15 +210,16 @@ We need one extra OAuth client for the EOS backend itself. You only need to do t
 7. Select **Web application** as the application type from the dropdown.
 8. Set an appropriate name such as "EOS Backend".
 9. Leave the "Authorised JavaScript origins" and "Authorised redirect URIs" sections blank.
-10. Click **Create**. 
+10. Click **Create**.
 
 You will be shown a pop-up that provides a client ID and secret. Make a note of the client ID, as we will use them to configure the EOS backend in a moment.
 
 :::danger
 The client ID for the EOS backend should be kept separate from the client IDs for the Android app, as they have different purposes:
+
 - Client IDs for the Android app: These will go in `DefaultEngine.ini` (or `AndroidEngine.ini`).
 - Client ID for the EOS backend: These will go in the Epic Online Services developer portal.
-:::
+  :::
 
 With all the credentials created, you should now see something like this:
 
@@ -244,8 +243,8 @@ For each of the **Android client IDs** that we got before (there should be at le
 1. Click **Add credential** on the right-hand side of the screen.
 2. Select "Android" as the Type if it isn't selected already.
 3. For the name, pick one of the following options:
-	- If this is the client ID associated with [the Google Play automatic fingerprint](#get-the-google-play-app-signing-key-fingerprint), use the actual name of your game. That's because this is the name that will be presented to players.
-	- If this is the client ID associated with one of the other fingerprints, it's recommended that you name it something like `<game> - <start of fingerprint>` to keep the credentials identifable in the credential list, for example `EOS TEST GAME - 68:D9:91:0E:54`. The name is limited to 30 characters, so you might need to shorten the game name to keep it identifiable in this case.
+   - If this is the client ID associated with [the Google Play automatic fingerprint](#get-the-google-play-app-signing-key-fingerprint), use the actual name of your game. That's because this is the name that will be presented to players.
+   - If this is the client ID associated with one of the other fingerprints, it's recommended that you name it something like `<game> - <start of fingerprint>` to keep the credentials identifable in the credential list, for example `EOS TEST GAME - 68:D9:91:0E:54`. The name is limited to 30 characters, so you might need to shorten the game name to keep it identifiable in this case.
 4. If you see the "Use for new installs" option, make sure you tick this if the fingerprint is the Google Play automatic fingerprint.
 5. For the "OAuth client", select the appropriate client ID. Since you're associating each credential, you're going to repeat steps 1 through 7 picking a different OAuth client each time.
 6. Click **Save changes**.
@@ -256,7 +255,7 @@ If you have not added the EOS backend credential as a "Game server credential" y
 1. Click **Add credential** on the right-hand side of the screen.
 2. Select "Game server" as the Type if it isn't selected already.
 3. For the "OAuth client", select the EOS backend OAuth client from the dropdown.
-	- If you don't see the correct OAuth client, click **Refresh OAuth clients**.
+   - If you don't see the correct OAuth client, click **Refresh OAuth clients**.
 4. Click **Save changes**.
 5. Click **Configuration** in the sidebar to go back to the credential list.
 
@@ -401,7 +400,7 @@ Ensure that the account you are using to sign in with on the Android device is a
 
 ### Check services testers list
 
-*This is a different tester list*. Ensure that the account you are using to sign in with on the Android device is an approved testing account under "Play Games services" -> "Setup and management" -> "Testers" -> "Testers" tab. This is in addition to the internal app testing list that you configured above.
+_This is a different tester list_. Ensure that the account you are using to sign in with on the Android device is an approved testing account under "Play Games services" -> "Setup and management" -> "Testers" -> "Testers" tab. This is in addition to the internal app testing list that you configured above.
 
 ### I get a screen with "File Verification Failed" and a progress bar when my game starts up
 
@@ -412,15 +411,15 @@ You haven't [enabled GooglePAD correctly](#enable-google-play-asset-delivery). T
 If you get a message "Failed to open descriptor file" when launching the game on an Android device from the editor, this can have several causes:
 
 - You have "For Distribution" enabled in the Project Settings. In this scenario:
-    1. Turning off "For Distribution". This option must only be used when making a final package for Google Play, and not for on-device testing.
+  1. Turning off "For Distribution". This option must only be used when making a final package for Google Play, and not for on-device testing.
 - You have the "Build Configuration" setting set to `Shipping` in Project Settings, or have selected `Shipping` as the configuration for Android via the editor toolbar. In this scenario:
-    1. Change the build configuration to `Development`, `DebugGame` or `Debug`. The `Shipping` configuration only works when the game is installed via Google Play, and does not work for on-device testing.
+  1. Change the build configuration to `Development`, `DebugGame` or `Debug`. The `Shipping` configuration only works when the game is installed via Google Play, and does not work for on-device testing.
 - You previously installed the game to the device via Google Play. In this scenario:
-    1. Uninstall the game from the device.
-    2. Delete the `Binaries/Android` folder from your project.
-    3. Delete the `Intermediate/Android` folder from your project.
-    4. On the device, launch the "Files" app. Scroll down and tap on "Internal storage". Delete the following folders if they exist:
-        - `obb`
-        - `UE4Game`
-        - `UnrealGame`
-    5. Launch the game again from the editor.
+  1. Uninstall the game from the device.
+  2. Delete the `Binaries/Android` folder from your project.
+  3. Delete the `Intermediate/Android` folder from your project.
+  4. On the device, launch the "Files" app. Scroll down and tap on "Internal storage". Delete the following folders if they exist:
+     - `obb`
+     - `UE4Game`
+     - `UnrealGame`
+  5. Launch the game again from the editor.
diff --git a/docs/support/gameplay_debugger.mdx b/docs/support/gameplay_debugger.mdx
@@ -3,7 +3,7 @@ title: Debugging with the gameplay debugger
 description: Using the gameplay debugger in the engine to diagnose P2P connectivity issues.
 ---
 
-Unreal Engine ships with the [Gameplay Debugger](https://docs.unrealengine.com/5.0/en-US/using-the-gameplay-debugger-in-unreal-engine/) which you can use to view the realtime state of the game in the editor and on-device.
+Unreal Engine ships with the [Gameplay Debugger](https://dev.epicgames.com/documentation/en-us/unreal-engine/using-the-gameplay-debugger-in-unreal-engine) which you can use to view the realtime state of the game in the editor and on-device.
 
 EOS Online Framework extends the gameplay debugger to provide information about the current P2P connections, the NAT type and the packet queue length:
 
