Adds Support for Telegram Topics and fix sql script datatype issue, also resolve #661 and little more improved code#660
Closed
KMohZaid wants to merge 5 commits intoGreyWolfDev:betafrom
Closed
Adds Support for Telegram Topics and fix sql script datatype issue, also resolve #661 and little more improved code#660KMohZaid wants to merge 5 commits intoGreyWolfDev:betafrom
KMohZaid wants to merge 5 commits intoGreyWolfDev:betafrom
Conversation
1. changes TelegramId datatype in `werewolf.sql` to `bigint` to fix issue 2. added `/setgrouptopic` command which admin can use to set group for werewolf bot 3. added new column in `dbo.Group` table : `GroupTopicId` to store topic id Note : I may have forget some places to update and make topic support TODOs : 1. maybe ignore command in other topics when topic id is set 2. add command to unset topic id, if group admin want to disable topics in group and use in normaly way 3. Remove redundant direct call to Telegram send API and make single method that send normal message or document based on flag parameter such as `msg_type: [TEXT,DOC,GIF]` 4. A database migrator system, so we can avoid manual database backup and restore
Author
|
i will add few commits later, specially commit that complete TODO 1 and 2 |
…nset. TODO 1 and 2 are unset featue and restrict to specified topic
…able, allow them to force join with warning
…ll print readable message without spamming error
which make it LF)
Author
|
added 4 new commit commit 1 : Completes TODO 1 and 2 commit 2 : resolve this issue #661 commit 3 : clean up error spam that node process throws when it's unable to communicate with controller process port commit 4 : just git config, fixes line ending problem when commit are made from different operating system (i use linux also, so line ending were changed to LF from CRLF) |
Author
NOTE :
name validator working screenshots are sent in "Grey Wolf Support" group : https://t.me/c/1060486754/788569 New TODO to look out for :-
|
This was referenced Jun 19, 2025
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By datatype issue i mean error occurs when we fetch
intTelegramId column value intolongvariable of C#. C# long is equivalent to databasebigintAnd here is commit message dump that gets added to PR by default :-
This PR resolves :
#649