YouTube
Codes and verification
+1 Height Per Jump Codes: Verified Status and Redeem Help
See whether any redeemable string currently meets the site's full active-code standard. Every active row needs an exact string, a publicly supported reward, a dated source, and an accepted verification method. When those fields are missing, the table stays empty instead of turning a listing or video title into an unsupported reward claim. The visible review date and source boundary explain what was checked and what still requires a live result.
Dated reviewSee when evidence was checked
Official-source priorityListings remain separate from live tests
Exact strings onlyNo guessed variants or placeholders
Reward boundaryUnknown rewards are not invented
Review a community code video carefully
Use community videos to discover what may need checking, never as automatic proof that a string is active, its reward is official, or the current server will accept it.
How the code status is decided
The official experience description included a redeem-code listing during collection, but the available packet did not confirm a live redemption or publish an official reward for that listing. Under this site's policy, that is not enough to create an active row. A code becomes active only when its exact capitalization, public reward, source URL, check date, and accepted verification method are all recorded. Official and creator-owned sources carry the most weight; undated reposts and video titles are discovery leads only. The live game result remains the final authority because strings, rewards, and interfaces can change without notice. A failed submission is not automatic proof of expiration: the string may be mistyped, already claimed, inactive, tested in an old server, or entered through a changed interface. Recopy once, remove extra spaces, join one fresh official server, and record the response. An expired table also needs evidence; a string missing from the active list is not silently moved there. This cautious split prevents an unverified reward from being promoted simply because a third-party page repeats it. Reports should include the official place, current date, fresh-server result, and public reward source while hiding account details. That record lets editors distinguish a genuine status change from a typo, stale server, or already-claimed reward.
How to test a code safely
The current interface location is not verified in the evidence packet, so follow the live menu instead of an old screenshot.
Open the official experience
Launch place 137202615981355 from Roblox and confirm Jump And Crash is the developer.
Find the current entry surface
Follow the live game's code, gift, shop, or settings wording without assuming a permanent button location.
Paste the exact string
Preserve capitalization, remove extra spaces, and submit once.
Record the response and reward
Use the on-screen result, date, fresh-server state, and publicly supported reward when reporting a status.
Code questions
Are there verified active codes right now?
No string currently meets every required evidence field, so the active list is empty as of the visible review date.
Why is an official listing not automatically active?
The active table also requires a publicly supported reward and accepted current verification. Listing status alone does not prove a live result.
Where is the redemption button?
The current location is not verified. Follow the live game's menu wording rather than an old screenshot.
Why might a submitted string fail?
It may be mistyped, already claimed, inactive, expired, or tested in an old server. Recopy once and try a fresh official server.
Where should new strings be checked?
Start with the official Roblox description and developer-controlled surfaces, then require the live or current official evidence fields before publication.
Use verified progress while the code list is empty
Read the Height guide or check the official group reward instead of relying on a string with an unpublished reward.