[Bug Report] 0.4.4.0 requires different Discord intents than previous versions

[shejan0]

Bug Description

When using 0.4.4.0, I can no longer launch the bot and have it connect to the WebSocket that worked perfectly fine on 0.4.3.9 and 0.4.3.8.

I cannot use 0.4.3.9 due to encryption methods being out of date (what 0.4.4.0 fixes)

Is there any documentation on how to enable these intents or where they are (alternatively, is there a way to not use these intents)

Steps to Reproduce

1. Install 0.4.4.0
2. Configure config.txt for the server and bot API for its use that works with 0.4.3.9
3. Attempt to launch 0.4.4.0 with the same config.txt and Discord side config.

Expected Result

The bot should launch and run as intended.

Debug Output

env[779861]: [05:18:39] [INFO] [WebSocketClient]: Connected to WebSocket
[05:18:39] [ERROR] [WebSocketClient]: WebSocket connection was closed and cannot be recovered due to identification issues
CloseCode[DISALLOWED_INTENTS](code=4014, meaning=Disallowed intents. Your bot might not be eligible to request a privileged intent such as GUILD_PRESENCES, MESSAGE_CONTENT, or GUILD_MEMBERS.)

Additional Info

No response

Checklist

• I have looked for information about this within the documentation
• I have searched for similar issues on the issues page
• I am using an official release from the releases page

JMusicBot Version

0.4.4.0

[theLucasAntunes]

Can confirm, also get this error:

[01:32:44] [ERROR] [JDA]: One of the EventListeners had an uncaught exception
java.lang.NoSuchMethodError: 'net.dv8tion.jda.api.entities.Member net.dv8tion.jda.api.entities.Guild.getSelfMember()'
        at com.jagrosh.jdautilities.command.CommandEvent.getSelfMember(CommandEvent.java:1055)
        at com.jagrosh.jdautilities.command.Command.run(Command.java:263)
        at com.jagrosh.jdautilities.command.impl.CommandClientImpl.onMessageReceived(CommandClientImpl.java:792)
        at com.jagrosh.jdautilities.command.impl.CommandClientImpl.onEvent(CommandClientImpl.java:623)
        at net.dv8tion.jda.api.hooks.InterfacedEventManager.handle(InterfacedEventManager.java:89)
        at net.dv8tion.jda.internal.hooks.EventManagerProxy.handleInternally(EventManagerProxy.java:76)
        at net.dv8tion.jda.internal.hooks.EventManagerProxy.handle(EventManagerProxy.java:63)
        at net.dv8tion.jda.internal.JDAImpl.handleEvent(JDAImpl.java:182)
        at net.dv8tion.jda.internal.handle.MessageCreateHandler.handleInternally(MessageCreateHandler.java:126)
        at net.dv8tion.jda.internal.handle.SocketHandler.handle(SocketHandler.java:39)
        at net.dv8tion.jda.internal.requests.WebSocketClient.onDispatch(WebSocketClient.java:936)
        at net.dv8tion.jda.internal.requests.WebSocketClient.onEvent(WebSocketClient.java:826)
        at net.dv8tion.jda.internal.requests.WebSocketClient.handleEvent(WebSocketClient.java:809)
        at net.dv8tion.jda.internal.requests.WebSocketClient.onBinaryMessage(WebSocketClient.java:980)
        at com.neovisionaries.ws.client.ListenerManager.callOnBinaryMessage(ListenerManager.java:385)
        at com.neovisionaries.ws.client.ReadingThread.callOnBinaryMessage(ReadingThread.java:276)
        at com.neovisionaries.ws.client.ReadingThread.handleBinaryFrame(ReadingThread.java:996)
        at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:755)
        at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:108)
        at com.neovisionaries.ws.client.ReadingThread.runMain(ReadingThread.java:64)
        at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)

YouTube Search no longer works, not sure if related to this.