Here is a interesting freeze issue. I've been gone for a little while and last night I updated minecraft. Now the game freezes after just a few minutes. i've deleted the cache and then I deleted the game itself. Reloaded everything and tried it again. This time I could play for a little while but now all of a sudden it has started it again. Not sure what the problem is. I even deleted all the old saves and started fresh. Any suggestions?
Try running it from a USB stick and see if this corrects the issue
the squids have to stop swimming through my house there are no doors and there is now water leaking in you have to swim down to the house then under and up they are coming in though all the glass walls and ceiling
I know the following does not seem to be fixed at least for older maps some how they are able to use this to troll still
Fix for a crash with pistons at the edge of the world
I found out about the following one when I went in and played on my sons game and changed his persons skin to default and he got pissed off and he said it took time to get that skin because that comes from the DLC and not form the Free one!!
Fix for bug allowing locked skins to be selected if they are beside a free skin
My Son is still able with allot of work to select skins that at in the pay skins some how. I did not buy these for him. I do have the skins on my Xbox his account is not on my Xbox. So how does he do this. He said his friends show him how.
Anyone know of any update for the server reset glitch where it sends everyone back to the spawn? The last update didn't fix it and I haven't heard of them announcing any plans to fix it in the future. It really does get old. This is bogging down my server extremely bad and I know mine can't be the only one that this is happening to.
Rollback Post to RevisionRollBack
"When you play the game of thrones, you win or you die."
Anyone know of any update for the server reset glitch where it sends everyone back to the spawn? The last update didn't fix it and I haven't heard of them announcing any plans to fix it in the future. It really does get old. This is bogging down my server extremely bad and I know mine can't be the only one that this is happening to.
If I remember correctly, they were still trying to figure out exactly what is causing this problem.
Rollback Post to RevisionRollBack
“We do not quit playing because we grow old; we grow old because we quit playing.”- Oliver Wendell Holmes
I have seen this before on a post. Someone had replied to the post and said that if you put a block by the water and then mine the block, that the water will behave normally.
if thats true then it is exactly what i said, it was generated like this with the source block there, because world generated sand wont fall untill you cause one to fall by mining near it/under it. causing it to update.
Rollback Post to RevisionRollBack
We avoid risks in life in order to make it safely to our deaths.
I'm putting this up because it might be related to the respawning issue [S-01 on list]. I started a new seed this morning and my original spawn point was in the very upper left corner of the map. I started to play around (offline, single player) and immediately experienced blocks reappearing after mining them. In particular, one piece of tall grass kept reappearing, but not in the same precise spot I mined it from. It would reappear on an adjacent block of grass. Also, it's appearance was much, much darker in color than the other tall grass immediately around it. I moved on and a short distance from that spot, I saw and cliff of dirt where three blocks were much, much darker than the other blocks beside it. I mined a adjacent block and all three of the others also disappeared.
At that point, I decided to exit the game without saving and start over to get rid of the lag. I re-entered the world without regenerating another new one and expected to respawn in approximately the same point on the map as I did originally. However, I have respawned kilometers from that first spawn point. I'm currently working my way back to the first spawn point, just to see whether the world is even the same now. I'll add the results to the bottom of this post.
ETA: Yep, same world. The big oak tree I originally spawned in is even still there (The first time into the world, I had chopped it down from the top in order to get to collect the wood and get to the ground at the same time). I just can't be certain where between the two places my actual original spawn point is.
ETA: World is still lagging though. I'm spotting lots of obvious rendering errors (much darker blocks not caused by shadows).
ETA: Third time entering this same world... and yet another completely different spawn point. This time I'm down in a cave... no wood, no axe, no dirt, no choice but to exit without saving yet again.
ETA: Just my luck, this world now really likes this spawning me in a cave idea... I'm deleting it now.
Not sure if it's a glith or not, When leaving the nether, instead of coming back through the same portal a new portal is made near original spawn point and you come back through there. annoying because I am so far away from there but good since i am getting risk free obsidian
Bug:Block doesn't get mined
Cause- If the players can not reach a block up in the air and places any slab and stands on it and tries to mine it it will just respawn 2secs later.
You have to use full blocks to reach it and mine completely.
Bug:Block doesn't get mined
Cause- If the players can not reach a block up in the air and places any slab and stands on it and tries to mine it it will just respawn 2secs later.
You have to use full blocks to reach it and mine completely.
Nice theory and it may work some of the time, but blocks have reappeared for me even after mining them while standing on the original ground (dirt) block from only 1 block away. Eg. Just recently I mined a piece of tall grass while standing walking exploring a newly created world. It immediately reappeared as tall grass (see my previous post on this thread). The only difference was that the block appeared darker than the other tall grass nearby. I mined it again and it reappeared again in the same spot. I mined it again, a darkened piece of tall grass appeared, but this time on an adjacent block. I tried a couple more times then moved on out of that area. I later encountered two pieces of stone that appeared quite a bit darker than there adjacent counterparts. I mined one. Both originally disappeared, but then the one I had mined reappeared. I then exited that world without saving and re-entered it. I spawned in a completely different place than I had spawned the first time. I exited again and respawned in yet another completely different place. I exited again and finally respawned in, I think, the same place twice (but it was in a cave with no wood or dirt to handy to even get started and I didn't feel like fighting it anymore). I exited and deleted that world... started another and the issues stopped for that session at least.
Coming back to the discussion about lava causing fire through walls, I have discovered that it is indeed not a bug, but actually how the code works, and is the same way in the PC version. See this thread for more information. (Also covers fire, like from burning Netherrack).
Rollback Post to RevisionRollBack
“We do not quit playing because we grow old; we grow old because we quit playing.”- Oliver Wendell Holmes
sometimes when I'm crouching over lava, I'll catch on fire. This doesn't happen on the pc version (Nor did it in 1.7.3 to my knowledge) so I'm assuming it's a bug.
In my world, I suddenly got a glitch where none of my redstone torch powered items are working properly when a pulse is sent to turn the torch off, it stays off so all my doors, piston or otherwise are stuck in the off position and will not close after opening. I tore the system apart and rebuilt and this does not fix it.
When I was playing minecraft and the auto save started all the text and the progress bar has vanished and I was left with the panorama background and had to restart my xbox. I have had minecraft since it was released on xbox and this has happened twice.
The game did save, I had to restart the xbox though...
I, too, have had this happen a couple of times. Very annoying.
Rollback Post to RevisionRollBack
“We do not quit playing because we grow old; we grow old because we quit playing.”- Oliver Wendell Holmes
If its a dead torch issue, clear your Xbox cache, this removes the cached chunks, thus fixing the dead torch issue, I have to do it the odd occasion pain in the ass :@
Then restart Minecraft: Xbox 369 Edition and re-install the updates.
Coming back to the discussion about lava causing fire through walls, I have discovered that it is indeed not a bug, but actually how the code works, and is the same way in the PC version. See this thread for more information. (Also covers fire, like from burning Netherrack).
I'm still mulling this one over. What the poster describes is a lava block that is completely surrounded by nonflammable blocks (i.e. no air blocks immediately adjacent to the lava, top bottom or to the sides) and then a sign placed on the outside of one of those insulating blocks which then catches fire and burns. The article claims that lava completely encased in nonflammable blocks will not set wood on fire that is placed right next to the flammable block; but it must be that the block with the sign is considered to be an air block and, therefore, would be subject to being converted into a fire block at any time by, at least a fire block within two or three blocks (?) of the fire block. However, the lava block is not itself a fire block, so the question is at what distance without an adjacent air block can lava convert an air block to a fire block. Is it a farther distance that its ability to burn a flammable solid block? If that is the case, then I believe a person could start on fire by standing up to 3 blocks away from a lava source on the other side of a 1 block solid wall, since the lava could convert the first encountered air block to a fire block and that fire block could ignite a player on the adjacent block. Theoretically then, a mining player could ignite even before they expose lava in their path. Has this ever happened to anyone?
Just to derail the thread, I made a few new worlds last night and the recent patch has successfully dealt with whatever caused the frame rate smash as you entered new areas for the first time.
Was there a fix just for new worlds? I still get some lag on my first world.
Bug:Block doesn't get mined
Cause- If the players can not reach a block up in the air and places any slab and stands on it and tries to mine it it will just respawn 2secs later.
You have to use full blocks to reach it and mine completely.
I've been getting this lately as well. Blocks sometimes will place and disappear and return to your inventory sometimes too if you're standing too close to the spot where you're laying it.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Try running it from a USB stick and see if this corrects the issue
Project Aztec Server Stats: Rage Quits - 132 Deaths - 311 Survivors - 13, 11:36
Project Aztec Server Stats: Rage Quits - 132 Deaths - 311 Survivors - 13, 11:36
Fix for a crash with pistons at the edge of the world
I found out about the following one when I went in and played on my sons game and changed his persons skin to default and he got pissed off and he said it took time to get that skin because that comes from the DLC and not form the Free one!!
Fix for bug allowing locked skins to be selected if they are beside a free skin
My Son is still able with allot of work to select skins that at in the pay skins some how. I did not buy these for him. I do have the skins on my Xbox his account is not on my Xbox. So how does he do this. He said his friends show him how.
Project Aztec Server Stats: Rage Quits - 132 Deaths - 311 Survivors - 13, 11:36
If I remember correctly, they were still trying to figure out exactly what is causing this problem.
if thats true then it is exactly what i said, it was generated like this with the source block there, because world generated sand wont fall untill you cause one to fall by mining near it/under it. causing it to update.
At that point, I decided to exit the game without saving and start over to get rid of the lag. I re-entered the world without regenerating another new one and expected to respawn in approximately the same point on the map as I did originally. However, I have respawned kilometers from that first spawn point. I'm currently working my way back to the first spawn point, just to see whether the world is even the same now. I'll add the results to the bottom of this post.
ETA: Yep, same world. The big oak tree I originally spawned in is even still there (The first time into the world, I had chopped it down from the top in order to get to collect the wood and get to the ground at the same time). I just can't be certain where between the two places my actual original spawn point is.
ETA: World is still lagging though. I'm spotting lots of obvious rendering errors (much darker blocks not caused by shadows).
ETA: Third time entering this same world... and yet another completely different spawn point. This time I'm down in a cave... no wood, no axe, no dirt, no choice but to exit without saving yet again.
ETA: Just my luck, this world now really likes this spawning me in a cave idea... I'm deleting it now.
Cause- If the players can not reach a block up in the air and places any slab and stands on it and tries to mine it it will just respawn 2secs later.
You have to use full blocks to reach it and mine completely.
I typed does not but then I forget to delete the rest of the not part when I decided to type Dones't
Nice theory and it may work some of the time, but blocks have reappeared for me even after mining them while standing on the original ground (dirt) block from only 1 block away. Eg. Just recently I mined a piece of tall grass while standing walking exploring a newly created world. It immediately reappeared as tall grass (see my previous post on this thread). The only difference was that the block appeared darker than the other tall grass nearby. I mined it again and it reappeared again in the same spot. I mined it again, a darkened piece of tall grass appeared, but this time on an adjacent block. I tried a couple more times then moved on out of that area. I later encountered two pieces of stone that appeared quite a bit darker than there adjacent counterparts. I mined one. Both originally disappeared, but then the one I had mined reappeared. I then exited that world without saving and re-entered it. I spawned in a completely different place than I had spawned the first time. I exited again and respawned in yet another completely different place. I exited again and finally respawned in, I think, the same place twice (but it was in a cave with no wood or dirt to handy to even get started and I didn't feel like fighting it anymore). I exited and deleted that world... started another and the issues stopped for that session at least.
I, too, have had this happen a couple of times. Very annoying.
Then restart Minecraft: Xbox 369 Edition and re-install the updates.
I'm still mulling this one over. What the poster describes is a lava block that is completely surrounded by nonflammable blocks (i.e. no air blocks immediately adjacent to the lava, top bottom or to the sides) and then a sign placed on the outside of one of those insulating blocks which then catches fire and burns. The article claims that lava completely encased in nonflammable blocks will not set wood on fire that is placed right next to the flammable block; but it must be that the block with the sign is considered to be an air block and, therefore, would be subject to being converted into a fire block at any time by, at least a fire block within two or three blocks (?) of the fire block. However, the lava block is not itself a fire block, so the question is at what distance without an adjacent air block can lava convert an air block to a fire block. Is it a farther distance that its ability to burn a flammable solid block? If that is the case, then I believe a person could start on fire by standing up to 3 blocks away from a lava source on the other side of a 1 block solid wall, since the lava could convert the first encountered air block to a fire block and that fire block could ignite a player on the adjacent block. Theoretically then, a mining player could ignite even before they expose lava in their path. Has this ever happened to anyone?
Was there a fix just for new worlds? I still get some lag on my first world.
I've been getting this lately as well. Blocks sometimes will place and disappear and return to your inventory sometimes too if you're standing too close to the spot where you're laying it.