AneeMate Co-op: agree on a revive call before the run
For a Co-op session that supports teammate revives, agree on a short help call and a clear way to describe your position before the pressure rises. AneeMate's published guide describes a two-player Survival run with revives. Check the mode and prompts in your installed build, then practise communication without assuming a guide guarantees every interaction's current behaviour.
This is a communication plan based on the official gameplay description, checked on 30 October 2026. It is not a hands-on verification of the current game build. We are not announcing a new Co-op release, cross-platform support, a revive timer or a particular button sequence. The aim is to make one shared decision easier to understand.
Separate needing help from being safe to help
A teammate needs two pieces of information: that help is needed and where to find you. They may also need to judge the approach. A repeated “come here” can be difficult to use when both players are looking at different views. Start with a landmark or a visible route rather than a direction that depends on your camera.
For example, “down beside the stone arch” is more useful than “on my left” if the players are facing opposite ways. This is a suggested communication convention, not an AneeMate map location or an official callout. Choose landmarks actually visible in your session and keep the vocabulary small enough to remember.
Agree on three short messages
Before starting, decide how you will communicate “I need help,” “I am approaching” and “I cannot reach you yet.” The exact wording is yours. What matters is that both players understand the difference. An acknowledgement can prevent someone from repeating the same message while the other player is already responding.
Do not require voice if a participant does not want to use it. Agree on a communication method available to both people. This article does not claim a particular text-chat or ping feature exists in the build. If your chosen method is outside the game, make sure both players can use it comfortably without losing track of the action.
Model example: one player falls behind
Imagine two players in a fictional practice situation. One has moved towards a landmark while the other is nearer the starting route. The first needs assistance. They identify the landmark, the second acknowledges, and both avoid filling the conversation with unrelated instructions. This example describes a communication pattern, not a tested AneeMate encounter.
If the second player cannot approach, they say so. That does not guarantee a successful recovery, but it makes the shared plan honest. The first player can stop expecting immediate help. Avoid inventing a safe strategy from a single screenshot or promising that one route will always work when enemies, player state and build behaviour may differ.
Check the interaction your build actually offers
When a revive situation occurs, read the visible prompt. Do not assume that a key from a general control list applies unchanged to every state. Note whether the prompt appears and what it requests. If the expected interaction is absent, report that observation with the mode and build rather than repeatedly pressing unrelated controls.
The controls and action-prompt guide explains this wider principle. The Co-op development explanation supplies context for the mode. Neither a repository commit nor a website label establishes that a specific packaged build has passed a particular revive test.
Review one moment after the run
Pick a single communication moment to discuss. Did the help message identify a location? Was it acknowledged? Did both players understand whether an approach was happening? These are questions about coordination. They can be answered without pretending to know the internal cause of a failed interaction.
If the game appeared to behave incorrectly, keep the observation separate from the communication review. “The prompt never appeared while we were next to each other” is different from “we did not realise the other player needed help.” A report that mixes them may send the next investigator towards the wrong problem.
Keep invitation codes and account details out of public screenshots. Share technical evidence through the game's appropriate support route. A useful report can describe roles and positions without exposing a live session code. Include whether the issue happened once or could be reproduced; do not invent a frequency from memory.
Questions before a Co-op run
Does this guide confirm Co-op is available in my build?
No. It discusses the mode described on the public website. Check your installed build and official current release information. Single-player, Co-op and offline play are separate availability questions.
Should we always attempt a revive immediately?
This article does not prescribe a combat tactic or guarantee a safe approach. Agree on a clear acknowledgement, observe the situation and use the interaction actually offered by the game.
How do we compare runs afterwards?
Compare the same mode and relevant conditions, and keep coordination notes separate from scores. The records-context guide explains why a board or period matters. One memorable recovery attempt does not establish a general success rate.
For the current mode description and official destination, start with AneeMate gameplay. A short communication plan is preparation, not a substitute for checking the build or learning what its on-screen prompts actually do.