-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown command #70
Comments
I think I detected the problem, //tnt is not executed, it is that it is not executed directly because the mod is not capable of executing plugin commands on a hybrid server. |
If the command is part of a mod you can use If you're wanting to spawn in tnt you can use |
Hey there! Unfortunately some of the mods/plugins implement their client-only commands as something that is not defined under Minecraft's command definiton. TwitchSpawn is unable to perform EXECUTE with something that is not executable by the Minecraft Command Dispatcher. 😢 (Checkout the implementation) TwitchSpawn/src/main/java/net/programmer/igoodie/twitchspawn/tslanguage/action/ExecuteAction.java Lines 38 to 41 in dc7ce5a
Though, I think I shall come up with an action that is able to mimic writing something on the actual client-side chat input. Maybe something like In the meantime, as a workaround, you can use the vanilla command to summon a TNT entity.
Sorry for the inconvenience! |
Describe the bug
After configuring the mod on a 1.18.2 server, when an event like Twitch Follow plays, it returns two messages in the chat that say "Unknown command".
To Reproduce
Steps to reproduce the behavior:
Join a server 1.18.2 with TwitchSpawn inside the folder "mods" of the server and client.
Place a EXECUTE rule for Twitch Follow:
EXECUTE %/tnt 1 0.1 4 (replace with mc username)%
ON Twitch Follow
See error
Expected behavior
I suspect that it is because the commands must be entered in the console without / and the mod requires placing the /, therefore it is executed:
//tnt...
Version (please complete the following information):
The text was updated successfully, but these errors were encountered: