NEXANOW SPY SMP — OFFICIAL WHATSAPP BOT

The NEXANOW WhatsApp Bot is the official automation and community assistant for the NEXANOW network, primarily serving the SPY SMP Minecraft server and its connected WhatsApp groups.

It acts as a living bridge between the in-game Minecraft world and the WhatsApp community, relaying events, executing administrative commands, and protecting the community from abuse.

The bot was built specifically for high-traffic SMP servers where thousands of interactions happen daily: joins, quits, referrals, shop transactions, flash events, and staff moderation.

Every feature of the bot is designed with two goals in mind: keep the players informed, and keep the game economy and the community safe.

The bot is a first-party tool operated by the server owner. It is not affiliated with or endorsed by Mojang Studios or Microsoft Corporation.

The bot understands Minecraft server telemetry, reads live server logs, connects to RCON for command execution, and reads the Vault economy database to build leaderboards.

Because the bot lives inside WhatsApp, players do not need to install anything, open a browser, or configure software — the server and the community meet inside the app they already use.

This page documents what the bot is, what it can do, how to use it safely, and the rules under which it operates.

The bot is continuously improved: new commands, protections, and automations are added across seasons based on community feedback and observed abuse patterns.

All bot activity is recorded through an audit logging system so that every administrative action is traceable, reviewable, and accountable.

The bot runs as a WhatsApp Web client connected to a dedicated phone number, watched by a Node.js process that listens for incoming messages in real time.

When a player types a command such as .ip or .leaderboard, the bot recognizes the command pattern, looks up the requested information, and replies inside the same group.

When a Minecraft player joins or leaves the server, the bot watches the live server console log and broadcasts a short notification into the allowed group channels.

When a flash event drops, the bot checks in-game event claims and awards free dollars directly into player balances through RCON.

When players are referred, the bot verifies the referee has actually joined the server before a single dollar is paid out — the anti-abuse gate.

The bot queries the Minecraft server using the game console protocol (RCON) for commands like op, kick, ban, time, weather, and the player list.

It also reads the Vault economy storage through a plugin bridge so it can compute money, kills, and playtime leaderboards on demand.

The moderation pipeline scans messages for invite links, bad words, spam, caps-lock flooding, mass mentions, NSFW, and suspicious bot-like behavior before the message is treated as legitimate.

All sensitive operations are gated by permission checks: group admins can use a safe read-only subset, the owner and secondary admins get the full command set.

The bot persists state across restarts using configuration files and a local message store, so cooldowns, settings, and case data are not lost.

To use the bot, simply join any official NEXANOW WhatsApp group that the bot is a member of.

No download, account link, or registration is required to talk to the bot inside a group.

The most useful first command is .ip, which prints the server IP for both phone (Bedrock) and PC (Java) players.

New players should run .register and .login inside the Minecraft server as displayed by the join screens — the bot cannot register you in-game, but it tells you how.

The .bedrock command prints the direct IP and port for mobile players who struggle to connect on cellular data.

The .tcs command prints the WhatsApp Bot Terms & Conditions and links to the full legal page, available to any member.

Group admins can enable or disable features with allowed commands; the owner controls everything from the master switchboard.

When in doubt about a command, type .help or .menu to see what the bot can do.

The bot answers only within groups that are explicitly allowed in its configuration, protecting members of other chats from unsolicited activity.

An individual WhatsApp user can influence bot behavior only through the commands publicly documented on this page.

.ping and ping — reports the bot latency and confirms the bot is alive.

.status and mcstatus — live server telemetry including TPS (20.0 target), memory, and player counts.

.online, .players and list — shows the current online players and the server capacity.

.ip and server — prints the Java IP, the Bedrock IP and port, and the quick-start registration instructions.

.bedrock, .bdip and .bd — dedicated card for Bedrock/PE players with mobile-data tips.

.leaderboard and .top — the top players leaderboard across all tracked statistics.

.hours, .hour, .playtime — hours played for all players, or a specific player when a name is included.

.kills, .mobkills, .balance and .wealth — specialized leaderboards for PvP, PvE and money.

.event, drop, flashevent — starts, stops or reports flash drop events being broadcast to the group.

.time, .mctime, .day, .night — world time readout and quick day/night toggles through the group-admin gate.

.weather, .mcweather — world weather readout and selector for the current world.

.clearlag, .lag, .lagg — runs lag cleanup and reports the timings short summary.

.website and .web — replies with the official NEXA Network website URL.

.help and .menu — the public help card listing available features.

.op — grants operator in-game; owner and gated admins only.

.deop — removes operator status; owner and gated admins only.

.mckick — kicks a player from the Minecraft server.

.kick, .remove, .kickwa — removes a WhatsApp participant from the group (@mention, reply, or phone number).

.mcban and .ban — bans a player from the Minecraft server.

.pardon and .unban — unbans a player from the Minecraft server.

.resetwarn — resets the warning counter for a target member.

.playerjoinnotif and .joinnotif — toggles join/leave notifications for the group.

.tcs — prints the WhatsApp Bot Terms & Conditions and links to the legal page.

.console, .c and .mccmd — executes any server console command; restricted to the owner.

.mute — silences a member from the group (owner and gated admins only).

Word commands without a dot are auto-normalized: typing ip or mc works like .ip.

Slash and exclamation forms are normalized to dot commands for convenience.

Every command is rate-limited per group so one user cannot flood a channel.

All administrative commands are recorded in the audit log with sender, group, command, and timestamp.

The full, always-up-to-date command list lives in the .help card — this reference covers the core set.

The bot operates several reward systems that pay real in-game dollars when predefined events are proven.

The Referral System automatically detects when a member adds a new WhatsApp contact, links the invited players account, and later checks the referee actually joined the Minecraft server.

A verified referral credits the referrer $50,000 and the referee $10,000 — but only after the referee connects to the server for the first time.

The referral engine enforces three anti-loophole rules: no self-referrals, no simulated bots, and only one claim per player per season.

Flash drop events reward players who claim drops in-game; the bot verifies claims through the event telemetry before paying.

Economy payouts are executed via RCON and verified afterward against the economy database, so overpayment or exploitation is prevented.

The bot operates a watchdog that monitors the Minecraft process, restarting the server cleanly if it hangs or crashes.

A shop-price watchdog audits every shop item to ensure sell prices never exceed fair craft costs, closing money-printing loopholes.

A dedicated bedrock monitor watches for Bedrock client timeouts and alerts the owner when mobile players struggle to connect.

Scheduled audits of top earners flag suspicious economy movement such as buying-and-reselling sprees for abnormal multiples.

Maintenance announcements, seasonal wipes, and economy resets are broadcast by the bot ahead of time so players are never surprised.

Automated announcements are rate-limited and opt-in per group; the owner can block any feature in any group instantly.

Every official group is protected by a layered, silent moderation pipeline that removes toxic and spam content without cluttering the chat.

Anti-Link scans for external invite links and strips them automatically, protecting members from phishing and raid groups.

Anti-Badword filters profanity and slurs before the message reaches other members.

Anti-Spam detects message floods and repeated identical messages, auto-warning and then muting offenders.

Anti-Tag prevents mass-mention abuse so members cannot tag the entire group repeatedly.

Anti-All blocks the @everyone-style broadcast attempts that would disturb the whole chat.

Anti-NSFW bins adult content and links to it immediately.

Anti-Caps collapses shouty all-caps message bursts so chats stay readable.

Anti-Bot flags automated or scripted accounts that join only to advertise.

Slowmode enforces minimum intervals between a single member messages during peak hours.

Codee Mode applies a stricter zero-reply policy: violations are deleted silently with no feed-back chat.

Muted users cannot speak at all until a moderator unmutes them, and their messages are deleted on arrival.

Moderation actions are logged through the audit system, and NexaStaffAudit forwards in-game staff actions to the group.

The owner and bot administrators are totally immune from all automated enforcement, rate limits, and restrictions by design.

Any member who disagrees with a moderation decision can type .tcs to review the terms and then contact the owner directly with evidence.

The bot broadcasts a short line whenever a Minecraft player joins or leaves the server, in the groups that have notifications enabled.

Join and leave notices are rate-limited per player to four minutes, so a player who relogs repeatedly cannot spam the channel.

Different groups can configure notifications independently: one group may see them while another keeps the feed clean.

The notification service is served from the live server log, so it reflects true connection events, not client-side chatter.

Owners and group admins toggle the feature with .playerjoinnotif.

Player-friendly and compact, notifications always pair with real availability, so players know when friends can be interrupted.

The bot reads the economy and player-stat databases to answer who is richest, who plays the most, and who fights the most.

.leaderboard shows the top of the seasonal charts for money, hours played, PvP kills, and mob kills.

.hours prints a personal playtime profile including global rank and total hours in the season.

Statistics refresh on every request, so the leaderboards are never stale.

Playtime is tracked per season and resets with the economy on seasonal wipes.

Leaderboard queries respect player privacy: only public in-game names and aggregate numbers are returned, never phone numbers.

The same data powers the website player profiles, keeping the web and WhatsApp views consistent.

The owner number (and approved secondary admins) have the full command surface, including the console gateway and economy operations.

The console gateway .c/.console/.mccmd turns the bot into a remote terminal for the Minecraft server, gated exclusively to the owner.

The owner can reconfigure allowed groups, notification scopes, cooldowns, and reward amounts without touching server files.

The owner receives direct private alerts for referrals, exploit flags, bedrock timeouts, and watchdog events.

Audit logs feed the owner a complete paper trail of every administrative command ever executed.

Seasonal operations such as economy resets, referral windows, and maintenance are orchestrated through owner-only switches.

Staff plugins like NexaStaffAudit and NexaShopGuard report directly to the owner channel, centralizing security monitoring.

The owner may override or reverse any automated payout when evidence of loophole abuse is found.

The bot stores only what it needs: group identifiers, sender identifiers, and command history required for moderation and rewards.

WhatsApp message contents are processed in memory for moderation and are not published anywhere outside the group.

A secret player-mapping system matches WhatsApp identities to Minecraft usernames without sending any data into the chat.

RCON credentials, HTTP tokens, and webhook keys are stored outside the working directory and are never exposed to commands or chat.

The HTTP APIs that serve the bot and the website are loopback-only; the public internet cannot reach the control plane.

Audit logs contain no message text beyond the exact command string a user typed, and rotate automatically.

Personal data is retained only as long as the player remains a member and can be removed on request.

The bot does not track, sell, or share user data with third parties, and has no advertising or analytics payloads.

The API bearer token is required for any programmatic interaction, and it is not shared with plugin code.

Data is processed in line with the NEXA Privacy Policy available on the website.

Public cards such as .ip, .bedrock and .tcs enforce a per-group cooldown so one user cannot re-post spam.

Join and leave notifications enforce a per-player four-minute window to keep channels clean.

The owner and administrators are exempt from all these limits by design — they are immune.

Commands that query the live server (status, online, leaderboards) may be throttled during gameplay spikes to protect server TPS.

Repeated command abuse results in progressively longer mute intervals enforced by the moderation pipeline.

Fair use keeps the bot responsive for everyone: thousands of members rely on it every day.

The bot depends on third-party services: WhatsApp Web, the Minecraft server itself, and the box it runs on.

WhatsApp connections occasionally age out; the bot reconnects automatically and queued notifications may be missed in the seconds of downtime.

If the Minecraft server is offline, telemetry and economy commands cannot respond until it returns.

Automated moderation is deterministic and may occasionally flag a legitimate message; members can appeal to the owner with evidence.

Automated payouts are only as accurate as the telemetry feeding them; the owner reviews and can reverse flagged payouts.

The bot is provided as-is with no warranty of uninterrupted availability, accuracy, or fitness for a particular purpose.

No automated message, payout, or moderation action constitutes legal, financial, or business advice.

In-game currency and rewards have zero real-world monetary value and cannot be redeemed for cash.

Any attempt to exploit, harass, spoof, or interfere with the bot or its operators may result in removal from all services.

Users who abuse the bot understand that the owner and administrator decisions are final.

Q: Do I need to install anything to use the bot? A: No. The bot lives inside your WhatsApp group.

Q: Is the bot a real person? A: No. It is an automated assistant operated by the server owner.

Q: Can the bot register me on the Minecraft server? A: No — you must type /register and /login inside the game as shown on the join screen.

Q: The bot deleted my message; what happened? A: Your message likely matched the anti-link or anti-badword filter. Type .tcs to review terms and appeal to the owner.

Q: Can I change a group setting myself? A: Group admins can toggle features with allowed commands; everything else belongs to the owner.

Q: How do I get the server IP? A: Type .ip in the group, or check the website play page.

Q: Why do I sometimes wait to re-trigger .ip or .tcs? A: A short per-group cooldown prevents flooding; the owner is exempt.

Q: How are referral bonuses paid? A: $50,000 to the referrer and $10,000 to the referee, only after the referee joins the server once.

Q: Can the bot pay me money for nothing? A: No. Every payout is tied to a proven event and verified against the economy before release.

Q: The bot is offline; what now? A: The watchdog restarts it automatically. If it stays down, contact the owner in the group.