🛠️ Opening the Sims 4 cheat console on Mac
There always seems to be some confusion over how to open the cheat console on a Mac because Mac users normally substitute the CMD key for the CTRL key in everyday Mac usage (CMD + C, CMD + V for copy...
Forum Discussion
Hii!
I have a problem with the cheat bar in my sims 4 on my mac. I never had a problem opening the cheat bar in sims 3 on the same mac, but for some reason it just won't work for sims 4.. I've tried starting over both my computer and the game, and i've tried looking up other help topics here, but it just doesn't seem like i can find a proper one that will make it work?
Can any of you help with it? Is there anything i can do or ?
(I have the Catalina software update, so I can't check if it still works on my sims 3)
Hope some of you can help! Thank you!
@Stylikpaylinoran
Please try this solution offered by @Bluebellflora in an older thread:Go into System Preferences > Keyboard > Modifier Keys and set another key as your CTRL key.
This issue has nothing to do with a bug or glitch in the game. It is down to one or more of the following:
- Broken CTRL key(s). Connect another keyboard to see if this is the case.
- 3rd party software that has changed the keyboard mapping, e.g. - screenshot software or video capture software.
- 3rd party software that is conflicting with the game. Close down any other apps that are running.
- User changes to the modifer keys in System Preferences. Has someone used your Mac under your user account and changed something without you knowing?
- The Input Source in System Preferences > Keyboard has been changed to a different language. You could also try adding another language to see if this resolves the issue.
Just to confirm, to bring up the cheat console you type in CTRL, SHIFT and C. It has never been the CMD key. Yes, we normally substitute the CMD key for the CTRL key but not for Sims.
I followed the advice to "change my modifier keys" but they weren't ever messed with by another user. However, when I changed my control key to my command and my command to my control, it worked. Would that mean my control key is conflicting with something? The normal control key still works when I need to take a screenshot.
For anyone in the future searching through multiple tabs for the answer, heres the best I can give for Mac users whose cheat bars wont open and/or the commands for it take a screenshot:
Steps
1) Make sure that any other programs you may be using are closed. This can be done using F4. If you're having issues with the program quitting, force quit it in the activity monitor in your launchpad.
2) If this doesn't work, click the apple logo in the top left of your display and open 'System Preferences"... "Keyboard"... "Shortcuts" ... "Screenshots". Under Screenshots turn everything off.
3) If this still doesn't work then you have a key on your keyboard that is not working properly. This means you have to change what command your keys are programmed to. Under "Keyboard" in System Preferences, at the bottom right corner click "Modifier Keys". Make sure the keyboard it is set to is the one you are using. Then change the control key option to "no action" and change the Function Key (fn) to control.
If this does not work, you probably still have a program running you're unaware of or your Sims is being possessed. Good Luck!
Hi there - I've tried all of the steps below - still nothing. ☹️
- Try plugging in or bluetoothing another keyboard to your Mac. You may have a broken CTRL key(s).
- Check for 3rd party software that has changed the keyboard mapping, e.g. - screenshot software or video capture software.
- 3rd party software that is conflicting with the game. Close down any other apps that are running.
- User changes to the modifer keys in System Preferences. Has someone used your Mac under your user account and changed something without you knowing? Go into System Preferences > Keyboard > Modifier Keys and set another key as the CTRL key
- The Input Source in System Preferences > Keyboard has been changed to a different language. You could also try adding another language to see if this resolves the issue.
