|
What are the expected and observed result?
Also, here is how the settings system works. When a setting is changed it is cached off in a map on the client side. Every 1.5 seconds the client will pick a setting out of the map and send it to the server. This is done to prevent hitting the message rate limit when the player is quickly rotating through settings (like holding left on the thumb stick in the gamepad options for a horizontal list selector). The cache can be flushed manually by calling SendAllCachedSettingMessages() and it is also flushed automatically when the player changes zones or logs off. However, if it sends so many options updates that the message rate limit is hit, some of them can be lost.
ApplySettings() exists because some options changes (like graphics settings) are very disruptive when they are changed, sometimes requiring a reload. So they don't get put into effect until apply is called. I don't think this is your issue though.
|