Talk:SaveNumber (Method)

Stressing the fact that there's a cache

Should we do this? Would the end user care if there are many requests per game or not?

^{Posted by blocco (talk) on Feb 17, 2011 (Thursday) at 01:35 (UTC) [Discuss format]}

Changed PlayerAdded to PlayerRemoving.--Itunes89 14:14, 28 February 2012 (EST)

And the point of that is why? Saving when a player is leaving shouldn't be encouraged as it oftentimes does not work. Legend26 (talk | contribs) 17:07, 28 February 2012 (EST)

It should not be saved when the player joins??--Itunes89 13:00, 17 March 2012 (EDT)

PlayerRemoving

Use PlayerRemoving or don't use it if you want, but if you do use it, then don't use the WaitForDataReady method... If the player is leaving, you don't have the time to wait for the data to be ready. Just check if the DataReady property is true. If it is, save. If it isn't, then don't save. If you just wait, then the player will have left...

You can't wait in the PlayerRemoving function...

JulienDethurens

18 March 2012