Repository navigation
Labymod module no longer completely working #1283
Description
Stacktrace
No stacktrace.
Actions to reproduce
Use CloudNet V4-RC9 with Labymod 4.
In the config, it says:
"discordJoinMatch": {
"enabled": true,
"excludedGroups": []
},and
"discordSpectateMatch": {
"enabled": true,
"excludedGroups": []
},But they both do not work.
Let's just say half of the module is not working, lol.
CloudNet version
[03.08 21:49:45.183] INFO:
[03.08 21:49:45.184] INFO: CloudNet Blizzard 4.0.0-RC9 f6ca4c38
[03.08 21:49:45.184] INFO: Discord: <https://discord.cloudnetservice.eu/>
[03.08 21:49:45.184] INFO:
[03.08 21:49:45.184] INFO: ClusterId: 10f3b547-****-47b9-****-4242a50a736f
[03.08 21:49:45.184] INFO: NodeId: Node-1
[03.08 21:49:45.184] INFO: Head-NodeId: Node-1
[03.08 21:49:45.184] INFO: CPU usage: (P/S) .13/11.3/100%
[03.08 21:49:45.185] INFO: Node services memory allocation (U/R/M): 37888/37888/81920 MB
[03.08 21:49:45.185] INFO: Threads: 135
[03.08 21:49:45.185] INFO: Heap usage: 82/256MB
[03.08 21:49:45.185] INFO: JVM: Private Build 17 (OpenJDK 64-Bit Server VM 17.0.8+7-Ubuntu-122.04)
[03.08 21:49:45.185] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: beta
[03.08 21:49:45.185] INFO:
Other
https://canary.discord.com/channels/325362837184577536/818777626663321671/1136743021724049418
Full context ^
Issue uniqueness
- Yes, this issue is unique. There are no similar issues.
Activity
[-]Labymod is no longer completely working[/-][+]Labymod module no longer completely working[/+]derklaro commentedon Aug 14, 2023
While the official developer documentation states that these features can be activated in the client, the last information that I got is that neither join nor spectate are implemented in the client.
IIRC there were plans to remvoe these two config options due to that. CC @0utplay
chore: update labymod module (#1309)