Skip to main content

Token of Functions

Token of Functions - is a method of payment for certain types of functionality.

It is used to prevent abuse and control, through symbolic payment, for the operation of functions that have the least predictable scenarios of use (both in terms of volume and method of application), while giving a significant load on the server. In other words, so that heavy functions paid once do not generate a load on the server endlessly. Works on the same principle and with the same purpose as Token of Group.

📆 50,000 renewable Tokens of Functions available monthly.
You can check the number of available Tokens of Functions in:
☞ 🔐Admin

The bot has functionality of periodic admin notification about the depletion of the "Tokens of Functions", triggered in case tokens are needed for the functioning of the bot's features. The first notification will come directly at the moment of the tokens depletion. Subsequent notifications will come, if the bot encounters a situation where the user could not use the function that requires tokens for its work, BUT no more than once in every 5 minutes.

Additional ones can be purchased if necessary. Function tokens are purchased on a separate BOT and can only be used in it.

Function Token.
To purchase, go in your bot:
☞ 🔐Admin | 🧩Extensions | 📂Actions

 

TOKEN CONSUMPTION STATISTICS
Send the bot the required System Command to interact with the statistics data:
/tokens - will show the cumulative statistics on the use of tokens in your bot, since the last reset.
/resettokens - resets token usage statistics in your bot.

 

Features spending Tokens of Functions

1. Expressions

Cost: 0.1 Token for each triggered bool_symb, bool_symbn, int_symb, format_num

2. Checking group multi-subscription

● Check on Data Base - Cost: 1
● Verification by group - Cost: 5 (verification in Data Base with a negative result is included in the price)

More info about the rules of tokens deduction read in manual on Multi-subscription.

3. Forms with conditions

Cost: 1 (For each condition check of the user data input)

4. Paste the copied button

Cost: (number of buttons + number of messages) * 100

5. Actions

● Triggering any Action (except those listed below) - Cost: 1
● Action of Referral - Cost: 1 for each referral parent along the chain
● Action of Text - Cost: 3 for each operation performed.

6. Pagination

Delete Previous Page - Cost: 1 Token for every page deleted

7. Commands

/userinfo - Cost: 5

Cost: 10 - For each search (page change is not counted)

9. Batch update of a variables

/varaddall, /varmultall - Cost: (number of updates) * 1

10. Withdraw button

● Withdrawal Operation - Cost: 5 (Button Press: 1, Success: 4, Cancel: none)
● Cancellation of withdrawal with a refund - Cost: 5

11. Macros of referral parent data

Consumes 1 token for each data substitution in the message.

12. Bot content protect

Any change in the protection state on a message - protection and removal of protection - consumes 1 token (it does not matter, protection is applied to a separate message or to all messages of the button in batch mode).

Tokens deduction does not have the goal of earning. This is a way to protect against useless and thoughtless switching on and off of protection - since when setting protection on individual bot elements, it is necessary to actually make changes to the bot's files - each such element (message) individually. This is justified and not noticeable if you do not have many messages to protect. If there are a lot of messages, then use the "Whole bot" protection. Protecting the "Whole Bot" does NOT consume tokens - because it does not actually make or save any changes - it's just a "flag" (if you understand what that means).

13. Instant unsubscription check

● Unsubscription check of a user who is NOT in the bot - Cost: 1
● Unsubscription check of a user who IS in the bot - Cost: 2

14. Buttons Visibility Condition

Once checked, the visibility condition consumes 0.1 Token of Functions for each calculation and check. Checking is performed only for those buttons that have a visibility condition and, accordingly, the payment is charged only for them.

For example: If there are 9 regular buttons in the menu and one with a visibility condition, 0.1 token will be charged when entering this menu.


Back to top