A useful Enfosi maps list does more than repeat names. It shows how each current map changes statue visibility, incoming routes, disguise inspection, resource access, class positioning, and boss movement. The official experience description does not provide a complete public roster, so this page does not invent or freeze map names from older community tables.
Use the live map selection and loading UI to build the current Dex. Record every entry with a check date and leave unknown fields blank.
Map record fields
Identity
Displayed name, availability, variant, and UTC check date.
Challenge
Current map rating, selected game difficulty, modifiers, and displayed reward relationship.
Objective
Statue position, visible approaches, blind sides, and safe central anchor.
Enemy routes
Arrival lanes, crowd junctions, isolation space, and boss rotation.
Resources
Verified heal and ammo stations, travel risk, interaction, and return path.
Class fit
Useful sight lines, setup points, movement demands, and close-range zones.
This structure supports a lookup without pretending the unverified fields are known.
Verify a map name
Capture the name from the current game UI with enough context to show Enfosi and the selected map. Distinguish a map, difficulty label, mode, and modifier. If community sources use two spellings, prefer the live display and preserve the other only as an alias.
Check whether the map is currently selectable, rotational, locked, or event-specific. One old screenshot does not prove present availability. Repeat on another session if the roster appears temporary.
Map the objective and lanes
At spawn, rotate once from the statue. Mark each approach with a short landmark name. Identify where crowds overlap and one place where a confirmed threat can be separated safely.
Record which lanes remain visible from center. A lane that requires several blind turns needs an explicit owner or mobile coverage. Avoid map notes that rely only on “left” and “right” because player orientation changes.
Verify resources
Walk to each apparent heal or ammo station, confirm interaction, and return to the statue. Record travel time qualitatively, number of blind turns, whether an enemy route crosses it, and any visible cooldown or limit.
Do not infer function from pad color alone. The Heal and Ammo Locations guide provides a full route test.
Record difficulty and reward
Use the current selection display for any map rating or reward multiplier. Include selected game difficulty and modifiers. Do not combine a map’s label with Maniac or event pressure and call the result one permanent score.
Completion reliability belongs beside reward. A demanding map may advertise more but progress slower if the team repeatedly fails.
Note class fit
Gazo needs clean sight lines and ammo access. Cheerer needs predictable crossings. Gleeber can bridge distant approaches but must stop safely. Glaaber prefers compact routes. Gloober needs reachable central positioning, while Gembo needs isolation space for burst.
These are route observations, not fixed class bonuses. A player’s loadout and the current mode can change the fit.
Solo and squad entries
For solo, record how long the statue leaves view during each rotation and whether one player can cover simultaneous approaches. For squads, write a simple lane assignment and where players regroup.
Avoid declaring a map easy because one coordinated team cleared it. Include the composition and conditions.
Common map-list mistakes
- Copying an old roster without confirming current availability.
- Treating a mode or difficulty label as a map name.
- Listing station coordinates without verifying interaction and return path.
- Recording left/right without a shared landmark orientation.
- Calling the largest reward the best map.
- Filling unknown fields with estimates to make the Dex look complete.
Maps-list questions
Why are unverified map names not listed here?
The official public description does not establish the complete current roster. The live UI is required to avoid presenting stale names as fact.
What makes a good map entry?
Current name, availability, mode context, objective sight lines, approaches, resources, class fit, and check date.
Should variants be separate entries?
Yes when the live game presents a distinct layout or rule that changes routes. Record the relationship to the base name.
How often should the list be rechecked?
After major updates and whenever the live selection or route differs from the dated record.
Sources checked
- Official Enfosi Roblox experience
- Current community maps index
- Community Enfosi reference — map details require current verification