The ASPIS What About That Way achievement requires ten attempts to leave through the edges of the game world, so knowing what counts as an escape attempt is essential. This guide explains the objective, common timing mistakes, related achievements, and a practical approach for tracking each attempt.
Understanding the ASPIS What About That Way Objective
The official achievement list describes What About That Way as a task involving ten attempts to exit the game world through its edges. That wording gives players a clear target, but it leaves one important question unanswered: what exactly counts as an attempt, and how should the attempts be separated?
Because the achievement depends on repeated boundary interactions, the safest approach is to treat every deliberate movement toward an edge as one attempt, including a failed attempt. Do not wait for a successful escape before trying again. The goal is to reach the boundary and trigger the game’s escape behavior repeatedly, not to complete ten successful exits.
The achievement belongs to a larger Steam set of 12 achievements. Other entries include That Was Easy, Management Approves, I Will Stay Here, and As Ordered, which makes the escape task one part of a broader set rather than an isolated challenge. The official ASPIS achievement list on Steam is the best reference for confirming the exact wording of each entry.
| Achievement | Official objective summary | Main player action |
|---|---|---|
| What About That Way | Make ten attempts to leave through the edges of the game world | Repeatedly reach an edge and attempt to exit |
| That Was Easy | Open the KGB building combination lock in under 90 seconds | Solve the lock before the time limit expires |
| Management Approves | Re-enter the system | Complete the stated system interaction |
| I Will Stay Here | Listen to Maria right after the first meeting | Reach the dialogue and listen to her |
| As Ordered | Unpack an empty container | Use the packing machine correctly |
How to Count and Track Ten Escape Attempts
The most common mistake is assuming that only a complete escape counts. The achievement wording does not say that ten successful exits are necessary. Instead, it asks for ten attempts to leave through the edges, which supports a more flexible approach: attempt the boundary, return to the playable area, and repeat.
Keep a simple tally while playing. Mark one attempt whenever you deliberately go to an edge and try to leave. If the character stops, turns back, or the game interrupts the attempt, the safe method is to count it once and then clearly reset before trying again. The main objective is to ensure that the game recognizes the action rather than creating accidental attempts through random movement.
| Attempt | What to do | What to record |
|---|---|---|
| 1 | Select the nearest accessible edge and move directly toward it | Mark one boundary attempt |
| 2 | After the game returns you, approach the same or another edge | Mark the second attempt |
| 3 | Repeat the boundary interaction without changing unrelated objectives | Mark the third attempt |
| 4 | Return, reposition, and try again | Mark the fourth attempt |
| 5–9 | Continue the same cycle, checking that each interaction completes | Update the tally after every attempt |
| 10 | Make the tenth deliberate boundary attempt | Check Steam for the unlock notification |
A written tally is more dependable than memory because ASPIS includes exploration, dialogue, and system interactions that can interrupt the sequence. The broader ASPIS achievement guide can help with the surrounding set, but this particular objective is best tracked separately.
Keeping Attempts Separate
Repeatedly holding an interaction key or running into a corner may not create distinct attempts if the game treats the action as one continuous interaction. Wait for the character to regain control, move away from the edge, and then approach it again. This gives the game a clear opportunity to register another attempt without adding extra steps that are not supported by the official description.
The achievement does not require different locations, different endings, or ten separate playthroughs. Nothing in the official text states that the attempts must occur at the same edge, and it does not specify a time limit or completion percentage. The practical objective is simpler: deliberately test the world boundary ten times and let the game track the repeated action.
What to Do If the Counter Does Not Move
First, check whether the current action was actually an exit attempt or merely ordinary exploration. A character brushing against scenery is different from moving through a world edge and activating the escape prompt. Second, make sure the previous interaction has ended before trying again. Third, vary the route slightly and select another edge if the first one produces no visible response.
If the achievement still does not appear, review the achievement list for the Management Approves entry, which the official source says involves re-entering the system. Some players may be confusing system re-entry with edge escapes. The aspis persistent escape objective is best kept separate from re-entry goals until the boundary action is confirmed.
Where to Attempt the Edge Escapes
The official achievement text refers to the edges of the game world but does not identify a single named location. That means the guide should not invent a specific map area or claim that one edge is guaranteed to be correct. The reliable method is to find an accessible boundary and interact with it deliberately.
In ASPIS, movement through a strange environment can be interrupted by story events, combat, dialogue, and the behavior of the surrounding space. Before beginning the ten-attempt sequence, clear nearby distractions when possible. That does not mean you must complete the story or defeat a particular enemy. It simply means you should avoid confusing a forced event with a failed escape attempt.
| Situation | Likely interpretation | Best response |
|---|---|---|
| The character reaches a visible world boundary and tries to leave | Clear boundary attempt | Count it, then repeat |
| The character is blocked by an ordinary object | Environmental navigation | Reposition and find the actual edge |
| A cutscene interrupts the movement | Story event | Wait for control, then make a separate attempt |
| A door or transition activates | Room transition | Do not count it unless the game confirms an edge escape |
| The character returns without a visible prompt | Unclear registration | Reposition and make a fresh attempt |
| The tenth attempt ends with no notification | Possible delay or missed state | Check Steam achievements and retry the action |
Community reports may describe particular routes or visual landmarks, but those details are not part of the official achievement description. Treat them as suggestions rather than fixed requirements. The absence of a published missable flag also means there is no official basis for warning that the achievement can be lost.
Preparing the Run for Reliable Tracking
Before the first attempt, open the Steam overlay or another unobtrusive note and write down the current count. This sounds simple, but interruptions from story events make memory less reliable than a visible tally. After each attempt, update the number only after the character has regained control or the game has clearly returned him to the playable area.
The game’s official store page identifies the setting as the USSR in 1987 and explains that Andrey navigates a world connected to a larger experiment. The aspis I Will Stay Here achievement, meanwhile, requires listening to Maria immediately after the first meeting. Dialogue can be part of natural progression, so completing that moment first may provide a convenient checkpoint before concentrating on the escape objective.
| Preparation step | Practical benefit |
|---|---|
| Complete nearby dialogue when it is already available | Prevents an interruption during counting |
| Keep the Steam achievement window accessible | Confirms the unlock without restarting the game |
| Write down the current count | Prevents overcounting or losing track |
| Approach edges directly | Reduces accidental movement and unclear interactions |
| Wait for full control after every event | Prevents several actions from merging into one attempt |
Troubleshooting a Missed ASPIS Unlock
A missed unlock can feel deceptive because the game does not publish a visible counter for this objective. The player may perform many boundary movements while the achievement remains unmarked. The solution is to slow down and separate each test into a clear sequence: approach, attempt, wait, return, and record.
Begin by testing one edge. Move all the way toward the world boundary, attempt to leave, and wait for the game to respond. If no notification appears, verify the current achievement list in Steam. Then return and repeat the same action. If repeated attempts still do not register, use another edge and observe whether the game responds differently.
| Check | What it tells you | Action |
|---|---|---|
| Current Steam achievement list | Whether the achievement has already unlocked | Refresh the overlay and look for the title |
| Recent game events | Whether an interruption consumed the attempt | Resume only after the event ends |
| Edge accessibility | Whether you reached the true world boundary | Find a more clearly defined perimeter |
| Attempt spacing | Whether several movements occurred as one action | Pause, reposition, and retry |
| Same-session progress | Whether the achievement state is delayed | Continue one more complete set of attempts |
Do not repeatedly reload the game after every failure, since doing so can erase useful knowledge about what caused the mismatch. If you want a broader diagnostic, the ASPIS secret achievements guide can help distinguish an ordinary failed objective from a notification or tracking issue. Official material does not publish a specific bug or fix, so the best approach remains controlled testing rather than assuming a patch solution.
Avoiding Double-Counting
The achievement requires attempts, but registering the same movement more than once does not add value. If you attempt one edge and immediately slide along the perimeter, the game may view the entire movement as one interaction. Step back into the playable area, change position, and initiate a fresh approach.
Using different edges can also help confirm that the action is recognized. There is no requirement to alternate locations, but testing a second boundary is a practical way to rule out an unusual obstruction. If both produce the same result, restart the session and make ten spaced attempts rather than continuing a rapid sequence that may not register.
Related ASPIS Achievements and Their Distinct Goals
Aspis That Was Easy is a separate timed challenge involving the KGB building’s combination lock. Its target is to open the lock in under 90 seconds, which means players should not treat it as a substitute for the ten escape attempts. The two achievements can be pursued independently, although grouping them in a checklist may make achievement hunting easier.
Aspis Management Approves refers to re-entering the system. This is also distinct from attempting to leave through the world’s edges. If you are unsure whether an action has actually registered, check the official names and descriptions rather than assuming every system interaction counts toward What About That Way.
The aspis Maria achievement appears under the official title I Will Stay Here, whose objective is to listen to Maria right after the first meeting. Finally, Aspis As Ordered relates to unpacking an empty container at the packing machine. These objectives involve different interactions, so tracking them separately reduces confusion during a completion run.
| Related objective | Official title | Core action | Confusion risk |
|---|---|---|---|
| Timed KGB lock | That Was Easy | Open the combination lock in under 90 seconds | Mistaking the timer challenge for edge escapes |
| System re-entry | Management Approves | Re-enter the system | Treating re-entry as leaving the world |
| Maria dialogue | I Will Stay Here | Listen to Maria after the first meeting | Missing a short contextual prompt |
| Empty container | As Ordered | Unpack an empty container | Confusing the container with an escape point |
For a broader checklist, see how to get all ASPIS achievements. Keep the main focus on the official wording: the edge objective is a count of ten deliberate attempts, while the related achievements test entirely different actions.
A Reliable Ten-Attempt Routine
Use a repeatable routine that separates travel, interaction, and tracking. First, choose an accessible edge. Walk directly toward it without opening unrelated menus or starting unrelated objectives. Second, trigger the boundary interaction and wait for the game to respond. Third, return to a point where the character clearly has control again. Fourth, update the written tally, then repeat.
The routine does not require perfect route knowledge, and there is no official evidence that a particular edge is more valuable. Its value comes from consistency. If the first edge produces an unclear result, move to another perimeter location rather than repeatedly pressing the same action while the character remains against the boundary.
A compact tracking method looks like this:
| Round | Approach | Interaction | Verification |
|---|---|---|---|
| 1–2 | Use one accessible edge | Attempt to leave twice, with control restored between them | Update the tally twice |
| 3–4 | Try another edge if needed | Repeat the same deliberate process | Confirm the count |
| 5–7 | Continue with whichever edge works | Keep actions separated and paced | Check for the unlock after the seventh |
| 8–10 | Finish three clean attempts | Avoid interruptions and accidental movement | Verify the achievement in Steam |
The achievement text does not mention a specific edge, time limit, or requirement to escape successfully. It also does not state that the objective can be missed. As a result, there is no reason to prioritize risky routes over a clear, accessible boundary. The fastest safe method is repeated interaction with a known perimeter and careful counting.
Frequently Asked Questions
Does ASPIS What About That Way require ten successful escapes?
No. The official wording asks for ten attempts to leave through the edges of the game world. Count each deliberate boundary attempt, including one that fails, provided the game recognizes the action. Wait for control to return before beginning the next attempt so that separate movements are not accidentally treated as one interaction.
Can the ten attempts be made at different world edges?
The official achievement description does not require all attempts to occur at the same location. Use any accessible edge that allows you to attempt leaving the game world, although changing edges can help you test whether a particular boundary is obstructing the action. Keep a simple tally so every registered attempt is counted once.
Why is the achievement not unlocking after several attempts?
Common causes include remaining against the same boundary, counting ordinary exploration as an escape attempt, or having a story event interrupt the action. Move away from the edge, regain control, and make a fresh approach. The official source does not publish a known tracking bug, so test the action in a clear sequence and verify the achievement list afterward.
Are Management Approves and What About That Way connected?
They are separate achievements. Management Approves concerns re-entering the system, while What About That Way counts attempts to leave through the world’s edges. Re-entering may be useful for testing objective states, but it should not be counted as an escape attempt unless the game identifies the action as one.
Should I restart the game if the tenth attempt seems missed?
Restarting is reasonable when a notification has not appeared, but it is not required by the official objective. First, confirm that Steam has not updated the achievement list and make one more clean, separated attempt. If the state still does not change, reloading and repeating the controlled routine is a practical troubleshooting step because no specific patch fix is documented.