I can confirm this, I really hope this will be fixed before the weekend, I really want to have fun with the new features this weekend.
Edit : I fixed the issue by removing the item frames for now we didn't use a lot of them in our current world so I don't think they will be missed till they fix this issue, I went back to 14w11b on my world and removed all of the item frames, then switched the server back to the new 14w18a and have no problems to report beside a lot of light bugs on the stairs and half slabs.
I can relate to this issue also, I've lost so many horses because of this bug, now I place a chest next to them and I always deposit the horse armor and saddle, already lost 4 saddle and 4 iron horse armors. I've built a Stable for them but they still vanish, even 2 with nametags, like if they were deleted by the game.
You can temporary fix this issue by extracting the redstone textures from the 14w17a or 14w18a.jar located in the .minecraft/versions folder, I did it myself because I can't stand to play with 16x default textures, I love the Faithful32x a lot more, I simply copied the redstone textures for the line and cross + the overlay of the .jar and it works #1 Redstonefix14w18a.png
Just to be clear, it will never ever be fixed, its the new way the blocks and items are coded and it won't change anytime soon for really good reasons, so don't expect mojang to correct this, the work must be done by the ressource pack teams instead.
And for Lukas Fischer, the link is to a picture, not a website, can't understand why I can't link to pictures here.
This is what files you need to copy to any ressource pack/Texture pack to fix this issue, it will get you the default textures for the redstone, but at least it works with any texture pack you may have at the moment.
Please god, don't tell me that bug isn't corrected, I need a working slimefarm quickly, the swamplands are empty at night except if its a full moon, I'm doomed. BTW : I use MC1.8 PR 3 at the moment, will check if a slimefarm work or not quickly its my project for tonight since I need slimeballs for all my sticky pistons for my projects.
Got the same damn problem since I've started playing on the 1.8Pr1 then 2 and 3, I had this problem before in 1.7.10 modded also but it only happened around 1-2 times each month, I had plenty of servers since version 1.2.5, we never ever changed the server computer is the same as before, ISP speed is still the same (Fiber 50mbps/50mbps fully tested with a ping of 8ms) Its starting to really be annoying, can't believe they did something that cause that problem and never fixed it since before the 1.7 release, it was actually in the snapshots of the 1.7, weird thing is we had a server in the snapshots of the 1.7 and also one in most of the snapshots of the 1.8 (we stopped at 14w21b to play modded 1.7.10 for awhile without any problems at all) and I've seen that error a couple of times in the past but it was actually happening 1-2 times by month I would say, now it happens every 15-30 minutes most of the time. I just got killed by a zombie (my ghost player, not me, but once I've disconnected and connected, I was dead) because of this bug, thankfully we're not in the Nether yet, I would have deleted the whole server thing if I've lost all my valuables in lava in the Nether because of a bug like this, I'm not the kind to rage quit when I die usually, but if it happens because of this, I don't know what I would do.
And for thoses that would say its my ISP (the server is at my brother house, around 10-15km from my own place), look here : [URL=http://www.speedtest.net/my-result/3723195403][IMG]http://www.speedtest.net/result/3723195403.png[/IMG][/URL]
Now its not fixed in the official 1.8 and its getting on my nerves so much, can't go in the Nether, can't go cave mining, can't do anything were I could die because of this stupid bug, please fix it, its not on my server fault, not on my ISP either, you screwed up something and now I can't enjoy the game in survival mode without worrying because I neve know when this bug will kick me out of the server, hell yesterday I was just cooking stuff in my furnace without moving for more than 20 minutes, there's no entity near my cooking base, then I got kicked out again with this stupid error. I guess complaining here is useless but I never know.
Good luck to receive any support, Mojang doesn't even take a look at theses bug reports, I'm quite sure they screwed something really badly and don't want to go back to to rewrite the part that got screwed up.
I'm in the same boat since starting my server in 1.8, computer for the server isn't bad for a 2 players only we settled up in this :
ASUS P5K-E
Core2Quad Q6600 2.4GHZ
8GB DDR2 800
128GB Adata SSD drive
Windows 7 Ultimate 64 bits
We've played on a heavy modded 1.6.4 server (140 mods loaded) with this beast without any lags or any kind of problems with 3 players online
Now we couldn't even run a basic vanilla 1.8 server, this can't be true.
The only task running on this machine is the Minecraft server Official 1.8 release
computer is up to date, got both latest versions of java (32 and 64 bits version) made sure the server used the latest one by cleaning up all the older versions of it also.
Since bukkit and spigot are now dead (google is your friend, you'll learn all the bad news quickly), I don't think we're going to see any kind of bug fixing like that Io.netty error anytime soon, Mojang needs to develop an alternative to bukkit or spigot ASAP, the life of all the Minecraft servers is the key so I think we're going to wait for awhile before they even think about fixing any kind of bugs.
Ben Campbell, you didn't read all the comments I've made, read my server specs description, read the ISP I have, on both the server and the client they are ones of the best we could have, and even my brother got the problem while at his home, the server is in his bedroom and he has a wired connection between the router and the server is also wired to the router to avoid wireless problems. Both our machines are more than able to handle Minecraft, we had a heavy modded 1.6.4 server based on FTB plus a bunch of extra mods, and never ever experienced any problems, even with an overload of logistic pipes and such. And now the same server couldn't handle a vanilla Minecraft 1.8, this might be an error message, but I've only seen it 1-2 times and only since Minecraft 1.7.X serie, and since I've upgraded to 1.8, I keep getting it, this is ridiculously annoying, they can fix this one I'm 100% sure, but they are busy with something else and don't really care about bug reports.
The base 1.8 vanilla server had 2GB set for the vanilla 1.8, I bumped it to 3GB for now, just to clarify 1 thing, the map was created in the first 1.8 Pre-Release (the PR1) we had a map before in the 1.8 snapshots but we stopped playing it around 14W21B and played a lot on a modded 1.7.10 and that is when the error happened 2-3 times max in more than 2 months of playing. Now we decided to create a brand new map in the 1.8 and since we couldn't wait for the release, we choose to start it in the pre-release which is normally not a problem at all. I don't think corrupted chunks could be the problem since I didn't experience this problem for 2 days in a row, but now that I'm building a fully automatic xp mob spawner, I'm getting worried that I could have problems when there's a lot of mobs in the spawner. Server has 8GB installed and working (64 bits OS) and I did a bunch of ram tests to make sure the ram wasn't a problem, the test passed 100% for 2 nights in a row, so I think the ram is out of the problem. I'm suspecting there's a problem with the entity and the way server does prioritize entities instead of the players, this might be what they need to fix.
Guess what, since now we know it does also happen on realms which clearly rules out any problems that would be linked to Internet or the specs of our servers, I'm more than certain they will solve it for the Realms really quickly, they care about their paying customers but won't care at all about the other users.
So that means for now, all XP farms (mine is a standard skeleton one, if I get more than 40-50 skeleton waiting, I get kicked out with that damn Io.netty error (tested on my secondary machine wired to a simple switch to rule out ISP or router problems), got the same build in a 1.7.10 test server I have right here on my secondary machine too, I get 160 mobs waiting for me and absolutely no problems except really low FPS of course) and that's not even counting the 60-70 cows that are on top of the spawner in that world, so now all villager breeders and all contraptions with a lot of mobs in them are now officially impossible to build because of this bug, if they can't fix it, I'm quitting Minecraft, I love to build crazy mob farms, villager markets and such, if I can't do it anymore, what is the point of playing this game.
How would you explain that the same exact build never ever caused any problems in a 1.7.10 server and now I get kicked out with the same thing in 1.8
Yup Server tick time is probably the culprit here, I've examinated my server.properties files closely and I didn't have it on my 14w21b and also not in my 1.7.10 server, I've seen on a topic that disabling it could solve this issue so put it to -1 and it should be disabled, trying it myself, will report back if it works.
Can confirm that disabling the watch dog doesn't solve the problem totally, and its sure to be related to entities somehow, I now have a spider string farm and I get disconnected because of the spider jockey didn't get killed by the system (I will take care of this now that I know it can cause problems but that is another urrelated story)
I've never ever touched to the view distance in my server.properties file, I did it once while playing modded and settled it to 5 and the map wasn't complete on FTB so I switched it back to 10, I didn't see any improvments from touching this.
I'm not saying it won't be fixed, but I really doubt they will ever work on this special issue since its not really a bug, we can only hope they will do something about this, but I really think they don't really care about this one. No one was ever affected to the issue and this problem is really old from pre MC1,7, we're now in MC1.8 if they had any intentions of fixing it, it would have been done, seriously, maybe they work on it but its not one of their top priority also.
In my case, this isn't fixed, I can't use any mob spawner for XP grinding at all without getting kicked out when there's more than 40-50 mobs waiting, which is quite a challenge, I must stay in front of my PC with the game open at all time if I want to grind some XP, can't go AFK anymore, I have an auto-fish farm that works overnight and get me some XP, but its a lot less efficient. Hope for a fix, but I think I'm going to wait a long time for this one to be fixed.
Starting to think this could be different depending on the exact CPU the computer does run on, since they added threaded stuff and the mob AI is on a separate thread now, perhaps the model of CPU used can cause this issue for some people, There's so many CPU, dual core, quad core CoreI3, CoreI5, CoreI7 and that's just for Intel cause I don't know that much about AMD CPU, maybe this is different depending on the exact model of CPU, my PC use a Intel Core2Quad Q9400 at 2.6GHZ
I can relate to this one but it doesn't freeze for me just a massive fps drop, I've tested a few things up and it looks like it does this when I use the /kill and I get to the spawn chunks, my fps goes from stable 120fps to 18-20fps max, if I go around 20 blocks from the spawn point, everything is back to 120fps, if I wait around 1 minute and go back to spawn, fps is stable again too but if I'm too quick, fps goes down to 19-20fps at the exact spawn location.
Intended, you can choose the type of arrow you want to use by having them in your off hand, you couldn't choose the type of arrow otherwise, and if you don't have any special arrow in your off hand, normal arrows will be used if you have some in your inventory.
Again, you couldn't choose the type of arrow if we couldn't put something in the off hand while using the bow, intended behavior for arrows at least, perhaps we shouldn't be able to have a sword there, we'll see what Mojang decides there, its still a snapshot in alpha stage, so it may have this kind of problems.
Les packs de texture de la 1.8 ne sont pas compatibles avec la 1.9, et c'étais déjà prévu alors ce n'est pas vraiment un bug. A chaque version de Minecraft, c'est la même chose, les développeurs de pack de textures doivent refaire leur travail de nouveau.
Oui, ya des textures qui doivent être refaites, le GUI par exemple, et je ne crois pas qu'aucun créateur de texture packs ne va faire quoi que ce soit avant la release officielle de la 1.9, car tout peut encore changer quand ce sont des snapshots. Ya moyen de piquer les textures Vanilla de la 1.9 pour remplacer celles d'un texture pack a problèmes, je l'ai fait en 1.8 avec le nouveau GUI de la table d'enchantements pour pouvoir utiliser Faithful32 dès le départ, ya juste je GUI de la table et les nouveaux matériaux qui étaient en 16x dans le pack que j'avais crée.
Enchanting is broken seriously, tested in 1.8.8 enchanted 10 diamond helmets to level 30, everything was perfect, tried same thing with 14w31b and all enchants were low level for all of them. Tried with books and obtained same results.
That would explain the weird behavior of the enchantments table, despite having 30 levels and choosing a 30 level enchant, the results are always a mix of low level enchants on everything I've tried so far, max unbreaking level I got is 1, max level of Fortune and Looting is also 1, can't go higher also on all other enchants, the only ones that seems to work is Thorns.
Never mind, looks like I had a problem with my enchanting system somehow, maybe my Minecraft was corrupted somehow, I've just created a brand new Minecraft instance and the system seems to work now correctly but now its clear that the system isn't exactly like in 1.8.8 anymore, maybe some balancing was made there but now its gonna be a hell to get a fortune 3 diamond pickaxe from now on, we will have to combine them in a Anvil, just tested this out in creative, 30 diamond pickaxes and only 4 of them had Fortune on it 3 with fortune 1 and 1 with Fortune 2. I normally get around 4-5 pickaxes with at least Fortune 2, they did something clearly there.
I can relate to this one in 15w31c has well, found my 2nd zombie spawner and there's an enchanted book with nothing in it, I'll try and set the same seed in 1.8.8 and go to the same coordinates, I'll see if there's an enchanted book in it and I'll give myself the same in my 15w31c world. I think we can't really consider this cheating, I call it bug correcting.
No problem with mine, I've got around 100 cows in a pen and the only bugs that happen sometimes is when I first connect to that world (private family server on my 2nd PC), some are out of the pen, but that bug is really an old one and not exactly related to this one either.
Neat, it just gave me some ideas for new mob traps, iron trapdoors are the most awesome addition of 1.8 and now that we can place them like this, it gave me some imaginative plans I'll have to test them out.
FYI some texture packs seems to work really well, I'm using the Faithful32 pack by Vattic and updated some of the textures from his official forum thread on minecraftforum.net and so far it works really well, I'm not a pro at modding texture packs and can't really tell if something is wrong but for me its perfect with this pack.
Is there any method of randomly generating any enchanted book in MC 1.8.8, two times I came accross an enchanted book and they have no enchants on them, if I could give myself some random one in a 1.8.8 using a command block or a /enchant command I could try to give it to myself in my 15w31c world.
I can confirm this and also they don't drop bows anymore in my mob spawner I've been testing this for the past 45minutes getting some XP levels and didn't receive a single bow, usually I have more than my fair share of them, they don't seem to drop any armor pieces and I didn't see any wearing armor either, not sure if I should report this bug or not since most likely I'll get a duplicate assigned to it and I won't ever find when it will be solved.
The world was created and spawner was discovered in 1.8.8 around 3 days before the first snapshot for 1.9 was released, I worked on the spawner in 15w32a for the first time, if its just a matter of recreating the spawner to make it work again, I will do it in creative cause it worked flawlessly in 15w32b at least I have 2 full chests of bows that proves this was working fine, its when I switched to 15w33b (I didn't do the 15w33a update) that it stopped working, also in c doesn't work, drops bones and arrows fine, but no bows anymore.
Just testing right now, it seems that it only affect the armor I was wearing prior to update from 15w33c to 15w34b, the rest of them and even some of my old armors seems to work fine.
If its intended, please tell me its not the same for swords and such, that would be insanely bad and mean we would need to carry 3-4 swords and 2 full sets of armors when exploring new caves. I understand its not final and theses changes need to be adjusted but it makes it much more harder right now especially against witche and skeletons.
Now that I have an AFK auto-fisher in my world, its getting extremely annoying, I got a ton of enchanted books that have no enchants on them, I've searched everywhere if there was a way to generate a randomly enchanted book but most methods I've found so far gave me an enchanted book with no enchants on them. If anyone know the correct way to generate a valid random enchanted book even with a command block, I don't care, I'll put one in my world right now if this can generate random enchanted books until this annoying problem is solved.
I'm here and report that all my minecart network doesn't work correctly anymore, none of them will let me ride to the destination, I got killed once and lost all my items (since I consider this as a testing world and this kind of bug is expected I gave myself all the items back), like the Minecart went into the ground and wouldn't let me back up, I had to disconnect from the server and connect back and I was stuck in the rocks around the track and died.
Can you assign the job to someone else, according to recent infos, dinnerbone isn't working on Minecraft anymore for awhile after today, so if we want to see it resolved, we better transfer it to someone that will see it, otherwise we may have a 1.9 final release with that bug still in it.
Never ever had an out of memory before, they did something in 15w44b that cause this, that server started with the first 1.9 snapshot and we are just 2 brothers on it, strictly family private server, we run a gold farm made out of nether portals and I never had the slightest problem with this, the server is running right now, my brother is AFK in the gold farm and I'm AFK in a skeleton farm with dogs killing them and no problems in 15w44a...
Please, don't assign a duplicate, I won't be notified of future updates and I'm lost when I have to follow multiple bugs and can't remember why I follow one with a title that has no relation to my bug reports.
Yup, will have to remember that mob killed by wolfs = ticking entity error I have, not easy sometimes, I'm tracking and reporting bugs for 3 different games right now
That would explain the problem we have, our AFK gold farm use iron golems to kill the zombie pigmen, so if that is the problem, we won't be able to migrate to 15w44b anytime soon. Now I totally understand cause I wasn't near the gold farm and had no problems, soon as my brother connected he's always near the gold farm, the crash started to happen.
It was assigned to Dinnerbone if I can remember, and since he's out of the project, he's not assigned anymore, I think we will end with a 1.9 without a fix for this bug which at this point is the most inconvenient and most annoying bug I've ever seen in a game, unusable minecarts and horses for more than 2 months already.
I've copied the file to my local saves folder from the server and if I play it in single player, the zombie spawner works flawlessly, so it must be related to a server issue somehow.
I know we're not supposed to comment but to help someone here, if you don't want to follow this thread anymore (I'm going to do the same since its fixed) look on the right of the bug report there's a number of watchers, right next to it, there's an option to stop watching this bug, this will stop sending you emails about this bug report.
Tested, horses jump fine in 15w51b, 16w02a, 16w03a, 16w04a and 16w05b, I can do a video if you get any doubts about this, this issue is affecting only 16w06a right now.
I can confirm this, was wondering why my horses were dying when I parked them in their stalls, tested it multiple time, to reproduce grab a horse, ride it for awhile and park it, they take serious damage and some die instantly if they don't have enough hearts.
Affect 1.9pre1 2 3 and 4, they need to fix this issue, a blaze fired at a pigmen near my blaze farm and I was dead in no time, lucky for me I always place important stuff in my ender chest
The wither skeletons can't really hit a pigmen, but you can accidentally hit a pigmen while hitting a wither skeleton, or a damn regular skeleton can hit the pigmen. Its a nightmare right now, I avoid the Nether like the plague, and I don't think they consider this a bug so I would be surprised if the fix this issue. Its getting worse with the new combat update, a swing of your sword can hit a pigmen while you wanted to just kill a blaze and bam, you're dead.
Any forums to discuss that horrible issue and vent a little, just got killed again by a horde of zombie pigmens that got shot by a ghast, smart me killed the ghast and then, I've lost a full set of diamond armors with mending on each pieces 3 stacks of nether quartz half a stack of glowstone blocks, a silk touch pick with mending on it, around 45 steak and 6 fire resistance potion. All of this because of a stupid bug that should have been fixed before but nope.
My guess is optimization isn't in their top priority list right now, so many bugs need to be squashed down, I feel like the 1.13 release is still in a snapshot state and shouldn't have been released yet, but before release, there's not that much about bug reports, you start seeing them once something is officially released, cause I'm going to say perhaps only 15-20% of Minecraft players test the snapshots, the others wait for real release.
I've decided to stop playing Minecraft 1.13, I'll wait till this is really fixed, its ridiculous how this game was released so badly optimized and now any simple redstone contraption for mob spawners or automation makes the game lag like crazy. Its an awesome update and I love all the new changes and the Aquatic Update, but this Vanilla update is worst in performance and fps wise than when I play Foolcraft 3 modpack which rely on a crap ton of mods and is on 1.12.2. So its clearly not my PC that is the problem. And its not only redstone, but just roaming around makes the game lag like crazy. RIP Aquatic Update, lets hope Mojang really cares about optimization soon enough. Oh yeah, its a brand new world created in 1.13 so its not an old world conversion problem either. At first my adventures were nearly smooth as butter, but the more stuff I build, the worst the performance become. Also I tested to run the server on a better PC and on my Main rig, it doesn't change anything, perhaps a little better at loading chunks on my 2nd rig that has a better SSD. 2nd rig is I5 3550, 16GB, GTX 770, Windows 8.1 Pro 64 bits.
Main PC Specs:
Intel I7 4790K stock 4.0GHZ speed
16GB DDR3
GTX 770 OC WF3 4GB edition
Samsung 840 Pro SSD 512GB edition
Windows 10 Pro 64 bits
Latest version of Java 8
Server running the world Vanilla in 1.13 pre1
I'm the only player on this world since its family only.
Every 5-10 blocks or when I reach a chunk border, it freeze the game for a few seconds, its not a ram problem, it makes the game unplayable PC is I7 4790K 16GB, game on SSD on a GTX 770 latest java 191
I also noticed this even while running a server on a 2nd PC, and also while just mining blocks in the same chunk, every single time you break a block, it stutters for a few seconds, I'm guessing its the new lighting engine, cause I see the same issue while just replacing the floor of a new house, every block I put down cause a slight freeze, I've tested this in the official 1.13.2 and I didn't see this problem at all.
I can confirm its still in 18w43c, I'm not surprised being one of the first released snapshot for this version, perhaps it was a little bit too early, I'm blaming the new lighting engine on this one, I see the same lag for each block I mine or I put down, so I suspect its the way the new lighting engine is calculating its way out.
Seems to be fixed, I can confirm, but I see a little lag spike after chopping down a tree now, its not extreme, but I think its related to the leaves despawning mechanic, which is maybe a new bug report, I'll browse through the new ones tomorrow when I have more time, if its not there, I'll try to reproduce it again and report it.
Since you can change the color of the text now, I'm not sure if this could be considered a bug, just right click with the dye of your choice to change the color of the text on any signs, you can do this multiple times if you want.
Vindicators in Patrols are killing the game for me, you can't even start any new game because they will find and kill you before you even have resources to deal with them, even in full iron armor, they killed me right away, there's no more peaceful days in this game, I give up, if this isn't adjusted to only spawn at night, the game is now unplayable. I use 18w46a.
Now worried that Mojang totally ignores this bug, it makes the game unplayable and yet absolutely no correction, no update, nothing in over 3 days, if its anything like the 1.13 release that had a very annoying bug (can't remember which one), we may have to wait up to a month before they fix this which is extremely annoying. I would urge anyone that want to play 1.14 to use the pre-release 5 version, if only we could find the download link for the servers for it at least.
Kyle Lane and McDodge34, the "max-tick-time" option is for Watchdog, which shuts down your server if it is lagging. You can look at MC-63590 for more info, but it is probably not related to this issue.
McDodge34
MC-86832
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
I can confirm this, I really hope this will be fixed before the weekend, I really want to have fun with the new features this weekend.
Edit : I fixed the issue by removing the item frames for now we didn't use a lot of them in our current world so I don't think they will be missed till they fix this issue, I went back to 14w11b on my world and removed all of the item frames, then switched the server back to the new 14w18a and have no problems to report beside a lot of light bugs on the stairs and half slabs.
I can relate to this issue also, I've lost so many horses because of this bug, now I place a chest next to them and I always deposit the horse armor and saddle, already lost 4 saddle and 4 iron horse armors. I've built a Stable for them but they still vanish, even 2 with nametags, like if they were deleted by the game.
You can temporary fix this issue by extracting the redstone textures from the 14w17a or 14w18a.jar located in the .minecraft/versions folder, I did it myself because I can't stand to play with 16x default textures, I love the Faithful32x a lot more, I simply copied the redstone textures for the line and cross + the overlay of the .jar and it works #1
Redstonefix14w18a.png
Just to be clear, it will never ever be fixed, its the new way the blocks and items are coded and it won't change anytime soon for really good reasons, so don't expect mojang to correct this, the work must be done by the ressource pack teams instead.
And for Lukas Fischer, the link is to a picture, not a website, can't understand why I can't link to pictures here.
This is what files you need to copy to any ressource pack/Texture pack to fix this issue, it will get you the default textures for the redstone, but at least it works with any texture pack you may have at the moment.
Please god, don't tell me that bug isn't corrected, I need a working slimefarm quickly, the swamplands are empty at night except if its a full moon, I'm doomed. BTW : I use MC1.8 PR 3 at the moment, will check if a slimefarm work or not quickly its my project for tonight since I need slimeballs for all my sticky pistons for my projects.
Got the same damn problem since I've started playing on the 1.8Pr1 then 2 and 3, I had this problem before in 1.7.10 modded also but it only happened around 1-2 times each month, I had plenty of servers since version 1.2.5, we never ever changed the server computer is the same as before, ISP speed is still the same (Fiber 50mbps/50mbps fully tested with a ping of 8ms) Its starting to really be annoying, can't believe they did something that cause that problem and never fixed it since before the 1.7 release, it was actually in the snapshots of the 1.7, weird thing is we had a server in the snapshots of the 1.7 and also one in most of the snapshots of the 1.8 (we stopped at 14w21b to play modded 1.7.10 for awhile without any problems at all) and I've seen that error a couple of times in the past but it was actually happening 1-2 times by month I would say, now it happens every 15-30 minutes most of the time. I just got killed by a zombie (my ghost player, not me, but once I've disconnected and connected, I was dead) because of this bug, thankfully we're not in the Nether yet, I would have deleted the whole server thing if I've lost all my valuables in lava in the Nether because of a bug like this, I'm not the kind to rage quit when I die usually, but if it happens because of this, I don't know what I would do.
And for thoses that would say its my ISP (the server is at my brother house, around 10-15km from my own place), look here : [URL=http://www.speedtest.net/my-result/3723195403][IMG]http://www.speedtest.net/result/3723195403.png[/IMG][/URL]
Now its not fixed in the official 1.8 and its getting on my nerves so much, can't go in the Nether, can't go cave mining, can't do anything were I could die because of this stupid bug, please fix it, its not on my server fault, not on my ISP either, you screwed up something and now I can't enjoy the game in survival mode without worrying because I neve know when this bug will kick me out of the server, hell yesterday I was just cooking stuff in my furnace without moving for more than 20 minutes, there's no entity near my cooking base, then I got kicked out again with this stupid error. I guess complaining here is useless but I never know.
Good luck to receive any support, Mojang doesn't even take a look at theses bug reports, I'm quite sure they screwed something really badly and don't want to go back to to rewrite the part that got screwed up.
I'm in the same boat since starting my server in 1.8, computer for the server isn't bad for a 2 players only we settled up in this :
ASUS P5K-E
Core2Quad Q6600 2.4GHZ
8GB DDR2 800
128GB Adata SSD drive
Windows 7 Ultimate 64 bits
We've played on a heavy modded 1.6.4 server (140 mods loaded) with this beast without any lags or any kind of problems with 3 players online
Now we couldn't even run a basic vanilla 1.8 server, this can't be true.
The only task running on this machine is the Minecraft server Official 1.8 release
computer is up to date, got both latest versions of java (32 and 64 bits version) made sure the server used the latest one by cleaning up all the older versions of it also.
Since bukkit and spigot are now dead (google is your friend, you'll learn all the bad news quickly), I don't think we're going to see any kind of bug fixing like that Io.netty error anytime soon, Mojang needs to develop an alternative to bukkit or spigot ASAP, the life of all the Minecraft servers is the key so I think we're going to wait for awhile before they even think about fixing any kind of bugs.
Ben Campbell, you didn't read all the comments I've made, read my server specs description, read the ISP I have, on both the server and the client they are ones of the best we could have, and even my brother got the problem while at his home, the server is in his bedroom and he has a wired connection between the router and the server is also wired to the router to avoid wireless problems. Both our machines are more than able to handle Minecraft, we had a heavy modded 1.6.4 server based on FTB plus a bunch of extra mods, and never ever experienced any problems, even with an overload of logistic pipes and such. And now the same server couldn't handle a vanilla Minecraft 1.8, this might be an error message, but I've only seen it 1-2 times and only since Minecraft 1.7.X serie, and since I've upgraded to 1.8, I keep getting it, this is ridiculously annoying, they can fix this one I'm 100% sure, but they are busy with something else and don't really care about bug reports.
The base 1.8 vanilla server had 2GB set for the vanilla 1.8, I bumped it to 3GB for now, just to clarify 1 thing, the map was created in the first 1.8 Pre-Release (the PR1) we had a map before in the 1.8 snapshots but we stopped playing it around 14W21B and played a lot on a modded 1.7.10 and that is when the error happened 2-3 times max in more than 2 months of playing. Now we decided to create a brand new map in the 1.8 and since we couldn't wait for the release, we choose to start it in the pre-release which is normally not a problem at all. I don't think corrupted chunks could be the problem since I didn't experience this problem for 2 days in a row, but now that I'm building a fully automatic xp mob spawner, I'm getting worried that I could have problems when there's a lot of mobs in the spawner. Server has 8GB installed and working (64 bits OS) and I did a bunch of ram tests to make sure the ram wasn't a problem, the test passed 100% for 2 nights in a row, so I think the ram is out of the problem. I'm suspecting there's a problem with the entity and the way server does prioritize entities instead of the players, this might be what they need to fix.
Guess what, since now we know it does also happen on realms which clearly rules out any problems that would be linked to Internet or the specs of our servers, I'm more than certain they will solve it for the Realms really quickly, they care about their paying customers but won't care at all about the other users.
So that means for now, all XP farms (mine is a standard skeleton one, if I get more than 40-50 skeleton waiting, I get kicked out with that damn Io.netty error (tested on my secondary machine wired to a simple switch to rule out ISP or router problems), got the same build in a 1.7.10 test server I have right here on my secondary machine too, I get 160 mobs waiting for me and absolutely no problems except really low FPS of course) and that's not even counting the 60-70 cows that are on top of the spawner in that world, so now all villager breeders and all contraptions with a lot of mobs in them are now officially impossible to build because of this bug, if they can't fix it, I'm quitting Minecraft, I love to build crazy mob farms, villager markets and such, if I can't do it anymore, what is the point of playing this game.
How would you explain that the same exact build never ever caused any problems in a 1.7.10 server and now I get kicked out with the same thing in 1.8
Yup Server tick time is probably the culprit here, I've examinated my server.properties files closely and I didn't have it on my 14w21b and also not in my 1.7.10 server, I've seen on a topic that disabling it could solve this issue so put it to -1 and it should be disabled, trying it myself, will report back if it works.
Can confirm that disabling the watch dog doesn't solve the problem totally, and its sure to be related to entities somehow, I now have a spider string farm and I get disconnected because of the spider jockey didn't get killed by the system (I will take care of this now that I know it can cause problems but that is another urrelated story)
I've never ever touched to the view distance in my server.properties file, I did it once while playing modded and settled it to 5 and the map wasn't complete on FTB so I switched it back to 10, I didn't see any improvments from touching this.
I'm not saying it won't be fixed, but I really doubt they will ever work on this special issue since its not really a bug, we can only hope they will do something about this, but I really think they don't really care about this one. No one was ever affected to the issue and this problem is really old from pre MC1,7, we're now in MC1.8 if they had any intentions of fixing it, it would have been done, seriously, maybe they work on it but its not one of their top priority also.
In my case, this isn't fixed, I can't use any mob spawner for XP grinding at all without getting kicked out when there's more than 40-50 mobs waiting, which is quite a challenge, I must stay in front of my PC with the game open at all time if I want to grind some XP, can't go AFK anymore, I have an auto-fish farm that works overnight and get me some XP, but its a lot less efficient. Hope for a fix, but I think I'm going to wait a long time for this one to be fixed.
Starting to think this could be different depending on the exact CPU the computer does run on, since they added threaded stuff and the mob AI is on a separate thread now, perhaps the model of CPU used can cause this issue for some people, There's so many CPU, dual core, quad core CoreI3, CoreI5, CoreI7 and that's just for Intel cause I don't know that much about AMD CPU, maybe this is different depending on the exact model of CPU, my PC use a Intel Core2Quad Q9400 at 2.6GHZ
I can relate to this one but it doesn't freeze for me just a massive fps drop, I've tested a few things up and it looks like it does this when I use the /kill and I get to the spawn chunks, my fps goes from stable 120fps to 18-20fps max, if I go around 20 blocks from the spawn point, everything is back to 120fps, if I wait around 1 minute and go back to spawn, fps is stable again too but if I'm too quick, fps goes down to 19-20fps at the exact spawn location.
I can confirm this issue, I'll upload my crash log if it can help
Crash log when trying to place a cocoa bean on a jungle tree in latest snapshot 15w31a
Intended, you can choose the type of arrow you want to use by having them in your off hand, you couldn't choose the type of arrow otherwise, and if you don't have any special arrow in your off hand, normal arrows will be used if you have some in your inventory.
Again, you couldn't choose the type of arrow if we couldn't put something in the off hand while using the bow, intended behavior for arrows at least, perhaps we shouldn't be able to have a sword there, we'll see what Mojang decides there, its still a snapshot in alpha stage, so it may have this kind of problems.
Les packs de texture de la 1.8 ne sont pas compatibles avec la 1.9, et c'étais déjà prévu alors ce n'est pas vraiment un bug. A chaque version de Minecraft, c'est la même chose, les développeurs de pack de textures doivent refaire leur travail de nouveau.
Oui, ya des textures qui doivent être refaites, le GUI par exemple, et je ne crois pas qu'aucun créateur de texture packs ne va faire quoi que ce soit avant la release officielle de la 1.9, car tout peut encore changer quand ce sont des snapshots. Ya moyen de piquer les textures Vanilla de la 1.9 pour remplacer celles d'un texture pack a problèmes, je l'ai fait en 1.8 avec le nouveau GUI de la table d'enchantements pour pouvoir utiliser Faithful32 dès le départ, ya juste je GUI de la table et les nouveaux matériaux qui étaient en 16x dans le pack que j'avais crée.
Confirmed here, hope for a quick fix or next week at least, would be nice especially for torch while mining.
I can confirm as well.
Enchanting is broken seriously, tested in 1.8.8 enchanted 10 diamond helmets to level 30, everything was perfect, tried same thing with 14w31b and all enchants were low level for all of them. Tried with books and obtained same results.
That would explain the weird behavior of the enchantments table, despite having 30 levels and choosing a 30 level enchant, the results are always a mix of low level enchants on everything I've tried so far, max unbreaking level I got is 1, max level of Fortune and Looting is also 1, can't go higher also on all other enchants, the only ones that seems to work is Thorns.
Never mind, looks like I had a problem with my enchanting system somehow, maybe my Minecraft was corrupted somehow, I've just created a brand new Minecraft instance and the system seems to work now correctly but now its clear that the system isn't exactly like in 1.8.8 anymore, maybe some balancing was made there but now its gonna be a hell to get a fortune 3 diamond pickaxe from now on, we will have to combine them in a Anvil, just tested this out in creative, 30 diamond pickaxes and only 4 of them had Fortune on it 3 with fortune 1 and 1 with Fortune 2. I normally get around 4-5 pickaxes with at least Fortune 2, they did something clearly there.
I can relate to this one in 15w31c has well, found my 2nd zombie spawner and there's an enchanted book with nothing in it, I'll try and set the same seed in 1.8.8 and go to the same coordinates, I'll see if there's an enchanted book in it and I'll give myself the same in my 15w31c world. I think we can't really consider this cheating, I call it bug correcting.
No problem with mine, I've got around 100 cows in a pen and the only bugs that happen sometimes is when I first connect to that world (private family server on my 2nd PC), some are out of the pen, but that bug is really an old one and not exactly related to this one either.
Neat, it just gave me some ideas for new mob traps, iron trapdoors are the most awesome addition of 1.8 and now that we can place them like this, it gave me some imaginative plans I'll have to test them out.
FYI some texture packs seems to work really well, I'm using the Faithful32 pack by Vattic and updated some of the textures from his official forum thread on minecraftforum.net and so far it works really well, I'm not a pro at modding texture packs and can't really tell if something is wrong but for me its perfect with this pack.
Is there any method of randomly generating any enchanted book in MC 1.8.8, two times I came accross an enchanted book and they have no enchants on them, if I could give myself some random one in a 1.8.8 using a command block or a /enchant command I could try to give it to myself in my 15w31c world.
I can confirm this and also they don't drop bows anymore in my mob spawner I've been testing this for the past 45minutes getting some XP levels and didn't receive a single bow, usually I have more than my fair share of them, they don't seem to drop any armor pieces and I didn't see any wearing armor either, not sure if I should report this bug or not since most likely I'll get a duplicate assigned to it and I won't ever find when it will be solved.
Seed is : 46676285
Coordinates are : X 11 Y 33 Z 214 (spawner is around 5-7 blocks from theses.
The world was created and spawner was discovered in 1.8.8 around 3 days before the first snapshot for 1.9 was released, I worked on the spawner in 15w32a for the first time, if its just a matter of recreating the spawner to make it work again, I will do it in creative cause it worked flawlessly in 15w32b at least I have 2 full chests of bows that proves this was working fine, its when I switched to 15w33b (I didn't do the 15w33a update) that it stopped working, also in c doesn't work, drops bones and arrows fine, but no bows anymore.
Just testing right now, it seems that it only affect the armor I was wearing prior to update from 15w33c to 15w34b, the rest of them and even some of my old armors seems to work fine.
If its intended, please tell me its not the same for swords and such, that would be insanely bad and mean we would need to carry 3-4 swords and 2 full sets of armors when exploring new caves. I understand its not final and theses changes need to be adjusted but it makes it much more harder right now especially against witche and skeletons.
Now that I have an AFK auto-fisher in my world, its getting extremely annoying, I got a ton of enchanted books that have no enchants on them, I've searched everywhere if there was a way to generate a randomly enchanted book but most methods I've found so far gave me an enchanted book with no enchants on them. If anyone know the correct way to generate a valid random enchanted book even with a command block, I don't care, I'll put one in my world right now if this can generate random enchanted books until this annoying problem is solved.
Confirmed, stairs are wrong when put upside down...
I'm here and report that all my minecart network doesn't work correctly anymore, none of them will let me ride to the destination, I got killed once and lost all my items (since I consider this as a testing world and this kind of bug is expected I gave myself all the items back), like the Minecart went into the ground and wouldn't let me back up, I had to disconnect from the server and connect back and I was stuck in the rocks around the track and died.
Can you assign the job to someone else, according to recent infos, dinnerbone isn't working on Minecraft anymore for awhile after today, so if we want to see it resolved, we better transfer it to someone that will see it, otherwise we may have a 1.9 final release with that bug still in it.
Never ever had an out of memory before, they did something in 15w44b that cause this, that server started with the first 1.9 snapshot and we are just 2 brothers on it, strictly family private server, we run a gold farm made out of nether portals and I never had the slightest problem with this, the server is running right now, my brother is AFK in the gold farm and I'm AFK in a skeleton farm with dogs killing them and no problems in 15w44a...
Please, don't assign a duplicate, I won't be notified of future updates and I'm lost when I have to follow multiple bugs and can't remember why I follow one with a title that has no relation to my bug reports.
Yup, will have to remember that mob killed by wolfs = ticking entity error I have, not easy sometimes, I'm tracking and reporting bugs for 3 different games right now
That would explain the problem we have, our AFK gold farm use iron golems to kill the zombie pigmen, so if that is the problem, we won't be able to migrate to 15w44b anytime soon. Now I totally understand cause I wasn't near the gold farm and had no problems, soon as my brother connected he's always near the gold farm, the crash started to happen.
It was assigned to Dinnerbone if I can remember, and since he's out of the project, he's not assigned anymore, I think we will end with a 1.9 without a fix for this bug which at this point is the most inconvenient and most annoying bug I've ever seen in a game, unusable minecarts and horses for more than 2 months already.
I've copied the file to my local saves folder from the server and if I play it in single player, the zombie spawner works flawlessly, so it must be related to a server issue somehow.
I know we're not supposed to comment but to help someone here, if you don't want to follow this thread anymore (I'm going to do the same since its fixed) look on the right of the bug report there's a number of watchers, right next to it, there's an option to stop watching this bug, this will stop sending you emails about this bug report.
Tested, horses jump fine in 15w51b, 16w02a, 16w03a, 16w04a and 16w05b, I can do a video if you get any doubts about this, this issue is affecting only 16w06a right now.
I can confirm this, was wondering why my horses were dying when I parked them in their stalls, tested it multiple time, to reproduce grab a horse, ride it for awhile and park it, they take serious damage and some die instantly if they don't have enough hearts.
Affect 1.9pre1 2 3 and 4, they need to fix this issue, a blaze fired at a pigmen near my blaze farm and I was dead in no time, lucky for me I always place important stuff in my ender chest
At the same time, this bug can be helpful, you can park your horse anywhere, just dig a 4x1 deep hole and you can park it there
The wither skeletons can't really hit a pigmen, but you can accidentally hit a pigmen while hitting a wither skeleton, or a damn regular skeleton can hit the pigmen. Its a nightmare right now, I avoid the Nether like the plague, and I don't think they consider this a bug so I would be surprised if the fix this issue. Its getting worse with the new combat update, a swing of your sword can hit a pigmen while you wanted to just kill a blaze and bam, you're dead.
Any forums to discuss that horrible issue and vent a little, just got killed again by a horde of zombie pigmens that got shot by a ghast, smart me killed the ghast and then, I've lost a full set of diamond armors with mending on each pieces 3 stacks of nether quartz half a stack of glowstone blocks, a silk touch pick with mending on it, around 45 steak and 6 fire resistance potion. All of this because of a stupid bug that should have been fixed before but nope.
My guess is optimization isn't in their top priority list right now, so many bugs need to be squashed down, I feel like the 1.13 release is still in a snapshot state and shouldn't have been released yet, but before release, there's not that much about bug reports, you start seeing them once something is officially released, cause I'm going to say perhaps only 15-20% of Minecraft players test the snapshots, the others wait for real release.
I've decided to stop playing Minecraft 1.13, I'll wait till this is really fixed, its ridiculous how this game was released so badly optimized and now any simple redstone contraption for mob spawners or automation makes the game lag like crazy. Its an awesome update and I love all the new changes and the Aquatic Update, but this Vanilla update is worst in performance and fps wise than when I play Foolcraft 3 modpack which rely on a crap ton of mods and is on 1.12.2. So its clearly not my PC that is the problem. And its not only redstone, but just roaming around makes the game lag like crazy. RIP Aquatic Update, lets hope Mojang really cares about optimization soon enough. Oh yeah, its a brand new world created in 1.13 so its not an old world conversion problem either. At first my adventures were nearly smooth as butter, but the more stuff I build, the worst the performance become. Also I tested to run the server on a better PC and on my Main rig, it doesn't change anything, perhaps a little better at loading chunks on my 2nd rig that has a better SSD. 2nd rig is I5 3550, 16GB, GTX 770, Windows 8.1 Pro 64 bits.
Main PC Specs:
Intel I7 4790K stock 4.0GHZ speed
16GB DDR3
GTX 770 OC WF3 4GB edition
Samsung 840 Pro SSD 512GB edition
Windows 10 Pro 64 bits
Latest version of Java 8
Server running the world Vanilla in 1.13 pre1
I'm the only player on this world since its family only.
Intel Q9400 2.6GHZ
8GB DDR2
Samsung 840 Pro 256GB
Video card irrelevant since its a server
Wndows 7 Ultimate 64 bits
Latest version of Java 8
Every 5-10 blocks or when I reach a chunk border, it freeze the game for a few seconds, its not a ram problem, it makes the game unplayable PC is I7 4790K 16GB, game on SSD on a GTX 770 latest java 191
I also noticed this even while running a server on a 2nd PC, and also while just mining blocks in the same chunk, every single time you break a block, it stutters for a few seconds, I'm guessing its the new lighting engine, cause I see the same issue while just replacing the floor of a new house, every block I put down cause a slight freeze, I've tested this in the official 1.13.2 and I didn't see this problem at all.
I can confirm its still in 18w43c, I'm not surprised being one of the first released snapshot for this version, perhaps it was a little bit too early, I'm blaming the new lighting engine on this one, I see the same lag for each block I mine or I put down, so I suspect its the way the new lighting engine is calculating its way out.
Seems to be fixed, I can confirm, but I see a little lag spike after chopping down a tree now, its not extreme, but I think its related to the leaves despawning mechanic, which is maybe a new bug report, I'll browse through the new ones tomorrow when I have more time, if its not there, I'll try to reproduce it again and report it.
Since you can change the color of the text now, I'm not sure if this could be considered a bug, just right click with the dye of your choice to change the color of the text on any signs, you can do this multiple times if you want.
Vindicators in Patrols are killing the game for me, you can't even start any new game because they will find and kill you before you even have resources to deal with them, even in full iron armor, they killed me right away, there's no more peaceful days in this game, I give up, if this isn't adjusted to only spawn at night, the game is now unplayable. I use 18w46a.
Now worried that Mojang totally ignores this bug, it makes the game unplayable and yet absolutely no correction, no update, nothing in over 3 days, if its anything like the 1.13 release that had a very annoying bug (can't remember which one), we may have to wait up to a month before they fix this which is extremely annoying. I would urge anyone that want to play 1.14 to use the pre-release 5 version, if only we could find the download link for the servers for it at least.