WR Demo discussion - two demos with the same
IMO, its lame to count with 0.001 secs, cuz u will watch "the same WR" with other player.. +the timer is not used to count milisecounds +WTF will be that demorelease ?! with milisecounds WR ?! and how the "new WR holders" will submit their demos without knowing have they really beated the current WR?(they will upload A LOT OF "WRs", and the admins would need some time to check all demos to approve/deny them) Its too much and too hard work for admins + u can see that these days u must wait a long time to see the new WRs. And admins must re-check all current WRs to count and add their milisecounds...
now think, you're gonna make a demo on some uber hard and long map. You make 1 sec better time than current wr. Then you go to demolyser and see that current wr was 01 secs better than your time, which was 1 sec better on timer. It will be very lame, like got pwned by some program.
stick to the way it is
Leave it as it is, it worked until here, so why change it? 00:00 demos are unbeatable, care? There are about 500 more demos to record...
Kz was about fun, this is making it gay. Stick to the way it is. Hel's demo > FOF. Peace
Originally posted by akMKz was about fun, this is making it gay. Stick to the way it is. Hel's demo > FOF. Peace
So you want FoF's WR to be replaced with a slower demo? Thats just dumb imo.
It doesn't makes sense to use a buggy timer, when there is an accurate timer available!
if someone sends in coldbhop with 26seconds, but with a better time than t3d, it should not be accepted.
if two people send in coldbhop with both 25sec, then the demo with a better time in fps death should get accepted.
edit: btw, only the fps-death time counts for me. and only intervals which are at least 1 sec.
Seriously, I would totally hate this idea. Releases with maps getting beat by 0.1 secs, it's just not interesting at all. This is only fun at public for short speed maps.
Originally posted by s1ghI told you it was just a matter of time until this blew out of proportion, thopa. All it takes is one demo.
Look, you guys have to realize how lame it is to do a map faster than someone else and not get the credit for it. Everyone thinks that if this rule is applied then suddenly all the records will be beatable. This is true, and this is how it should be. But what you guys don't understand is that it doesn't make the record BAD! Just because bibo's time on cg_coldbhop_v2 is actually 57 seconds and not 56 seconds, that doesn't mean that the record suddenly sucks and anyone could beat it. Just because Hannibal's longjumper[x] is 5.xx seconds doesn't make it easier to beat, it just makes it POSSIBLE.
This is going to happen at one time or another. KZ is reaching a point where demos are becoming so perfect that it will have to happen.
The chances of you seeing a demo like kz_world beaten by .2 seconds are incredibly low. If the jumper is fast enough to beat it, it's safe to assume he'll beat it by more than one second.
However, I know people who can tie certain world records on shorter maps. On a 20 second map, .2 seconds is a lot more than you might think.
That's why these should be the rules, in my opinion:
-If ANY demo is tied, but the real time is faster than the in-game time, it should be replaced. Again, chances are this will only apply to short maps.
-If a demo has been beaten according to the in-game time, but not the real time, it should NOT be replaced.
-If a demo has been beaten according to the real time, but not the in-game time, it should STILL BE REPLACED. It is FASTER.
As for the display on the website -- I know thopa disagrees with me here, but I think the best solution is to split the "Time" column into two columns: "In-Game Time", and "Actual Time".
This should not be too difficult or overwhelming to do, and it will provide people with all the information.
If someone thinks, "hmm, I think I'll try to beat rpz_downfall[boxes]", he won't care what the in-game time is. He'll want to know the real time, so it only makes sense to display both of them on the website.
As for the display on the releases -- I think that if a demo is beaten by more than 1 second, only seconds is necessary, and if it is beaten by less, then the accurate time should be written.
The last issue is that of the time limit. I thought a good idea would be to have it 0.1 seconds for all 1+ min maps, and 0.01 for shorter ones.
However, I thought it through, and I realized that it is crucial that the rules will be exactly similar for all of the demos, long or short. This might seem unnecessary for longer demos, but who cares? Once again, the chance of a long (or even short) demo being beaten by 0.01 seconds is VERY small.
That's why I think 0.01 should be as far as demo admins go.
XJ has to finally make the shift from the crappy, unreliable in-game timer to the fps-death timer. It's long been known that the in-game one utterly sucks. eDark has full confidence in the fps-death timer's accuracy, and personally, I trust him on that.
Also, my last point is that changing this rule does NOT exempt people from restarting their server every 60 minutes. It would be retarded to see a demo with an in-game timer of, let's say, 10:00:xx, and an actual time of 10:30:xx.
As an extra rule, I would suggest that if there is too huge of a discrepancy between the in-game timer and the actual time, the demo will not be accepted. This will be up to the demo admins to decide, because it depends on the length of the specific map. I think we can trust them with that, and if something isn't agreed upon by the community, it can always be debated.
So for example:
j2s_westbl0ck_s1gh_0255 (Actual time 2:59:27) ---> should NOT be accepted.
j2s_westbl0ck_s1gh_0258 (Actual time 2:59:32) ---> should be accepted.
risk_compound_s1gh_0009 (Actual time 0:10:04) ---> should be accepted (unless supa has a shorter actual time)
risk_compund_s1gh_0008 (Actual time 0:10:09) ---> should NOT be accepted.
Sorry for this huge rant, but people need to realize this is important and should be taken seriously. I hope XJ admins change their minds and make the right choice.
I agree with you all the way..
For instance;
- StormZz has done clintmo_bhoptoon faster and with more skips than the current WR.
- The same goes for Cordyline on clintmo_bhopwarehouse
- And the same goes for me on clintmo_bhopriver..
This would just increase the competition on every level, and we would end up with even more perfect demos.
It's a shame that some people are against this. Really.
[blockquote]
What if someone ties a world record with the same ingame time?
- The demo with faster record time get accepted.
[list]Check with demolyser or fps death.
What's an reasonable limit?
- 1
[/blockquote]
That thing about 0.1/0.01/00.001 is just stupid for me....
But about WRs... You should accept demo with REAL time and limit should be 1s, For example:
player_name1
kz_blablabla done in 02:02 (ingame) and 120.789 (REAL time) (player_name2 2:01 (ingame) and 121.656 (REAL time))
And instead of creating such a rule about 0.1/0.01/0.001 mappers should start using Shizuka's and Sadpuppy's timer, which is a way better than current one (no slide SCs, better time calculation).
Originally posted by .cHoseNOriginally posted by spr1nbad idea imo
kreedz timer is a built in thing and you wanna ignore that. ye its not perfect, but cmon I dont wanna see a map improved each release by 0.1 second or even less. thats sensless and very stupid imo. whats next? you wount count lj blocks but real distance?
+1
+1
Originally posted by IchWillIMO, its lame to count with 0.001 secs, cuz u will watch "the same WR" with other player.. +the timer is not used to count milisecounds +WTF will be that demorelease ?! with milisecounds WR ?! and how the "new WR holders" will submit their demos without knowing have they really beated the current WR?(they will upload A LOT OF "WRs", and the admins would need some time to check all demos to approve/deny them) Its too much and too hard work for admins + u can see that these days u must wait a long time to see the new WRs. And admins must re-check all current WRs to count and add their milisecounds...
totally agree.
Originally posted by s1ghDid stormzz tell you to say that?! dam dam dushhhhh.
(I love you don't hurt me)
You said:
"this is the way the maps are designed."
Maps aren't designed to be unbeatable. They are designed... to be played.
"just do the map again and quit whining."
I will not want to do the map again if i did it fast enough to get a world record, but it is not accepted because the other guy had a slight timerbug?
"if there are no hard demos to beat, where is the fun for the top players?"
We're not talking about hard demos to beat. We're talking about impossible demos to beat. Other than those - the "system" will not impact ANY of the longer maps. All it will do is make impossible maps to beat possible to beat, and eliminate the stupid timerbug.
@qewi - thanks for making an argument.
"I will not want to do the map again if i did it fast enough to get a world record, but it is not accepted because the other guy had a slight timerbug?"
then simply dont?
"We're not talking about hard demos to beat. We're talking about impossible demos to beat. Other than those - the "system" will not impact ANY of the longer maps. All it will do is make impossible maps to beat possible to beat, and eliminate the stupid timerbug."
eventually they will be impossible to beat aswell. then we will have the same discussion all over. for like 0,000 and it will continue to grow.
"Maps aren't designed to be unbeatable. They are designed... to be played."
so if its unbeatable it cannot be played? im not feeling you quite on this one..
NOW IF this decimal rule would be implented, and 50% of the community is against it. Isnt it better to just leave it as it is while everyone is happy? now youre probably gonna say, then the other half wont be happy? well, they started kreedzing with this system. and they can damn continue.
Originally posted by yYy.JeOriginally posted by .cHoseNOriginally posted by spr1nbad idea imo
kreedz timer is a built in thing and you wanna ignore that. ye its not perfect, but cmon I dont wanna see a map improved each release by 0.1 second or even less. thats sensless and very stupid imo. whats next? you wount count lj blocks but real distance?
+1
+1
+1
Go away with your ljstats and demos beat by decimals! This is totally not fun.
Well, this is probably one of the must difficult issues I've seen here at XJ, it's really hard to decide what to think about it.
I get that it sucks when you tie the WR, but in fact beat the time when you check it in Demolyser. But come on ...
I'm on a little different side here, which might seem like I'm contradicting myself.
Well, I think that heL's demo should NOT be accepted.
thopa made the completely right decision, and imagine how many idiots who were gonna flame him about accepting heL's demo, when they saw that his time was in fact slower. Or is that really a fact? I want to know how accurate Fps-Death/Demolyser's timer is!
For a record to be beaten, I think the time must be faster at BOTH the Kreedz timer and the timer in Fps-Death/Demolyser.
Let me give some examples (as s1gh did):
faker's rpz_downfall[boxes] is done in 00:05 on the Kreedz timer, but the real time in Demolyser is 5.8158.
rpz_downfall[boxes] done in 00:05 (real time 4.9982) - Not accepted, 'cause it is only faster in Demolyser/Fps-Death.
rps_downfall[boxes] done in 00:04 (real time 5.9128) - Not accepted, 'cause it is only faster on the Kreedz timer.
rpz_downfall[boxes] done in 00:04 (real time 5.5031) - Accepted, 'cause it is faster on both timers (even though the Kreedz timer might be bugged in both cases).
Another one:
Fact or Fiction's kzno_xtremeblock is done in 02:00 on the Kreedz timer, but the real time in Demolyser is 120.9761.
kzno_xtremeblock done in 02:00 (real time 120.7238) - Not accepted, 'cause it is only faster in Demolyser/Fps-Death.
kzno_xtremeblock done in 01:59 (real time 121.1514) - Not accepted, 'cause it is only faster on the Kreedz timer. This is by the way heL's case.
kzno_xtremeblock done in 01:58 (real time 120.2834) - Accepted, 'cause it is faster on both timers (even though the Kreedz timer might be bugged in both cases).
By bugged I mean that it maybe isn't showing the exact time as Fps-Death/Demolyser, although it is within the same second. Example:
04.95 would be the bugged time, where 05.10 would be the real time.
That is practically the same as:
05:55 would be the bugged time, where 05:70 would be the real time.
Maybe the Kreedz timer is really bugged, but beating demos only in Demolyser/Fps-Death just seems incredibly retarded to me.
Like all fucking records will be replaced like every month (who has time for checking those anyway?)!
Don't worry guys, kz is developing every second someone is playing, and I'm pretty sure we will find new ways to beat times, simply become better or less frightened to do crazy stuff in the demos.
To the mappers I can only say:
- Make longer maps!
- Think about improvement when you make the map, make sure you make the map as "unbeatable" as possible, think about alternate routes and stuff like that.
- Use a reliable timer, or stop crying about this! I'm actually not sure how precise Shizuka and Sadpuppy's timer is. Otherwise, build your own, or find someone that can build one. Will be cool to see new timer designs and shapes too.
Originally posted by spr1nbut cmon I dont wanna see a map improved each release by 0.1 second or even less. thats sensless and very stupid imo.
Originally posted by PuppetZ^Like all fucking records will be replaced like every month (who has time for checking those anyway?)!
Why do you guys keep saying that?
Do you really think that all WR's are so easy to beat with 0.1/2 seconds?
Of course the demo-ftp would not be spammed with wr-ties, if it was so easy to get a wr-tie, then why not just get the wr with more than one second?
I'm sorry, but I don't get this argument whatsoever.
-
I can understand(while I disagree) if you think 0.5 for instance is not enough for beating a wr, but saying XJ would get spammed with demos is just pathetic.
I think you are wrong cheche, because I think that's exactly what will happen, in the first few releases with a new rule that you can beat demos by 0.1 seconds, people will post all the demos with their WR-ties and others would record maps they know they can beat easily with 0.1 seconds.
Originally posted by wRath`I think you are wrong cheche, because I think that's exactly what will happen, in the first few releases with a new rule that you can beat demos by 0.1 seconds, people will post all the demos with their WR-ties and others would record maps they know they can beat easily with 0.1 seconds.
Yes of course in the first release - people will upload all their improved wr-ties (which I doubt is that many). That's just a transition.
But a 0.1 update in every release is not gonna happen, because wr's are simply not that easy to beat - and it's definatly not a valid argument for not making this change.
Originally posted by SpiNeOriginally posted by s1ghMaps aren't designed to be unbeatable. They are designed... to be played.
Best line in here. But I still think it should be limited to maps that are under 30S long. I would go for .1, .01 is too much IMO.
Either that or ... leave it at A SECOND
walls of text hurt my eyes O_O
Originally posted by PuppetZ^Fact or Fiction's kzno_xtremeblock is done in 02:00 on the Kreedz timer, but the real time in Demolyser is 120.9761.
kzno_xtremeblock done in 02:00 (real time 120.7238) - Not accepted, 'cause it is only faster in Demolyser/Fps-Death.
kzno_xtremeblock done in 01:59 (real time 121.1514) - Not accepted, 'cause it is only faster on the Kreedz timer. This is by the way heL's case.
kzno_xtremeblock done in 01:59 (real time 120.2834) - Accepted, 'cause it is faster on both timers (even though the Kreedz timer might be bugged in both cases).
As it is today.
And when someone ties a WR he can easily check the record time in demolyser. It takes only 40 sec maximum (put in correct folder, start demolyser, load demo). Then submit it to XJ.
Leave the demo spamming to me, and probably extra XJ demo admins, it's not as much work as you think.
It's a very hard question, and many people think alike and different.
Please log in to post replies.