How to Join

• You must be in the Discord server first.
• You need your exact Minecraft username ready before whitelist submission.
• Java usernames and Bedrock/Geyser usernames can be different. Submit the exact one for your platform.
• Bedrock players must use the exact gamertag shown in Minecraft.
• Do not spam reconnect attempts while waiting for whitelist approval.

Purpose: get into the onboarding and whitelist workflow before attempting to connect in-game.

1. Open the Discord invite/community link: Open Discord.
2. Read the welcome/onboarding channel from top to bottom.
3. Go to the whitelist or request area described by staff/bot.
4. Use the required request format exactly if one exists.
5. Keep Discord open so you can respond to staff follow-up questions quickly.

Common mistake: joining voice/chat and asking for manual whitelist before reading onboarding instructions.

Purpose: provide exact access details so whitelist approval works on first try.

1. Specify platform clearly: Java or Bedrock.
2. Provide exact username/gamertag (case-sensitive where applicable).
3. Mention device type: console, mobile, Windows Bedrock, or Java edition.
4. Wait for explicit approval message before trying to join.
5. If denied/corrected, resubmit using the exact corrected name.

Common mistake: sending display name or Discord nickname instead of actual Minecraft account name.

Purpose: prevent unnecessary login failures and keep moderation queue stable.

1. Staff/bot approval must happen before joining.
2. If you join early, you may be kicked or receive whitelist errors.
3. Approval flow protects server stability and moderation quality.
4. Once approved, continue to Java or Bedrock instructions below.

Purpose: connect Java client correctly on the first attempt.

1. Open Minecraft Java Edition.
2. Use the current supported version shown in server channels (currently 1.21.11).
3. Click Multiplayer.
4. Click Add Server.
5. Server Name: Drak's Twisted World.
6. Server Address (LAN/private preview): 192.168.0.75:25565.
7. Later/public address is posted in Discord; use that value when public routing is enabled.
8. Click Done, select the server, then click Join Server.
9. Accept required/recommended resource pack prompt if shown.
10. If pack download fails, retry once, then report issue.

Common mistake: connecting with the wrong client version and assuming whitelist failed.

Purpose: add Bedrock server entry correctly and complete first pack sync.

1. Open Minecraft Bedrock.
2. Go to Play.
3. Open the Servers tab.
4. Scroll to Add Server.
5. Server Name: Drak's Twisted World.
6. Server Address: 192.168.0.75.
7. Port: 19132.
8. Save, then join the server.
9. Accept/download resource packs if prompted.
10. If stuck downloading packs, fully close Minecraft and retry once.

Common mistake: using the Java port on Bedrock or leaving old server entries with incorrect values.

Purpose: bridge console clients through BedrockTogether when direct entry is unavailable.

1. Install/open BedrockTogether on a phone or tablet.
2. Enter server IP and port in BedrockTogether.
3. Start the BedrockTogether session.
4. Leave the app running and unlocked while joining.
5. On console, open Minecraft.
6. Go to Play → Friends/LAN Games.
7. Select the LAN server entry and join.
8. If LAN entry does not appear, verify phone and console are on the same Wi-Fi.

• Java pack is pushed by the server.
• Bedrock pack stack is delivered through Geyser workflow.
• First join can take longer while packs sync.
• Do not cancel pack download unless frozen for several minutes.
• If visual bugs happen, screenshot and report platform/version details.

• "Not whitelisted" → wait for approval and verify exact username submitted.
• "Outdated client/server" → switch to supported version.
• "Disconnected" → retry once, then report.
• "Resource pack stuck" → restart client and retry.
• "Bedrock cannot find server" → verify IP/port and local network.
• "Console cannot see LAN game" → BedrockTogether device must stay awake on same network.

Use this exact format when reporting onboarding failures:

Open Issue Intake