Actually, I'm always having lag issues. The only way I can play Minecraft is on a laptop with one gig of RAM, so it's a persistent problem. But I've always had different kinds of lag problems in SMP and SSP.
For instance, on a multiplayer server, say I encounter a creeper and just as I'm about to start swording it to death, Minecraft chokes up on lag. I'm left staring at a still frame of a creeper for 10-30 agonizing seconds, waiting to be able to respond. Then the lag clears, my client catches up with what happened in the world while I stood there helpless and unable to input anything, and I find the creeper has blown me to kingdom come.
Frustrating. But on SMP, I can grit my teeth and accept it. That's just what happens when you try to play multiplayer with a crappy computer, right? The world can't stop for my lag.
On SSP, it used to be a different story. When Minecraft would lag up on me, I could generally count on being able to resume where I left off when the lag cleared. After all, it was my lag in my world; the world was lagging with me.
Not so anymore, however. Now if I see a creeper coming towards me in SSP, and the client chooses that moment to have a lag seizure, I'm dead; while I'm lagging out, that creeper has walked up to me and exploded, and too bad for me if I was far from spawn and/or carrying anything valuable. This is... really unpleasant. I can understand it working like this in multiplayer, but when my own singleplayer world does this to me - and remember lag is a constant problem for me - it really rankles.
It's made even worse by the fact that I can't even pause anymore. Pausing the game used to be an incredibly important way of managing lag for me, if it started to get unbearably slow I could just hit escape to pause and let the client calm down and get itself straightened out before resuming. The loss of this feature is really frustrating; paired with the other problem, it could make Minecraft unplayable for me. I've almost entirely stopped playing SMP because of those issues, I really didn't want them to follow me to singleplayer.
I do understand the reasoning behind merging the singleplayer and multiplayer logic, and agree that it should be done. But is there any way to fix these issues? Singleplayer should play like singleplayer.
Actually, I'm always having lag issues. The only way I can play Minecraft is on a laptop with one gig of RAM, so it's a persistent problem. But I've always had different kinds of lag problems in SMP and SSP.
For instance, on a multiplayer server, say I encounter a creeper and just as I'm about to start swording it to death, Minecraft chokes up on lag. I'm left staring at a still frame of a creeper for 10-30 agonizing seconds, waiting to be able to respond. Then the lag clears, my client catches up with what happened in the world while I stood there helpless and unable to input anything, and I find the creeper has blown me to kingdom come.
Frustrating. But on SMP, I can grit my teeth and accept it. That's just what happens when you try to play multiplayer with a crappy computer, right? The world can't stop for my lag.
On SSP, it used to be a different story. When Minecraft would lag up on me, I could generally count on being able to resume where I left off when the lag cleared. After all, it was my lag in my world; the world was lagging with me.
Not so anymore, however. Now if I see a creeper coming towards me in SSP, and the client chooses that moment to have a lag seizure, I'm dead; while I'm lagging out, that creeper has walked up to me and exploded, and too bad for me if I was far from spawn and/or carrying anything valuable. This is... really unpleasant. I can understand it working like this in multiplayer, but when my own singleplayer world does this to me - and remember lag is a constant problem for me - it really rankles.
It's made even worse by the fact that I can't even pause anymore. Pausing the game used to be an incredibly important way of managing lag for me, if it started to get unbearably slow I could just hit escape to pause and let the client calm down and get itself straightened out before resuming. The loss of this feature is really frustrating; paired with the other problem, it could make Minecraft unplayable for me. I've almost entirely stopped playing SMP because of those issues, I really didn't want them to follow me to singleplayer.
I do understand the reasoning behind merging the singleplayer and multiplayer logic, and agree that it should be done. But is there any way to fix these issues? Singleplayer should play like singleplayer.