Poll For Minecraft Versions Regarding Recent Lag

What version of Minecraft do you connect with?

  • 1.8 (and/or sub versions)

  • 1.9 (and/or sub versions)

  • 1.10 (and/or sub versions)

  • 1.11 (and/or sub versions)

  • 1.12

  • 1.12.1

  • 1.12.2


Results are only viewable after voting.

MonMarty

Nothingburger
Staff member
Lore
Joined
Jun 29, 2012
Messages
4,439
Reaction score
34,444
Points
663
Age
33
The server is experiencing some extreme KeepAlive Packet issues as of late, with random time-outs, disconnects without any particular reason and extreme block placement/breaking lag where blocks just randomly start disappearing. These issues are not natural and have only started occuring since recent. Additionally, players with cellular connections and less than stellar cable connections have reported constantly timing out when connecting to the server.

This is, inherently, all caused by a single plugin. Probably. Very likely anyway. This plugin has always been a problem to MassiveCraft, and for years have we been trying to patch up the issue. But, since the reset, we don't have the benefit of perfect TPS and the problems have only snowballed ever since. On average, per logging period, the server kicks 90 or so players for false reasons, and then we're not even capable of tracking the damage done to buildings by ghost block placement.

So. We're asking the players to clarify what Minecraft Version they connect to the server with. This is important data to get right, and truthfully. If you connect with multiple versions, just clarify which version you use the most, say, to 80% of the time. If you use multiple connection mediums like Minechat and Minecraft Java Version, only clarify the version you use on the Java Program.

Thank you for your assistance in sourcing the problem.
 
Ghost blocks are a big problem!! A wall will look like its filled, then once you relog/the server catches up, half the damn wall is gone! It's workable, but sometimes painful lol. Thanks for all the work you've been doing!
 
I experienced ghost blocks for the first time yesterday. I thought it was just my trash internet, so I'm glad it's being addressed. It's making building an absolute pain.
 
This is a Big Issue But if we do make it 1.9 or above then we should make it like 1.8 pvp not the slow attack so all of the pvpers in the community will stay and not leave just because of the slow attack.
 
This is a Big Issue But if we do make it 1.9 or above then we should make it like 1.8 pvp not the slow attack so all of the pvpers in the community will stay and not leave just because of the slow attack.
We have MassiveCombat. Regardless of what version players play on, the "slow" Minecraft combat update swinging speed of weapons is never going to be a problem, since our plugin makes sure that you have fast weapon swing on every version.
 
As someone who PvP's, I obviously prefer 1.8 hit registration over 1.12. However, the benefit of 1.8 hit reg doesn't even appear as it is so laggy. I personally wouldn't mind scrapping protocol support if it improves the gameplay of the majority. Overall, I'd rather have a less laggy fight with slightly worse hit reg if it means the server benefits.
 
I always experienced mob lag, block lag, and now recently ghost blocks. How very unusual. I'm sure you'll pick the right choice.
 
As someone who PvP's, I obviously prefer 1.8 hit registration over 1.12. However, the benefit of 1.8 hit reg doesn't even appear as it is so laggy. I personally wouldn't mind scrapping protocol support if it improves the gameplay of the majority. Overall, I'd rather have a less laggy fight with slightly worse hit reg if it means the server benefits.
This is the kind of stance that I believe all PvPers need to take. Well said, Wooperr.
 
I do connect 80% of my time with 1.12. However, for PvP I always use 1.7 or 1.8 for obvious reasons.
I agree with what has been said above and so I would not mind connecting with 1.12 only, however, if possible I would want to keep the possibility to connect with 1.7/1.8.
 
I thought most people preferred the 1.9 combat system - I know I do.

I guess I'm a bit out of sync :/
I prefer it as well because it adds strategy beyond just preparation besides running around and clicking as quickly as possible and buffing when needed.
We will not change to 1.9-style combat regardless; MassiveCombat allows us to imitate pre-1.9 combat even on post-1.9 clients. Pre-1.9 clients just do a much better job at reducing the "clunkyness" of 1.9 pvp, they're not required to keep 1.8-style pvp.
 
Screw it

Disable 1.8 compatibility in my opinion

It's likely easier to fix hit registration issues later down the line with 1.12+ than it will be to weed this issue out amongst all the plugins.
As shown by the poll, looks like a substantial majority of the players use 1.12 anyway