Loading...
  OR  Zero-K Name:    Password:   

Post edit history

How can the mex spot dedection fail so badly?

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
3/28/2013 8:10:50 PMLTrank[pikts]wolas before revert after revert
Before After
1 [quote]Well what was the intention of the mapmaker by putting that grey stuff there? 1 [quote]Well what was the intention of the mapmaker by putting that grey stuff there?
2 Don't blame the algorithm for mistakes of the mapmaker. Ofcourse you can find some procedure for an individual corner case, but that doesn't help at all. There's cases where the grey stuff is supposed to be a mex. There's cases where it's not. There's cases where the input is completely nonsensical and even a human couldn't place mexes properly. 2 Don't blame the algorithm for mistakes of the mapmaker. Ofcourse you can find some procedure for an individual corner case, but that doesn't help at all. There's cases where the grey stuff is supposed to be a mex. There's cases where it's not. There's cases where the input is completely nonsensical and even a human couldn't place mexes properly.
3 \n 3 \n
4 TL;DR: The mexspot fetcher is not the problem. [/quote] 4 TL;DR: The mexspot fetcher is not the problem. [/quote]
5 \n 5 \n
6 \n 6 \n
7 You are so wrong it makes me puke... 7 You are so wrong it makes me puke...
8 Its ZK who uses some hacks which prevents building mexes anywhere, even more I almost guarantee that this map is older than this "mex something" "feature" which was added to ZK only so far, how you dare to blame mapper for this? Either it was to make it look cooler in F1, or whatever reasons( even if it is accidentally outlined! YES EVEN) with normal spring without any hacks it works as mapper intended, its absolutely ZK fault, mappers in ZK are already anally raped with constantly removed features from what engine offers so DONT DARE TO BLAME MAPPERS for ugly ZK hacks which doesnt work. 8 Its ZK who uses some hacks which prevents building mexes anywhere, even more I almost guarantee that this map is older than this "mex something" "feature" which was added to ZK only so far, how you dare to blame mapper for this? Either it was to make it look cooler in F1, or whatever reasons( even if it is accidentally outlined! YES EVEN) with normal spring without any hacks it works as mapper intended so its absolutely ZK fault, mappers in ZK are already anally raped with constantly removed features from what engine offers so DONT DARE TO BLAME MAPPERS for ugly ZK hacks which doesnt work.