Site Updates - v57 Released!

Practice Log

The practice log has been a bare-bones corner of the site for a long time. This release turns it into something worth keeping.

• Log a single target. Shot a few slow fire targets and called it a night? Log just that. Pick slow fire, timed fire, rapid fire, or a full match, and the form only asks for what you shot
• Pick the day you shot it. You can write up Saturday’s range trip on Sunday morning and have it land on the right day
• Fix a mistake. Every score has an edit and a delete button. A typo no longer has to stay forever
• Your notes get saved. The notes box was always there, but what you typed into it was being thrown away. It sticks now
• Practice Log is back in the menu. It had quietly dropped out of the navigation and was only reachable from the home page

Seeing Your Practice History

• Charts and the score list now cover a period you choose: last week, month, three months, six months, year, or everything. It opens on the last six months
• Longer histories come in pages of twenty five, or fifty or a hundred if you would rather scroll
• Course of fire averages no longer count a course you did not shoot as a zero. If you only shot slow fire that day, only your slow fire average moves — before, a session like that dragged your timed and rapid averages toward the floor

The Practice Log On Your Phone

• The practice log fits a phone screen properly. The date range buttons use short labels, the score table drops the columns it cannot fit, and the charts label their dates as dates

Dummy Score Rules Are Now Yours To Set

When a team is short a shooter, BullseyeTracker fills the gap with a “dummy” score based on the lowest score that counted toward either team that match, minus a set number of points. Every league we had seen agreed on that. Where leagues differ is what happens when a team needs a second dummy in the same match — and until now, only one answer was available.

When you create a division you can now set two things:

• Which score each dummy is based on. Either the next lowest counted score each time — lowest for the first dummy, second lowest for the second — or the same single lowest score for every dummy
• Whether the deduction grows. Either the same deduction for every dummy, or a deduction that increases each time: ten points off the first, twenty off the second, thirty off the third

Neither setting changes anything if your teams only ever need one dummy in a match, which is most leagues most of the time.

Nothing changes for divisions you have already created. The defaults are exactly what BullseyeTracker has always done, so your past seasons and your current one score the same as they did yesterday.

The Rules tab now has its own Dummy Scores section that spells out what your division actually does, in plain language and with the real point totals rather than a description of the formula.

Add Your Own Rules

• Divisions now have a free-form rules box for anything BullseyeTracker does not have a setting for — range commands, local etiquette, what happens in a tie, whatever your league has written down
• It shows up under “Other League Details” on the “Rules, etc.” tab of your league page
• You get a proper editor, so headings, bold text and lists all work
• It is set per division, so writing this year’s rules never rewrites what a past season said

Team Scores

• When two shooters are tied for the last spot that counts toward a team score, the tie now breaks on rapid fire, then timed fire, then slow fire, after the existing handicap total, X count and raw score. The same order is used for sorting weekly stats

A Faster League Page

• The league page loads considerably faster, particularly for larger leagues with a lot of teams and matches
• Weekly stats now load after the page appears instead of holding it up, so you see your league sooner

Bugs Fixed

• The timezone list on your profile no longer varies depending on which server answered your request
• Charts across the league, team, shooter and practice pages were rebuilt on a current charting library, fixing a handful of display quirks along the way

Behind the Scenes

• Deployments are smoother and less error prone now, thanks to an improved workflow for site files and much better automated testing coverage