mojira.dev

Lance

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MCPE-223221 Vibrant visuals bug in caves Duplicate MCPE-96879 Ice bug Works As Intended MCPE-43811 Certain Entities Not Working On Realm (No Behavior?) Duplicate MCPE-40755 replaceitem for specific player replaces item for all players. Cannot Reproduce MCPE-40752 Command Block minecart despawn/disappear Duplicate MCPE-40601 Repeating Command Blocks randomly not working as intended. Cannot Reproduce MCL-9436 The game crashed whilst initializing game Error: java.lang.NullPointerException: Initializing game Duplicate MC-70612 I hit tab then game crashed. I was on a multiplayer server. Incomplete MC-50010 Item frames are no longer interactive after death. Duplicate MC-48141 Giants no longer attack players Duplicate MC-47698 stat.damageDealt increments a score by 10*damage Works As Intended

Comments

Unknown, when I try to play the downloaded map it says it was from a newer version of the game. My game is up to date.

This is a different issue, there is a whole section at my worldspawn that is not updating correctly... even doors on pressure plates stay wide open for long periods of time... What is happening??? It's like this area of my world is out of sync time wise with everything else.

It is still not working,this is hecrash-report

 


Minecraft Crash Report ----
// I blame Dinnerbone.

Time: 6/10/18 9:03 AM
Description: Initializing game

org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:247)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bib.at(SourceFile:635)
at bib.aq(SourceFile:458)
at bib.a(SourceFile:404)
at net.minecraft.client.main.Main.main(SourceFile:123)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Thread: Client thread
Stacktrace:
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:247)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bib.at(SourceFile:635)
at bib.aq(SourceFile:458)

– Initialization –
Details:
Stacktrace:
at bib.a(SourceFile:404)
at net.minecraft.client.main.Main.main(SourceFile:123)

– System Details –
Details:
Minecraft Version: 1.12.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 158958640 bytes (151 MB) / 234881024 bytes (224 MB) up to 1073741824 bytes (1024 MB)
JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.12.2
LWJGL: 2.9.4
OpenGL: ~ERROR~ RuntimeException: No OpenGL context found in the current thread.
GL Caps:
Using VBOs: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs:
Current Language: ~ERROR~ NullPointerException: null
Profiler Position: N/A (disabled)
CPU: <unknown>

I just found that critical hits can add 5 to stat.damageDealt.

I'm fairly certain this is intended.

I assumed that because a score below five seemed impossible that this stat was unintentionally 10*damageDealt rather than 1*damageDealt.

The best we can hope for is that it's been fixed for the next snapshot, I guess. :/