I don't think I'm actually that bothered to complain about Minecraft. I like it the way it is...to me, it doesn't need updates - they're just a plus. Everyone cares about the new updates, I don't really. It's just an addition to an already awesome game!
Well said. However, if Mojang tells us they're going to make a new update, but take a year to do it, then it is disappointing. Some people want updates that will completely change Minecraft. Not me.
Really, I don't think that 1.8 wasn't that bad, but definitely not my favorite. I was disappointed by the wait time and the minimal amount of features that it added. However, all of the engine rewrites were good. The bulk of the update is in the commands, which is really good for people working with command blocks. It's basically turned into an in-game API. There were tons of glitches, which is a given with big updates. 1.8.1 took care of a lot of them. I do agree that Mojang needs to step it up and get updates out faster.
So... a lag spike for whatever reason would cause you to get booted as well? It is impossible to tell, from a computer's standpoint, what is exactly causing the lag spike, so any FPS drop would trigger the boot. This sounds very flawed.
And if you are joining a server where somone is blowing up THAT much TNT, that is probably a bad server to begin with.
Yes, a lag spike could kick you off the server, but you still wouldn't be able to play if you were encountering a lag spike. It's up to the admins to decide where the FPS threshold may be, different levels may work better than others. This isn't just for TNT, it's to stop game crashes. Now that I realize it, you may only crash if you have 1 or 2 FPS, so I'll change the suggestion to fit that.
There's no reason to make a chunk 40 blocks tall; it's currently already a power of 2 so making it not a power of 2 would just complicate things. Also, making the horizontal dimensions 32 blocks would mean you'd need to combine existing chunks in groups of 4, unlike the 16x16x16 system.
I'm probably the wrong person to be trying to explain this stuff, if anyone could explain this better than I could that would be nice.
Ah, now I see. I was trying to make the world generation faster by only having to load a few chunks at a time. However, the world conversion wouldn't work with that.
Have you ever gone on a server only to find out that some idiot is blowing up a bunch of TNT right beside you? Have you gotten a crash because of this? Well, I have a solution.
The server should kick people off if they go below a set frames per second (FPS) threshold. If you experience a lot of lag on the server due to stuff blowing up or some command block contraption gone wrong, then it will kick you before you can crash. The FPS threshold can be customized in the server.properties file, but it will not let you set it above 5 FPS because of the possible abuse. 1 FPS is probably the best option.
Why should this be added? To make sure that your Minecraft or even your computer doesn't crash by trying to kick you off before it can happen.
Do you like this idea or not? Vote above and comment below!
I really like this suggestion. You explained it well and showed us why it wouldn't lag. However, I think that the chunk size should be 32X40X32. Why? The chunks at the bottom, Y=1-40, would only load if you were in a cave. The chunks from Y=41-80 would only load if you were above ground. I did the math, and 32X32X32 chunks would make the chunk loading 4 times faster, while 32X40X32 chunks would be 6.4 times faster. I calculated this by determining how many blocks needed to be loaded in a specific area.
Nice mod. However, you should add something other than just ores, tools, and armor. For example, the ashstone charm, where if you sprint with it in your inventory, it will give you speed I and jump boost I. Additions like that would make the mod a little less "bland". You might want to consider my suggestion for your "Simple Ores" mod too.
Cool, I did not know about tags or variables since I never got that detailed into command blocks. I have another suggestion though:
/place <item ID> <amount> <stacked?> <inventory?> <coordinates>
Places the <item ID> with the amount of <amount> at the chest you are looking at, or if <inventory?> is true, it will place it in your inventory. <coordinates> will let you place the items in the chest at <coordinates>.
/remove <item ID> <amount> <stacked?> <inventory?> <coordinates>
Removes the <item ID> with the amount of <amount> at the chest you are looking at, or if <inventory?> is true, it will remove the item in your inventory. <coordinates> will let you remove the items in the chest at <coordinates>.
/fill <item ID> <inventory?> <coordinates>
This command will fill the chest you are looking at with that item, or at the coordinates <coordinates>, and if <inventory?> is true, then it will fill your inventory instead.
/empty <item ID> <inventory?> <coordinates>
This command will empty the chest you are looking at with that item, or at the coordinates <coordinates>, and if <inventory?> is true, then it will empty your inventory instead. If there is no item ID, then it will empty everything.
These commands are complete time-savers and can be used with command blocks for adventure maps, and many, many other uses.
/warp goto <name>
Teleports you to the warp <name>
/warp goto <name> <player>
Teleports <player> to the warp <name>
/warp set <name> <coordinates>
Sets a warp at <coordinates> named <name>
/warp sethere <name>
Sets a warp to your location named <name>
/warp delete <name>
Deletes the warp <name>
/warp list
Lists the warps
/warp limit <allow/deny> <player/all/op/commandblock>
Limits warps so that only <player/all/op/commandblock> are <allowed/denied> to use the warp.
This would be pretty cool for singleplayer, since you may have to fly all the way to one location, and it can be cleverly used with command blocks for cool adventure maps.
0
Amen to that. However, 1.8.1 fixed some of the mistakes (emphasis on some).
1
Well said. However, if Mojang tells us they're going to make a new update, but take a year to do it, then it is disappointing. Some people want updates that will completely change Minecraft. Not me.
0
0
0
Yes, a lag spike could kick you off the server, but you still wouldn't be able to play if you were encountering a lag spike. It's up to the admins to decide where the FPS threshold may be, different levels may work better than others. This isn't just for TNT, it's to stop game crashes. Now that I realize it, you may only crash if you have 1 or 2 FPS, so I'll change the suggestion to fit that.
0
No, that's not it. Like cheese said, the purpose of this is for you to not have to relaunch minecraft or be forced to Alt + F4.
0
Ah, now I see. I was trying to make the world generation faster by only having to load a few chunks at a time. However, the world conversion wouldn't work with that.
0
The server should kick people off if they go below a set frames per second (FPS) threshold. If you experience a lot of lag on the server due to stuff blowing up or some command block contraption gone wrong, then it will kick you before you can crash. The FPS threshold can be customized in the server.properties file, but it will not let you set it above 5 FPS because of the possible abuse. 1 FPS is probably the best option.
Why should this be added? To make sure that your Minecraft or even your computer doesn't crash by trying to kick you off before it can happen.
Do you like this idea or not? Vote above and comment below!
0
Hope this helped!
0
0
/place <item ID> <amount> <stacked?> <inventory?> <coordinates>
Places the <item ID> with the amount of <amount> at the chest you are looking at, or if <inventory?> is true, it will place it in your inventory. <coordinates> will let you place the items in the chest at <coordinates>.
/remove <item ID> <amount> <stacked?> <inventory?> <coordinates>
Removes the <item ID> with the amount of <amount> at the chest you are looking at, or if <inventory?> is true, it will remove the item in your inventory. <coordinates> will let you remove the items in the chest at <coordinates>.
/fill <item ID> <inventory?> <coordinates>
This command will fill the chest you are looking at with that item, or at the coordinates <coordinates>, and if <inventory?> is true, then it will fill your inventory instead.
/empty <item ID> <inventory?> <coordinates>
This command will empty the chest you are looking at with that item, or at the coordinates <coordinates>, and if <inventory?> is true, then it will empty your inventory instead. If there is no item ID, then it will empty everything.
These commands are complete time-savers and can be used with command blocks for adventure maps, and many, many other uses.
0
/warp goto <name>
Teleports you to the warp <name>
/warp goto <name> <player>
Teleports <player> to the warp <name>
/warp set <name> <coordinates>
Sets a warp at <coordinates> named <name>
/warp sethere <name>
Sets a warp to your location named <name>
/warp delete <name>
Deletes the warp <name>
/warp list
Lists the warps
/warp limit <allow/deny> <player/all/op/commandblock>
Limits warps so that only <player/all/op/commandblock> are <allowed/denied> to use the warp.
This would be pretty cool for singleplayer, since you may have to fly all the way to one location, and it can be cleverly used with command blocks for cool adventure maps.