{"id":574,"date":"2026-05-13T03:21:59","date_gmt":"2026-05-13T03:21:59","guid":{"rendered":"https:\/\/sites.wsagames.com\/jz15n24\/?p=574"},"modified":"2026-05-13T03:21:59","modified_gmt":"2026-05-13T03:21:59","slug":"level-design-research-how-to-prevent-backtracking-from-becoming-repetitive-traversal","status":"publish","type":"post","link":"https:\/\/sites.wsagames.com\/jz15n24\/2026\/05\/13\/level-design-research-how-to-prevent-backtracking-from-becoming-repetitive-traversal\/","title":{"rendered":"Level Design Research: How to Prevent Backtracking from Becoming Repetitive Traversal"},"content":{"rendered":"\n

In level design, backtracking<\/strong> refers to the player returning to an area they have already passed through. It is not inherently bad design, but if the player does not have a new objective, new risk, or new understanding when returning to an old area, the route can easily become simple repeated traversal. The player may feel that they are only wasting time, rather than re-exploring the space. Woodbury (2010) argues that the issue with backtracking is that it may be understood by players as part of experiencing the world, or it may simply be perceived as a restriction that extends the playtime. This supports my judgement that backtracking itself is not the problem. The problem is whether the player gains a new objective, new information, or new spatial understanding when returning to an old area.<\/p>\n\n\n\n

Therefore, I think effective backtracking needs to let the player return to an old area \u201cwith change\u201d. The key point is not whether the map itself has changed, but whether the player\u2019s way of understanding and using the space has changed when they return.<\/p>\n\n\n\n

If the player simply moves from point A to point B, and is then asked to return to point A along the same route, with no new events, enemies, resources, or route changes along the way, then this backtracking is likely to be only repeated movement. By contrast, if the player has gained a new item when returning to point A, discovers that a previously inaccessible route can now be entered, or finds that new enemies, sounds, or state changes have appeared in the old area, then the player\u2019s understanding of that area will be updated. At this point, returning to the old area is no longer just repetition, but a re-reading of the same space.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

In our project, this issue is also related to production scope. I previously discussed with our Technical Designer, Kevin, whether the player should be allowed to return to the previous map area. This design may have gameplay value, because the player could return to an old area to look for missed items, re-plan their route, or reuse the space according to a new task objective. However, from a technical perspective, this would also increase complexity, especially in terms of map state management.<\/p>\n\n\n\n

If the player can return to an old map, the game needs to record many states: which items have already been picked up, which enemies have appeared or disappeared, whether NPC states have changed, whether the player has already triggered certain events, and whether certain routes are still open. If these states are not saved correctly, the player may encounter problems such as items respawning repeatedly, enemy states being incorrect, or task conditions becoming confused when they return.<\/p>\n\n\n\n

Therefore, for this project, backtracking cannot exist only to extend playtime. If we allow the player to return to old areas, we need to make sure that the return action has a clear purpose, such as returning to an old location to verify clues after gaining new information, using a new item to open a previously inaccessible route, or deciding under timer pressure whether it is worth going back. Otherwise, within a limited project scope, backtracking may create extra technical burden without clearly improving the player experience.<\/p>\n\n\n\n

In my initial level design concept, I once considered using Sierra\u2019s bracelet to create a meaningful moment of backtracking. According to the narrative setting, the player reaches the game\u2019s starting point while escaping in panic. This means that the route before the starting point is not a completely unfamiliar space, but an area the protagonist has passed through while fleeing. At the same time, the GDD also mentions that Sierra has lost a bracelet that is very important to her. Since this item is important both to the narrative and to character relationships, it should not be obtained by the player as easily as an ordinary pickup item.<\/p>\n\n\n\n

Therefore, my initial idea was that the player would unexpectedly discover Sierra\u2019s lost bracelet during later map exploration, but would not be able to obtain it immediately. The player would first need to become aware of the bracelet\u2019s location, then return to a previously visited map to find a tool or route that allows them to reach it. In this way, the bracelet would not only be an item that increases reputation, but also an objective that makes the player reinterpret the old map.<\/p>\n\n\n\n

The focus of this design is not to simply make the player walk back the way they came, but to let the player return to an old area with a new purpose. When the player first passes through the area near the starting point, they may only be escaping and adapting to the environment, and may not notice every detail. However, once the player knows that the bracelet exists, the old area gains a new meaning. When the player returns, they are no longer repeating movement, but looking for paths, tools, or spatial clues that they previously ignored.<\/p>\n\n\n\n

From the perspective of mechanics and level design, this design can serve several goals at the same time. First, as an important item belonging to Sierra, the bracelet can provide a higher reputation reward, making the player feel that this backtracking is worthwhile. Second, the player needs to obtain it through observation and route planning, rather than directly picking it up, which gives the item stronger design weight. Finally, this design can connect narrative information, character relationships, and map structure, making backtracking a behaviour driven by both narrative and gameplay.<\/p>\n\n\n\n

However, this design would also create technical issues. If the player needs to return to a previous map, the game must record the state of the old map, such as whether the player has previously passed through certain areas, whether the item has already spawned, whether enemies or events have been triggered, whether the tool leading to the bracelet has already been taken, and whether the map should preserve its previous state when the player returns. Therefore, although this idea is meaningful in terms of level design, it would also increase the complexity of technical design, especially in terms of map state saving and cross-map return logic.<\/p>\n\n\n\n

Therefore, my understanding of backtracking is that it should not exist only to extend the route or reuse the map. Only when the player returns to an old area with new information, a new objective, or a new tool can backtracking truly create value. The design idea of Sierra\u2019s bracelet made me realise that an effective backtracking route needs to satisfy narrative motivation, reward value, map reinterpretation, and technical feasibility at the same time.<\/p>\n\n\n\n

Resource<\/strong>\uff1a<\/p>\n\n\n\n

Woodbury, D. (2010) \u2018Backtracking and Non-Essential Areas\u2019, Game Developer<\/em>, 22 December. Available at: https:\/\/www.gamedeveloper.com\/design\/backtracking-and-non-essential-areas<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

In level design, backtracking refers to the player returning to an area they have already passed through. It is not inherently bad design, but if the player does not have a new objective, new risk, or new understanding when returning to an old area, the route can easily become simple repeated traversal. The player may […]<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[],"class_list":["post-574","post","type-post","status-publish","format-standard","hentry","category-s2-research"],"_links":{"self":[{"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/posts\/574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/comments?post=574"}],"version-history":[{"count":1,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/posts\/574\/revisions"}],"predecessor-version":[{"id":578,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/posts\/574\/revisions\/578"}],"wp:attachment":[{"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/media?parent=574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/categories?post=574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.wsagames.com\/jz15n24\/wp-json\/wp\/v2\/tags?post=574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}