i cant wait until the internal server error is fixed (and this)
Minecraft has crashed!
----------------------
Minecraft has stopped running because it encountered a problem; Exception in server tick loop
This error has been saved to C:\Users\Nathan\AppData\Roaming\.minecraft\crash-reports\crash-2012-08-04_08.28.48-server.txt for your convenience. Please include a copy of this file if you report this crash to anyone.
--- BEGIN ERROR REPORT dd7dab80 --------
Generated 8/4/12 8:28 AM
- Minecraft Version: 1.3.1
- Operating System: Windows 7 (x86) version 6.1
- Java Version: 1.6.0_25, Sun Microsystems Inc.
- Java VM Version: Java HotSpot™ Client VM (mixed mode), Sun Microsystems Inc.
- Memory: 374214672 bytes (356 MB) / 519110656 bytes (495 MB) up to 1037959168 bytes (989 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- Type: Integrated Server
- Is Modded: Unknown (can't tell)
- Profiler Position: N/A (disabled)
- Player Count: 1 / 8; [gt['superx76'/533, l='server', x=-1829.15, y=65.00, z=2196.15]]
- World server Entities: 0 total; []
- World server Players: 0 total; []
- World server Chunk Stats: ServerChunkCache: 0 Drop: 0
java.lang.NullPointerException
at yz.a(SourceFile:356)
at abg.a(SourceFile:29)
at abd.a(SourceFile:39)
at xm.a(SourceFile:424)
at gp.a(SourceFile:140)
at wk.a(SourceFile:704)
at gp.c(SourceFile:82)
at go.(SourceFile:26)
at gn.a(SourceFile:171)
at gn.a(SourceFile:202)
at et.a(SourceFile:103)
at et.c(SourceFile:138)
at et.a(SourceFile:80)
at axx.b(SourceFile:72)
at net.minecraft.server.MinecraftServer.q(SourceFile:452)
at net.minecraft.server.MinecraftServer.p(SourceFile:383)
at axu.p(SourceFile:111)
at net.minecraft.server.MinecraftServer.run(SourceFile:316)
at ep.run(SourceFile:539)
--- END ERROR REPORT a77ceddf ----------
Will it come out at all? I haven't heard anything about a 1.3.2. Granted, judging by the number of complaints around here we do need a patch to fix some stuff, but who can say if we'll get one.
We really need a fix for animals and water suffocating the player in blocks. It's probably the worst glitch I've seen in a release of this game since I started playing in late 1.8.
Rollback Post to RevisionRollBack
Under no circumstances do I want villagers building ugly little houses in my world. That's my job. Link Removed
We really need a fix for animals and water suffocating the player in blocks. It's probably the worst glitch I've seen in a release of this game since I started playing in late 1.8.
The problem has to do with the player colliding with the blocks. It is also what causes you to sometimes get stuck in blocks when using Nether portals, or in a worst case falling through the map and hitting the void. I lost a full set of diamond gear along with a full inventory of loot a few days ago due to that bug. It's pretty random, but it's a bad enough that I now place an enderchest on each side of a nether portal so I can stash my gear while I step through.. just in case.
i think there just gonna go threw the usual pre realeeses or snapshots into 1.4
That would be unacceptable. Some glitches are inexcusable. Giant patches of land not loaded, respawning in SSP gives you the SMP glitches (falling through the world, which forces you to wait or log in/out), etc. I heard there's one bug with the Nether portal that kills you if you're unlucky.
Fix the really annoying bugs. I'd say we have a right to that. Other little stuff, I can stand waiting.
Ok, so the forums work like this:
1. If Mojang won't release a update fast, they complain.
2.If Mojang releases a update with bugs, they complain.
YOU CAN'T HAVE BOTH
My point exactly.
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
This whole, "People need to stop complaining about bug fixes AND complaining it won't come out fast enough," thing needs to stop. Stop attributing these two different complaints to every person. Just because some guy bitched about the game not coming out fast enough doesn't mean when I ***** about bugs that I had done the same thing prior to the release. If you know for a fact that someone did this, go ahead and berate them, but it's overwhelmingly stupid when we start calling every single person who bitches either about the bugs or the release date a hypocrite. Shut it.
However, asking for an update to come fast and come powerful is equally if not more stupid.
----------------------
Minecraft has stopped running because it encountered a problem; Exception in server tick loop
This error has been saved to C:\Users\Nathan\AppData\Roaming\.minecraft\crash-reports\crash-2012-08-04_08.28.48-server.txt for your convenience. Please include a copy of this file if you report this crash to anyone.
--- BEGIN ERROR REPORT dd7dab80 --------
Generated 8/4/12 8:28 AM
- Minecraft Version: 1.3.1
- Operating System: Windows 7 (x86) version 6.1
- Java Version: 1.6.0_25, Sun Microsystems Inc.
- Java VM Version: Java HotSpot™ Client VM (mixed mode), Sun Microsystems Inc.
- Memory: 374214672 bytes (356 MB) / 519110656 bytes (495 MB) up to 1037959168 bytes (989 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- Type: Integrated Server
- Is Modded: Unknown (can't tell)
- Profiler Position: N/A (disabled)
- Player Count: 1 / 8; [gt['superx76'/533, l='server', x=-1829.15, y=65.00, z=2196.15]]
- World server Entities: 0 total; []
- World server Players: 0 total; []
- World server Chunk Stats: ServerChunkCache: 0 Drop: 0
java.lang.NullPointerException
at yz.a(SourceFile:356)
at abg.a(SourceFile:29)
at abd.a(SourceFile:39)
at xm.a(SourceFile:424)
at gp.a(SourceFile:140)
at wk.a(SourceFile:704)
at gp.c(SourceFile:82)
at go.(SourceFile:26)
at gn.a(SourceFile:171)
at gn.a(SourceFile:202)
at et.a(SourceFile:103)
at et.c(SourceFile:138)
at et.a(SourceFile:80)
at axx.b(SourceFile:72)
at net.minecraft.server.MinecraftServer.q(SourceFile:452)
at net.minecraft.server.MinecraftServer.p(SourceFile:383)
at axu.p(SourceFile:111)
at net.minecraft.server.MinecraftServer.run(SourceFile:316)
at ep.run(SourceFile:539)
--- END ERROR REPORT a77ceddf ----------
Link Removed
The problem has to do with the player colliding with the blocks. It is also what causes you to sometimes get stuck in blocks when using Nether portals, or in a worst case falling through the map and hitting the void. I lost a full set of diamond gear along with a full inventory of loot a few days ago due to that bug. It's pretty random, but it's a bad enough that I now place an enderchest on each side of a nether portal so I can stash my gear while I step through.. just in case.
That would be unacceptable. Some glitches are inexcusable. Giant patches of land not loaded, respawning in SSP gives you the SMP glitches (falling through the world, which forces you to wait or log in/out), etc. I heard there's one bug with the Nether portal that kills you if you're unlucky.
Fix the really annoying bugs. I'd say we have a right to that. Other little stuff, I can stand waiting.
I had that happen to me and i sweared to my my self that im never going to the Nether again
1. Everyone complains that mojang didn't spend enough time bug-fixing for 1.3.
2. Everyone want 1.4 to be bigger than 1.4 and take less time.
My point exactly.
However, asking for an update to come fast and come powerful is equally if not more stupid.