1.8 client crash (possible <1.13) #738
Comments
|
Nothing in that stacktrace even remotely hints at BTLP being the issue, so what makes you think that? |
Because I checked that and I'm 100% sure. Simply disabling the tablists allow users to join without crashing. Somewhere probably needs to be a string, not BaseComponent. Remember that it's client crash. |
|
That doesn't proof anything. This stacktrace doesn't make sense for a proxy, so I assume it's from your client logs? |
|
It is client crash. No errors on the proxy. I am 100% sure that it's BTLP's issue. |
|
Without any errors on proxy by btlp I doubt it is. Errors caused by plugins on a proxy usually also show errors. Please share your proxy's full latest.log through https://mclo.gs |
|
I already told you, if you still don't believe me, you can check that by yourself. Sending wrong data to the client will result in a client crash, not plugin side error. |
|
As long as you're not providing any data to work with (proxy type and build, client version, etc.) we can't and won't help. So, instead of excuses, just provide the logs I asked you for already. |
|
The latest bungeecord. The lastest BTLP. Have any tablist. Join with 1.8 and probably any version below 1.13. You get the crash. If you need more, check that by yourself, I assured you more than 3 times. No errors on the proxy, I gave you crash from the client. |
|
And I told you 3 times now to give the logs of the proxy because client logs do absolutely nothing for us. Also, make sure to join with latest 1.8 (1.8.9 iirc) since there were major changes between it and older 1.8 versions. |
|
I told you what happens, I told you because of what, I already gave you everything that you wanted. I can't wait for the fix so I can update BTLP and bungee again. 🚀 |
|
You didn't give everything I asked for... I write it a final time and in caps so you hopefully get it: BTLP is a plugin, so we needs proxy logs for info. Like in all honesty, stop acting like you know what we need here. |
|
I don't have interest in talking with an disrespectful ignorant. I told you everything, if you want more you can download and test it. |
Ironic that this comes from someone refusing to do what is a literal copy-paste job here. |
|
That's great, but you literally have everything that you wanted. |
|
Someone close this dumb report. |
Very intelligent creature we have here. Let's find you a reward for this awesome achievement, but let's summarize you. |
More incoherent rambling that once again provides no proxy logs, and no server side logs. |
No point in discussing with you if you can't even read, greetings. |
|
I can assure you, your issue will never be solved without:
Zero effort will always equal zero help, thus this issue will certainly go unnoticed for months to come. I shall take my leave, farewell. :) |
Great, till the time you will learn how to read this issue will be fixed, you can go waste your useless energy somewhere else. |
Yet, you haven't provided any real info related to the proxy itself. And so far you only mentioned 1.8 clients, so your I've asked you several times to provide the full logs of your BungeeCord proxy, yet you constantly avoid it like the plague, which makes me believe you don't even have access to the proxy in question to proof you have issues there, otherwise why not give the logs as requested? And no, your client-side logs are not any proof of this being a BTLP issue, as any other plugin sending bad packets could be the issue... Or client mods... or the actual backend server itself. Finally, you constantly say 1.8... And if you actually mean 1.8 and not 1.8.9 or similar, then please use the latest 1.8 version (1.8.9) for your client as there were changes between the versions that make clients incompatible with latest proxy versions.
I doubt that you're any older than them. If anything your mental age is that of a kid who doesn't want to do what an actual adult askes them to do. You constantly try to push your views here and when people won't budge you block.
I constantly asked to give the full logs of your proxy, not just what YOU think is relevant.
It certainly is not, or else the OP of the issue would've said "This issue still exists, but now different", but they say it's fixed for them, so this is a unrelated issue.
No. This is not a product you buy and expect a dedicated team behind to work on. Also, to now cover your "Just download and test it".
All for testing this?
Looking at this, I feel like the things you should do would have a lot less work than what I should do what is most likely a bug you caused on your end... |
Here is everything is needed. I'm not going to discuss anything else. If you don't believe that it is different than what I described, you can check by yourself and I will give you my honour. |
|
At this point the best thing to do would be for Mr. CodeCrafter to go to this user's profile and press "block user". They will no longer be able to comment or open any new issues. |
|
You really think there is something more needed in this issue or you are just trolling? |
The irony of that comment is beautiful |
Ok, you don't need to answer anything more :D There is second possibility, but I don't want to spam and insult you. You literally have everything that you wanted, everything that is possible, if you think otherwise I don't want to discuss and convince you. |
|
Resolved by PR #741 - @andreasdc I would suggest closing this issue and waiting for the PR to be merged from Issue #739 which contains the info required to resolve the bug. |
The latest version crashes 1.8 client and I guess all below 1.13
[12:05:37] [Client thread/FATAL]: Unreported exception thrown!
java.lang.NullPointerException: Cannot invoke "a.b()" because the return value of "aul.l()" is null
at avo.a(SourceFile:276) ~[minecraft-1.8.8-client.jar:?]
at bfk.a(SourceFile:1021) ~[minecraft-1.8.8-client.jar:?]
at ave.av(SourceFile:915) ~[minecraft-1.8.8-client.jar:?]
at ave.a(SourceFile:325) [minecraft-1.8.8-client.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [minecraft-1.8.8-client.jar:?]
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[?:?]
at java.base/java.lang.reflect.Method.invoke(Method.java:578) ~[?:?]
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:243) [NewLaunch.jar:?]
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:278) [NewLaunch.jar:?]
at org.multimc.EntryPoint.listen(EntryPoint.java:143) [NewLaunch.jar:?]
at org.multimc.EntryPoint.main(EntryPoint.java:34) [NewLaunch.jar:?]
The text was updated successfully, but these errors were encountered: