search

WaterfallMC / Waterfall-Old

[UNMAINTAINED] Waterfall prior to becoming patch-based, see the project website at
https://papermc.io
Other
35 stars 12 forks source link

Error when joining disabled server #59

Open ghost opened 8 years ago

ghost commented 8 years ago

Hi, when I try to join to a disabled default server it shows me this error ( https://scr.hu/mBR3M1 )instead of normal message which was set in the messages.properties.

ghost commented 8 years ago

Can someone fix this?

Janmm14 commented 8 years ago

This looks like a client issue with forge or similar. Please report client version, error (stack trace) in the clients log files (alternatively put launcher to stay open to see the clients console), waterfall version, backend server version.

ghost commented 8 years ago

It's impossible, BungeeCord doesn't habe this error.

Janmm14 commented 8 years ago

Still the error includes net.minecraft.client - the error is just client-side.

ghost commented 8 years ago

Why is it happening? It doesn't happen with BungeeCord.

Janmm14 commented 8 years ago

Still you should provide the information I mentioned as otherwise you can close this because we can't find out "Why is it happening?" otherwise.

ghost commented 8 years ago

I think it is happening on every 1.7 version,

"This server is running Waterfall version git:Waterfall-Bootstrap:1.9-SNAPSHOT:ba75eaa:192 by the Waterfall team"

Janmm14 commented 8 years ago

Please report client version, error (stack trace) in the clients log files (alternatively put launcher to stay open to see the clients console), waterfall version, backend server version.

Techcable commented 8 years ago

What is the client log?

ghost commented 8 years ago

There is nothing.

Techcable commented 8 years ago

There is always something in the client log.

ghost commented 8 years ago

Why you can't check it?

UnfixableExploit commented 8 years ago

... need the client log to check it :/

ghost commented 8 years ago

How to check logs?

Janmm14 commented 8 years ago

Google google can help my friend. Check .minecraft folder.

ghost commented 8 years ago

There's nothing in logs. CHECK IT

Techcable commented 8 years ago

Here is a snippet of my latest client log, available in /home/nicholas/.minecraft/logs/latest.log

[16:44:13] [Client thread/INFO]: Setting user: Techcable
[16:44:21] [Client thread/INFO]: LWJGL Version: 2.9.4
[16:44:24] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge
[16:44:25] [Sound Library Loader/INFO]: Starting up SoundSystem...
[16:44:25] [Thread-8/INFO]: Initializing LWJGL OpenAL
[16:44:25] [Thread-8/INFO]: (The LWJGL binding of OpenAL.  For more information, see http://www.lwjgl.org)
[16:44:25] [Thread-8/INFO]: OpenAL initialized.
[16:44:26] [Sound Library Loader/INFO]: Sound engine started
[16:44:28] [Client thread/INFO]: Created: 16x16 textures-atlas
[16:44:30] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge

If there is nothing in your client logs then your client is seriously bugged.

ghost commented 8 years ago

@Techcable Error on 1.7.10 version: https://scr.hu/7zKyjY Error on 1.7.6 (or 1.7.2) version: https://scr.hu/ZR1Pq2 In the latest.log file there is just [Client thread/INFO]: Connecting to [ip], [port]

Techcable commented 8 years ago

@CzlowiekKuktas I need the entire log file pastebinned. Thanks for cooperating though :)

ghost commented 8 years ago

@Techcable As it shows just the connecting information. You can check it by yourself.

phase commented 8 years ago

@CzlowiekKuktas Multiple instances of the same error usually help when debugging, as it can narrow down the exact cause of the issue.

Techcable commented 8 years ago

Plus the stacktrace....... and prior information messages.