Tyler Renelle 2d23803207 classes: use predictable randomness. This allows us to run an op on both ... client and server, and if randomness is involved (eg, item drops, critical hits, losing gear/stats on death) - then it will be equivalent on both client and server, while still seeming "random". This is required for the new death mechanic. Kudos to @snicker for providing the predictableRandom() function. @paglias we can probably stop using _.tmp now, and simply flag on the client when user drops an item / streak bonus. @SabreCat this will be used for crits, I'll keep you posted		2013-12-14 12:49:37 -07:00
..
content.coffee	[https://github.com/HabitRPG/habitrpg/issues/1977] APIv2 WIP - start of a framework where operations are shared between client & server. If the op is called on the client, it updates the user & then POSTs to the server with op of the same name. If called on server, it updates the user and user.save()s	2013-12-11 21:42:05 -07:00
index.coffee	classes: use predictable randomness. This allows us to run an op on both	2013-12-14 12:49:37 -07:00