Bonk.io commands control movement, chat, moderation, and in-game behavior in this browser-based multiplayer platformer. This guide explains default keybinds, chat syntax, server moderation tools, and how to customize controls for desktop and mobile play. You will learn which commands are client side and which require operator or moderator privileges, plus how to interpret server logs and response messages. Notes on latency, input handling, and common pitfalls help you use commands reliably in public rooms and private servers.
Core Movement and Camera Controls
Basic navigation in Bonk.io relies on simple keyboard and mouse inputs that work consistently across browsers and devices. Understanding these fundamentals is essential before adding advanced or server specific commands to your workflow.
Keyboard defaults for desktop
- Move left: A or ←
- Move right: D or →
- Jump (and dash in some modes): W or ↑ or Space
- Sprint: Hold Shift (where enabled)
- Camera pan: Mouse movement while not in chat
Mouse and touch controls
Mouse click initiates the primary dash in most modes, while touch on mobile maps tap to dash and swipe to move. On touchscreen devices, on screen buttons mirror the same axis driven inputs used on keyboard, so command logic remains consistent across platforms.
In Game Chat Commands
Chat commands in Bonk.io allow quick actions, team organization, and room signaling. They typically start with a prefix such as / or ! and are processed client side before being relayed to other players in the room.
Quick action and team chat
/teamor/t: Switch to team chat/pubor/public: Switch to public chat/ignore [player]: Hide messages from a specific player/unignore [player]: Remove ignore for a player
Room and lobbies
Commands related to room joining, creating, and listing are often limited depending on server configuration. Some rooms use custom prefixes or require moderator approval for creation, while others rely on a browser based lobby UI instead of chat driven commands.
Moderation and Operator Commands
Server operators and moderators have access to administrative commands that manage users, mute offenders, and control room behavior. These commands are not available to regular players and are only executed when issued by authorized roles.
Common operator commands (server side)
/kick [player]: Remove a player from the room/ban [player]: Prevent a player from joining future rooms/mute [player]: Disable chat for a specific user/warn [player] [reason]: Issue a warning with an optional note
Room settings and state
Operators can change game mode, map, and downtime settings through either a visual control panel or scripted commands, depending on the server software. These adjustments affect all players currently in the room and any who join afterward.
Custom Keybinds and Control Settings
Bonk.io allows players to remap many inputs to suit personal preference or to accommodate alternate devices. Changes apply to the client locally and do not affect server logic or other players.
How to remap keys
- Open the in game settings menu
- Select Controls or Input
- Rebind desired actions to preferred keys or touch positions
- Save and test in a private room before using in public
Recommended setups
- WASD + Space for keyboard users
- Mouse dash on left click, tap to jump on touch
- Separate team chat shortcut to avoid accidental public messages
Server Configurations and Command Availability
Not every command is available on every server. Server administrators can enable or disable specific features, including chat commands, game modes, and input restrictions. The table below summarizes common attributes you may encounter across different rooms.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Default chat prefix | / or ! depending on server | Server config variable |
| Moderation commands | /kick, /ban, /mute, /warn | Operator only |
| Team chat shortcut | /team or /t | Client side |
| Key rebinding | Supported in settings menu | Client side |
| Public room creation | Often limited or UI based | Server dependent |
| Input handling | Client prediction with server reconciliation | Engine behavior |
Troubleshooting and Best Practices
Even with known command syntax, network conditions and server rules can affect behavior. Latency, packet loss, and strict server filters may delay or block certain actions. Adopting consistent habits reduces confusion and prevents accidental penalties.
Check list before reporting an issue
- Confirm the command is supported by the current server
- Verify your role (player, moderator, operator)
- Test the command in a private room if possible
- Review server logs or response messages for errors
- Ensure client is updated and browser permissions allow input
Platform Specific Notes
Desktop browsers support the full range of keyboard commands, while mobile clients rely on on screen controls and limited gyroscope features. Touch layouts vary by device and operating system, so button mappings may appear different but should follow the same logical actions.
Conclusion
Bonk.io commands cover movement, chat, moderation, and accessibility options that remain stable across updates. By mastering the default keybinds, chat syntax, and server specific rules, you can navigate public rooms and private servers with confidence. Use this reference to verify command behavior, customize controls, and troubleshoot issues consistently over time.