Minecraft-Performance-Flags-Benchmarks VS minecraft-wayland

If that doesn't work, try using Java arguments: https://github.com/brucethemoose/Minecraft-Performance-Flags-Benchmarks and/or increase the amount of allocated ram to 10GB.

You can try Java tweaks - https://github.com/brucethemoose/Minecraft-Performance-Flags-Benchmarks or performance mods - https://github.com/TheUsefulLists/UsefulMods

If you insist, though, there's this page that talks more about JVM arguments.

Take a look at https://github.com/brucethemoose/Minecraft-Performance-Flags-Benchmarks

I can't attest to how valid these benchmarks are, but this explores the topic - https://github.com/brucethemoose/Minecraft-Performance-Flags...

Are you using the patched GLFW?

I'm making an attempt to make Minecraft run natively on Wayland using these instructions. One of the steps is to patch libglfw, provided by the glfw-wayland package. I have no experience with compiling xbps packages from source or applying diff patches.

Download the one-nineteen branch and unzip then inside the folder run makepkg https://github.com/Admicos/minecraft-wayland/tree/one-nineteen

for 1.13 and onwards, theres a guide here that makes the game use a patched GLFW version to run (effectively) nativly on wayland with some (if any) performance loss.

Once that's corrected, I think you chose the patch url wrong given that all it is is a README change, which you even filter out. I assume you want the .patches that were committed to the upstream repo?

I followed this guide.

prev: final: { glfw = glfw.override (oldAttrs: rec { patches = oldAttrs.patches ++ [ (prev.fetchpatch { url = "https://github.com/Admicos/minecraft-wayland/commit/ceda97a3f0717050f27093ed2b6682b29415e8d1.patch"; sha256 = "0000000000000000000000000000000000000000000000000000"; excludes = [ ".SRCINFO" "PKGBUILD" "README.md" ]; }) ]; }); }

I have four different .patch-files (from here) in /etc/portage/patches/media-libs/glfw/ and expected portage to automatically apply these patches when emerging media-libs/glfw, but it somehow doesn't.

Already possible.