Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
We need a stopwatch for races or adventure worlds. It should save the time so you could see other peoples records.
Offline
that's exactly what we need right now
This would have to be a clientside feature, otherwise latency would be an issue. The random deviation in time taken to send/receive a packet from the server would mean that two players finishing a race at the exact same time would be recorded as having slightly different times. It's why you can't code an accurate stopwatch bot.
Unless you're happy with accuracy to the nearest second.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
This is something I'd really love to see in the game.
I don't think many people speedrun worlds right now, but this could change that. If there were highscores for every world, people would probably start playing worlds more in general too!
Offline
This would have to be a clientside feature
And then whatever your time is client side will be automatically uploaded server side for others to view. (You probably mean that but I'm just clarifying).
Offline
Kira wrote:that's exactly what we need right now
Kira wrote:that's exactly what we need right now
PLEASE DO NOT POST THIS! kthx
Hypocrite
thanks zoey aaaaaaaaaaaand thanks latif for the avatar
Offline
AnatolyEE wrote:Kira wrote:that's exactly what we need right now
AnatolyEE wrote:Kira wrote:that's exactly what we need right now
PLEASE DO NOT POST THIS! kthx
Hypocrite
my rules are only rules as long they are in my topic
there should be a block for that so when u touch th eblock it stops time
thanks hg for making this much better and ty for my avatar aswell
Offline
Tomahawk wrote:This would have to be a clientside feature
And then whatever your time is client side will be automatically uploaded server side for others to view. (You probably mean that but I'm just clarifying).
That's a horrible idea. A stopwatch in EE is a bad idea.
Offline
This would have to be a clientside feature, otherwise latency would be an issue. The random deviation in time taken to send/receive a packet from the server would mean that two players finishing a race at the exact same time would be recorded as having slightly different times. It's why you can't code an accurate stopwatch bot.
I don't believe it would be too significant.
Miss Everybody Edits? Check out PixelWalker.net!
[imghttps://mm.sirjosh3917.com/PW?scale=1img]
Offline
Tomahawk wrote:This would have to be a clientside feature, otherwise latency would be an issue. The random deviation in time taken to send/receive a packet from the server would mean that two players finishing a race at the exact same time would be recorded as having slightly different times. It's why you can't code an accurate stopwatch bot.
I don't believe it would be too significant.
From testing I did a while back, my connection latency could cause deviations of up to 150 or 200ms in the time recorded by a serversided-stopwatch.
0.2 seconds is a lot when it comes to speedrunning, and that's with a decent internet connection.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
Pages: 1
[ Started around 1733341509.1965 - Generated in 0.271 seconds, 13 queries executed - Memory usage: 1.6 MiB (Peak: 1.79 MiB) ]