betacraftuk / betacraft-launcher

A launcher for Minecraft focused on legacy versions of the game
https://betacraft.uk
GNU General Public License v3.0
320 stars 41 forks source link

[Linux] When clicking (left or right click) in Classic / early Indev versions, pause menu opens #168

Open Secret-chest opened 2 years ago

Moresteck commented 2 years ago

Provide more information (your distro, kernel version, desktop environment, Java version)

Secret-chest commented 2 years ago

Linux Mint 20.3, Linux 5.15.0-41, Cinnamon, Java 8

Moresteck commented 2 years ago

I managed to reproduce the issue. Will see what I can do with it. Seems to affect precisely c0.0.13a_03 to in-20091223-1459, then in-20100131-2244 to a1.0.1

Secret-chest commented 2 years ago

@Moresteck any progress?

Secret-chest commented 2 years ago

@Moresteck please fix

ghost commented 2 years ago

this also happens with ARM Linux.

SprainedSpark89 commented 1 year ago

try turning on offlinedat save and login when using indev and infdev

Secret-chest commented 1 year ago

try turning on offlinedat save and login when using indev and infdev

How?

SprainedSpark89 commented 1 year ago

go into edit instance to turn on offline save and press login to login to your minecraft account

Black-Rock-Shooter commented 1 year ago

I'm also getting this issue, so far on almost every classic-infdev version I've tried. I can still open chests, for example in in-20100128-2304(1.049) in the indev house, but sometimes it doesn't, as if my crosshair isn't quite where it appears to be(And by centering my cursor when in the menu, then unpausing and moving slightly, then pausing again I can see that my cursor is not being locked to where my crosshair is during play. Hopefully this could be a clue?). I've tried logging in as well as turning on the Offlinedatsave addon, but neither seem to have changed anything. My system info: Distro: Ubuntu 22.04.1 LTS (64-bit) Kernal: 5.19.0-38-generic Desktop: Gnome 42.5 Java: Openjdk version "1.8.0_362"

Secret-chest commented 1 year ago

@Moresteck anything more? this is critical

Moresteck commented 2 weeks ago

Might not fix for v1. But if the problem still persists on v2, we are going to fix it