Loading...
  OR  Zero-K Name:    Password:   
Back to List

Intersection_v3 Supported

By Saktoth
Rating:

Intersection v3
Size: 10 x 10

PLAY ON THIS MAP


Downloads: 5983
Manual downloads:
http://spring1.admin-box.com/maps/intersection_v3.sd7
http://zero-k.info/autoregistrator/maps/intersection_v3.sd7
http://api.springfiles.com/files/maps/intersection_v3.sd7


Preview
Filter:    Player:  
sort



AUrankSaktoth
4 years ago
New version of Intersection.
+0 / -0


EErankAdminAnarchid
4 years ago
Does this one have lava sumo?
+0 / -0

FIrank[ffc]killer
4 years ago
lava sumo? what?
+0 / -0

ESrankElTorero
4 years ago
in last version if u jumped sumo in the road it died because the hole it made reached water/lava
+0 / -0

USrank_Shaman
18 months ago


This map seems severely broken for me.
+3 / -0

ESrankElTorero
18 months ago
¡¡¡¡SHINNY!!!!
Googlefrog told me to use /advmapshader for a temporary fix
+0 / -0




AUrankAdminGoogleFrog
15 days ago
Why is this in supported? A newer version is featured.
+0 / -0



CHrankAdminDeinFreund
15 days ago
What does supported mean besides being eligible for Elo? Games on this map are still meaningful to estimate one's skill. We should try to include as many maps as possible into the skill estimation pool in order to make ratings meaningful.

+0 / -0




AUrankAdminGoogleFrog
15 days ago
Old versions of maps should not be supported:
  • They clutter up the list.
  • If anyone reports a bug on it the response is "try the latest version".

+1 / -0



CHrankAdminDeinFreund
15 days ago
(edited 15 days ago)

Should we then add an (invisible?) tag for maps that count for ratings? Otherwise tagging this map as unsupported would mean invalidating all past games for elo calculation.

For example "special:true/false" could be replaced by "rated:true/false" with untagged maps defaulting to false.
+0 / -0


USrankAdminSprung
15 days ago
quote:
tagging this map as unsupported would mean invalidating all past games for elo calculation

I don't think our Elo implementation is retroactive so the only change is for recalculation from scratch. In that case it's trivial to just make an exception for those battles that did change Elo even if the map has since been unsupported.
+0 / -0



CHrankAdminDeinFreund
15 days ago
(edited 15 days ago)

Just because our current elo system is unable to cope with this doesn't mean we can ignore it. Anyone who wants to understand or reproduce how our system works will be unable to do so because of a lack of information. This is part of the reason why it is near impossible to simulate zk elo outside of the live system.

WHR or normal Elo using the new rating interface will properly apply map settings and allow you to retroactively change map settings. This makes it both easy to test the rating system outside of the live server and possible to administrate the rating system, for example by retroactively removing games with cheaters in them. *

[Spoiler]

Besides that, I don't think this map is any less usable for elo estimation now than it was a year ago. So why would we have this status be time-dependent?
+1 / -0




AUrankAdminGoogleFrog
15 days ago
I'm not interested in keeping hacks in place so WHR can work. Make a proper system to support WHR. People are accidentally playing this map and it clutters up map search lists. How do you propose to fix those problems?
+0 / -0



CHrankAdminDeinFreund
15 days ago
(edited 15 days ago)

https://github.com/ZeroK-RTS/Zero-K-Infrastructure/issues/1909
+0 / -0
Back to List