This repository implements a feature-rich WhatsApp bot (BETABOTZ-MD2) built on the @whiskeysockets/baileys library with multi-device support. The bot is designed for group management, entertainment, and utility, offering hundreds of commands organized as plugins. Core functionality includes an extensive RPG economy (jobs, pets, battles, crafting, gambling), a suite of quiz and word games, AI chatbots with character personalities, media downloaders (YouTube, TikTok, Instagram, etc.), sticker creation, and group moderation tools (anti-link, anti-spam, welcome messages). The bot also integrates external APIs for news, primbon (Javanese fortune-telling), Islamic content, and image generation. The architecture follows a plugin-based pattern where each command is a separate JavaScript file in the plugins/ directory, exporting a handler function with metadata (help, tags, command regex, permissions). The core bot logic resides in an obfuscated main.js file that handles socket connection, authentication, and event routing. Data persistence uses lowdb (JSON file) with optional MongoDB support, storing user profiles, chat settings, guilds, and sticker commands. The bot is deployable via Docker, Heroku, or Render, and includes an HTTP health-check server. A critical dependency is the external API at api.betabotz.eu.org, which powers most downloaders, AI, and content features. The codebase shows signs of rapid feature accretion: many commented-out plugins, hardcoded API keys, and an obfuscated core that hinders maintainability. Despite these issues, the plugin system and game logic modules (e.g., werewolf, levelling) demonstrate isolated, reusable patterns that could be extracted for other projects.
This repository is a collection of heavily obfuscated Node.js scripts designed to automate various JD.com (Jingdong) activities such as check-ins, bean collection, farm tasks, lotteries, and coupon management. The scripts are intended to run on the Qinglong (青龙) panel, a cron-based task scheduler. They rely on environment variables for configuration (cookies, notification settings, proxy) and use custom obfuscated signing algorithms to interact with JD's APIs. The codebase is tightly coupled to the JD ecosystem and the Qinglong platform, with no tests, no dependency pinning, and minimal documentation. The heavy obfuscation makes maintenance and reuse extremely difficult, and the reliance on external JD APIs introduces high technical drift risk. While the scripts are functional for their intended purpose, the overall software quality is low due to obfuscation, duplication, and lack of engineering best practices.