A modern Telegram bot built with Telegraf v4 (ESM), a modular plugin system, and a lightweight JSON database (LowDB). It includes hot‑reload for plugins and a tiny HTTP status endpoint.

• Node.js ESM + Telegraf v4
• Modular plugins in plugins/ with hot-reload
• JSON database via bundled LowDB (no external DB)
• Role/permission helpers (owner, admin, premium)
• Daily command limit system (auto reset)
• Small HTTP status server with auto port selection

• Node.js v20+
• A Telegram Bot Token from @BotFather

1. Clone the repository

git clone https://github.com/ShirokamiRyzen/NaoESM-Telebot.git
cd NaoESM-Telebot

2. Install dependencies

npm install

3. Configure your bot

• Copy config.example.js to config.js
• Edit config.js and set at least:
  • global.token with your BotFather token
  • global.ownername, global.ownerid (comma/space separated or array)

4. Run the bot

npm start

On start you’ll see OS/RAM info, the HTTP status port, and the plugin summary. The status endpoint responds on / with a small JSON.

All settings live in config.js (see config.example.js for defaults).

• token: Telegram bot token string
• ownername: Your display name
• ownerid: Single ID or a list of owner IDs (string/array)
• premid: Premium user IDs (optional)
• botname: Public bot name used in messages
• prefix: Array of prefixes, e.g. ['/','.', '#','!']
• wib: Time offset (hours) for some date/time helpers
• message: Common error/guard messages
• ports: List of ports the tiny HTTP server will try in order
• limit: Default daily command limit per user
• APIs / APIKeys: External API base URLs and keys, e.g. ryzumi: https://api.ryzumi.vip

Security tips

• Don’t commit secrets. Prefer editing config.js locally copied from config.example.js.
• Rotate tokens/keys if they ever leak.

• File: database.json (auto-created on first run)
• Backend: LowDB JSON file (bundled under lib/lowdb/)
• Auto-save interval: ~15s
• Daily limit reset: handled internally for each user

Back up database.json regularly if you care about the data.

Plugins live in plugins/ and are hot‑reloaded on change. A plugin can be a function export and may attach metadata used by the core handler.

Minimal plugin example

// plugins/hello.js
export default async function (m, { conn }) {
  await m.reply('Hello World!')
}

// Optional metadata used by the handler
export const command = /^(hello|hi)$/i
export const tags = ['main'] // for your own grouping/menus

Supported fields (attach as named exports or properties on the default function):

• command: string | RegExp | (string | RegExp)[] — matcher for the command (required to trigger)
• customPrefix: string | RegExp | (string | RegExp)[] — override global prefixes
• before(m, extras): optional pre-hook; return false to skip
• after(m, extras): optional post-hook
• exp: number — XP awarded (default 17)
• limit: boolean | number — consume N limits (true = 1)
• rowner, owner, premium, group, private, admin: booleans to guard command

Handler parameters

• m: normalized message object with helpers like m.reply(text)
• extras: { conn, args, text, command, usedPrefix, isOwner, isPrems, isAdmin, isBotAdmin, participants }

Explore existing examples in plugins/.

index.js starts a tiny Express server and auto-picks the first open port from global.ports. Hitting / returns a small JSON to verify the bot is alive.

• “Telegraf library is not installed”: run npm install again.
• Stuck on token error: ensure global.token in config.js is set and valid.
• Node version: must be 20+. Check with node -v.

This project is adapted and refactored for ESM and Telegraf v4 by ShirokamiRyzen.

Original author and repository (base work):

• ERLANRAHMAT — https://github.com/ERLANRAHMAT/telebot-wa

The codebase also references “Original Script by BETABOTZ” in logs. We extend thanks to the original authors and contributors.

ISC License © ShirokamiRyzen