Free Fire India Map Changes and the OB54 Correction

This page deals with one specific problem: map details in old announcements may already have been changed. OB54 (2026-06-23) explicitly states that Bermuda 2.0 and Alpine were removed from the game, which directly overturns the reading that “it is still on the official site, so it is still valid”. Below is the order of judgement for this kind of conflict, and how to label versions and effective dates when editing.

What map content did OB54 actually change?

The patch explicitly states that Bermuda 2.0 and Alpine were removed from the game. Three knock-on conclusions follow:

The old official map page and the map lists in historical customer service articles cannot be treated directly as the current map pool.
The name correspondence between Bermuda Remastered and Bermuda 2.0 needs checking against the client — different names do not mean two maps, and do not mean the same map either.
The patch also changed interactions and movement on the map, so historical landmark usage descriptions must carry dates.

Evidence level: Global reference — OB54 is the global announcement of 2026-06-23; it does not prove that the India client took effect the same day or received identical content.

Why does “the site still loads” not mean “the content is still valid”?

This reasoning error does not appear only on maps. The character skill page has a clear counter-example: early Chrono’s force field let you shoot outward, and the official source later removed that ability, yet old pages may still say you can shoot out. The same logic applies to maps: a map page is a directory, not a version status table.

The order of judgement is best fixed at three steps: historical list, latest patch, local client. The first two can only show “it once existed” or “it was once changed”; only the third can show “this is how it is now”. For the collected landmark material and official descriptions, see Map overview and landmarks.

Which map facts must be tagged “Historical version”?

These are all the type that was true at the time of the announcement and now needs rechecking:

Fact	Announcement timing	What to watch now
Bullseye is a new Bermuda area; Hot Zone spawns high-tier supplies	2019	The area may have been reworked or renamed
Peak changed building layout, raised loot density and quality, adjusted terrain height	2023 rework announcement	Terrain height and fighting space may be adjusted again
Clock Tower, Katulistiwa, Factory, Peak have frost rails laid	Winterlands announcement	Frost rails are event-period facilities
Mill and Clock Tower added revival points, Kota Tua revival point removed	2025 announcement	Revival points are the easiest thing for later patches to move
Rim Nam Village and Mill added player launchers	2025 announcement	Launcher positions need confirming against the client
Vending machines near Hangar moved inside the area	2025 announcement	Vending machine positions may change again
Factory turned into a football pitch	Fire Kickoff event, 2026-06-05 to 06-23	The event has ended; whether it returned to normal needs checking
PLASMA limited to Bermuda	At the time of one patch note	“Limited at the time of that announcement” does not mean still limited now

The purpose of this table is not to give conclusions but to give a list of facts that must carry a date when cited. For the equivalent problem on the weapon side, such as a gun’s mechanic being changed by a later patch, see Weapon categories and official descriptions.

Why can’t the ranked map list be written as a fixed list?

A 2023 patch put Purgatory back into ranked and temporarily moved Kalahari out; later patches added Platinum V and Diamond V to refine the season reset. This shows that neither map rotation nor tier structure is a permanent setting. Therefore:

Writing a “ranked map pool” must be tied to a season or patch number.
Writing a “season reset table” must be tied to a season.
Do not use “usually” or “generally” in place of a version number.

For the mapping between patch numbers and announcement dates, see Versions and events archive.

How should versions and effective dates be labelled when editing?

It is best for every map fact to carry four pieces of information: patch number, announcement date, effective date, evidence level. If the announcement gives no effective date, write “not stated in the announcement”; do not add one yourself.

A compliant map fact looks like this:

Bermuda’s Mill and Clock Tower added revival points, and the revival point at Kota Tua was removed. Version: 2025 announcement (patch given in the sources); effective date: not stated in the announcement; evidence level: Global reference; verification date: 2026-10-28.

The bad version is “Bermuda’s revival point is at Mill” — no version, no date, no evidence level, so readers cannot tell whether it has expired.

The minimum record format for one map fact

Field	Writing requirement
Patch number	Write a number such as OB52 / OB53 / OB54 / OB55, not “the most recent update”
Announcement date	Use the date in the announcement text; if no time zone is given, do not add a specific hour
Effective date	If the announcement does not state it, write “not stated in the announcement” explicitly
Before and after	Write “what it was” and “what it became” separately; do not write only the result
Affected modes	BR / ranked / CS / special mode, labelled separately
Evidence level	One of four: India official / Global reference / Historical version / Unverified
Verification date	Record the date you checked the client this time
Source link	Point to the specific announcement page, not the home page

Event makeovers and permanent changes must stay separate

Events temporarily change the map. Fire Kickoff (2026-06-05 to 06-23) turned Factory on Bermuda into a football pitch; Lost Treasure (2026-02-20 to 03-06) made a Bermuda desert makeover and Sunken Chamber. Both are ended event content and cannot be written as permanent map facilities. For the line between event mechanics and permanent rules, see Special modes.

Evidence level: Historical version — The event dates are as written in the announcements; whether the map returned to normal after the event and whether facilities were kept need checking on the client.

How does this page divide work with the map overview?

Map overview and landmarks covers “which maps exist and what the official source says about each landmark”; this page covers “when those statements expire and how to date them when citing”. Both pages follow the same rule: landmark names come from the official directory, mechanic descriptions come from announcements, and status comes from the client. Miss any of the three and you write a conclusion that looks sourced but has already expired.

For the full conflict-handling process, see Conflicts and gaps; for the definition of evidence levels and the verification steps, see Research methodology.

Sources and limitations

Official sources:

Unverified items:

Whether the India client applied OB54’s map removals, and when, is unverified.
The name correspondence between Bermuda Remastered and Bermuda 2.0 needs checking against the client.
The current position, facilities and loot state of each historical landmark on the India client.
Whether the maps fully returned to normal after Fire Kickoff and Lost Treasure ended is unverified.
The current composition of the ranked map pool: no first-hand list for the corresponding season has been obtained.