AneeMate controls: trust the action prompt, then check your binding
When an AneeMate shortcut does something unexpected, identify the action and the current context before changing keys. The official guide lists keyboard defaults and describes configurable controls, but a default list is not the same thing as your saved configuration. Start with the prompt shown in the game, then compare it with your settings.
This explanation is based on the official gameplay guide, checked on 28 October 2026, and a review of the current development input configuration. We have not tested every controller, touch layout or remapping screen in a packaged build. Device support should be checked against the version you are using.
Name the action before naming the key
“I want to interact with this object” is a clearer starting point than “E should work here.” A key is a binding; interaction is an intention. That distinction matters when a player changes a shortcut or moves between a keyboard and controller.
The public guide lists movement, running, jumping, interacting, throwing a Yipee, switching Yipee types, becoming an AneeMate and opening several menus. It also describes different combat actions while controlling a creature. Read the label with the situation around it.
For example, a key used for an action while controlling the kid should not automatically be treated as the same action while wearing an AneeMate. The creature switching guide covers why the controlled character changes the question.
Use the default list as a reference
The published keyboard list describes WASD movement, Shift for running and Space for jumping. It also lists E for interaction, F for a Yipee throw, X for changing Yipee type and K for becoming the next creature.
Those defaults help a new player orient themselves. They do not overrule a custom mapping, a changed release or a prompt for a different interaction. If your screen shows another binding, investigate that configuration instead of repeatedly pressing the default.
Menu shortcuts deserve the same care. The guide identifies separate actions for the Matebook, map, quests and building. Opening one menu is not evidence that another action is unavailable. Make sure you are testing the action you actually intended.
A simple troubleshooting sequence
First, stop in a safe location and write down the action label you are trying to use. Note whether you are controlling the kid or a creature, whether a menu is open and which device is active.
Next, open the relevant settings and compare the binding with the prompt. Change one thing at a time. If two actions appear to compete for an input, capture that observation rather than guessing which should win.
Then try the action in a context where it should apply. Interaction may require a suitable object; a combat action has different conditions from opening the map. A test that omits the required context cannot tell you much about the shortcut itself.
Finally, if you changed a binding, check the visible prompt again. If it still shows the old input, that is a useful detail for feedback. Do not assume that repeatedly restarting or deleting local files is a necessary remedy.
A model report that helps development
Here is an invented report structure: “In this build, while controlling the kid near the camp barrel, the interaction prompt shows my newly assigned key. Pressing it does nothing, while the previous key still interacts. The settings screen continues to show the new key.”
That report separates the intended action, displayed mapping and observed behavior. A developer can investigate those relationships. It does not claim to know whether the fault is in input handling, saved preferences or the prompt.
Add the game version and device model when relevant. Avoid including account secrets, private messages or unrelated personal information in screenshots. The testing feedback guide explains how a reproducible observation is more useful than a general verdict.
A configuration file is not a player manual
Development projects can contain legacy mappings, engine defaults and newer input systems at the same time. Reading a familiar key name in a configuration file does not prove that it is the active gameplay binding in a shipped build.
The reviewed development configuration enables Enhanced Input user settings. That is an implementation clue, not proof that every remapping path is complete on every supported device. This article therefore uses the public guide for player-facing defaults and keeps untested behavior qualified.
Do not edit project or save files to imitate a development setting. Use the game's own supported controls where available, and report a mismatch when the interface does not behave as described.
Common questions
Why does a shortcut from a video differ from mine?
The video may show another build, device or custom configuration. Compare the action and current prompt before treating it as a fault.
Does a controller icon prove every menu supports my controller?
No. A prompt is evidence about that moment. Full device support requires testing navigation, gameplay and recovery paths together.
Should I reset everything immediately?
Start by recording the current mapping and changing one relevant option. A broad reset can remove useful evidence and personal preferences.
Keep the controls understandable
Use the official guide for orientation, the current prompt for the immediate action and a precise report for anything that disagrees. Visit AneeMate for current access and release information.