MC-65168Crash reports in 31a show that the server is non-integrated when its clearly not
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
From MC-64076
Server brand: vanilla Server type: Integrated singleplayer server
What actually happened was that a crash report showed something like this:
From MC-64024
Server brand: vanilla Server type: Non-integrated multiplayer server
Steps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.
Created Issue:
Crash reports in 31a show that the server is modified when its clearly not
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
Server brand: vanilla Server type: Integrated singleplayer serverWhat actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverSteps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.Environment
N/A
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
Server brand: vanilla Server type: Integrated singleplayer serverFrom
MC-64076What actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverSteps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
Server brand: vanilla Server type: Integrated singleplayer serverFrom
MC-64076What actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverFrom
MC-64024Steps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
Server brand: vanilla Server type: Integrated singleplayer serverFrom
MC-64076What actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverFrom
MC-64024Steps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
From
MC-64076Server brand: vanilla Server type: Integrated singleplayer serverWhat actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverFrom
MC-64024Steps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.
Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
From
MC-64076Server brand: vanilla Server type: Integrated singleplayer serverWhat actually happened was that a crash report showed something like this:
Server brand: vanilla Server type: Non-integrated multiplayer serverFrom
MC-64024Steps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.Note that although I technically can't show you a crash report from me at the moment (computer currently being repaired), I have an example from a 30c crash, and a 31a crash.
What "I" expected to happen was for the crash report to show something like this:
From
MC-64076Server brand: vanilla Server type: Integrated singleplayer serverWhat actually happened was that a crash report showed something like this:
From
MC-64024Server brand: vanilla Server type: Non-integrated multiplayer serverSteps To Reproduce:
1. Start a server using the 31a jar
2. Connect to the server
3. Manually perform a force crash by holding down F3+C or FN+F3+C for 10 seconds while on said server.
Crash reports in 31a show that the server ismodified when its clearly notCrash reports in 31a show that the server is non-integrated when its clearly not
N/A
But there is no sign of being modded (tested for 14w31a right now):
Modded looks like this:
Server brand: CraftBukkit Server type: Non-integrated multiplayer serverLog of
MC-64024shows that it's a multiplayer session: