Ctrl+Click = Right Click on Mac not working

Please do not mark unreleased versions as affected. You do not have access to this yet.

Duplicate of MC-13841. Yes, this one was reported earlier, but all the other duplicates have been redirected to MC-13841.

This is an issue with the new version of LWJGL (2.9.0) shipped with the new launcher.

Is there any sort of bug report that I can track in LWJGL?

This is a ruinous bug for MacBook users, and yet I can't find any report for it that isn't marked "Duplicate" or "Invalid."

The reason this is invalid is that it isn't Minecraft's issue. The new version of LWJGL that the new launcher automatically installs is the cause for this bug.

A bug (or feature downgrade) introduced by software Minecraft installs and uses heavily seems like something worth letting people upvote here if it's important to them, regardless of whether someone at Mojang personally programmed the thing in question. Mojang might be inclined to make a specific workaround for it if a lot of people indicate they care, for example (and users could express their concern in vote form without having to post comments that have to be read, like mine).

It's unfortunate that all the duplicates have been redirected here, because Grum has commented on MC-13841, where all the duplicates were previously directed. I'll copy it here for convenience:

Not sure what to do with this. This is indeed changed because of lwjgl, I can indeed see that if you were used to this ancient mac behaviour that you might want it back (I mean, nowadays they make mouses that actually have 'two buttons' (not really but you can still do the gesture on them).
I think we might need some sort of option for this. However it will also destroy the possibility to 'record' ctrl being used as a modifier for other things.

I agree with above commentors. The bug is indeed ruinous for those on macbooks with no mouse. I would like to be able to vote for this issue. I'm frustrated to see it marked as invalid. Please help.

So, since Grum has seen the issue, does that mean it will be fixed? It will involve possibly reinstalling the new launcher. And if it is not resolved, where do we report bugs for the new launcher?

I copied Grum's comment here in hopes that people would read it. Let's try this again, slowly:

Not sure what to do with this.

Grum recognizes that it's a valid concern, but doesn't yet know what the best way to solve it is, or if it can even be reasonably fixed.

I think we might need some sort of option for this.

He's got an idea, and thinks this is a valid enough issue to make an attempt at solving it. He's not making a guarantee that they'll be able to, but they're going to work on it.

Part of the point of the new launcher is that it's supposed to be able to update itself, which the old one wasn't capable of. You'll still probably have to redownload it once 1.6 goes live, but after that, you shouldn't have to manually update or reinstall it. It's unlikely that they'll make a separate project for the launcher, even though it's technically a separate program, because it is so closely related to Minecraft. Thus bugs for it should be reported here on the Mojira, under the Minecraft project, until further notice.

Why, oh why, is this INVALID?

So basically buy a mouse or you can't play on a Mac with a trackpad? Yeah, how about no?

Why, oh why, can't you READ?
Because it's an issue with lwjgl, and not Minecraft. Grum may create a workaround, but the actual issue described here will either be fixed by lwjgl, or not at all.

Hi Torabi, thank you for your kind and patient response.

We have indeed read and comprehended Grum's comment. Thank you for adding it to the thread.

Reasons that people continue to respond:

• Grum's original suggestion of just using a mouse suggests that he isn't a mac/laptop user. We are providing perspective.

• Bugs in vendor libraries can indeed be addressed by a company. Mojang has worked with lwjgl to get issues addressed in the past. Please look on the net and you will see this. At the least a reference to the corresponding lwjgl bug would be helpful, but perhaps this is not available.

• A closed bug with a quiet comment thread doesn't seem likely to get addressed. "May create a workaround" is better than nothing, but.

• Most importantly, when I do a two-finger tap, I flub and end up hitting testificates in the head and my iron golem kicks my ass 🙂.

For the time being, I have remapped the right-click to "R", but the setting does not equally apply to inventory management (I still need a double-click to divide a pile in two, drop one element of a pile, etc.) It is confusing to have the remapped controls apply to placing the block but not to inventory management.

Since we can't vote for this issue (I think), I suggest that people who care add themselves as watchers for this issue.

Does anyone know--is there a way to downgrade lwjgl or is that crazy? If so wouldn't that fix things for us? As far as I'm concerned, this is a game breaking issue, even if Mojang aren't responsible directly.

@Torabi:

If a game is made for a platform, why can't newer technologies be used? Minecraft has been designed for multiple specific platforms. Mac OS X is one of them. So it should technically be able to run properly (disregard minor bugs, they'll happen anyways), but as of right now it does not. So explain to me why there is even a version of the new snapshot or launcher when it doesn't work right unless you change bindings or use external hardware?

I've never encountered games that are built for one platform, such as XBox, Wii, or anything else like that where one key or button doesn't work in that particular game, but in other games it's fine. That shouldn't happen, and it's a good thing that most of the time it doesn't! So why not actually fix the problem instead of making the minority group use workarounds? Other games that use LWJGL work fine with Control-Click, but Minecraft doesn't. It's fixable and should still be a valid issue, because that's exactly what it is: A valid issue.

I agree, I am NOT (NOT, EVER) going to purchase a mouse to play a game that worked perfectly fine before the new launcher and library updates.

THIS IS NOT RESOLVED! I thought Mac and Windows users were both treated equally when buying this game, obviously they don't care if Mac users are struggling to play with weird controls.

Indeed. At this rate, a status of "Won't Fix" would at least be more honest. A comment from Mojang saying, "Up yours, MacBook owners," is optional.

We pay for the game to support you guys, instead of pirating it. All we want is more bug fixes 😞

As of 10 May, this issue is still unresolved; why it's marked "resolved", I don't know.

This issue has been a problem ever since the new launcher was released, every snapshot i check and see if it is fixed and it still isn't so why do all these say there resolved when there not. And im not going to use a mouse because ive always played with a trackpad on the old launcher and it worked just fine. I think out of all platforms minecraft is on mac osx is the most neglected. So please fix this or I will just stay with the old launcher.

@Todd Turnidge
I actually develop on a macbook, I hate playing using the trackpad which is why I just never do this (and probably also didn't notice the change)

@FireHunterX
Also Minecraft is most definitely not `designed` for multiple platforms, that is just a benefit of java. The only thing we do is pointing at a 'sane' user-folder.

@Andy Smith
All users on whatever operating system are just users, we all treat them the same.

@Cole Kelley
If any platform would be 'neglected' it would be linux, non of the developers of Minecraft run that. Also there is no way to use the old launcher for snapshots after 1.5.1 or upcoming 1.6.

And slightly more back ontopic:
We could in theory attempt to emulate this behavior in Minecraft but I rather not, it should be fixed in the 'right place'.

If you really think this is a major 'bug', please file an issue at: https://github.com/LWJGL/lwjgl/issues

Sofar no-one reported this bug to LWJGL leading me to believe it's not a serious issue?

Issue is now reported: https://github.com/LWJGL/lwjgl/issues/37

Grum, it's not an serious issue, it has only 2 votes.

This issue is not supposed to be 'closed'.

Grum: Thanks for your attention and your reply on Github. In addition to the inability to upvote, I was experiencing an inability to comment on this thread (until you reopened the issue). It's odd because I was able to comment here when it was locked before, but I don't know if something about the bug tracker was changed or if a mod considered the discussion here unhelpful. Anyway, reopening appreciated and I'll cease the general grumbling now.

Although Grum believed this issue was closed by a bot, according to the history it was actually closed by @unknown on May 12th, probably to silence the whining. As to why there was only two votes, most people, here or on just any other website with a voting function, have trouble finding, using, or understanding the value of it. For some reason, they can figure out how to post, but clicking a voting link is too difficult. If you want people to use the function more, you're going to have to emphasize both its existence, and its role in issue prioritization. If people believed it made a difference, then they'd do it. Otherwise, they'll do what satisfies their egos: shout at the wind.

Issues marked as "Resolved" cannot be voted on. They retain any vote totals made before the transition to that status, but votes cannot be added or removed. This issue has been marked resolved (or closed) since April 19th. Since it was created on April 18th, there was only a single day for users to vote on it. Users are quite obviously poor at searching (see the 26 duplicates of this issue, or just filter on Duplicates - currently sitting at 9898 issues out of 17208, for nearly 58%!), so most people would be unlikely to find this in a week, let alone a day.

Issues marked "Closed" cannot be voted on, or commented on, at least not by regular users. Seeing as Grum, Tails, and Kumasasa all posted while it was closed, [Mojang] and [Mod] users can apparently still comment. I'm not sure if this is the default behavior of JIRA (the documentation does not specify, as far as I can find), or if the workflow has been customized that was (which the documentation does indicate can be done). Regardless, that's how it currently appears to work.

@Torabi

Most of us kept starting new threads knowing full well there were others because each one we started was subsequently locked without a satisfactory answer.

I'd say the two comments above accurately summarize the current situation for the bug report. As for the bug itself, I myself am refraining from updating Minecraft because the issue has been so distracting. As has been stated, it seems the problem lies outside of the realm of the Minecraft development team. I'm not sure at what frequency or leniency the LWJGL is updated, especially for OS-specific issues that don't affect major performance, but I'll still hold out hope that it will be changed. I don't know what more can be done here by the regular Minecraft users.

There are usability problems by just introducing 'ctrl-left-click' as 'rightclick'. Like not being able to drop a single item from the stack, because 'ctrl' is pressed when you 'fake' to use the right-mouse-button which drops it on the floor.

From my POV the 'ctrl-leftclick' being 'equal' to 'rightclick' is just the worst horrible kind of hack from the period where some group of people though it was 'superduperuseful' to have a 'giant single button mouse'. Must have been too expensive to have that second button.

Unless we're getting these events actually as mouse-events without modifiers being pressed you will always have weird behavior using this hack. Which is where LWJGL has to come in.

I'd like to note I think one-button hardware is arrogant and stupid; nuts to Apple for doing it. All the same, lots of us have this type of setup. Also, Control isn't used for a lot in Mac software (owing mostly to its use as a right-click modifier?); Command is the modifier of choice (it's the Mac equivalent of Ctrl in Windows). In this regard, I'd kinda fault Minecraft for hard-coding the Control key when everything else is configurable.

What all is the Control key used for in Minecraft? The only thing I can think of, or find on the wiki, is Ctrl+Q to drop an entire stack. Is it really a hack to allow the user to assign modifier+key or modifier+button combinations to a specific function? Is the issue that you've hardcoded control and shift to do specific things, even though the sneak command is configurable, but bound to shift by default?

Most applications that allow you to configure keyboard shortcuts allow combinations of modifier keys, such as "ctrl+shift+e". Is it somehow more difficult to recognize modifier keys in combination with mouse buttons?

@Grum,

Since you've got a stick up your butt about "no right click" let me bring you up to date on Apple hardware. MacBooks have no button at all. It's one big trackpad, and you can click down part of it. Rest another finger on the trackpad when you click, and you've got yourself a "right click" menu. For every function except games, this is FASTER than a windows laptop with two separate buttons, because the thumb doesn't have to move at all. It just so happens that Minecraft interprets this natural modified click by scrolling through the hotbar. An imac or mac pro, likewise, comes with a mouse capable of a traditional left and right "click", they just aren't buttons. But none of us are using a desktop--that's the point.

As for "hacks" etc, the game works perfectly in its present state. There is no weird behaviour. I can drop a single item from the stack using the K key which I have assigned that to.

In the interest of sharing, I have an older MacBook with a single trackpad button. At work, I use a Magic Trackpad, but at home (the only place where I play(ed) Minecraft) I use the laptop without peripherals (there's only room for a laptop on my cooling lap pad). In either mode, I use software called BetterTouchTool to reconfigure which buttons do what: on the Magic Trackpad, tiptap-right (index to index+middle) is my right-click, but with the built-in trackpad I stick to Control-click because the small trackpad was picking up stray tiptaps too much (especially in Minecraft). Two fingers at once is my scroll function.

I dislike any Minecraft right-click solution which conflates "look" with "destroy" or "use," because it's really nice to be able to let up on the action while continuing to look around at what's jacking me up from behind. (Also, two fingers would apparently overlap with scrolling, as the above post brusquely described.) To that extent, I'm not sure how well I'd handle the buttonless trackpad described above.

But getting back to the point: I still heavily use Control-click as right-click at home, it worked well for Minecraft, and I think at least part of the latest problem could be solved by not hard-coding Control to game functions (Control isn't just any old key in OS X; Command is a better equivalent for how PC users treat their Ctrl key). All the alternatives I've tried in Minecraft have left me feeling so clumsy that I'm more comfortable just not playing at all.

Dear devs, I really don't give a rats ass why this doesn't work anymore. But I, and as it seems many others, were using it. For us, it is about as bad as having to press 7 to walk forward instead of w. You would fix that, wouldn't you? I was able to do speed challenges with my trackpad before this!

Don't whine about technical difficulties… Just acknowledge the bug to make everyone happy. And fix it eventually. And don't just close your eyes and actively try to avoid to even figure out how many people are affected by this.

It seems a certain (smallish) subset of players feel passionately about this change. I wish we could collectively be passionate about it without being so rude, but anyway, the analogy about the W key isn't unfounded; this method of right-clicking was a critical part of our ability to play well.

I am a "passonate" Mac user and I have adapted my gameplay around using X to place blocks and use items. I have remapped CTRL to bring up the command console (as if I pressed /) to retrain myself not to use CTRL anymore.

I can still split stacks with two finger clicks. I can still place one item from a stack with two finger clicks.

I don't like this, but I am able to play Minecraft at about the same proficiency as I did before the change to LWJGL. I don't think the average player impacted by this will find it very convenient and likely they will stop playing all together. They will probably be even more rude than the people in this thread. It's unfortunate, but true.

I understand Mojang's position that it's not really their bug. I understand the user's frustration at Mojang's assertion that it's not really their bug.

Maybe what Mojang should do is either officially drop Mac Trackpad support or fork LWJGL to fully support it. LWJGL has taken the Mac Trackpad hostage and if Mojang is ok with that, they should make it official.

To make it a little more clear what the actual problem is, here one of the scenarios where it matters:

To craft a furnace, I used to take a stack of stone, hold control and draw a circle on the workbench while clicking at every cell. Now I have to stop at every cell, move a second finger to the touchpad and then click (I use the real button to klick, not just a touch). This takes about 3 times longer and feels extremely annoying.

I don't think we should file a bug at LWJGL, since it is not. They changed the behaviour. The bug is Minecraft relying on the thing they changed. It's not about emulating right clicks, but using control as a modifier key for certain actions.

Wait so you're seriously not going to fix this for the new release? Well, maybe the optifine guys will work something out. The modding community has always worked much harder and been far more innovative than the MC dev team anyway (only Notch excluded).

Insults aren't necessary; let the vote count here speak for itself. As 1.6 goes live and the wider community begins to complain on forums about the change (assuming 1.6 updates everyone's LWJGL version), let's link them here and tell them to vote it up.

It would be in Mojang's interests to sort this out before release, or at least have a plan. It will be perceived as a withdrawal of support for the mac (especially in conjunction with the response to "designed for" the mac earlier from the Mojang staff). It is effectively unplayable for me this way. I want to upgrade my SMP server. My other players will want horses. I won't upgrade if I can't play! If I get stalled too long on this I'll be gone. Minecraft is awesome, but if it's too hard, there's other things in the world that are awesome.

It seems very possible to me that this isn't a bug with LWJGL, and they've just decided that direct key access is more important for games.

Either way, Mojang, if you just add key-customisation for the other places we use clicks/right clicks, or have a check box at the top of the customisation to use the fight/use keys for all click/right click areas, that would be enough to hold me. A promise probably would, actually.

One further comment - Mojang, you're the ones responsible to your user base. Blaming the library and shrugging off responsibility is not a good look, even though it's a sadly common malaise among IT staff. Be the leaders here. It's your code. If you think it is a problem with the library, please raise it as an issue yourselves. Because it's your code, you can provide much better and more relevant information to LWJGL than we can. We'd be happy to throw votes behind it. We have supported your program. Support us. Do the right thing here.

They should just duplicate the same setup as the other versions, such as windows and linux

Previously, LWJGL on a Mac told Minecraft that it had received a right-click when it had actually received a ctrl+click. Now, LWJGL is passing the ctrl+click to Minecraft. I can understand why they wouldn't want to implement a check to determine whether the game is running on a Mac, and whether the user has a one-button mouse or trackpad, and conditionally interpret ctrl+click as right+click. That's just messy, and LWJGL is supposed to handle most of the platform or hardware dependent stuff for them. The Minecraft code is platform-agnostic, and that's how they want to keep it. Mac and Linux support is basically a freebie because it's Java.

The clean solution, however, would be to let the user assign ctrl+click to button 2 in the Minecraft options. Ideally, you should be able to assign any combination of modifier + key or button to whatever you want, rather than control and shift having special meanings that cannot be changed. Shift is particularly problematic, because it is by default assigned to "sneak", but also has other special meaning that doesn't change when you reassign the sneak function to another key. When they're both bound to shift, you can't tell the difference, but if you change the sneak key, certain functions will still require you to hold shift, while others will require you to hold the sneak key instead.

The problem is this just isn't "fun" code, isn't some cool new feature for a developer to get excited about. It's a quality of life issue, one that apparently doesn't affect any of the Mojang developers. They apparently all use the default keys. See MC-5687 and MC-14126.

What Torabi said.

What would be of great benefit to most players would be proper key assigment, where using modifiers actually work. Right now, Mojang argues that if they enable ctrl+mouse1 as right click, they can't use the modifiers for other stuff - why not leave this up to the user? Default keys as they are, but allow for changing key binding for all inputs, not only the basic stuff. Of course, this would be considered a more advanced setup, that might be better off hidden behind an "Advanced controls" button or so, but it would allow for much more customization for the gameplay. I know that I would like to rebind certain functions to be on the same key, with modifiers, as that's how I usually set up most of my other apps where that's possible.

They couldn't use the ctrl key for anything else so far, because it was pre-mapped on macs; so what changed? And why not just a different modifier key, like command (which doesn't even exist on other platforms). Command would be even better than ctrl, since shift can be pressed at the same time.

I even think other platforms would benefit from a modifier key as right-click alternative. How many times have you hit your dog when you wanted to make him sit? You can make fun of single button mouses as long as you want, but they are easier to use. IMO, right clicks should never be used for primary functions.

I'm not a big fan of having to change some "advanced controls" before being able to play the game. It should just work.

This could be fixed by just providing the option of allowing the user to select what version of LWJGL they want.

I can't fathom that being a viable option, insofar as Mojang upgraded LWJGL because it included features they wanted to take advantage of in 1.6 and beyond, didn't they? I vote in favor of making all modifier keys configurable to give the option of freeing up Control for faux-rightclick. I still haven't heard any explanation for why Control was ever given hard-coded functions to begin with.

I say we start a fund to hire the OptiFine guy to build a fix.

I have the same problem CAN SOMEONE PLEASE TELL ME HOW TO BRING BACK Control + Click

@ Sky Michael Scott

There is no way to get control+click back. There might be eventually, but not now. Also please click "vote" at the top because that's the only way Mojang will consider this important.

This affects the release version 1.6.1 and is absolutely NOT the way to code for the Mac platform. Control-click is a "right-click" in the Mac UI.

Just use the right click built into the mouse or trackpad. I am a mac user and I find it tedious to use control+click.

Ezekiel, simply because an alternative works for you does not make it the correct UI approach. Many of the modern trackpads are not by default configured for the "built in right-click" you mention - this behavior has been deprecated in the Apple UI in favor of the double-tap and control-click.

what I am talking about is the double finger click. I agree it's a bug, but it isn't a critical bug.

It's worth noting that downloading 1.5.2 using the new launcher into a new profile fixes the issue. If it's a major problem I'd stick with 1.5.2 until Mojang fixes the issues. I must admit though certain aspects of the new update are very sloppy. I tend to think the only thing Java has going for it is cross platform compatibility.

We have told @Ezekiel this before but he does not listen. Two-finger-click for right click is incredibly cumbersome and slow in Minecraft. It also ends up spinning you through your hotbar half the time. Dumb.

@Peter Day

Agreed about sloppy, in general. They pushed through another cycle to give us...the carpet update? Wow...

this is a huge issue for me, like others, I rely heavily on the Control + Click to play this game.

This happens to me too and heavily affects my ability to play.

Everybody who wants attention on this issue: VOTE AT THE TOP. That is how to get Mojang's attention.

I have been using a MacBook for awhile, and when this issue came up, I have had so many issues playing. Punching my horses in the face is not ideal for me. I've resorted to a wireless mouse, but this is VERY annoying due to the fact that I am using a laptop, not sitting at a desk.

A passable solution for me is to use one of the bottom corners of the trackpad to right-click- it takes a couple seconds for your finger to get over there, but it's better than the two-finger click.

and as i'm sure everyone has deduced by now, this is present in 1.6.1.

While I appreciate that this bug appeared because of an update in lwjgl, it would be nice if we had more options when it came to key customization. My first instinct was to reset left-click to ctl-click, but the game will not recognize these input combinations.

As many people have pointed out, Apple has begun to move away from traditional mouse layouts in their design logic. Some of these changes are good, they let me work faster in the programs I use professionally from home, but some of these changes are difficult when it comes to java-based and platform-independent games.

I would vote for giving more options in the control selection menu over asking the developers to hack a mac specific fix. If lwjgl is now recognizing ctrl+click as ctrl+click instead of left+click, fine, at least give me the option to set that in my controls menu.

...Count me as one of the people who was really excited for horses and crushed to find 1.6 essentially unplayable on my MacBook. A little warning would have been nice, at least.

This decision on the part of lwjgl is irritating, but I think the suggestion above-- the ability to use modifier keys in setting key bindings-- would be a nice compromise.

I use a Mac OS 10.6 desk top and I have the same exact problem as everyone else. 😞

I have been using the control+ click for right click on my Mac for years and I won't stop now. Please change/ fix the controls soon! It is incredibly frustrating trying to adjust to right- clicking with two fingers on the mouse pad. i am also one of those people who find Minecraft drained of a lot of its fun. 😞

Another long time user (since alpha) on a MacBook Pro that is greatly affected by this change. I waited until the release of the update to try it, and now can't really play comfortably at all. If I could simply map ctr+click to be right click most of the problems would be fixed, but you can't seem to map modifier+key, only single keys.

I do agree with several others who said that ctr+click should just automatically be interpreted as a right click the way lwjgl used to do it. If the lwjgl people changed this for some reason and won't change it back, Mojang should just do it on their end instead.

Also a long time user on a MacBook Air and I can't use control click to do anything anymore 😞 Super bummed about this regression.

So what is Mac Version, for what did he made Mac Ver.?
Virtually Mac Users use MacBook series with the multi touch trackpad.
Already Apple casted away the super combo drive, you know. the mouse is too.
so we need A control click, we don't need a retrogression.

bump!!

+1 for super bummed

I took today off work to have fun with 1.6, and now discover I can't enjoy playing it until this bug is resolved.

Also a little pissed off to be told "buy a mouse", even as a joke. https://github.com/LWJGL/lwjgl/issues/37#issuecomment-20333665

"Fixed". I've hacked some rudimentary support for this into the game and tested the usual suspects of stack-splitting, single-item-dragging.

Side-effects:
1) Anything that use CTRL before now exclusively uses CMD on osx. (Meaning the default stack-drop-keybinding will quit your game 😃)
2) Wonky button-states when releasing a 'fake'-rightmouse press.

Obviously bugs reported against those two issues will be pointed straight here 🙂

Let's see if this makes the game playable again for you guys.

It'll be in 1.6.2 which should be out 'soonish'.

Whey! Cheers Grum!!

Thank-you.

Thank you Grum!! Can't wait for 1.6.2 and give this a try!

What do you mean for side effect 1?

I too am experiencing the missing ctrl-click and option-click on the Mac (specifically the MacBook Pro)

The "Drop" command, which drops one of the currently held item on the ground, is bound by default to the "Q" key. Ctrl+Q will drop the entire stack. Command+Q on a mac quits the current application. Thus, changing control+Q to command+Q means that pushing the key combination to drop a stack will quit the game. Fortunately, the "Drop" command can be bound to something other than Q in the options.

Grum, I'm surprised you went for the platform-specific hack, rather than allowing users to bind modifier+key/button combinations in the controls page. I suppose this was quicker and easier, but certainly not ideal. I would hope that you guys would revisit that in the future, rather than a hack you may have to maintain as things outside your control shift under your feet (Apple, LWJGL, etc.)

Now that I've played a little bit, binding directly to the alt or control key isn't that bad. BUT there needs to be consistency. It appears that when in working on the workbench or in a furnace, the key binding defaults back to a 3 button mouse... and not what the key binds are set to by the user.

IF there was consistency then I believe users could get used to this. Otherwise, it feels like the bindings only apply to certain parts of the game.

Agree with Bill - I could get used to consistent key bindings. At least in the short-medium term while a modifier key strategy is figured out.

Unfortunately because I was watching this forum (hoping, I guess) rather than play (while there was no real possibility of playing an up to date game) at the moment, the windows users on my server upgraded happily in anticipation of horses, so now I'll get to upgrade a server I can't yet play on.

I am not interested in being told to buy a mouse. I'll be getting a Leap before I get a mouse.

Is this going to be fixed in 1.6.2?

I'm having this problem but it doesn't seem to affect the play world, only inventory right-clicking. That is highly annoying but means I can still play creative ok. It seems to only be happening in 1.6.1, 1.5 was fine regarding this issue.

I'm a mac user and I've been playing since early alpha. This change seems pointless to me. I am dumbfounded as to why you would need to change a perfectly good layout after all these years. PLEASE do change it back. I NEED the control click!!

This need changed back immediately! I've been playing since early alpha and it is way too late now in the game to change something like that

While I agree with the previous post that this issue should be addressed, I think it's great that the game is still in active development.

Oh man, that 1.6.2 Control-clicking feels so good. All is right with the world. 😃

I've just downloaded the 1.6.2 snapshot and it seems to solve the ctrl click issue with one exception...

You can't ctrl+click to set the control back to "button 2", but hey, that's really no big deal. It works in game and in inventory and I'm now happy.

Thanks for addressing this.

Oh, yeah, good point, Christopher. The controls interface still recognizes the Control keypress instead of Grum's fix. Workaround for now: If you don't already have Use Item assigned to "Button 2," your only way to take advantage of the fix for now is to briefly plug in a 2-button mouse just to get the controls menu to use that setting.

Works great now! Cheers @grum - Should point out I've noticed a bug with this. Don't know if it's just me but after playing using Control + Click for a short while, The mouse suddenly goes insane on a left click (Destroy blocks) loop and the only way to clear it is trying to trigger ctrl or two finger clicking the pad. This happened about 4 times in a 15 min test. Could anyone else confirm this?

@Peter: I could swear I recently saw the sticky left-click issue mentioned on MinecraftForum (not just a Mac issue?), but I'm not able to find the post now. I also remember having this happen to me in past versions, but not with the frequency you and others have described.

@Joe Ah right, I never used to have any issues with "Sticky" Control; Been playing since Beta 1.8! And it seems Perfect in 1.5.2 if I install that under a profile in the launcher, Non working in 1.6.1 and Working yet occasionally going mental in 1.6.2 Snapshot; Have tried rebooting the system and the bug remains, Also seems to go on a placing block rampage too; Although right now I'm unable to place my finger on what causes it exactly!

OK After playing for a while on another Mac I can confirm it's if you quickly add / delete blocks using CTRL in succession (If CTRL is triggered too quickly it can get stuck and the mouse click event loops)

I am undergoing the same issue with CTRL sticking in the 1.6.2 pre-release version.

Great to hear you've found out the cause. I guess I have to take it easy with adding/deleting blocks for awhile.

Still an issue even in 1.6.2!

Hmm, is there a mod fight going on as to whether this should be reopened? I'm wondering if the people who report it's still affecting 1.6.2 are reporting this because the Controls menu isn't privy to Grum's hack: while Control-click is interpreted as button 2 in-game, you have to have Controls set up to use button 2. In 1.6.2, if you try to change Use Item to button 2 using Control-click, Use Item gets set to the Control key instead. That's the existing bug I know of.

I for one believe it is fixed.

The perceived problem may in fact lie in the difficulty in setting the key bindings back to button 2/3.
Maybe a 'set to defaults' button could solve this?

I had to edit the options.txt file located at: (specific to a Mac ONLY)
/Users/[username]/Library/Application\ Support/minecraft/options.txt

and set the following items near the bottom of the file:
key_key.attack:-100
key_key.use:-99
key_key.pickItem:-98

Once this was done, and the app restarted then all was as it originally was.

IMHO, The 'sticking issue' should be moved to another ticket.

@Joe Rovang

Might i point you at the second point:
2) Wonky button-states when releasing a 'fake'-rightmouse press.

There is no sane way around it, this has to be implemented a lower level.

@grum but ⌘+a,v,x,c still doesn't work 😞

Could this be made into an option please? It breaks keyboard mappings. For example, I'm a left-handed player who uses right-ctrl for sneaking.

Still not fixed for me... Not sure why this is resolved. 1.6.2 and I try to pull back a bow and it just sits there at full pull until I hit esc or similar.... still have the hanging click issue.

Did you read any of the comments? Like the one just a few above yours from Grum? It's as fixed as Mojang can fix it. A real fix is going to have to come from LWJGL, so go make your voice heard over there.

I paid Mojang for Minecraft .... not LWJGL. I get that they have issues. But ultimately if Mojang is releasing code they are responsible for it. I complain to those that I paid.

PS as a software developer "fixed as I can get it but still broken" and "resolved" are two different states.

In that respect, you are correct. "Resolved" in no way implies "Fixed". Resolved means that a decision has been made. Fixed means that a change has been made. In no respect does any of it imply that everyone (or anyone) is going to be happy with the outcome.

You can satisfy your ego and worldview, or you can do the thing most likely to result in a satisfactory outcome. It's up to you. But you can't choose both the course of action and the outcome. A specific path leads to a specific destination, and no amount of complaining (at least not to the right people) is going to change that.

I still think the current solution should be made into an option like "[ ] Ctrl+click simulates right click" or something like that. At least until a proper solution has been found, either in Minecraft itself or LWJGL.

That way the track pad players have a workaround, even if it is flaky at best, and those who map a function to the Control key can completely disable it so that the keyboard functions as in Windows, Linux and most, if not all, other games under Mac OS.

Although Ctrl+click is still a standard in the OS itself and cannot be disabled, most applications and games override this behavior. Which, in my opinion, is a good thing.

This bug seems to be on the server side (Java version 1.7.0_25). Just ran in to the problem doing the following:
1. Closed minecraft server app
2. Added a user to ops.txt (no other ops in list)
3. Restarted minecraft server app
4. Banned user from minecraft client
5. "Right click" stopped working for some non-ops users (this issue follows the user independent of OSX version - tested 10.6.8 & 10.7.5)
6. Removing user from ops.txt & restarting minecraft server app caused user to lose "right click" on OSX 10.6.8 & 10.7.5
7. Adding user back to ops.txt restores "right click" function
8. Elevating affected users by "/op" restores "right click" function; "/deop" removes "right click"

• Unaffected users may not have been online during "/ban" of user

• Removing banned player (text file edit) does not fix the problem.

Reid, I find that very hard to believe but I'll see if I can reproduce that behavior later today.

Added more comments to MC-20704.

when "/ban" player is used, all currently online players (OSX) lose the ability to modify server blocks near spawn point.

Non-op is unable to change blocks near spawn point if they were online when "/ban" was executed.

• Continue updating on this thread or MC-20704?

Please continue in (reopened) MC-20704

What bugs me about this now that it has been implemented is that it's not optional. I use a standard mouse and this "feature" prevents me from left-clicking while holding control even though control-click is disabled in my OS.

A solution that has been working great for me is KeyRemap4MacBook. It allows you to remap keys and mouse buttons and supports multiple profiles that can be activated by a shortcut. So you can, for example, add a profile for Minecraft that remaps the Control key to F13.

I myself use it to remap the modifier keys on a PC keyboard to match the standard Mac layout.

I'm left handed and use the cursor keys for movement and my thumb on the right control key for crouching. The right control key on a PC keyboard is on the same location as the Option key on a Mac keyboard. Using KeyRemap4MacBook I remapped Control_R to Option_R which fixed the issue for me.

Any chance of a fix to the 'fix' for this? Ctrl-click sticks like crazy.

See MC-23132.

Or better yet, see the LWJGL issue on GitHub. Specifically:
kappaOne:

Implemented this feature back into LWJGL, ctrl + mouse click will now register as right mouse click (restoring the LWJGL 2.8.5 and below behaviour).

grum:

Awesome, we'll make sure to get this tested soon for Minecraft 🙂

So once this is implemented and working in a stable release of LWJGL, grum will almost certainly pull his hack, and everything will work as it did before.

This looks to be an issue again in 1.13, with LWJGL 3.

Can confirm this makes the game unplayable on Mac laptops once again when using the latest snapshots.

There's a new report about this: MC-121905