Invite V2 is an advanced version of the invite module that offers more flexibility and gives more control over the invitation process than the previous version.
Detailed functions:
1. Use database — allows you to upload a list of users to invite. This can be a file obtained after parsing or simply a list of usernames entered manually into the field (one per line). Without usernames the system will not work — Telegram allows inviting only by username.
2. Groups — here you enter links or usernames of the chats where people should be invited. Each chat should be on a new line. If it's a private group, you must use an invitation link.
3. Total users per account — sets how many people one account will invite within the task. A safe range is from 5 to 10 to avoid Telegram restrictions.
4. Total users per request — sets how many people will be invited in one batch. It's better to start with small values and then adjust depending on the situation — Telegram is sensitive to sudden spikes in activity.
5. Delay — allows you to set a time range between invitations. The greater the spread and pauses — the more natural the behavior appears, reducing the risk of Telegram treating it as spam. The delay is randomly selected from the specified range.
6. Maximum timeout (FloodWait) — if Telegram issues a temporary restriction, the module checks whether it fits within the specified limit. If yes — it simply waits. If not — it disables the account to avoid breaking the rules.
7. Select accounts — you can manually select the accounts to be used. When selecting, check for activity, presence of avatar and bio, recent history of actions, and other signs of «liveliness» to minimize the risk of being blocked.
8. Forced number of invited users — when enabled, the system counts the invitation as successful only if the user actually joins the chat. Inactive or unavailable users are not counted.
9. Check if user is in group before inviting — this function checks whether the user is already in the selected group. It saves limits and avoids duplication. If this option is not enabled, the software will go through all accounts regardless of whether they are in the group or not and mark even those already added as «Done,» which can cause a mismatch between actual added users and the recorded additions in the database.
10. Leave the main group — after the task is completed, the account can automatically leave the group where it was sending invites. If the account wasn’t in the group before — it will temporarily join it for the task and then leave.
11. Streams сontrol — allows you to run several accounts (threads) in parallel. You can specify the number of threads and the delay range between starts. The number of threads equals the number of accounts, and the delay is taken from the specified range — each time randomly. This helps scale the task without overloading.
12. Auto stop — enables protection: the system automatically stops the task if accounts receive certain statuses, such as spam block, flood, or ban. You must specify after how many such cases everything should stop (e.g., after 1 or 10 incidents), and once the condition is met, the software will stop the module.
Detailed functions:
1. Use database — allows you to upload a list of users to invite. This can be a file obtained after parsing or simply a list of usernames entered manually into the field (one per line). Without usernames the system will not work — Telegram allows inviting only by username.
2. Groups — here you enter links or usernames of the chats where people should be invited. Each chat should be on a new line. If it's a private group, you must use an invitation link.
3. Total users per account — sets how many people one account will invite within the task. A safe range is from 5 to 10 to avoid Telegram restrictions.
4. Total users per request — sets how many people will be invited in one batch. It's better to start with small values and then adjust depending on the situation — Telegram is sensitive to sudden spikes in activity.
5. Delay — allows you to set a time range between invitations. The greater the spread and pauses — the more natural the behavior appears, reducing the risk of Telegram treating it as spam. The delay is randomly selected from the specified range.
6. Maximum timeout (FloodWait) — if Telegram issues a temporary restriction, the module checks whether it fits within the specified limit. If yes — it simply waits. If not — it disables the account to avoid breaking the rules.
7. Select accounts — you can manually select the accounts to be used. When selecting, check for activity, presence of avatar and bio, recent history of actions, and other signs of «liveliness» to minimize the risk of being blocked.
8. Forced number of invited users — when enabled, the system counts the invitation as successful only if the user actually joins the chat. Inactive or unavailable users are not counted.
9. Check if user is in group before inviting — this function checks whether the user is already in the selected group. It saves limits and avoids duplication. If this option is not enabled, the software will go through all accounts regardless of whether they are in the group or not and mark even those already added as «Done,» which can cause a mismatch between actual added users and the recorded additions in the database.
10. Leave the main group — after the task is completed, the account can automatically leave the group where it was sending invites. If the account wasn’t in the group before — it will temporarily join it for the task and then leave.
11. Streams сontrol — allows you to run several accounts (threads) in parallel. You can specify the number of threads and the delay range between starts. The number of threads equals the number of accounts, and the delay is taken from the specified range — each time randomly. This helps scale the task without overloading.
12. Auto stop — enables protection: the system automatically stops the task if accounts receive certain statuses, such as spam block, flood, or ban. You must specify after how many such cases everything should stop (e.g., after 1 or 10 incidents), and once the condition is met, the software will stop the module.
Последнее редактирование: