Randy Archer

whatever they did in 1.9pre2 seems to have fixed it for me. Runs real stable now

My free food spawners (1 cow 1 sheep) sparkle but create no mobs

Well I offer my server for any testing Mojang wants. I am still running 15w47c but I have all the snapshots loaded on the server. I know with 16w07a the elytra no longer works. seems like every snapshot makes it more obvious this is a microsoft product. Everything past 15w47c will not run more than 3 hours w/out crashing and my server has 3 to 8 players almost 24/7. It has come to the point I am about to throw in the towel. Doesn't anyone a Mojang actually play the game? Or run a server? When it does crash weird things happen too - I had piston flip flops - actual stones would disappear. A simple redstone torch one repeater clock locks up. Purple repeat unconditional always active cb's randomly stop working, I copy the code, break and replace cb - reinsert code and it works again... Seems like you guys need to have a little conference and see what is going on.

How can this still be unconfirmed? Mojang you are more than welcome to use my server to observe how bad this crashes my system. Does not take long. The crashes do extensive damage - simple redstone clocks freeze, purple repeater always active command blocks sometimes need to be replaced to work again. This is really a mess. Been this way since the release after 15w47c.

look at what it is doing on last set [13:24:49} Dont you find it strange the move packets go from 6 to 7 to 8 to 9 sequentially to 22? how big is a packet? 6 + 7 + 8 .... +21 + 22 = 238 packets in under 1 second.... Seems wrong to me..That and the fact it never did this before the latest release

more alleged ticks than actual time passing... something MUST be wrong - I have tons of these - even when i am only one on server:

13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (6 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (7 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (8 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (9 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (10 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (11 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (12 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (13 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (14 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (15 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (16 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (17 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (18 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (19 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (20 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (21 packets since last tick)
[13:24:44] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (22 packets since last tick)
[13:24:45] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (6 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (6 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (7 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (8 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (9 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (10 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (11 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (12 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (13 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (14 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (15 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (16 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (17 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (18 packets since last tick)
[13:24:47] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (19 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (6 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (7 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (8 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (9 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (10 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (11 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (12 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (13 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (14 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (15 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (16 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (17 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (18 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (19 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (20 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (21 packets since last tick)
[13:24:49] [Server thread/WARN]: Cervidaevian is sending move packets too frequently (22 packets since last tick)

I have the exact same problem on my server. And it's a screamer system wise. This is new and never happened before this 47 ver came out. It cant be works as intended.

I can not log on now at all - get this every time now.

I am a moron... just checked level.dat and apparently one of my mods turned mobspawning false... so sorry

Endermen and dragon still in the end

No mobs in Netherworld either