How to Copy Your KocakZ Key and Loader

A KocakZ key can be valid and still fail if one character is missing, an extra space is attached, or the wrong part of a formatted message is pasted into the executor. Loader code has a similar problem: it may look complete on screen while manual selection omits its first or last line.

The reliable approach is to treat the key and loader as separate items, use their dedicated copy controls, and verify the shape of what you pasted without exposing the credential. This guide shows that workflow on desktop and mobile, explains common formatting traps, and gives you a clean recovery process.

If you have not generated access yet, follow How to Claim Your First KocakZ Key first.

Know what you are copying

The completed claim displays two related outputs:

• Key: the private credential linked to your Discord account.
• Loader: Lua code that starts the current KocakZ loader and may contain or request the key.

They are not interchangeable. A key copied into a place expecting a full Lua snippet will not run as code. A loader pasted into a key field will not match the stored credential.

The labels beside the controls tell you which value is being copied. Pause long enough to read them. Fast repeated clicks often create confusion because the clipboard can only hold the most recently copied item.

Why the loader must also be treated as private

Even when the key is displayed in its own field, a generated loader snippet may include the same value. Hiding the key field in a screenshot is not enough if the credential remains visible lower down inside Lua code.

Before sharing any screenshot or message, inspect:

1. The key field.
2. The loader code.
3. Browser address and tabs.
4. Clipboard-history panels.
5. Console or executor messages that might repeat submitted values.

A support report normally needs the error text and stage, not the credential itself.

Use the built-in copy controls

The safest default is simple:

1. Open the completed claim while signed into the owning Discord account.
2. Select Copy Key when you need only the credential.
3. Paste it into the intended key field.
4. Return to the result page.
5. Select the loader copy control when you need the complete Lua snippet.
6. Clear the destination editor before pasting the loader.

Copy controls avoid the selection handles and hidden overflow that can affect manual copying, especially on a phone. They also reduce the chance of including explanatory text above or below a code block.

After clicking, wait for the page's copied feedback before switching applications. If no feedback appears, do not assume the clipboard changed. Try the control once more or paste into a private temporary text field to confirm what is currently stored.

Understand Markdown code fences

Discord and blog pages often display code inside fenced blocks. The fences are three backtick characters placed around the code for presentation:

```lua
-- loader code appears here
```

The outer ```lua and closing ``` are not part of the Lua program. A dedicated copy button normally copies only the code. Manual selection may include the fences, surrounding labels, or a leading line break.

If your pasted text begins with the word lua or three backticks, recopy it from the source control. Do not keep deleting characters at random until the executor accepts something; return to a known original.

Check the pasted key without revealing it

You can verify basic shape without posting the actual value. Look for these properties privately:

• It is on one line.
• It has no quotation marks added around it.
• There is no visible space before or after it.
• It did not wrap because a newline was inserted.
• It came from the current KocakZ result, not an old message.

Do not compare full keys in a public channel. If support asks whether two private copies are identical, compare them locally or describe only whether their length and beginning format differ. Never paste them into an unfamiliar "key checker" website.

KocakZ provides its own read-only key check through the loader workflow. Third-party validation pages can collect submitted credentials and are unnecessary.

Check the pasted loader as code

A loader should be copied as one complete source snippet. Clear old code first so two loaders do not become concatenated.

Look at the beginning and end of the pasted content. It should not contain chat labels such as "Get Script," Markdown fences, or prose telling you what to do next. Quotation marks and punctuation inside the code may be required; do not replace straight quotes with typographic quotes.

A useful private check is to paste the loader into a plain-text editor first. Plain text reveals whether a messaging app introduced formatting. It does not validate the code or key, but it makes invisible-looking structure easier to inspect.

Do not paste the loader into a public online formatter. Formatting is not required merely to run the official snippet, and sending it to another service may expose an embedded key.

Desktop workflow

On desktop, keep the completed claim and destination side by side when possible. This reduces tab switching and makes it easier to distinguish the key from the loader.

1. Confirm the claim page shows the intended Discord account and a valid expiry.
2. Copy the key.
3. Focus the exact key input and replace its contents.
4. Copy the loader.
5. Replace the entire old script in the destination.
6. Run one controlled attempt.
7. Save the non-secret error if it fails.

Avoid using a clipboard manager that syncs sensitive entries to a shared device or account unless you understand and accept that storage. If clipboard history is enabled, remove the credential afterward using the operating system's normal controls.

Do not leave the completed claim open on a shared screen. Sign out or close the page when you are finished, particularly on a computer used by several people.

Mobile workflow

Mobile selection handles make manual code copying particularly fragile. Prefer the site's buttons and watch for copied confirmation.

If you must move the loader from phone to computer, avoid public messages and shared group chats. A private channel is still a stored copy outside KocakZ, so use the shortest reasonable path and remove it afterward if the service supports deletion.

A better workflow is to open the completed claim directly on the device where you will paste the loader, using the same owning Discord account. If that is not possible, transfer the snippet through a private method you control and verify that line breaks remain intact.

When a mobile browser wraps a long line visually, that does not necessarily mean the clipboard contains a newline. Paste into a plain-text editor and inspect the cursor movement before editing the source.

Common copy failures and fixes

Symptom	Likely copy problem	Clean fix
Key is immediately rejected as invalid	Missing/extra character or whitespace	Copy the key again with the button and replace the whole field.
Executor reports syntax error near the first line	Markdown fence or label included	Recopy only the loader source.
Syntax error appears near the end	Final line or delimiter was omitted	Replace the complete script from a fresh copy.
Code shows curly quotation marks	Rich-text formatting changed characters	Paste through plain text or use the direct copy control.
Old behavior remains after copying	New snippet was appended to old code	Clear the destination, then paste once.
Clipboard contains the loader when key was expected	Another copy action replaced it	Return to the page and use Copy Key again.
Screenshot still exposes access	Key also appears inside loader	Redact the entire credential and relevant code line.

The clean fix is almost always replacement from the original, not manual repair. A known-good source is more reliable than remembering which characters you changed.

Separate copy errors from access errors

A correct copy can still be rejected for a legitimate access reason. Once you have recopied the original exactly, read the server or loader message.

• Expired: the key's validity period has ended.
• Revoked: an administrator has disabled the key.
• HWID limit: the device identifier does not fit the key's current bindings.
• Session limit: the key already has its maximum active sessions.
• Unavailable or network error: the request could not complete reliably.

Do not keep copying when the message clearly names one of these conditions. Move to the relevant diagnostic step in What to Check When Your KocakZ Key Does Not Work.

A different error after a clean recopy is useful evidence. It suggests the original failure involved formatting and the new message now describes the real access state.

Retrieve the stored key instead of using an old copy

KocakZ stores one current key per Discord account. If the key is still valid, Get Key returns it rather than generating a duplicate. This gives you an authoritative place to copy it again.

Do not rely on a months-old note, screenshot, or chat history when the current site can return the stored value. An old free key may have expired, and premium expiry follows the paid entitlement rather than the date a note was created.

If the key expired, complete the appropriate new claim. If it remains valid, retrieving it does not extend its lifetime; it simply gives you another accurate copy.

A two-copy verification method

When you suspect clipboard trouble, use this controlled method privately:

1. Copy the key with the official control.
2. Paste it into a local plain-text field.
3. Clear that field.
4. Return to the claim and copy the key again.
5. Paste it into the same local field.
6. Confirm that the two attempts have the same visible shape and length.
7. Clear the temporary field and clipboard history afterward.

Do not save either copy in a file merely for comparison. The purpose is to identify whether your copy action is stable, not create another long-term credential store.

For loader code, compare the beginning, ending, and line count rather than publishing a diff. If two button copies differ, reload the completed claim and report the problem without including the contents.

Keep support screenshots useful and safe

A screenshot should show the error and enough nearby interface to identify where it happened. It should not reveal the access needed to reproduce the request as you.

Before sharing:

• Cover the complete key with an opaque block.
• Cover the key inside the loader snippet.
• Hide private Discord conversations and account email addresses.
• Crop unrelated browser tabs and bookmarks.
• Keep the exact non-secret error visible.
• Add one sentence describing the action that produced it.

Blur can sometimes leave characters recoverable, especially when the original is high resolution. Use a solid redaction and inspect the exported image, not only the editing preview.

A reliable reset procedure

If several copy attempts have left the destination in an uncertain state, reset the process without changing your account or key:

1. Stop the current run.
2. Clear the destination key field and script editor.
3. Close duplicate claim tabs, keeping the completed result.
4. Copy the key once and paste it into the expected field.
5. Copy the loader once and paste it into an empty editor.
6. Run one attempt.
7. Record the exact result before making another change.

This procedure changes only the copied input. If the same access error remains, you can investigate the key state without wondering whether old source fragments caused it.

Before your next attempt, replace any uncertain pasted text with a fresh copy from the original result page. Use an empty destination for the loader, keep the key separate, and check that you have not included formatting marks from a message. This gives you a clear basis for deciding whether copying was the problem.

If the same rejection appears after that clean copy, work through the checks for a KocakZ key that does not work. Follow the check that matches the error you actually see, and keep a redacted record if you need help.