Version 4.8.0 Update

New Features Overview

The version 4.8.0 update introduces several powerful enhancements to improve your bot development experience:

  1. New Account Class: Direct access to account-level operations through the globally accessible Account variable.

  2. Enhanced Resource Management: New accountRes class for managing account-level resources.

  3. Improved Server Stability: Enhanced server maintenance and durability.

  4. Command Aliases: Support for command aliases in the upcoming UI update.

  5. Bot Recovery System: Ability to recover deleted bots within 90 days.

  6. Coming Soon - Bot Store: A marketplace for discovering, sharing, and deploying pre-made bots.

  7. Coming Soon - Points Faucet: System to obtain unlimited points for running your bots.

Advertising and Points System

Points System Enhancements

Telebot Creator continues to offer one of the most generous free bot hosting solutions available:

  • Initial Allocation: New accounts receive 100,000 points upon creation.

  • Command Cost: Each command execution costs just 1 point.

  • Free Additional Points: Users can request additional points at any time by contacting admins in the TBC Help Group.

  • Upcoming Points Faucet: In the next update, a points faucet system will allow users to obtain unlimited points.

Ad Policy Clarification

Telebot Creator maintains a minimal advertising approach to keep the platform free while ensuring a great user experience:

  • Low Frequency: Advertisements appear only 2-4 times per month.

  • Non-Intrusive Format: Ads are delivered as a single broadcast message, not as continuous spam.

  • User-Friendly: This approach ensures that bot users enjoy an uninterrupted experience.

New Account Class

The 4.8.0 update introduces the powerful Account class, giving developers direct access to account-level operations. This class allows for comprehensive management of bots, commands, statistics, and more from a centralized interface.

Accessing the Account Class

The Account class is globally accessible in your bot code through the Account variable, similar to how you access the Bot and User classes:

No initialization is needed as the variable is automatically created with the correct authentication and database connections.

Account Data Management Methods

saveData

Stores data at the account level, accessible across all bots.

Parameters:

  • name (Required): Name identifier for the data.

  • data (Required): The data to store (limited to 10MB).

Example:

Example Output:

getData

Retrieves previously stored account data.

Parameters:

  • name (Required): Name of the data to retrieve.

Example:

Example Output:

deleteData

Deletes account data by name.

Parameters:

  • name (Required): Name of the data to delete.

Example:

Example Output:

getDataFile

Returns account data as a file that can be sent to users.

Parameters:

  • name (Required): Name of the data to retrieve.

  • output_format (Optional): Format of the output file (currently supports "txt").

Example:

Example Output:

getAllData

Retrieves all account data entries, optionally filtered by name pattern.

Parameters:

  • name (Optional): Name pattern to filter data.

  • output_format (Optional): Format of the output file (currently supports "json").

Example:

Example Output:

deleteAllData

Deletes all account data, with optional exclusions and bot data inclusion.

Parameters:

  • except_data (Optional): List of data names to preserve.

  • include_bot_data (Optional): Whether to also delete bot-level data.

Example:

Example Output:

info

Returns basic account information.

Example:

Example Output:

Bot Management Methods

start_bot

Starts a bot by setting its webhook.

Parameters:

  • botid (Required): ID of the bot to start.

Example:

Example Output:

stop_bot

Stops a bot by removing its webhook.

Parameters:

  • botid (Required): ID of the bot to stop.

Example:

Example Output:

restart_bot

Restarts a bot by stopping and then starting it.

Parameters:

  • botid (Required): ID of the bot to restart.

Example:

Example Output:

create_bot

Creates a new bot with the given token.

Parameters:

  • bot_token (Required): Telegram bot token.

  • bot_name (Optional): Name for the bot (retrieved from Telegram if not provided).

  • bot_username (Optional): Username for the bot (retrieved from Telegram if not provided).

Example:

Example Output:

delete_bot

Deletes a bot (temporarily or permanently).

Parameters:

  • botid (Required): ID of the bot to delete.

  • permanent (Optional): Whether to permanently delete or keep for recovery.

Example:

Example Output:

recover_bot

Recovers a previously deleted bot.

Parameters:

  • botid (Required): ID of the bot to recover.

  • new_token (Optional): New token if the original is no longer valid.

Example:

Example Output:

get_deleted_bots

Retrieves a list of deleted bots that can be recovered.

Example:

Example Output:

get_deleted_bots_stats

Provides statistics about deleted bots, including counts and expiration information.

Example:

Example Output:

permanent_delete_bot

Permanently removes a deleted bot from the recovery system.

Parameters:

  • botid (Required): ID of the deleted bot to permanently remove.

Example:

Example Output:

clear_expired_bots

Admin-only method to clear expired bots (deleted over 90 days ago).

Example:

Example Output:

clone_bot

Creates a clone of an existing bot.

Parameters:

  • botid (Required): ID of the bot to clone.

  • new_token (Optional): Token for the new bot.

Example:

Example Output:

get_bots_list

Retrieves a list of all bots in the account.

Example:

Example Output:

get_bot_info

Retrieves detailed information about a specific bot.

Parameters:

  • botid (Required): ID of the bot to get information for.

Example:

Example Output:

get_bot_status

Checks the status of a bot.

Parameters:

  • botid (Required): ID of the bot to check.

Example:

Example Output:

get_bot_data

Retrieves stored global data for a specific bot.

Parameters:

  • botid (Required): ID of the bot to get data for.

  • name (Required): Name of the data to retrieve.

Example:

Example Output:

set_bot_data

Stores global data for a specific bot.

Parameters:

  • botid (Required): ID of the bot to store data for.

  • name (Required): Name identifier for the data.

  • data (Required): The data to store (limited to 10MB).

Example:

Example Output:

Command Management Methods

create_command

Creates a new command for a bot.

Parameters:

  • botid (Required): ID of the bot to create the command for.

  • command (Required): Name of the command.

  • code (Required): Code for the command.

Example:

Example Output:

delete_command

Deletes a command from a bot.

Parameters:

  • botid (Required): ID of the bot to delete the command from.

  • command (Required): Name of the command to delete.

Example:

Example Output:

edit_command

Updates the code of an existing command.

Parameters:

  • botid (Required): ID of the bot to edit the command for.

  • command (Required): Name of the command to edit.

  • code (Required): New code for the command.

Example:

Example Output:

get_command_list

Retrieves a list of all commands for a bot.

Parameters:

  • botid (Required): ID of the bot to get commands for.

Example:

Example Output:

get_command_info

Retrieves detailed information about a specific command.

Parameters:

  • botid (Required): ID of the bot the command belongs to.

  • command (Required): Name of the command to get information for.

Example:

Example Output:

get_command_usage

Retrieves usage statistics for a specific command.

Parameters:

  • botid (Required): ID of the bot the command belongs to.

  • command (Required): Name of the command to get usage for.

  • period (Optional): Time period for statistics ("hour", "day", "week", "month", "all").

Example:

Example Output:

User Management Methods

blockUser

Blocks a user from using a specific bot.

Parameters:

  • user_id (Required): ID of the user to block.

Example:

Example Output:

unblockUser

Unblocks a previously blocked user.

Parameters:

  • user_id (Required): ID of the user to unblock.

Example:

Example Output:

getBlockedUsers

Retrieves a list of blocked users for a specific bot.

Parameters:

  • botid (Required): ID of the bot to get blocked users for.

Example:

Example Output:

getBlockedUsersFile

Generates a file containing blocked users information.

Parameters:

  • botid (Optional): ID of the bot to get blocked users for. If omitted, gets all blocked users.

  • output_format (Optional): Format of the output file ("csv" or "json").

Example:

Example Output:

Statistics and Reporting Methods

get_bot_stats

Retrieves comprehensive statistics for a specific bot.

Parameters:

  • botid (Required): ID of the bot to get statistics for.

Example:

Example Output:

get_bot_usage

Retrieves detailed usage statistics for a specific bot.

Parameters:

  • botid (Required): ID of the bot to get usage for.

  • period (Optional): Time period for statistics ("day", "week", "month", "all").

Example:

Example Output:

get_bots_stats

Retrieves statistics for all bots in the account.

Example:

Example Output:

get_stats

Retrieves comprehensive account-level statistics.

Example:

Example Output:

Import/Export Methods

export_bot

Exports a bot's configuration and commands as a JSON file.

Parameters:

  • botid (Required): ID of the bot to export.

Example:

Example Output:

import_bot

Imports a bot from an export file.

Parameters:

  • import_data (Required): The JSON data from an exported bot.

  • new_token (Optional): Token for the new bot.

Example:

Example Output:

API Management

revoke_api

Revokes the current API key and generates a new one.

Example:

Example Output:

Enhanced Resource Management

New accountRes Class

The 4.8.0 update introduces a new accountRes class for managing account-level resources, complementing the existing resource management system.

Parameters:

  • name (Required): The name of the resource to manage.

Resource Management Methods

All methods from the BaseRes class are available:

  • value(): Gets the current value of the resource.

  • add(value): Adds to the resource value.

  • cut(value): Subtracts from the resource value.

  • set(value): Sets the resource to a specific value.

  • reset(): Resets the resource value to zero.

Example:

Example Output:

Server Improvements

The 4.8.0 update includes significant server-side improvements:

  1. Enhanced Stability: Improved error handling and recovery mechanisms to prevent service disruptions.

  2. Optimized Performance: Reduced response times and better resource allocation for smoother operation under high load.

  3. Improved Webhook Handling: Faster and more reliable webhook processing for better bot responsiveness.

  4. Advanced Monitoring: Better monitoring systems to detect and address issues before they affect users.

These improvements ensure that your bots remain operational and responsive, even during peak usage times or when handling complex commands.

Command Aliases

The upcoming UI update will introduce support for command aliases, allowing multiple command triggers to execute the same code. This powerful feature will enable:

  1. Multi-language Support: Create different command names for different languages.

  2. Command Variations: Support both full and abbreviated versions of commands.

  3. Intuitive Interactions: Allow users to trigger commands with natural language variations.

The alias system will be fully integrated into the command management system and accessible through both the UI and API.

Bot Recovery System

The new bot recovery system allows users to recover accidentally deleted bots within 90 days, with features including:

  1. Temporary Deletion: Bots are moved to a recovery collection rather than being permanently deleted.

  2. 90-Day Recovery Window: Generous timeframe to recover deleted bots.

  3. Statistics Tracking: Monitor how many bots you've deleted and how many can be recovered.

  4. Expiration Management: Clear visibility into when deleted bots will expire.

Example:

Coming Soon Features

Bot Store

The upcoming Bot Store will revolutionize how users discover and implement Telegram bots:

  • Pre-made Bot Templates: Access a library of ready-to-use bot templates for various industries and use cases.

  • Community Sharing: Share your own bot creations with the TBC community.

  • One-Click Deployment: Deploy complete bots with just a single click, without any coding required.

  • Categorized Listings: Browse bots by category, popularity, or functionality.

  • Custom Modifications: Use templates as starting points and customize them to your specific needs.

This feature will significantly reduce the time and effort needed to create powerful bots, making advanced bot functionality accessible to users of all skill levels.

Points Faucet

The Points Faucet system will ensure that all users have unlimited access to points for running their bots:

  • Unlimited Points: Obtain as many points as you need to run your bots without restrictions.

  • Completely Free: All points remain 100% free, with no hidden costs or premium tiers.

  • Automated System: Request points automatically through the faucet system without needing to contact admins.

  • Instant Credits: Points are credited instantly to your account.

  • No Usage Limits: Create and run as many bots as you want without worrying about running out of points.

This system reinforces Telebot Creator's commitment to providing a completely free platform for bot creation and hosting.

Both of these features are currently in final development and will be released in an upcoming update. Stay tuned to the TBC announcements channel for release dates and additional information.

Last updated