If a leap requires two GFIs and sure feet is used on the first one, a failure on the second gfi will not allow the use of a team reroll, but rather result in an immediate turnover. This happened a few hours ago, as can be seen here:
hi @Netheos I know this is an old thread, but rather than reiterate the request I figured I'd reply here:
this is a very high impact quality of life change that should be relatively effort-light on the development side. Some form of sorting teams that isn't "date of creation" would be super helpful. I've listed a few suggestions below, in order of (my personal) preference. Of course ideally coaches would have access to all of these options and be able to sort according to their method of preference, as in most modern applications, but in my opinion implementing ANY single one of these would solve most or all of the mess that is the current team list.
-Teams can be stickied by the coach, to be listed before non-stickied ones
-Teams that are currently in a competition go first in the list, followed by those in a league but not in a competition, followed by those in neither league nor competition.
-All teams are sorted by when they last played a match (most recent first)
-Complete manual sorting by coach
@kaiserlunwood I'm pretty sure Dode would be in favor of allowing leagues to change the amount of randomness (say, removing kick-off events or changing their place on the 2d6 table), without deviating from the rules in the official ladder.
When it comes to the dice, minimizing risk means you're constantly working with probabilities, even if (or because) you don't actively roll them.