A few of the suggested solutions to Combat-Logging depended on how the spawn was formed. An example of this was a suggestion for a smaller spawn. This would allow people to build traps where they normally couldn't, letting us counter combat logging near spawn.
However, these suggestions were misinformed for a very long time. We were missing a key fact in how Minecraft is coded:
Upon logging in, you have a 2-second godmode
Traps don't work. 99% of the time, Combat-Loggers will prevail. It doesn't matter if you are inside or outside the glowstone border.
Because of this, I think there is a simple solution.
- Remove the 2-second godmode upon logging in.
It can be argued that this 2-second godmode is a glitch. Either way, it gives Combat-Loggers a 99% chance at success. There are some pros out there that can set up a trap that will bypass this, but until this is changed a Combat-Logger doesn't have much to worry about.
Rebuttals!
What about lava? Combat-Loggers can't survive this!
Lava is nothing to Diamond Armor. It's very easy to survive this trap.
What if someone stumbles upon you after you log out?
Read suggestion 2.
This isn't vanilla
YoungsMC wrote:I think it's possible to convince you that 3 is vanilla. If it was for loading chunks, I'm sure Notch wouldn't have expected for anything to ever go on in that 2 second period of time. But he was wrong, and what happens for that small period of time where everything is loading starts interfering with the gameplay. Chunk errors are a problem with how the game loads that interfere with the gameplay, I doubt he wanted that to happen. If this 2 second godmode was for how the game loads, I doubt he'd want it to interfere with the gameplay as well.