bundle of changes / updates

.vuepress/config.js

@@ -88,7 +88,7 @@ module.exports = {
                         'BUILD-FROM-SOURCE', // Building PojavLauncher from source
 						'SIGN-IN', // Signing in
 						'INSTALL-MC', // Downloading Minecraft
-						'DEFAULT-CONTROLS', // Taking a look at the controls
+						'CUSTOM-CONTROLS', // Customizing the on-screen controls
 						'DISCORD', // Official PojavLauncher Discord server
 					]
 				},
@@ -104,7 +104,6 @@ module.exports = {
 							children: [
 								'JIT', // iOS and "JIT"
 								'APPSTORE', // Will PojavLauncher ever come to App Store for iOS?
-								'IOSMODPACKS', // how do i install modpacks on PojavLauncher iOS?
 							]
 						},
 						{
@@ -120,8 +119,6 @@ module.exports = {
 								'ZINK', // What's Zink, and why it's not what you think
 								'SHADERS', // Look what we got here.
 								'RENDERERS', // I have no idea what they do and why PojavLauncher needs it.
-								'3PTYCLIENTS', // Reminders about installing third party clients from unknown sources
-								'117CC', // Basics to get 21w10(?)a+ running. Useless
 							]
 						},
 						// FAQ that applies to both platforms goes here
@@ -133,13 +130,11 @@ module.exports = {
 					collapsable: true, 
 					sidebarDepth: 1,
 					children: [
-						'CUSTOM-CONTROLS', // Customizing the on-screen controls
 						'OPTIMIZATION', // Optimizing the game
 						'CUSTOM-MC', // Custom Minecraft!
 						'MODPACKS', // Everything you need to know about Modpacks support
 						'ENV-VARS', // Using environment variables
 						'JAVA-ARGS', // Adding custom Java arguments
-						'DEBUG-LOG', // Debugging issues with the launcher
 					]
 
 				},
@@ -165,9 +160,8 @@ module.exports = {
             collapsable: false,
             sidebarDepth: 1,
             children: [
-                'CONT-POJAV', // Contributing to PojavLauncher itself
 				'CONT-WEBSITE', // Contributing to this website
-                'CONT-TRANSLATIONS', //Contributing to PojavLauncher translations, hopefully website translations later on
+               			'CONT-TRANSLATIONS', //Contributing to PojavLauncher translations, hopefully website translations later on
             ]
 
         },

32BIT.md

@@ -1,17 +1,24 @@
 # PojavLauncher's 32-bit support
-Most of you, Android users, who are reading this now, won't be bothered by this documentation, but for the poor souls who have a 32-bit device, let's press ~~L~~ F to pay respect to them.
+Most of you, Android users, who are reading this now, won't be bothered by this documentation, but for the poor souls who have a 32-bit device, let's press ~~L~~ F to pay respects to them.
 
-Before ARM transitioned into the more-powerful, more-utilizing `arm64/aarch64` architecture; everyone was using `arm/aarch32`
+ARM transitioned into the modern `arm64/aarch64` architecture, which significantly improved utilization and stability compared to its widely used predecessor, `arm/aarch32`, while also maintaining compatibility using code blocks for parity between both architectures.
 
-We're not here to give you historical information of it, but feel free to read [this documentary about the ARM platform.](https://en.m.wikipedia.org/wiki/ARM_architecture_family)
+We won't get into much detail regarding it, but if you'd like to learn more about it have a read of [this documentary about the ARM platform.](https://en.m.wikipedia.org/wiki/ARM_architecture_family)
 
-**You may encounter issues while using PojavLauncher on 32-bit devices. Here's a list of stuff that's known to be problematic:**
+**You may encounter issues while using PojavLauncher on 32-bit devices. Here's a list of things that are known to be problematic:**
 
 ## RAM Allocation
-* **Real 32-bit devices (32-bit hardware and firmware), can't allocate more than 768MB of RAM to PojavLauncher. This can't be changed even if the device has more free RAM.**
-* Examples of real 32-bit SoCs: Qualcomm Snapdragon 801, 800, 600, 400, S4, S3, S2, S1
-* **64-bit devices limited to 32-bit firmware can't allocate more than ~1000MB of RAM. As said earlier, this can't be changed.**
-* Examples of 64-bit SoCs limited to 32-bit firmware: MediaTek Helio G37, G35, G25, P35, P25, P23, P22
+
+**Real 32-bit devices (32-bit hardware and firmware), can't allocate more than 768MB of RAM to PojavLauncher. This CAN'T be changed even if the device has extra RAM to spare.**
+
+* Examples of real 32-bit SoCs: Qualcomm Snapdragon 801, 800, 600, 400, S4, S3, S2, S1, etc.
+
+**64-bit devices limited to 32-bit firmware can't allocate more than ~1000MB of RAM. As said earlier, this CAN'T be changed.**
+
+* Examples of 64-bit SoCs limited to 32-bit firmware: MediaTek Helio G37, G35, G25, P35, P25, P23, P22, etc.
 
 ## Performance
-Due to 32-bit's processing speed limit, Minecraft's performance is always compromised. Even with optimization mods installed, you may get big stutters even on lowest settings. Decreasing RAM Allocation may help performance in certain scenarios.
+Due to 32-bit's processing speed limit, Minecraft's performance is always compromised. Even with optimization mods installed, you may receive big stutters even on the lowest settings. Decreasing RAM Allocation may help performance in some scenarios.
+
+## Compatibility
+As of snapshot [24w14a](https://minecraft.wiki/w/Java_Edition_24w14a), Minecraft has officially dropped support for the 32-Bit architecture, ultimately meaning if you own a 32-Bit device you will **NOT** be able to run Minecraft 1.20.5+ on said device.

APPSTORE.md

@@ -1,6 +1,10 @@
 # Will PojavLauncher ever come to App Store for iOS?
 
-## from the AppStore review guidelines
-2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. Such apps must make the source code provided by the Application completely viewable and editable by the user.
-Also, $99 per year is required for pushing updates.
-So you will know if PojavLauncher will ever be pushed to App Store.
+### From the App Store review guidelines:
+__2.5.2__: Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. Such apps must make the source code provided by the Application completely viewable and editable by the user.
+
+Apple Developer Documentation Referenced: [Section 2.5.2](https://developer.apple.com/app-store/review/guidelines/#performance:~:text=Apps%20should%20be,by%20the%20user)
+
+Additionally, $99 per year is required for pushing updates.
+
+**If PojavLauncher is ever pushed to the App Store, you will know!**

CUSTOM-CONTROLS.md

@@ -1 +1,61 @@
-# Customizing the on-screen controls
+# Customizing the on-screen controls
+
+## Android
+
+ There is "Custom controls" button in the main menu, by clicking that you will be able to change you custom controls.
+
+<img src="https://github.com/user-attachments/assets/a476f630-c3a9-4c3c-83d1-ff39454d0105" width=45% height=45%>
+
+ You can access the options by clicking the cogwheel at the top of the screen.
+
+<img src="https://github.com/user-attachments/assets/8209a266-524e-45e2-b841-72f1d76aea43" width=75% height=75%>
+
+ After clicking the cogwheel, you get a drawer with the following options:
+
+<img src="https://github.com/user-attachments/assets/d70b38b8-2396-4bfe-b405-390a369f3776" width=75% height=75%>
+
+ 1- Adds a button of your liking.
+
+ 2- Adds a button drawer, if you press it, your buttons that you assigned will show up.
+
+ 3- Adds a joystick.
+
+ 4- Loads custom controls.
+
+ 5- Saves current custom controls.
+
+ 6- Option to select default custom controls.
+
+ 7- Exports current controls.
+
+## iOS
+
+To start editing your controlmap in iOS, head to top-left and press the sidebar. (shown in image)
+
+<img src="https://raw.githubusercontent.com/Dev1ss0/Dev1ss0.github.io/main/images/Actions/ios/IMG_3219.png" width=45% height=45%>
+
+Press the custom controls button.
+
+<img src="https://raw.githubusercontent.com/Dev1ss0/Dev1ss0.github.io/7d01c01011b0e135aac34849846a8fd48893ecbf/images/Actions/ios/IMG_3220.png" width=75% height=75%>
+
+After that, long press anywhere for more options.
+
+<img src="https://raw.githubusercontent.com/Dev1ss0/Dev1ss0.github.io/main/images/Actions/ios/IMG_3221.png" width=75% height=75%>
+
+Now you will get a pop-up with the following options:
+
+<img src="https://raw.githubusercontent.com/Dev1ss0/Dev1ss0.github.io/main/images/Actions/ios/IMG_3222.png" width=75% height=75%>
+
+1- Exits the controlmap editor.
+
+2- Saves the current layout/edited controlmap.
+
+3- Loads an existing .json (controlmap) from the controlmap folder.
+
+4- Adds a safe area where buttons are restricted from getting outside of the safe area, whilst not registering touches nor gestures outside the safe area.
+
+5- Adds a button to your liking.
+
+6- Adds a button drawer, has a function of adding a sub-button binded to its drawer. When pressed, buttons binded to it will show up, configurable to make it hold button instead of toggling.
+
+7- Adds a joystick.

DEVICES.md

@@ -11,7 +11,7 @@
 ### Recommended requirements:
 - Qualcomm Snapdragon 820 (or equivalent) with Vulkan API support
 - Android 8.0 and newer
-- 4GB RAM
+- 4GB RAM or higher (the more the merrier)
 
 ### ChromeOS
 - Chromebooks have very similar system requirements, however Android version does not matter, as long as you can install Android apps.
@@ -27,4 +27,4 @@
 ### Recommended requirements:
 - Apple A14/A12X Bionic SoC
 - iOS 14
-- 4GB RAM
+- 4GB RAM or higher

DISCORD.md

@@ -2,3 +2,5 @@
 
 The only official invite for the PojavLauncher server, beware of invites created by other users.
 [invite link](https://discord.gg/pojavlauncher-724163890803638273)
+
+NOTE: A Minecraft account is **REQUIRED** in order for you to be able to seek PojavLauncher-based support in the server.

FFMPEG.md

@@ -1,15 +1,15 @@
 # Exporting videos with Replay Mod
 
-1. Download the ffmpeg binary [here](https://github.com/Khang-NT/ffmpeg-binary-android/releases/tag/2018-07-31). Choose one according to your device’s architecture.
-	- (For GitHub builds) Due to the limit of Replay’s command window, you need to rename the executable to a short name, like -> `:fr:`. Let’s call it `<exec_name>`.
-2. Install an APK Editor from Google Play or everywhere else.
+1. Download the ffmpeg binary [here](https://github.com/Khang-NT/ffmpeg-binary-android/releases/tag/2018-07-31). Choose one based on your device’s architecture.
+	- (For GitHub builds) Due to the limit of Replay’s command window, you'll need to rename the executable to a short name, like -> `:fr:`. Let’s call it `<exec_name>`.
+2. Install an APK Editor from Google Play or anywhere else (Make sure to use safe sources such as APKPure).
 3. Follow the instructions of the app to add the executable to `/lib/<device_architecture>` folder of the  APK. Then build the APK and install it.
-	- (Required for a clean install) Install everything needed (Forge, Replay Mod).
-4. Now launch Minecraft. We haven’t done yet, so force close it after launching.
+	- (Required for a clean install) Install required mods (Forge, Replay Mod).
+4. Now launch Minecraft. We're not done yet, so force close it after launching.
 5. Find latestlog.txt. 
 	- Open it and find this line: `Added custom env: POJAV_NATIVEDIR=<directory>`. 
 	- Copy the `<directory>` part.
-6. Launch the game again, go to Replay Viewer and load the record you want to export.
+6. Launch the game again, go to Replay Viewer and load the replay you want to export.
 7. Follow Replay’s instructions to add keyframes, then (press T show mouse cursor and) click at `Render Camera Path`.
 8. Scroll to the bottom, paste the text you copied in step 5 into the first command line window, then write `/<exec_name>` (step 1) at the end of the text line.
 9. Tap `Render` and enjoy your video.

INSTALL.md

@@ -47,21 +47,28 @@ Instructions for installing PojavLauncher on Apple devices.
 ::: details Sideloading (TrollStore)
 We recommend TrollStore for all users if possible. This method allows for automatic JIT enabling, more memory allocation, and non-revoking installs.
 
+Note: **Enable URL Schemes in TrollStore settings.**
+
 ### TrollStore compatibility depends on whether your iDevice is arm64 (A8-A11) or arm64e (A12+/M1+)
 
    #### For arm64, TrollStore is compatible with the following iOS versions:
 
     - 14.0 to 16.6.1
-    - 17.0
+    - 17.0 
+	- 16.7 to 16.7.8 (*)
+ 	- 17.0.1 to 17.5.1 (*)
+  	- 18 b1 to 18 b4 (*)
+
+ (*) - requires the palera1n jailbreak
 
    #### For arm64e, TrollStore is compatible with the following iOS versions:
 
     - 14.0 to 16.6.1
     - 17.0 (*)
 
-	(*) - No Installation Method.
+	(*) - No installation method at the moment.
 
-1. Follow the steps to install [TrollStore](https://github.com/opa334/TrollStore).
+1. Follow these steps to install [TrollStore](https://github.com/opa334/TrollStore).
 
 2. Download the latest release from [here](https://github.com/PojavLauncherTeam/PojavLauncher_iOS/releases/latest/download/net.kdt.pojavlauncher.ipa).
     - For a specific release, you can find its package on the [Releases](https://github.com/PojavLauncherTeam/PojavLauncher_iOS/releases) page
@@ -71,8 +78,8 @@ We recommend TrollStore for all users if possible. This method allows for automa
 You can now enjoy Minecraft: Java Edition on your iDevice!
 :::
 
-::: details Sideloading (Unjailbroken)
-**Requires an active Apple ID, that has signed into the [Developer Portal](https://developer.apple.com/account) at least once.**
+::: details Sideloading (Jailed)
+**Requires an active Apple ID, that has signed into the [Apple Developer Program](https://developer.apple.com/account).**
 
 PojavLauncher supports being sideloaded with AltStore, Sideloadly, and Xcode. Instructions to use AltStore are below--for other options, refer to their documentation.
 
@@ -88,7 +95,7 @@ Installing PojavLauncher is not the end for iOS devices. In order to play Minecr
 ::: details Sideloading (Jailbroken)
 **Currently, AppSync Unified is not supported.** There is an [issue](https://github.com/akemin-dayo/AppSync/issues/108) regarding the data directory when installed with AppSync.
 
-You can follow the `Sideloading (TrollStore)` or `Sideloading (Unjailbroken)` steps to sideload on a jailbroken iDevice. Regardless of the method, you will benefit from automatic JIT enabling and more memory allocation.
+You can follow the `Sideloading (TrollStore)` or `Sideloading (Jailed)` steps to sideload on a jailbroken iDevice. Regardless of the method, you will benefit from automatic JIT enabling and more memory allocation.
 :::
 
 ::: details GitHub Actions

IOS-SUPPORT.md

@@ -1,14 +1,14 @@
 # System support in future versions of PojavLauncher iOS
 *This announcement will be covering the next 3 releases of PojavLauncher iOS.*
 
-We've made some great strides with the iOS port of PojavLauncher: fixing [1.17 and newer](./OGL32.md), bringing [OpenJDK 8 to iOS](./JDK8.md), and now unveiling an [unjailbroken variant](./UNJAIL.md). However, all of the advancements we're making also stirred up old conversations, and we've come to a final conclusion: 
+We've made some great strides with the iOS port of PojavLauncher: fixing [1.17 and newer](./OGL32.md), bringing [OpenJDK 8 to iOS](./JDK8.md), and now unveiling an [jailed variant](./UNJAIL.md). However, all of the advancements we're making also stirred up old conversations, and we've come to a final conclusion: 
 
 **A future release of PojavLauncher will require iOS 14.0 and later.**
 
 ## But why?
 Supporting iOS 12.0 and newer was a feat of engineering. However, it created multiple issues with feature support and user experience. We need to verify that our code works on iOS 12 before going ahead and compiling--if it does not, this complicates our development as we are faced with two options: dropping the feature on older versions, or importing external libraries. This causes slower development times, or lack of the feature entirely for our users.
 
-We also took a look at the userbase currently playing on PojavLauncher. Most of the users asking for support in our Discord server (which is many times more active than the Issues tab on the GitHub repository) are already running iOS 14.0 or newer, and a few cases of users on iOS 13. We barely see users running iOS 12 anymore, and now that PojavLauncher works unjailbroken, users can update to a newer release of iOS while still retaining Java Edition.
+We also observed the userbase currently playing on PojavLauncher. Most of the users asking for support in our Discord server (which is many times more active than the Issues tab on the GitHub repository) are already running iOS 14.0 or newer, and a few cases of users on iOS 13. We barely see users running iOS 12 anymore, and now that PojavLauncher works jailed, users can update to a newer release of iOS while still retaining Java Edition.
 
 This decision also comes after we understood that we don't really have the ability to test on these older versions anymore. Our devices are already running iOS 14.0+, and so are most of our testers.
 
@@ -48,4 +48,4 @@ As part of this deprecation, beta builds of PojavLauncher 2.4 will move to iOS 1
 :::
 ::: details PojavLauncher 2.4 - iOS 14.0+ completed
 PojavLauncher 2.4 will complete the transition to iOS 14.0 APIs and be incompatible with iOS 12/13 without modification to the source code. 
-:::
+:::