This comment has been redacted by the moderator team because it contained offensive slurs.
I like the thinking. I've seen several runs like that, and there's no way to figure out the deficit. In the rule book it says add .100 if you miss the beacon but it's like a .8 deficit at least. I think its a good idea but it's not up to me.
I was thinking of a system where if you were 2 blocks off .2 would be added. Also if any of you guys remember this is the opposite of sandstorm xd.
We could allow for exclusively this map win effect timing as well as beacon timing to counteract this issue (and no for the same reasons we don't allow spawn lines we can't make a block the finish line unless you can find a beacon-like object you can go through to time xd)
The beacon BLOCK is a REFERENCE POINT for when to end the timer. If we go based on ping, it just undoes the non-ping-biased rules that we've already implemented. Using the slabs may not be the most practical way of timing, but it is not ping-biased.
Literally the only reason I am ok with the beacon is because it's very obvious when you make it in the thing, because your view will go inside the beacon. Anything like slabs WILL be biased, and a bias that we can avoid is a bias that I do not want. Also, the only non-ping-biased rule we've implemented which ping rules would stop is "stop the timer when you reach the beacon".
I was thinking of in general implementing the rule which Craftain made up; use both timings and favor the one which occurs first. The only map which this ever occurs in Fungi Galore, so the only map which has even a chance of having the ping bias will be Fungi Galore. And again, even if ping bias is bad, slab bias is even worse in my book because it's a dumb bias that can easily be avoided.
One final idea to appease everyone is to do the same as above but instill a .2-.5 delay (it needs to be absolute and not case-by-case) if you finish before the beacon. Would that make you happy?
