-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Sponge command still throws error #1954
Comments
Logs? Other information? This bug is near to useless. I don't know what error you're on about. This is the current error which is correct. I just tested it on a freshly downloaded SF 3221 myself and this is what I get. If you're not getting this, then I need more information, logs, commands written, etc. If you are getting this, this is the expected behaviour (as it stands). |
Uh, what is there to log?
Isn't the issue clear enough? I do not get the output that you get. This didn't happen on SpongeForge: 1.12.2-2705-7.1.0-BETA-3204 I notice it first on spongeforge-1.12.2-2705-7.1.0-BETA-3218.jar as well as others There was a "fix" of some kind for 3221 but I don't see any effect thus I reported again. |
this is unrelated to #1953 - sponge did not even load on your server, which is why the command doesnt work for you |
Are you sure? |
just because it found the jar doesn't mean it loaded successfully, if you read the log you will see that it errored after trying to load a mixin, and didn't output any further than that. |
I thought that belong to LagGoggle. Sponge complained that it needed mixin 0.7.10 and found 0.7.5 |
Indeed, removing LagGoggles allowed Sponge to load so it must be the conflicting Mixin that was included in LagGoggles? |
yes - this is probably an issue for LagGoggles, not SpongeForge |
Yes, this is nothing to do with #1953, this is why we ask for logs. Closing as this is nothing to do with Sponge. |
I am currently running
Issue Description
/sponge command and all its subcommand still missing and throwing error
#1953
The text was updated successfully, but these errors were encountered: