Find the smallest number of participants with resulting percentages

As far as I know it works like this:

  • Player is killed: This adds one kill. but no death yet.
  • Player receives a revive offer: This has no effect on any stats.

From then on there are multiple possibilities:

  • Player declines and spawns new: This costs the team one ticket and the player receives one death.
  • Player accepts, but is killed: This adds one kill. The player is no longer revivable, unless the last revive happened more than 20 seconds (or 10 seconds?) ago. This has no effect on tickets, but the player receives one death, if he's killed before being able to be revived once more. One ticket is used once he respawns though.
  • Player accepts and survives: This has no effect on any stats (although I think your "in one life" stats continue counting).

Anytime you deploy code to your salesforce org, be it a managed package update or some custom code, all your classes and triggers are marked "invalid" and must be compiled at some point before they can execute again. For most orgs it is fine to let this occur automatically when the classes are referenced. However, for orgs with a lot of managed code and/or custom code, compiling all classes can improve performance.

Even more important -- for an increasing number of orgs (including mine), some managed functions FAIL TO RUN if there's too much code that needs recompiled during a request cycle. The error message that's returned is that a dependent class is invalid and needs recompiled and the error preventing a recompile is a red herring.

It's at the point where we need to run "Compile all classes" repeatedly and "Compile all Triggers" as well, and then run all our tests and finally the managed package will begin working again. This is a robust, well-know managed package and it is not any fault of theirs. Salesforce has acknowledged the issue is theirs, but have not corrected it yet.

The compile all triggers options isn't available by default. You have to request that it be added to your org if you're having this issue.