I am suggesting a new variable, client.zoom, which would affect the way view is calculated and enforced. By default, client.zoom is 1 and has no effect on view calculations.
If client.zoom is changed to 2, then a view of 5x5 is enforced as if it is 10x10.
If client.zoom is set to 4, then a view of 5x5 is enforced as if it is 20x20.
As of now, performing a screen zoom via a plane master requires you to use a view size that is correct only for an unzoomed screen -- in other words, the game/engine does not acknowledge a plane master's zoom when it comes to view settings, and so you are always left with turfs outside the bounds that are processed regardless of whether you actually see them. The only way around this is to screen zoom by setting your map control's icon-size or zoom settings, but all developer control is lost in this case.
Something similar to my client.zoom variable would remedy this.
Sep 5, 6:09 am
Login to reply.