Reply to Vyndree's post

Quote Originally Posted by 'Vyndree',index.php?page=Thread&postID=139564#post 139564
By allowing the precedent of letting the COMPUTER decide how to effectively compute where to place a click (as a relative position on two different-resolution boxes), you are allowing the precedent of letting one click (on a X1, Y1 location) translate to a click on a totally different (X2, Y2) location.
Good point. The issue now becomes when that translation is defined. I would argue about the phrase "letting the COMPUTER decide how" implying automation and/or logic, but I think I can still defend this even with logic in the decision of where to click provided one thing: The replicator has no knowledge of any software that the clicks are going to. In this example you could map any location of a click to any location on the other clients. This still does not provide anything beyond translation. If you want to invert the click location, or map a certain region to a different region on clients that doesn't change the fact that you must configure this behavior beforehand and the user is making the decisions on the mapping. The main thing is that there is no game knowledge in this mapping that isn't provided by the user prior to the click. The replication isn't reacting to in game events, and it isn't doing anything the user isn't configuring it to do. This is not automation since the user has decided prior to the click how it would be transformed.

Most of the creative mapping for click location could be accomplished with keybinds, so I'm not sure it really opens a can of worms if the translation is fully mappable. If I have missed some exploit or trick that could be done with this, I'd be curious to know about it.

- Souca -