How can we help?

Usernames are case sensitive. Koula and koula are two different accounts, so if you signed up with a capital letter you have to type it the same way.

If that is not it, check that cookies are allowed for this site. Sessions are cookie based, so a browser set to block all cookies will accept your password and then immediately bounce you back to the login page.

Usernames are 3 to 16 characters and may only contain letters, numbers and underscores. Passwords need at least 8 characters and must include at least one letter and one digit.

Passwords are stored as salted hashes, never as plain text, so nobody — including us — can read yours back.

Use the reset panel above. Enter your username or email, we send a 4-digit code from [email protected], and you pick a new password. The code lasts 20 minutes and works once.

Tapping the button in that email from your phone confirms it even if you started on a computer — the computer's tab moves on by itself, with nothing to refresh.

No email on your account? Accounts created before email verification existed do not have one, and there is nothing to send a code to. Open a ticket with your exact username and roughly when you created it, and an admin can verify and reset it manually. Once you are back in, add an address under Settings → Email so it never happens again.

One: [email protected]. Sign-up codes, password resets, ticket receipts, complaint acknowledgements and downtime notices all come from it, and replying to it reaches a person — it is a real inbox, not a no-reply address.

Older addresses (support@, server@, no-reply@) still receive, so an old thread you reply to will not bounce. They all arrive in the same place.

We will never email you asking for your password. No genuine KoulaChat message ever needs it.

Check spam and promotions first — a first message from a new domain often lands there. Codes take a few seconds, not minutes.

Still nothing after two minutes? Press Send a new code on the sign-up screen: it issues a fresh code and resets the attempt counter. If a typo in the address is the problem, use Wrong address? to go back a step.

Sessions last 30 days and refresh on every request, so normal use should never log you out. Private or incognito windows drop the cookie when you close them, and some privacy extensions clear site data on a timer.

If you were playing as a guest, that is working as designed. Guest runs are tracked so you can see your own best, but they are deliberately kept off the public boards. Sign up and every guest best you have gets published automatically.

If you were logged in, note that each player holds exactly one row per game — your best. A run lower than your existing best will not replace it.

The merge runs against the guest cookie on the device you signed up from. If you played on your phone and then signed up on a laptop, the laptop has no guest history to merge.

Fix it by going back to the original device, logging into your new account there, and pressing Claim guest progress on your profile page.

Games pause automatically when the tab loses focus, and the frame delta is capped, so returning to a tab never fast-forwards the action. If a game is genuinely choppy:

• Close other heavy tabs — the canvas competes for GPU time
• Check hardware acceleration is enabled in your browser settings
• Try a smaller window; the canvas scales with its container

Shootout and Vault Runner use the layout every mobile game uses: hold and drag anywhere on the left half of the screen to move, drag on the right half to look, and the round buttons bottom-right are fire and reload. The stick appears wherever your thumb lands rather than sitting in a fixed corner, so you never have to look for it.

The first time you open a game on a phone, an overlay labels each area and lists what the buttons do. It shows once — tap ? in the game header to bring it back.

Anywhere a right click would be used, press and hold instead. That is how you open Starfall Command's turret menu and how you flag a square in Mine Field.

Your rotation lock is on. The game tries to detect this — if your phone is physically sideways but the screen has not turned, it says so and tells you the exact gesture for your device.

On iPhone, swipe down from the top-right corner and tap the padlock-with-an-arrow icon. On Android, swipe down from the top and turn Auto-rotate on.

There is always a Play in portrait anyway button if you would rather not, and that choice is remembered for that game.

Work through these in order:

1. Check the browser actually has microphone permission. Click the padlock in the address bar — microphone should say Allow.
2. Open Settings on the call page and pick your microphone explicitly. Browsers sometimes default to a device that no longer exists.
3. Press Test mic. The meter should move when you talk, and it plays your voice back afterwards. If the meter is flat, the browser is not receiving audio at all.
4. Check the Mute button is not on.

Calls need a secure context. Over plain HTTP the browser only grants microphone access on localhost; on any other host you need HTTPS.

Open Settings and press Test speaker. If you hear the tone, your output is fine and the problem is on their end. If you do not, pick a different output device from the list.

Output device selection needs setSinkId, which Chrome and Edge support but Firefox and Safari largely do not. On those browsers the call uses your system default output, so change it in the operating system instead.

Echo is almost always speakers feeding back into a microphone. Headphones fix it instantly. If someone will not wear them, ask them to mute while they are not talking.

That means signalling worked but the peer connection never completed. It is usually a restrictive network — some corporate and school networks block the UDP that WebRTC needs.

Try a different network or a phone hotspot to confirm. A TURN relay server is the proper fix for locked-down networks; the site currently uses public STUN only.

Yes. Calls start audio-only on purpose so a missing or broken camera never blocks a conversation. Press the camera button on the call bar to add video mid-call; the other side sees it appear without having to rejoin.

The website checks the bridge every 5 seconds by opening a TCP connection to 127.0.0.1:9010 and sending a ping. Disconnected means that check failed.

• Confirm the server is actually running — the bridge starts with it and logs [bridge] listening on 127.0.0.1:9010
• Check nothing else already holds port 9010
• If the mod runs on another machine, change bridge_host in config/config.json from 127.0.0.1 to an address that machine can reach

Full detail lives on the Minecraft client support page and the protocol docs.

The website can only push a call down to a mod client that has registered itself. The mod must send {"type":"register","username":"YourName"} after connecting and then keep the socket open.

The username it registers has to match the site username you are calling. Matching is case-insensitive.