AneeMate co-op: checking the Incinerator beam as a joining player

AneeMate’s 0.1.5-ce update makes the Incinerator’s beam visible to joining players in co-op. To check the correction, compare what the host and joining player can see during the same attack, while recording each player’s position and view direction.
The 6 November release report also describes a separate damage adjustment. Visibility and damage are different observations. Seeing the beam does not, by itself, measure the damage it deals.
Why the joining player’s view matters
A host can see an attack correctly while another player lacks the information needed to respond. From the joining player’s perspective, the problem is practical: a threat is harder to read when the expected visual cue is missing.
The released note identifies the joining player specifically. That makes the guest view the necessary place to check this correction. A host-only recording cannot establish whether that player receives the visual information.
This article uses the published release as evidence of availability. It does not claim that a fresh multiplayer session was run for this guide or describe an unverified replication implementation.
Prepare a comparison with enough context
Record the installed build, who hosts and who joins. Choose positions where each player has a clear view of the relevant area, with no obvious obstacle hiding the attack.
Capture both views if possible. A short recording from each player makes it easier to compare the same moment than two screenshots taken during different attacks.
Use a shared spoken cue or another visible reference to identify the moment in both recordings. You do not need precise synchronized equipment to make useful feedback, but you do need to know that the clips show the same event.
Observe the beam before judging the outcome
Begin by asking whether the joining player can see the beam when the host can see it. Then note the direction, approximate location and whether it remains visible through the relevant part of the attack.
Do not treat every difference between the two images as a fault. The players may have different cameras, graphics settings or sight lines. Those differences belong in the report because they affect what the screenshots show.
If one player is facing away or looking through an obstacle, repeat from a clearer viewpoint before concluding that the beam is absent. This avoids turning ordinary visibility limits into an incorrect report.
A model host-and-guest check
Imagine a hypothetical co-op session where the host and guest stand at separate safe viewpoints. Both record the same attack. The host’s clip shows a beam across the clearing; the guest’s clip shows the same clearing at that moment without the beam.
The useful report includes the two positions and both recordings. It states that the cue is absent in that guest view, without claiming why the rendering or networking behaved that way.
If a second attempt shows the beam correctly, preserve both results. An intermittent result is still useful when the sequence and conditions are clear. It should not be rewritten as either a universal failure or a universal pass.
Keep the damage adjustment separate
The release report says the Incinerator’s hit on the player is about 60 percent softer. That is the wording of the documented balance change, not a promise that every encounter is easy or that standing in the attack is safe.
A visibility review does not require deliberately taking damage. If damage feedback is also being investigated, document the relevant state and observations as a separate case.
The same notes say AneeMate projectiles no longer interrupt its attack. Do not use an older interruption expectation to decide whether the new attack sequence is broken.
Related co-op checks
A shared session contains several independent systems. Our day-and-night synchronization guide compares the phase seen by host and guest. The joining-player consumables guide focuses on item use and visible results.
Those checks can use a similar recording method, but they answer different questions. A correct sky or working consumable is not evidence that the beam renders correctly.
The development lesson is to define the player-facing acceptance case for each correction. Here that case must include the joining player seeing the relevant attack cue, rather than merely entering the session successfully.
Common questions
Must the two players stand together?
Their recordings need clear comparable views of the same event. Identical positions are not required, and differences in position should be documented rather than hidden.
Does seeing the beam prove co-op has no other issues?
It establishes that observation in that case. Session stability, damage, day phase and consumables require their own evidence. One successful cue cannot stand in for a complete multiplayer test.
What should I submit if it is still missing?
Provide the build, host/guest role, positions, viewing directions and a short clip covering the attack. Follow the tester feedback guide for a concise reproduction.
Visit AneeMate gameplay for the broader adventure. Clear feedback about a single cue helps make the shared experience easier to read.
Sources
- AneeMate weekly development report, 6 November 2026, co-op beam visibility and separate Incinerator balance notes.