PUBG MOBILE July 21 Hidden Leaf and Metro Royale Fix Guide

The July 21 PUBG MOBILE patch addresses two very different problems. In the NARUTO: Ninjas Assemble content, invisible walls in certain parts of Hidden Leaf Center could cause hits not to register. In Metro Royale's Arctic Base Assault Mode, the update notes clarify the daily acquisition rule for the scroll that transports players to the Nine-Tails battle: it can be obtained once per day, and the limit refreshes at 00:00 UTC.

The first issue affects combat trust. A player sees an enemy, places the crosshair correctly, fires, and receives no expected damage because hidden geometry blocks the shot. The second affects planning. A player needs to know whether another scroll can be earned now or only after the next daily reset.

This guide explains both changes, shows how to verify that the July 21 patch is active, and provides a structured way to separate remaining map problems from network delay, weapon spread, desynchronization, or an already-used daily limit.

July 21 Patch at a Glance

Area	July 21 information	Player impact
Hidden Leaf Center	Fixed an issue where invisible walls in certain areas could prevent hits from registering	Clear lines of sight should no longer be blocked by the affected hidden geometry
Metro Royale Arctic Base Assault	Nine-Tails battle transport scroll can be obtained once per day	Players cannot repeatedly farm another scroll before reset
Metro Royale reset	Daily scroll limit refreshes at 00:00 UTC	Local reset time depends on the player's time zone

The patch notes do not claim to fix every form of missed hit, touch-input problem, camera movement issue, or network delay. They identify one specific map-geometry defect in Hidden Leaf Center. Players should test that correction without treating every future missed shot as proof that the same bug remains.

What the Hidden Leaf Center Bug Looked Like

An invisible wall is collision geometry that blocks movement, projectiles, or interaction without a visible object matching it. In a shooter, this can create a particularly confusing hit-registration problem.

The attacker sees an opponent through an apparently open space. The crosshair is placed on the target. The weapon fires normally. However, the server processes the bullet path as colliding with hidden geometry before it reaches the opponent.

From the player's perspective, this can resemble several unrelated issues:

Network latency delays damage feedback.
Desynchronization means the opponent is not exactly where the client shows.
Weapon spread moves bullets away from the crosshair.
Recoil causes later shots to miss.
A visible object has unusual collision boundaries.
The target has already moved behind cover on the server.
A touch or input problem prevents the intended shot or aim adjustment.

The July 21 fix applies to invisible walls in certain areas of Hidden Leaf Center. It should improve those affected lines of sight, but it does not remove ordinary shooter variables.

How to Verify the Hidden Leaf Fix

Do not test the patch by firing one uncontrolled magazine during a live fight. Use repeatable conditions whenever possible.

Confirm the client is current

Open the official application store or launcher and check for updates. Restart PUBG MOBILE after installation. A server-side hotfix may not require a large download, but the client should still be allowed to refresh resources and event data.

Return to the affected location

When normal matchmaking places you in Hidden Leaf Center, pay attention to spaces where a visible gap previously behaved like solid cover. Do not risk a ranked match merely to stand in the open. Use ordinary combat opportunities.

Use controlled shots

A stable single shot or short burst provides better evidence than a long spray. Hold a clear angle, reduce movement error, and choose a target distance appropriate for the weapon.

Watch multiple feedback channels

Check hit effects, health reduction, elimination information, sound, and teammate observation. One missing visual effect can be an interface issue rather than a complete failure to deal damage.

Repeat from both directions

Collision can behave differently depending on the angle. If a line remains suspicious, observe whether shots fail only from one side or at one precise edge.

Testing should never involve exploiting a broken location against other players. The goal is to confirm normal combat behavior and report reproducible defects.

Invisible Geometry Versus Network Lag

A geometry problem is location-dependent. It tends to repeat along the same line, edge, doorway, roof section, or invisible plane. Network lag is more likely to affect several actions and locations during the same period.

Use this comparison.

Sign	More consistent with geometry	More consistent with connection or synchronization
Repeats at one exact location	Yes	Less likely
Other nearby actions remain responsive	Often	Less likely
Affects both bullets and thrown items along the same line	Possible	Less specific
Ping spikes or packet loss indicators appear	Not required	More likely
Doors, movement, inventory, and damage all respond late	Less likely	More likely
Problem disappears when the angle changes slightly	Often	Possible but less specific

This is not a perfect diagnostic tool. The same fight can contain both poor network conditions and problematic geometry. Record enough context before reaching a conclusion.

Invisible Geometry Versus Weapon Inaccuracy

PUBG MOBILE weapons do not send every bullet through the exact center of the reticle under all conditions. Movement, stance, recoil, hip fire, attachments, distance, and firing duration can change accuracy.

A missed long spray through a narrow opening is weak evidence of an invisible wall. A controlled shot from a stable stance into a clearly exposed target provides stronger evidence.

To reduce uncertainty:

Stop moving before the test shot when safe.
Aim down sights instead of relying on hip fire.
Use a familiar weapon with predictable recoil.
Fire a short burst rather than emptying the magazine.
Avoid testing through foliage, smoke, glass, or irregular visible cover.
Record the reticle and target at the moment of fire.

The July 21 fix improves affected geometry. It does not transform every weapon into a perfectly accurate laser.

Why the Fix Matters in Ranked Play

Hidden collision can distort decision-making even when it affects only a small area.

Players may abandon a strong angle because earlier shots failed. Defenders may believe a position is safer than it should be. Teams may waste grenades, abilities, or movement trying to solve a line of sight that the map presents incorrectly.

The most serious effect is loss of trust. Competitive players need the visible environment to communicate where bullets can travel. When the visual map and collision map disagree, learning the location becomes memorizing a defect rather than understanding tactical cover.

The fix should restore normal tactical expectations in the affected parts of Hidden Leaf Center. Players can still lose a fight because of aim, timing, armor, ninjutsu abilities, or team positioning, but the open space should behave like open space.

Remaining Hit-Registration Concerns

A specific fix does not close every possible report. Players may continue to discuss missed shots after July 21. The important step is to identify whether the new report matches the repaired problem.

Ask:

Is the problem in Hidden Leaf Center or another location?
Does it repeat at the exact same piece of map geometry?
Is the client fully updated?
What was the ping and connection state?
Was the player moving, hip-firing, or spraying at distance?
Did the opponent move behind cover from the server's perspective?
Did the shot produce any hit effect or damage?
Can another player reproduce the same line?

A report that answers those questions is more actionable than “bullets do not work.” It also protects players from misdiagnosing normal misses as a map defect.

How to Report a Suspected Remaining Invisible Wall

Collect evidence during ordinary play without revealing private account information.

Record or capture:

The map and exact named area.
A wider view showing the position of both players.
A close view of the suspected invisible boundary.
Weapon, optic, stance, and approximate distance.
Ping or network indicators.
Match time and server region.
Whether the result repeated from the same angle.
Client version and device model.

Use the in-game Customer Service option in Settings or the official community channel. Describe the defect as a suspected collision or hit-registration issue rather than declaring a cause you cannot verify.

Do not repeatedly abuse the location to gain an advantage. Once the evidence is collected, continue normal play and submit the report.

Metro Royale Nine-Tails Scroll Rule

The same July 21 notes include a Metro Royale rule for Arctic Base Assault Mode. The scroll used to transport players to the Nine-Tails battle can be obtained once per day. The acquisition limit refreshes every day at 00:00 UTC.

This is a daily acquisition limit, not necessarily a statement about how many scrolls can be stored, carried, consumed, or shared under every circumstance. Follow the item description and mode interface for those details.

The rule answers two practical questions:

If you have already obtained the daily scroll, another attempt before 00:00 UTC should not be expected to award a second one.
After 00:00 UTC, the daily eligibility refreshes, although the player may still need to complete the required in-mode action to obtain the next scroll.

A reset does not automatically place the item in inventory. It restores the opportunity to earn it.

Convert 00:00 UTC to Your Local Time

The Metro Royale limit uses UTC, not every player's local midnight.

Common conversions include:

UTC+8 regions: 08:00 local time.
UTC+9 regions: 09:00 local time.
UTC+2 regions during standard offset: 02:00 local time.
UTC-4 regions: 20:00 on the previous local calendar day.
UTC-7 regions: 17:00 on the previous local calendar day.

Daylight-saving changes can alter local conversion in some countries. Use a reliable time-zone converter and confirm the countdown shown in the game client.

The phrase “once per day” refers to the server's daily cycle. A player can sometimes obtain one scroll near the end of one server day and another shortly after reset, even though both actions occur on the same local calendar date.

A Safe Daily Scroll Routine

Use a repeatable sequence to avoid wasting an Arctic Base Assault run.

Before entering

Check whether the account already obtained the scroll during the current UTC cycle. Inspect the relevant mode page, mission state, or inventory indicator.

Confirm the reset

If waiting for a new daily opportunity, allow a few minutes after 00:00 UTC for server data to refresh. Return to the lobby or restart the mode page if the old state remains visible.

Complete the acquisition condition

Follow the actual Arctic Base Assault requirement. Do not assume that entering the map automatically awards the item.

Verify ownership

Check inventory or the mode interface before planning the Nine-Tails transport. A completed action and an owned scroll are separate states.

Plan the battle

Prepare equipment, ammunition, healing, and teammates before using the transport item. A limited daily acquisition deserves more preparation than an ordinary repeatable entry.

What If the Scroll Does Not Reset?

First, verify the time. 00:00 UTC is not 00:00 local time in most regions.

Second, reopen the mode page after the reset. Cached interface data may still show the previous daily state.

Third, confirm that the account is in Arctic Base Assault Mode and that the correct scroll condition is being completed.

Fourth, check whether the item already exists in inventory or whether another pending state prevents acquisition.

Fifth, restart the client and use a stable connection.

If the problem continues, record the UTC time, local time, player ID, server, mode page, inventory, and completed requirement. Submit the evidence through official support.

Planning the Nine-Tails Battle

A daily-limited transport item should not be consumed casually.

Enter with a clear objective. Decide whether the team is prioritizing the battle reward, mission progression, or extraction value. Bring ammunition capable of handling the expected enemies, sufficient recovery, and a route for the situation after the encounter.

Communicate who holds the scroll and when it will be used. A team should not separate immediately before activating transport. Confirm that every member has finished looting, healing, and inventory management.

The once-per-day acquisition rule increases the cost of poor coordination. It does not guarantee a successful battle or extraction.

Update and Account Safety

Use the official PUBG MOBILE client and recognized support channels. A hit-registration fix does not require players to install a third-party “map repair,” and a daily scroll does not require an external generator or paid unlock.

Players making normal supported purchases can review options through Topuplist. Visit the dedicated PUBG MOBILE top-up page, verify the player ID, region, product, delivery information, and final price, and do not buy Unknown Cash because an unofficial page claims it is needed to activate the July 21 fixes or reset the Metro Royale scroll.

Technical fixes and server reset rules apply through the game. Purchases do not change collision geometry or bypass the daily acquisition limit.

July 21 Player Checklist

For Hidden Leaf Center:

Update and restart the official client.
Test normal lines of sight during ordinary matches.
Separate location-specific collision from network or weapon behavior.
Record reproducible geometry issues.
Submit exact evidence through official support.

For Metro Royale:

Remember the scroll can be obtained once per UTC day.
Convert 00:00 UTC correctly.
Verify daily eligibility before entering.
Confirm the item is owned before planning transport.
Prepare the squad before using a limited daily opportunity.

Frequently Asked Questions

What did the July 21 PUBG MOBILE patch fix in Hidden Leaf Center?

It fixed an issue where hits sometimes failed to register because of invisible walls in certain areas of Hidden Leaf Center.

Does the patch fix every hit-registration problem?

No. The note identifies a specific invisible-wall issue. Network delay, desynchronization, weapon spread, recoil, touch input, and other map defects can still produce different symptoms.

How can I tell whether an invisible wall remains?

Look for a problem that repeats at one exact line or boundary under controlled shots. Record the map location, angle, weapon, connection state, and result.

How often can I obtain the Nine-Tails battle scroll?

In Metro Royale Arctic Base Assault Mode, the transport scroll can be obtained once per day.

When does the daily scroll limit reset?

The limit refreshes at 00:00 UTC. Convert that time to your region instead of using local midnight automatically.

Does the reset automatically give me a scroll?

No. The reset restores daily eligibility. Players still need to complete the required acquisition condition and confirm the item appears.

Why did my scroll not reset at midnight?

Your local midnight may not match 00:00 UTC. Check the time conversion, reopen the mode page, restart the client, and verify the current UTC cycle.

Where should I report a remaining problem?

Use the in-game Customer Service option in Settings or an official PUBG MOBILE community channel. Include reproducible evidence without exposing login credentials.

Final Interpretation

The July 21 patch improves two forms of reliability. Hidden Leaf Center should now align visible openings with bullet collision in the corrected areas. Metro Royale players have a clear server rule for the daily Nine-Tails transport scroll: one acquisition per day, refreshing at 00:00 UTC.

Neither change removes the need for careful diagnosis. A missed shot can have several causes, and a missing scroll can result from time-zone confusion, an incomplete acquisition condition, or cached interface data. Update the client, test methodically, verify the current UTC cycle, and report remaining issues with precise evidence.

Reliable information is as important as reliable hit registration. The patch fixes a specific defect and clarifies a specific limit; players should apply those facts without expanding them into claims the notes did not make.