Juha-Jarmo Heinonen
Assigned
Reported
Comments
Josh: That's actually their problem. If they wish to ship a broken product, it's up to them. Doing that would just be very unprofessional and demonstrates their lack of skill, but as we see, these guys are total amateurs. Remember, if this was open source, it would be a different situation. These guys get paid for what they do, it's just not a hobby they do for free, like open source is usually about. However, they bitch about an open-source framework they decided to use, like that would be an excuse.
Also, just piss me off a little bit more and my attitude of disappointment in minecraft (which I'd played more and recommended more if bugs like these were resolved in a timely manner) turns into hate towards Mojang, their developers and maybe even the game itself. It's your choice. I'm expecting an apology.
I'm here waiting-for-the-promised-ban doing my best at reminding everyone what this attitude is about, since you brought it up. This bug is still in all shipping units of Minecraft, so it's good to remind of it sometimes.
In soviet Mojang the customer must respect you.
The bug reporters are doing Mojang a favor here, not the other way around. The favor is finding and reporting bugs that would be a lost sale otherwise. Normally, software companies would need to hire their own testers. Remember that.
To me, this just sounds like Mojang is exploiting the attitude towards free open-source software and applying it to closed, commercial software.
Martin: Two years or so is a short timespan? And yes, in the commercial software world, the developer is responsible for their product. Just like an automobile maker would be responsible for fixing a car they sold with faulty brake pedals. Even more so, if they did a recall (update), where they broke it.
Minecraft - Reporting bugs is a privilege.
Especially early adopters should be banned, they have been whining about the same bugs for years! What good did they ever do to the game, right?
Grum: Then why not do it already? Why not ban all bug reporters, they're just annoying whining about bugs and stuff, right? Minecraft would be so much better without bug reports! It works so fine for you with your tweaked out dependencies that it doesn't matter what shit you distribute?
Martin: As for Java applets in the web browser, no it's not just Apple disabling it in Safari, it's Firefox and Chrome etc also disabling it in their browsers. Should be done on other platforms too, Java has been ridden with (cross-platform) 0-day exploits for quite a while already, and browser Java Applets were practically dead anyhow. Good riddance, I'd say. However, that's entirely offtopic and should be discussed elsewhere.
Grum: Ok, so apparently it takes a "horrible attitude" to fix one. Anyhow, good to finally have even a temporary solution and able to play the game without falling from heights or into lava etc because the key bindings are broken. As for the display value, I wouldn't care even if it was just showing hexadecimal values.
Markku: meanwhile I've been troubleshooting everything from installing and launching with Java 1.7 instead of the standard 1.6, running in 32bit mode, using latest stable and latest nightly lwjgl, etc. No effect on the issue, and mc is still the only app/game to do this. I also spent a fair while at browsing the lwjgl source, and nothing to be found there either, not at least on a glance. Meanwhile, the Java applets have become completely unsupported on this system, even Firefox has disabled Java completely now.
Also, created a new user account, same issue. Tested on another mac, same issue.
Martin: Good to hear.
Grum: 200% sure everything is vanilla here. Nothing about Java has been touched; that's on system defaults. I renamed the ~/Library/Application Support/minecraft directory too, and removed "/Applications/Minecraft.app". Then re-downloaded and had it re-install. Still, exactly the same issue.
Markku: yes, the NONE -keys apparently work. However, the duplicate ones don't. They also don't work when forced into the config file. I don't care about what's displayed as long as the keys work.
Some keys are also impossible to bind even on QWERTY. For instance, I'd prefer the Command to be the key on the right of the left shift, which is ` on Dvorak and exists on US-QWERTY on the left of the 1 -key. It's simply listed as NONE. Same for the keycode for the § key, which is where US-QWERTY's ` -key is. There are probably others, but IMO this demonstates it's not just Dvorak layouts where key bindings are broken, and broken in the same way as listed in the description of this ticket, just NONE and NONE on the leftmost keys on the top and bottom row in addition to that.
And yes, I'm 100% sure it's vanilla minecraft and the LWJGL version bundled with it. Grum: Are you sure your LWJGL is the one shipped with minecraft?
Same keys, minecraft 1.4.7, OS X 10.8.2, MacBook Retina, Dvorak layout. Not sure about circumflex, but I picked the key one row under A. The command is the slash key, which is also a Z. The forward is the dot (QWERTY-E) and backward is E (QWERTY-D).
Adam: What did you expect, some professionalism? No, these guys seem to be total newbies at issue tracking. For every bug reported, there are plenty of unreported bugs. For every bug reporter, there are hundreds or thousands of people who don't bother. How are they going to fix this issue by themselves? Especially as the mojang-lwjgl attitude is blaming each other back and forth, which has been my experience of this matter.
These guys should treat bug reports with some respect, instead of going trigger-happy prematurely closing everything. I guess this issue has to be cloned by someone yet again. I don't have permission to do that, so it's up to someone else. Anyhow, I'm pissed off now, so yeah. Definitely not going to recommend to anyone, also going to shut down my the server which many people enjoyed and will recommend one of the clones instead.