asdbee / modmail Goto Github PK

can you add something to like open a modmail with the person for example !modmail open so it dms them instead of them dming the bot?

When i start running the bot it will shows this

(node:177) UnhandledPromiseRejectionWarning: MongoError: bad auth : Authentication failed.
at MessageStream.messageHandler (/home/runner/ModMail/node_modules/mongodb/lib/cmap/connection.js:268:20)
at MessageStream.emit (events.js:376:20)
at processIncomingData (/home/runner/ModMail/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
at MessageStream._write (/home/runner/ModMail/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
at writeOrBuffer (internal/streams/writable.js:358:12)
at MessageStream.Writable.write (internal/streams/writable.js:303:10)
at TLSSocket.ondata (internal/streams/readable.js:745:22)
at TLSSocket.emit (events.js:376:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9)
at TLSSocket.Readable.push (internal/streams/readable.js:223:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
(Use node --trace-warnings ... to show where the warning was created)
(node:177) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:177) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This is the error

This dude stoled your modmail claming that it was his|

https://www.youtube.com/watch?v=H5H8Vx0XlBY&ab_channel=CrazyHQ

I Don't Know How to get the mongodb access token

I have the bot online but the bot is unresponsive and when I message nothing happens.

this is my console log

you can block and unblock in any channel, even when it isnt a modmail channel!

I don't know how to change the bot custom status type.

Unable to close tickets when the user had left the server.

Block/Unblock triggers even if the user is already blocked/unblocked

`> [email protected] start /home/runner/ModMail

node server.js

Database Connected
(node:233) UnhandledPromiseRejectionWarning: MongoParseError: Invalid connection string
at parseConnectionString (/home/runner/ModMail/node_modules/mongodb/lib/core/uri_parser.js:565:21)
at connect (/home/runner/ModMail/node_modules/mongodb/lib/operations/connect.js:282:3)
at /home/runner/ModMail/node_modules/mongodb/lib/mongo_client.js:223:5
at maybePromise (/home/runner/ModMail/node_modules/mongodb/lib/utils.js:662:3)
at MongoClient.connect (/home/runner/ModMail/node_modules/mongodb/lib/mongo_client.js:219:10)
at /home/runner/ModMail/node_modules/mongoose/lib/connection.js:788:12
at new Promise ()
at NativeConnection.Connection.openUri (/home/runner/ModMail/node_modules/mongoose/lib/connection.js:785:19)
at /home/runner/ModMail/node_modules/mongoose/lib/index.js:342:10
at /home/runner/ModMail/node_modules/mongoose/lib/helpers/promiseOrCallback.js:31:5
at new Promise ()
at promiseOrCallback (/home/runner/ModMail/node_modules/mongoose/lib/helpers/promiseOrCallback.js:30:10)
at Mongoose.connect (/home/runner/ModMail/node_modules/mongoose/lib/index.js:341:10)
at Object. (/home/runner/ModMail/database/databaseHandler.js:3:10)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
(node:233) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:233) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Mod role must be in main guild. [[-] Support Team]
Process exited with code 1`

Ok, OK... Last question this bot won't just shut off will it? With another ModMail bot I tried It kept shutting off.

/home/runner/Hub/node_modules/mongodb/lib/cmap/connection.js:268
callback(new MongoError(document));
^

MongoError: user is not allowed to do action [find] on [test.modmails]
at MessageStream.messageHandler (/home/runner/Hub/node_modules/mongodb/lib/cmap/connection.js:268:20)
at MessageStream.emit (node:events:390:28)
at MessageStream.emit (node:domain:475:12)
at processIncomingData (/home/runner/Hub/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
at MessageStream._write (/home/runner/Hub/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
at writeOrBuffer (node:internal/streams/writable:389:12)
at _write (node:internal/streams/writable:330:10)
at MessageStream.Writable.write (node:internal/streams/writable:334:10)
at TLSSocket.ondata (node:internal/streams/readable:754:22)
at TLSSocket.emit (node:events:390:28)
at TLSSocket.emit (node:domain:475:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at TLSSocket.Readable.push (node:internal/streams/readable:228:10) {
ok: 0,
code: 8000,
codeName: 'AtlasError'
}

No idea why this is happening right after I DM the bot.

In both block and unblock commands

if (checkMail === null) return bot.createMessage(msg.channel.id, '! This is not a thread.');

is not included which makes the bot respond even not in a thread and triggers:

bot.createMessage(msg.channel.id, '✔ Blocked user.');

when only the prefix that has been set is used

triggerUncaughtException(err, true /* fromPromise */);
^

DiscordRESTError [10003]: Unknown Channel
at RequestHandler.request (D:\ModMail\node_modules\eris\lib\rest\RequestHandler.js:71:15)
at Client.createMessage (D:\ModMail\node_modules\eris\lib\Client.js:1095:36)
at D:\ModMail\server.js:94:15

it was working i tried to fix it but i cant

people can send a dm and open the modmail but mods cant reply?

i basically messaged the modmail bot twice and it opened 2 modmails and i did !close , it said it was close but it didnt delete the channel and when i did it with the second modmail channel it said "no modmail affiliated with this channel"