Free Fire · Known issues & fixes

Free Fire Known Issues and Fixes: OB55 and Earlier Patch Records

Garena’s documented fixes for Santino getting players stuck, Nero’s plushie, missing weapon mastery and Alok’s range, with each correction tied to its patch.

Mobile
Official fix available

OB55: Nero’s plushie gets stuck in the ground

Platforms: MobileUpdated Evidence checked

The same patch corrects an issue that could leave Nero’s plushie stuck in the ground. Keep this separate from the plushie’s intended ability to pass through cover: the January OB52 notes had already described passing through the ground, floors and ceilings as supported behaviour. Passing through and becoming stuck are different observations. [1] [2]

Official fix available

OB55: Santino can enter unintended areas or become stuck

Platforms: MobileVersions: OB55Updated Evidence checked

Garena lists a Santino collision-volume problem as fixed in OB55. The stated consequences were entering unintended areas, getting stuck and exploiting glitches. This is a specific character interaction documented in the September patch; it does not identify the cause of every instance of a player becoming stuck on the map. [1]

Official fix available

OB53: USP-2 has no weapon mastery

Platforms: MobileVersions: OB53Updated Evidence checked

OB53 explicitly fixes the USP-2 lacking weapon mastery. The note concerns that weapon’s missing mastery support. It is not a promise to restore an unrelated account’s progress or rewards, and does not prescribe an account reset. [3]

Official fix available

OB52: Alok’s effect range and movement-speed boost

Platforms: MobileUpdated Evidence checked

In OB52, Garena fixes Alok’s effective skill range differing from its visual effect, and a movement-speed boost that sometimes failed to apply. OB53 separately changes how teammates’ Alok auras stack while the player’s own skill is active. That later balance restriction should not be confused with the earlier failed-boost bug. [2] [3]

Official fix available

OB52: damage does not register in certain Kalahari locations

Platforms: MobileVersions: OB52Updated Evidence checked

The January patch documents a Kalahari location-specific damage-registration correction. It does not establish that every missed hit, connection delay or later damage complaint has the same origin. Compare the map and symptom before treating this historical patch entry as the relevant correction. [2]

Sources & verification

Platform and version details belong to the individual issue or guide section. A documented workaround may not resolve every case.

  1. OB55 PATCH NOTES official-patch-notesRetrieved
  2. OB52 PATCH NOTES official-patch-notesRetrieved
  3. OB53 PATCH NOTES official-patch-notesRetrieved

Report a correction · More Free Fire coverage