matso/NS2-Scripts — comment on commit 389a580bae82ba03bce110bd34c6bbe4d6bbe22b
File:  line 0
By matso:

The only reason for the field is to allow them to be configured by the mapper individually. An unused feature at the
moment, so right now you could just replace that with PowerPoint.kUpdateRange value (60m seems to work fine on summit).

But does that matter? I assume that the snapshot doesn't send unchanged data, so it won't increase the bandwidth load any, now
that PowerPoints are always loaded.

/Mats

On Oct 11, 2011, at 23:57 , wackoisgod wrote:

> question... does updateRange need to be a network field ? I mean clearly the lights are a client side thing; so is the range at which the lights update on the client even required to be known by the server ? or even authoritative by the server? I mean the worst case is someone has a different value for their lights and they are either worse off or the same.
>
> I mean even if the value changes based on some sort of state stored on the server which I presume is already being replicated such as the current mode of the point it doesn't seem like we need to have another field that just there to be there.