In a party game, if a next player is unspecified, the player that has
been around the longest without getting a turn will get the turn.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@539 c613c5cb-e716-0410-b11b-feb51c14d237
asdoc tool fails to recognize the Events, and they don't end up in the documentation.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@537 c613c5cb-e716-0410-b11b-feb51c14d237
Moved everything onto sub-control objects.
Got rid of the Listener interfaces.
https://intranet.earth.threerings.net/metasoy/EZGame_API_Reorg
I'll go through and make the documentation nice next.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@535 c613c5cb-e716-0410-b11b-feb51c14d237
While testing the new code I discovered that redistribution of large data sets
that approximate a normal curve can cause some funny quantization because the
redistribution algorithm assumes all values in a single bucket are flatly
distributed, but if they actually skew substantially toward the high or low end
of the bucket, then the redistribution generates a choppy curve. Fortunately
this has almost no impact on the percentile curve, which is what's actually
important, it just makes the graph of the contents of the buckets look less
smooth and sexy. Alas.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@530 c613c5cb-e716-0410-b11b-feb51c14d237
(I check every time so that this still works after you're disconnected.)
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@526 c613c5cb-e716-0410-b11b-feb51c14d237
paremeter, it assumes you're supplying the description for the first parameter, even if you
supply the name of the parameter you're describing. This basically means that docs for functions
need to supply @params for all parameters or none.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@525 c613c5cb-e716-0410-b11b-feb51c14d237
call playerReady() rather than none of them. Also tidied up the way
EZGameController delays playerReady() until the game backend is connected.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@520 c613c5cb-e716-0410-b11b-feb51c14d237
(just to be safe), but let's document why we're doing that as well
as do it outside the try/catch, in case there's an error in our code.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@518 c613c5cb-e716-0410-b11b-feb51c14d237
We should always log any errors thrown from usercode. Oops.
Fixed.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@517 c613c5cb-e716-0410-b11b-feb51c14d237
that was stupid. Now they're called players. Next I added a list of watchers
rather than simply a count. If we're going to go to all the trouble to update
the table when the watchers change, let's have the goods.
This will probably break Bang and/or Yohoho. I'll fix them toot sweet.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@515 c613c5cb-e716-0410-b11b-feb51c14d237
won't be able to use clusters but you'll still be able to use locations and
portals.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@501 c613c5cb-e716-0410-b11b-feb51c14d237
player count selection and for any range parameter of less than 16 elements.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@497 c613c5cb-e716-0410-b11b-feb51c14d237
Ray Greenwell