Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[5.4.3] Made console logs more clean (#198)
Now console logs look as follows: ``` [10.01.2024 - 21:18] | Spawned shard 0 [10.01.2024 - 21:18] [WARN ] | Bot running on OPLevel: 1 [10.01.2024 - 21:18] [WARN ] | Debug mode is [ENABLED]! [10.01.2024 - 21:18] [WARN ] | Booting up the bot... DiscordMusicBot/v5.4.1 (ID: {redacted}) [10.01.2024 - 21:18] [WARN ] | Loading error handlers... [10.01.2024 - 21:18] [INFO ] | Loaded debug error handlers! [10.01.2024 - 21:18] [DEBUG] | Music engine "Erela" has been loaded [10.01.2024 - 21:18] [DEBUG] | Prisma ORM has been loaded [10.01.2024 - 21:18] [INFO ] | Slash commands have been loaded. Waiting for bot to finish initializing... [10.01.2024 - 21:18] [INFO ] | Schedules have been loaded. [10.01.2024 - 21:18] [INFO ] | Event listeners have been loaded. [10.01.2024 - 21:18] [INFO ] | WS is now listening on port 3201 [10.01.2024 - 21:18] [INFO ] | Successfully logged in as Arch Music Bot#0893 [10.01.2024 - 21:18] [INFO ] | API is now listening on port 3200 [10.01.2024 - 21:18] [DEBUG] | Node: LocalNode | Lavalink node is connected. [10.01.2024 - 21:18] [INFO ] | Slash commands have been pushed to application [10.01.2024 - 21:18] [SILLY] | DiscordMusicBot/v5.4.1 (ID: {redacted}) is online! prisma:info Starting a postgresql pool with 9 connections. [11.01.2024 - 00:00] [INFO ] | 'logs.log' has been purged. ``` ## Status and versioning classification: - Code changes have been tested against the Discord API, or there are no code changes - I know how to update typings and have done so, or typings don't need updating
- Loading branch information