PWNed BY 14:00 Maps

PWNed BY 14:00 maps are the spaces where one Killer or Entity pursues the Survivor team. The public Roblox description confirms the 1-versus-8 format but does not publish a map roster. Current community indexes name several locations and also mix live, upcoming, testing, reworked, removed, private-server, and legacy states. Use this page as a currently documented index, then confirm the voting screen or match intro in the main experience.

The names above come from a community map index crawled in 2026, not a first-party roster. A separate community update recap names additional locations around the Anywhere But Here release, while current discussions mention continuing map reworks. Because those sources can describe different builds, this page does not claim that every named location appears in today’s public rotation.

Confirm a map before planning around it

Launch the official main experience at Place ID 109073445674874. If the lobby offers voting, read the exact displayed name and note whether a special item or permission is required to vote. If there is no vote, record the match-intro name. Take the status from the current main game, not from a legacy place or private-server-only selector.

Record the UTC date, server type, and build context. The official experience is a prototype, and a fresh server can carry a newer build than an older running server. If two servers disagree, do not mark either layout as universal until the main experience settles on one version.

Do not promote a testing name to live merely because it appears in a video or public-test discussion. A previously visible Waffle Office testing-universe record returned restricted or unavailable data when checked again on September 26, 2026. That makes current main-game observation essential.

Map status index

Community indexes have separately named Contamination, PC Install Edition, and rockin4ward’s Place as deleted or unavailable, and have listed Facility_0, Nuke The Whales, Sillyweb’s Place, Hospital Nightmare 3, Santa’s Boat Ride, or Last Stop under upcoming or rework states. These labels are useful for avoiding accidental current claims. They are not an official roadmap and can become stale.

Learn any live map in three passes

On the first pass, find a central landmark, outer edge, and two obvious connectors. Do not attempt advanced loops. As Survivor, keep an exit in view and notice which routes narrow your camera. As Entity, learn where multiple branches converge so you can choose pressure instead of following one trail indefinitely.

On the second pass, test vertical changes, one-way drops, doors, corners, and objects that break line of sight. Record whether collision matches the visual model. A decorative gap may be blocked; a low object may be passable. Test without assuming an older map video still matches.

On the third pass, identify one recovery route for each side. A Survivor recovery route reconnects to teammates or changes sightlines without ending in a dead corner. An Entity recovery route lets you abandon a bad chase and reach another likely traffic point quickly.

Use landmark names that another player can recognize: a unique building, sign, color, room function, or major prop. “Turn left after a few seconds” breaks when spawn direction changes. “Leave the central room through the doorway beside the red machine” survives more starts, provided the landmark exists in the same build.

Map voting and selection

One community map page reports that voting can involve a Compass item in the lobby. That behavior is community reported and needs a current main-game test. Before spending or searching for an item, inspect the live lobby and current description. The presence of a voting screen in an old build does not guarantee the same requirement now.

If voting exists, distinguish a vote from guaranteed selection. Record the candidates, your selection, visible vote totals, and the chosen map. Do not assume ties, ownership bonuses, or private-server controls without repeating the result.

If voting does not appear, the server may be on another build, the feature may be disabled, or selection may be automatic. Avoid calling the system removed after one round. Rejoin a fresh server and compare.

Survivor route decisions

Avoid entering a branch simply because it looks long. Check where it reconnects, whether the Entity can cut across, and whether your current movement resource covers the distance. Keep the camera on likely approach lines without running backward into props.

When chased, change direction after the opponent commits, not continuously. Random movement consumes space without creating uncertainty. Use corners to hide your next choice, but do not stay at a predictable object after the Entity has seen the pattern.

When not chased, learn the map. Follow a teammate at a respectful distance, locate the lobby or objective-related cues shown by the current build, and remember where earlier chases ended. Map knowledge is shared progress even when your selected Survivor changes.

Entity route decisions

Start by moving toward information rather than clearing every room. Watch which routes several Survivors favor. A repeated branch is a better control target than a visually interesting dead area.

If the selected Entity uses traps or transport, place them where traffic is likely and where you can act on the result. A trap hidden in an unused corner has little value. If the character uses ambush movement, learn the sightline from the Survivor’s perspective before committing.

When a chase reaches a strong loop, ask whether the target is giving up anything: time, movement resource, a teammate, or access to another route. If not, leave. Returning from another angle can be stronger than forcing the same turn.

Why there are no map child pages yet

A useful map page needs a confirmed current name, spawn or intro context, recognizable landmarks, route connections, major risks, side-specific decisions, and a dated main-build check. The public evidence currently supports a cautious index but not stable, detailed routes for each location. Thin pages would turn uncertain names into false authority.

Once a map has enough reproducible live evidence, it can receive a route page without mixing legacy and current layouts. Until then, keep the status and route completeness visible here.

Map questions

What maps are in PWNed BY 14:00?

Recent community documentation lists IHasAFaceLULZ’s Happy Home, Klassic, Teapots Of Doom, Manufacturing, and GARDEN.MAZE as in-game, but each still needs a current main-rotation check.

Is every wiki map playable?

No. Community indexes also contain deleted, upcoming, reworked, private-server, public-test, and legacy maps. Check the current main selector or intro.

Is there map voting?

A community page reports a lobby voting interaction associated with a Compass. The current requirement and behavior need in-game confirmation.

Sources checked

• Official main Games API, checked September 26, 2026.
• Community map index, checked September 26, 2026; all roster states are community reported.
• Official legacy experience records, checked September 26, 2026.