complaint.

It's supposed to be slow, async is added to WE so it doesn't place blocks as fast. I think it's a horrible addition to WE, with all the restrictions as well.

 

That is what my old thread stated, that //brush and small WE Async should be removed.

Meanwhile, try to go to less populated servers for faster Async.

 

They use slower World Edit because everyone in the public has access to the World Edit, therefore making it faster would create a ton of lag, make it crash even more, and, unfortunately, abuse.

 

However, back in MCPVP, we didn't have async, but only restrictions. This still doesn't cause many crashes, and it's so much more efficient.

 

I don't really know much about MCPVP, but weren't there less people at MCPVP? I may be completely wrong (probably lol) and I don't really want to start an argument, but just wandering

 

I also think that Brawl's creative contributed. They had a strong Creative player base, that merged into build. Combine that with the McPvP player base and you get a much larger number than McPvP had alone. If Creative had never showed up, my theories is there would be about the same player base as McPvP.

But that is not the point of the thread.

 

It's true crashes were not as common, but was far easier for a player to crash the server if they chose to do so. Plus, since we didn't have the safe server restarts we have on brawl, it was common for other player's work was rolled back to the last time the server saved when the server crashed.

 

Is there an autosave feature? This isn't an attack, I actually don't know.

I am wondering because of a string of rather large resets on my map. Much more than minutes, which leads me to believe that the auto save function is broken, or not polished.

But hey, What does aGuy like me know?

 

You...

 

@aGuyInAsuite - I'm not sure if there's an autosave feature for when the server is running normally, but when the server's about to crash (or lagging badly and needs to be closed), the server, in theory, is supposed to save itself before restarting.

I haven't heard any complaints from players about rollbacks recently, but I suppose it's always possible there's a bug somewhere.

 

Yes they have what we call Async World Edit which prevents lag and shortens the task so the lag is a lot less. But obviously at the moment Build is experiencing many bugs still. Lag is a big issue. The chunks on the maps I believe @NomNuggetNom fixed. There was no way to reverse what had happened about the chunks. The only way to get it back was to make a back-up. But Build in general can be slow but just wait on the developers, some scripts might be hard to code which is why it can take some time. But I know nothing of scripting/coding so unlike the other people complaining that Nom is doing a bad job when they clearly don't really know how to code themselves.