You do not need to guess your way through a KocakZ claim. The process has three checkpoints of its own: prove which Discord account you are using, complete the human check, and finish the access checkpoint assigned to that account. Once those steps succeed, the same flow page shows your key and loader.
This guide explains the complete free-key path, what premium users see instead, and how to recover when a step does not behave as expected. If you only need a quick overview first, read Getting Started with KocakZ.
Before you start
Prepare the account and browser you intend to use. A clean start prevents most cases where a claim appears to belong to the wrong person or an old tab.
You need:
- A Discord account that you can sign into in the browser.
- Membership in the KocakZ Discord server.
- A browser that allows the site to use its required verification page.
- One active claim link.
- A place to paste the final loader without exposing your key publicly.
The website uses your Discord identity as the owner of the claim. It does not ask you to type a Discord ID into the free claim flow. If Discord offers several accounts, choose the account you actually use in the KocakZ server.
Do not open several claim links as a way to improve your chances. Each flow has its own identifier and expiry, so multiple similar tabs make it easier to return to the wrong one. Keep one attempt open until it either completes or clearly expires.
The KocakZ claim flow at a glance
The normal free-access sequence is:
- Start a claim from KocakZ or use the claim link returned by the Discord bot.
- Connect the intended Discord account.
- Join the KocakZ Discord server if the account is not already a member.
- Complete Cloudflare Turnstile on the claim page.
- Open the assigned blog checkpoint.
- Wait for the Continue control to become available.
- Return to the original flow page.
- Copy the generated key and loader.
The order matters. The server checks who owns the flow, whether it is still valid, and which stage has already completed. A copied URL does not let another account inherit the claim.
Premium access follows a shorter path. The website still identifies the Discord account and may perform the human verification, but an active premium account skips the free content checkpoint. The Discord bot can also return an existing premium key directly.
Step 1: Start one claim
Use the Get Key control on the KocakZ website or the Get Key button in the official Discord panel. A free Discord request creates a temporary flow URL. A request made while you already have a valid key should return the stored key rather than create a duplicate.
A flow is a temporary path to a key, not the key itself. It is designed to expire if it remains unfinished. Completing an older flow also does not reset the lifetime of a key you already own.
When a link opens, check the domain before signing in. The official production website is kocakz.vercel.app. A browser may show Discord during authorization and then return you to KocakZ. That change of domain is expected during OAuth, but the final claim should return to the KocakZ site.
If you began inside a Lua interface, the interface may copy a flow URL instead of opening the browser automatically. That is intentional because browser-opening support differs between executors. Paste the copied URL into your browser yourself.
Step 2: Connect the correct Discord account
Discord sign-in establishes ownership of the flow. The website asks for the identify permission so it can associate the claim with a Discord user. Server membership is checked separately through the bot.
Before approving the sign-in, look at the Discord username and avatar shown by Discord. If they belong to another account, switch accounts there instead of continuing and trying to repair the claim afterward.
After Discord returns you to KocakZ, one of three things normally happens:
- The account is recognized and the next step appears.
- The site asks the account to join the KocakZ server.
- The authorization fails and the flow shows a retryable message.
If membership is missing, use the server invitation shown by the website, join with the same account, and reload the flow. Joining with one account while the browser is signed into another will not satisfy the check.
Why server membership is checked more than once
KocakZ does not rely on a claim page that was opened earlier remaining trustworthy forever. Important flow actions check current membership again. This prevents an old browser state from being treated as proof that an account still meets the requirement.
A temporary Discord outage can therefore stop progression even when you are already a member. In that case, wait and retry rather than creating several new claims. The system fails closed when it cannot confirm membership.
Step 3: Complete the human verification
Cloudflare Turnstile helps reduce automated claim creation. The widget is tied to the claim action and the website's configured domain. Complete it on the same flow page after Discord is connected.
If the widget does not appear:
- Check whether the page shows a configuration or network error.
- Allow required site scripts for the KocakZ domain.
- Reload the flow once.
- Confirm that you are still signed into the intended Discord account.
Do not repeatedly submit the widget in several tabs. A successful result advances one specific flow. An expired or mismatched result cannot be reused for another flow.
Turnstile is one security layer, not proof that a visitor is harmless or that every automated request is impossible. The server still validates ownership, flow state, expiry, and later checkpoint completion.
Step 4: Finish the blog checkpoint
After verification, a free claim receives a blog article selected from the published posts that are marked as checkpoint eligible. The article remains ordinary public content: anyone can read it. Only a signed-in visitor with a matching unfinished flow sees the private checkpoint panel.
Read the article while the short server-timed wait runs. Reloading the article does not restart a valid stored deadline. When Continue becomes available, select it to finish the checkpoint and return to the flow.
You do not need to click an advertisement to obtain a key. Ads support the site, but an ad click is not used as proof of checkpoint completion. If an active checkpoint detects an ad blocker, it may ask you to allow the site and reload before the Continue control is enabled.
The countdown displayed in the browser is only feedback. The server decides whether enough time has passed. Changing a device clock or editing the visible number does not satisfy the server check.
What makes the checkpoint single-use
The checkpoint attempt belongs to one Discord user, one flow, and one selected article. When the server completes it, key issuance and flow completion occur together. Repeating the same completion request returns the existing result rather than issuing another key or extending its expiry.
Starting another free flow can replace the account's current unfinished blog attempt. This is another reason to keep one clear claim open instead of collecting links.
Step 5: Copy your key and loader
A completed flow displays the key and a loader snippet. These are related but distinct:
- The key is the credential associated with your Discord account.
- The loader snippet is the Lua code used to start the current loader.
Use the Copy Key and loader copy controls. Manual text selection on a narrow screen can omit the first or last character. When pasting code, do not include Markdown fences such as three backticks; those are display formatting, not Lua.
Treat the entire loader snippet as private if it contains your key. Removing the key from one visible field does not make a screenshot safe when the same value remains inside the code below it.
The generated key is not bound to hardware on the website. The first authenticated loader run supplies the device identifier and binds it when allowed. Free access supports one HWID and up to five active sessions. A free key lasts 24 hours from issuance.
Reuse the key you already have
KocakZ keeps one current key per Discord account. Get Key is therefore an idempotent action while that key is valid: it returns the existing credential instead of issuing a fresh one every time.
This behavior solves two problems. It prevents accidental duplicates, and it stops repeated claims from becoming a way to refresh an expiry. If a free key expires, the old access is removed and the account can complete a new claim.
A completed flow also remains completed. It does not turn back into an unused claim merely because the key later expires. Start a new claim after expiry instead of reopening an old completion URL.
Troubleshooting by the stage that failed
Use the last completed stage to choose the next action. This is faster than treating every failure as a broken key.
| Last visible stage | Likely area to check | Best next action |
|---|---|---|
| Discord authorization | Account selection or OAuth callback | Confirm the account and retry the sign-in from the same flow. |
| Join-server notice | Membership is not confirmed for that account | Join with the connected account, then reload. |
| Turnstile | Widget loading, domain, or verification | Allow required scripts and retry once. |
| Blog article | Wrong/expired flow, blocker gate, or countdown | Read the checkpoint panel and return through its Continue control. |
| Completed claim | Copying or key expiry | Copy again from the completed page and check the displayed expiry. |
| Loader start | Key, HWID, session, or network validation | Keep the exact loader error and investigate that specific limit. |
The claim says it expired
Start a new claim. A flow is intentionally temporary and cannot be revived after its claim window closes. Creating a new flow is appropriate here because the old flow itself is no longer usable.
The page says the claim belongs to another account
Check which Discord account is active in the browser. Return to the original account or start a fresh flow with the account you intend to use. Do not share a flow URL to transfer access; ownership is verified server-side.
The checkpoint has no available article
This means no published article is currently eligible for checkpoint selection. It is a site-content configuration problem, not something a visitor can solve by refreshing repeatedly. Report the message in the Discord server.
Continue stays disabled
Read any status message above the button. The server countdown, BlockAdBlock check, or a failed status request may still be pending. If the page explicitly offers Reload and check again, allow the site in your blocker and use that control. If the flow expired during the wait, begin a new claim.
The copied key is rejected
Return to the completed flow or request Get Key again with the same Discord account, then use the copy control. Check the expiry. If the loader names an HWID or session limit, generating another flow is not the correct fix while the same key remains valid.
Protect your access when asking for help
A useful support message includes:
- The step you were performing.
- The exact non-secret error text.
- The approximate time it occurred.
- Whether it happens again with the same flow.
- The browser or device type when relevant.
Do not include your complete key, session token, Discord token, browser cookies, or password. If you attach a screenshot, inspect the loader snippet as well as the key field. A solid redaction is safer than a light blur.
Avoid saying only that it does not work. A report such as "After Discord returned me to the flow, the page still asked me to join the server at about 20:10 WIB" identifies a stage and an observed result without exposing credentials.
A practical decision tree
Use this short decision tree whenever you are unsure what to do next:
- Do you already have a valid key? If yes, retrieve and reuse it. Do not open another free checkpoint.
- Is the flow expired? If yes, start one new flow. If no, remain on the existing flow.
- Is the connected Discord account a server member? If no, join with that exact account and reload.
- Has Turnstile succeeded? If no, complete the widget before looking for a checkpoint.
- Does the blog show a checkpoint panel? If yes, follow that panel; an ordinary article without the panel is not your active checkpoint.
- Has Continue become available? If no, read the current status. If yes, complete it once.
- Does the final page show a key? If yes, copy it and the loader separately. If no, keep the displayed error for support.
This order prevents the most common failure pattern: restarting the whole claim when only one clearly identified stage needs attention.
Once the result page displays your key, pause before closing it. Copy the key and loader using the available controls, check that you have the values you need, and keep both out of public messages. A completed claim is a useful place to stop and confirm what you have received.
Use the guide to what happens after a claim finishes for that handoff. It explains what to collect and what to check before your first attempt, so you can move forward without starting another claim unnecessarily.