07-Dec-2012, 6:44 AM
Ok, so I had an idea about this glitch but it's just a theory. To know if there's anything to it, some tests would be in order but I'm just lazy to try since currently it doesn't have an effect on anything major. I'll share the theory and you guys can judge if there's anything to it 
It's possible that TW might have a similar problem with cloning in lynx as what causes slide delay. When a cloned monster appears on the monster list, maybe some other monster is forgotten about for 1/20th of a second and falls out of synch? This pause is so small that it would be hard to notice in casual play, and would mainly be amplified in a stream of cloned monsters. The direction the monsters are moving might also have a small effect, since the "monster order" in lynx is just the reverse reading order of the monsters on the map at a given time (as I understand it), so the direction they move will effect in which order they are processed. In any case the explanation looks really complex.
Random8's Salsa example of a fireball hitting another one from the same source thus might be because the first fireball stalled for a brief moment, or because one of the blobs was out of synch with the other after having bumped into a wall a different amount of times (or something). As for the "lynx test" level with the pink ball appearing on two different frames while the other is exactly in the same place, these two pictures might in fact show how the first ball stalls. So the pictures could theoretically be from the same instance but taken 1/20th of a second apart, though undoubtedly Random8 actually captured them on separate attempts. More tests with this type of a setup (and it's mirror image) and maybe more monsters to compare the movement with might prove insightful.
As for the other stuff, you can get a ball not to clone in Four Plex with the right timing (and it's used again elsewhere like 3#149), and I don't know what to say about Temporary Man's level without actually seeing it.
-Miika
It's possible that TW might have a similar problem with cloning in lynx as what causes slide delay. When a cloned monster appears on the monster list, maybe some other monster is forgotten about for 1/20th of a second and falls out of synch? This pause is so small that it would be hard to notice in casual play, and would mainly be amplified in a stream of cloned monsters. The direction the monsters are moving might also have a small effect, since the "monster order" in lynx is just the reverse reading order of the monsters on the map at a given time (as I understand it), so the direction they move will effect in which order they are processed. In any case the explanation looks really complex.
Random8's Salsa example of a fireball hitting another one from the same source thus might be because the first fireball stalled for a brief moment, or because one of the blobs was out of synch with the other after having bumped into a wall a different amount of times (or something). As for the "lynx test" level with the pink ball appearing on two different frames while the other is exactly in the same place, these two pictures might in fact show how the first ball stalls. So the pictures could theoretically be from the same instance but taken 1/20th of a second apart, though undoubtedly Random8 actually captured them on separate attempts. More tests with this type of a setup (and it's mirror image) and maybe more monsters to compare the movement with might prove insightful.
As for the other stuff, you can get a ball not to clone in Four Plex with the right timing (and it's used again elsewhere like 3#149), and I don't know what to say about Temporary Man's level without actually seeing it.
-Miika