This post summarises the changes that have been implemented in version 3.0.13 of enterO.
Until now, the start wave feature in enterO has been limited to just allowing competitors to select a start wave. In this release a number of improvements have been made to start waves to make them more usable.
- Enforce maximum number of competitors per start wave
- Add start block length
- Allow last start block to have different length
- Add admin page to display start wave counts
- Improve mass start prompt
- Bugfix: Start wave is now saved on team create
Enforce maximum number of competitors per start wave (#84)
Each race can now specify the maximum number of competitors allowed per start wave.
The current count of available slots per wave is displayed when adding/editing a competitor. Note that the count displayed only includes Submitted and Confirmed entries; the count does not include the competitors in the entry that is being created.
If a wave is getting close to capacity (there are less than 10 slots available), a warning message is displayed on the entry review page however the entry can still be submitted. Note that the competitors in the current entry are included in the competitor count.
If the competitors in this entry exceed the capacity of a wave, an error message is displayed on the entry review page and the entry can not be submitted.
If a wave is already full or over capacity without including the competitors from this entry, an error message is displayed on the entry review page and the entry can not be submitted.
Add start block length (#85)
For races that are not mass start, the block length can now be specified to ensure that there is a gap between the start blocks. For example, if blocks are set at 60 minute spacing, the block length could be set to 50 minutes. This information is then displayed when selecting a start block in the entry process.
Allow last start block to have different length (#85)
By default, all start blocks are the same length. There are cases though where the last block may need to be shorter to fit into the available start window and so the length of the last block may be optionally set. In this example, the last block is set to 30 minutes.
Add admin page to display start wave counts (#89)
A page has been added to make it easier for administrative users to see how full each start wave is.
Improve mass start prompt (#87)
For mass start events, the race listing on the event landing page shows the mass start time.
For the case where the race is using start waves, this description has now been improved to say Mass starts from
Bugfix: Start wave is now saved on team create (#83)
A bug was identified where the selected start wave was not saved when a team was added even though subsequent saves did work.
This has now been fixed so that the start wave is always saved for teams.