• Following request by Zack Loggins, add support for downloading Corporate Teams from RunSignUp.
• At the request of Jenna Ginsberg, added two new commands to listings: Add and Sub (or Subtract). They do the same as the @Add and @Sub commands in “Enter/Edit Results” but can be done in a listing. Add adds a given time to all times in the event and Sub or Subtract subtracts a given time.
• Also, at the request of Jenna Ginsberg, we have provided a way to handle multi-day events by adding 24 hours to a chip/tag time for each day after the date specified in entries.ini. This is optional. You select it from the External Timer Initialization screen. At present it is only implemented for the RunScore Open interface but could be added for other systems when the day is not specified in the passing information.
• Steven Keith aka “Kei”, working with Jeannette MacDonald, discovered that RunScore Results had a problem. If you uploaded awards and asked for a certain number in each category, all finishers in that category were in the report instead of just the number requested. Fixed.
• Tom Plummer found that the control “GE Number of Laps” for a lap race was not working properly. Was showing results for participants that had not finished the specified number of laps. Fixed.
• Tony Newton asked for a time format to handle multi-day events. New format is: “DD-HH:MM:SS”
• Jenna Ginsberg requested that time-filtering as specified in each event’s definition be used with: Merge Events and Import of bibs and times. Done.
• Christian Lizier asked for Multiply and Multiply By to work for times. Done.
• We have documented a method to convert an individual database to a team database. We have also added two new sample races as illustration: TriTestIndividuals and TriTestTeams. This method uses Import Replace.

• It was reported by Steve Gajerski and Steven Finkelstein that Versions 8.2.8.1 and later could not be installed on a Windows XP system. Fixed.
• Found Import Replace was replacing the entire record. It should leave unaffected records alone. Fixed
• Art Stockman found Laps Left field overlapping another field in Announce. Also, the field was using the default color instead of the specified color. Fixed.
• Jenna Ginsberg requested that time filtering be done when doing a “Laps to Rounds” operation. That is, if time limits are set for the various rounds, those limits will be honored when moving the times from a lap-event to a round event.
• Sylvan Smyth reported that the change for control characters in Version 8.2.7.22 caused some Thai characters to be eliminated. Also Camilo Serrano Idrovo reported that the Spanish character Ñ was being eliminated. Fixed.

• The pop-up has been removed from the “Assign Numbers” command. If you like the pop-up, a new command, “Suppress pop-up” was implemented so the user has control over whether the pop-up appears or not.
• Robert Youngs, Super Race Systems, requested that control characters such as new-line be removed from imported CSV file. He had the case of a race director who sent him files with the new line character embedded within a field. All control characters are now excluded during an import.
• At Steven Keith’s suggestion several fixes to the handling of the registration_ids in race.ini were made.
• If a participant changes their event on RunSignUp, an incremental download will put them in the right event on RunScore. When RunSignUp changes a participant’s event, it creates a new entry and marks the old one as deleted. When RunScore does an incremental download it first checks for deleted participants and then downloads any changes.
• Steve Delahunty, RunTime Software, made a change to RunScore so that a listing file which is on auto-run, blinks to alert you to its status.
• Rob Crawford, Sportstats, suggested an enhancement to the pre-event feature. This is to prevent participants who have finished their race from recording at later locations/points. For example, say a parent finishes their run and their time comes into an event called FINISH. Then they go to watch their kid run whose event is KIDS5K. If they get close to the kids’ finish line, they might record some passings. To prevent this, you designate FINISH to be a pre-event for KIDS5K and, in addition, check the [new] checkbox: Discard times that are later than the pre-event time.
• Kyle Dunnack, The Last Mile Racing, asked us how to time a lap race where the first lap is shorter than the rest. We told him RunScore couldn’t handle it. This wasn’t a good enough answer for Steve Delahunty. Steve dove in and made changes to the RunScore code to allow you to enter two distances in the Lap Distance command. If there are two distances provided, the first one is the distance for the first lap and the second the distance for all subsequent laps. This is implemented for general reports , not for the Announce feature.
• Steve Delahunty made a change to avoid problems when using RunScore in Dropbox. Problem reported by Bill Teschek.
• At the request of Jenna Ginsburg, added a control, “No SMS Warning” to entries.ini. This will prevent a pop-up if there is an SMS problem. You would want to use this control if you are sending out SMS messages automatically and don’t want the process interrupted.
• Josh Gerber requested that RunScore support file-load of race|result files. Done. You use Tools/Chip options to tell RunScore if the file contains bib-tags or chip-tags.
• At the suggestion of Jon Krupa, you can chain the pre events. For example, say you set the START event as the pre event for the SWIM-IN event, the SWIM-IN event as the pre event for BIKE-OUT, and the BIKE-OUT as the pre-event for RUN-OUT. Then if a person has an early detection on the RUN-OUT mat, RunScore will check the BIKE-OUT for a time. If it finds one and that time is less than the RUN-OUT time it is rejected. If there is no RUN-OUT time, e.g. if the person missed the RUN-OUT mat, RunScore will see if the RUN-OUT event has a pre event. It does, so it will check there and so on.
• Greg McCormick requested that he be able to change an entrant’s event in RunScore and have it reflected to that entry at the RunSignUp database. This is implemented so that all you have to do is right-click on the “event name” field and select, from the menu, “Change event”. You’ll be presented with a list of the events so you can pick the new one.
• Eric Kramer requested that downloads from RunSignUp support corral assignments. Done.
• At the request of several users, have made changes to RSClient so that:

1. If RSServer is not up, you now get a beep and it keeps trying. The status line at the bottom of the screen informs the user that RSClient is still trying to connect. 2. If RSServer and RSClient are connected and RSServer is taken down or crashes, the user will hear a beep. The status line, after a few seconds, will display an “Attempt to connect” message. It will keep trying until RSServer comes up again. Note, this even works so that if, when RSServer comes back up, it is working on a different race.

• At request of Steve Stone add counties in a RunSignUp download. This feature was added so that a number of “include” RunSignUp commands could be used in addition to counties: template_participant, corrals, est_finish, corp_teams, registration_addons, coupon_details, registration_notes, checkin_data, waiver_info, usat_waiver_info.

• Steve Delahunty and Bill Rosen pointed out that if you select a results screen from the menu and that screen is already open, nothing happens. Now the one you selected comes to the foreground.
• Steve and Bill also pointed out that if you have file open for editing and you open the same one, you will now have two instances of that file. Fixed so that now if you try to open an already-open file, that file will pop to the foreground.
• Steven Keith reported that if you open results files using Alt-N more than once. Each screen will be a bit wider than the last one. Fixed.
• Added new command “List DNF” at suggestion of Tony Newton. When used, if a participant does not finish a leg of a race, the letters “DNF” are inserted in the time place instead of leaving the time blank, which is the default.
• Jenna Ginsberg reported that if an Auto Run/FTP session is running and the Internet connection is lost. Error messages pop-up. If they are not cleared, eventually RunScore must be restarted to continue the upload of files. Fixed by not doing a pop-up message. Instead the error message is displayed on the Listing Window status line and a beep is issued.
• Dennis Joffe wanted to include information about whether an entrant was in the club of the sponsoring organization. It turns out that RunScore was properly processing membership information for USATF membership and USAT membership but not for the generic club. This is now handled by putting the membership_id (club id) in a RunScore field. Once there, you can use a [control] section in entries.ini to, say, put the club name in a field or, say, put an X in a field indicating the participant is a club member.

• Made an improvement in Announce so that now you can use the Announce Event feature from RSServer. This allows you to send e-mail results to a finisher shortly after the finisher crosses the finish line.
• Bob Bickel, Founder of RunSignUp, offered that we could send E-mail under his contract with SendGrid. RunSignUp’s contract allows for very large numbers of e-mails, Bob said we could operate under their license for free. SendGrid is different from the other e-mail systems which RunScore supports because it is done through a web API (Application Programming Interface) rather than directly to e-mail. We have found it to be very fast and reliable. To use SendGrid, contact us at support@runscore.com to get a userid and password that will give you access to SendGrid.
• It has always been required that when doing Team Mixed scoring that you need to set the number of displacers equal to the number of finishers. If you didn’t, the results could be weird. This is now enforced. If you don’t have them the same, you will get a pop-up saying they are not the same and they will be forced to be the same.
• Working with Selwyn Blake, have made a lot of improvements to the Announce feature. You can now display, in addition to the Division (e.g.DIV or SEX) Place, Division total which shows the total number of finishers, who have finished thus far in the specified division.
• At request of Enrique Belchi Ruis, we have added a new command Pack Time to assign the time of the leader of a pack to all riders in the pack in a cycling race.
• The new command Pack Time can also be used in an Event to Database listing to insert the Pack Time to a field.

• When clicking on a search field in Browse, that field will appear at the bottom as the field to search on.
• Improvements to incremental uploads to RunSignUp, ChronoTrack Live, or Race Roster via right-click on listings file.
• Add “Auto Run” feature from right-click on a listing file. This is much more powerful than the old auto run from inside a listing file since you can multiple listing files doing auto run at the same time.
• RunScore can produce JSON formatted reports which can then be dynamically uploaded to a web site.
• Upgraded to latest version of Help and Manual, the program we use to generate the Help screens. The only think you will notice is a nice looking header at the top of each topic.
• And, as usual, some bugs were fixed.

• Steve Stone pointed out that if he assigned bibs in RunScore, the changed records did not get flagged as changed so did not get uploaded to RunSignUp. Fixed.
• Changed upload block size for RTRT uploads from 2000 to 500 to make the uploads more reliable.
• When opening a file from within RunScore, the file types *.lst, *.rsm, *.txt are provided. Have added *.ini.
• Updated the Sample races with new field “Name” which is the concatenation of “First Name” and “Last Name”. Makes listing simpler and allows uploading of “Name” to results as one field.
• Natalie Young pointed out that if she created a race series in RunSignUp that started in 2015 and finished in 2016, only the 2015 events could be downloaded. Fixed.
• Have made an improvement that users have been asking for to the RunScore Results incremental upload capability. Before you could only designate one file to do incremental uploads as the race is going. Now you can have multiple files active.
• Jon Krupa requested the ability to name the splits in a TFRRS race. Done. Just use the “Field Header” command to name the split.
• Raceroster.com added to list of supported registrations sites
• Jenna Ginsberg requested the ability to concatenate two fields together and put them in a third field but without a space between them. This can now be done by putting “Space (tab) 0” before the “Selected Value” commands.

• At request of Jon Krupa, sort meets by date when selecting a TFRRS meet. Also, allow selection of “All meets” or “Future meets.”
• Both Sid Steinweg and Brian Sparacino reported that they couldn’t send a TFRRS-XC report to the editor. Turns out that neither had obtained a login/password yet from DirectAthletics. However, you should be able to produce the report without having a signon. Fixed.
• We are encouraging users to update to this version since improvements have been made to the RunSignUp integration with RunScore Results as well as other fixes and improvements.
• Download of registrations from imATHLETE is now officially supported. An earlier beta version only allowed a download blocksize of 50. Due to a change at imATHLETE, that is now 1000. We would like some feedback from RunScore/imATHLETE users.
• Have included the TFRRSRace in the update download. The NCAA is working with DirectAthletics and have developed this required format for all college cross-county meets starting this fall. It will probably also be used for many high school race. We are looking for testers.
• Active Works no longer requires a timer to contact their Active representative for an app token. The new procedure is: “For a Timer to view an Event’s data, an Event Organizer must ‘invite’ them. When individuals accept an invitation to be a Timer in the system, ActiveWorks Endurance now automatically checks if they have an API token. If not, the system will automatically email the token to them. Additionally, Event Owners and Timers can email themselves an API token by clicking Get Timing API Token on the event dashboard.”
• Uploading RunScore Results to RunSignUp uses the reg_id.txt file in the race folder to store the registration_id values. A registration_id field is not needed. If it IS used, the results were getting the registration_id from the reg_id.txt file which could cause a problem if the id is in the field and not the file. Made a change so that RunScore now checks for the registration_id in both locations.
• Mark Toretsky and Steven Keith reported that a race simulation caused the first person in the race to be a non-runner, that is, someone without a bib number. The problem was introduced in 2014 when the simulation was changed so to not include the unregistered runner number. Fixed.
• Bill Teschek reported that the upload of changed records to ChronoTrack Live uploaded the same records each time. Fixed. Note: if fields such as the age-division field, often called DIV, changes, that does not result in that record uploading. The record is only flagged as changed if the field changed is one of those fields that are to be uploaded. To find out which fields they are, look in the CTLive_fields_mapping.ini file in the RunScore folder. The same is true when uploading changed records to RunSignUp.
• At request of Doug Liverside, extend the number of parameters from 20 to 36 (1 -10, ‘a’ – ‘z’). Had been implemented only as far as ‘j’.
• Added two features to Announce for use with lap races, requested by Andrés Alañón Vázquez: “lap distance field” for keeping the lap distance in a field. This is for races where everyone is not running the same distance. Likewise, added “laps left field” to specify the number of laps and to tell Announce to display the number of laps left when everyone is not running the same number of laps.

This version is a merge of RunScore Results, Version 8.0.0.3 and RunScore Version 7.5.5.7 to create RunScore Version 8.1.0.0. What does this mean? It means that from now on, whenever you use RunScore to interact with the RunSignUp site, you will be using the RunScore Results. Also, uploading and downloading registrations at both RunSignUp and ChronoTrack Live have gotten easier. We eliminated “Sync with server” and replaced it with a very easy way to download changes from the system and upload changes made in RunScore to the system. The RSRServer and RSRClient (RunScore Results server and client) have been retired. The new modules have the same name as the old ones. If you think you may want to go back to Version 7.5.5.7, save it. Or you can do a complete download using RunScoreSetup.exe to revert to 7.5.5.7. View the short video on the main RunScore page: www.runscore.com which highlights features of this new integration. Also on the main page is a document showing how to allow each runner to see themselves crossing the finish line on a YouTube video.

• You no longer need to have a field “registration_id” in your database. The registration_id information is kept in a separate file (race.ini) in the race folder.
• Also in the race.ini file are time stamps for each record that has been changed. This is used for upload of changed records.
• “Sync with server” has been removed due to problems. In its place you can do an “Incremental download” to get changed online records. Likewise, you can upload new and changed RunScore records with one click. This works for both ChronoTrack Live and RunSignUp.
• You can take advantage of these features without making changes to your normal RunScore setup.
• Results are extremely easy to post. You merely right click on a listing button and instead of sending to a printer or the editor, you send it online. Handles overall results, award listing, and team results. With one more click you can view the results online.
• Set up for e-mail and text notifications. Once set, a runner or his friends can go to the RunSignUp site and ask for e-mail and/or text messages for selected runners.
• Provide links for each finisher to the specific person in a YouTube video showing that person finishing. This is all done from RunScore.
• You can download from RunSignUp to get the participants or, if you have another way to obtain participants you can put them in RunScore and with one click upload them to RunSignUp.
• Not using the RunSignUp site for registrations for this race? You can still take advantage of the above features. There is a nominal cost for posting results. There is also a cost for text messages. If you ARE using RunSignUp for registrations, these services are free.
• At request of Troy Rebert, added External/Custom Report capability to Team Relay.
• At request of Fred Dunn and Les Morelles, made Division Place and Division Total headers in a “RunScore Results” of “ChronoTrack Live External” posting more meaningful. For example, for sex place and sex total they would now read “Sex place” and “Sex Total”.
• The headers of reports are always produced in proper case (e.g. “Name” instead of “NAME”). Sid Steinweg asked for a way to control the the capitalization of headers. This can be done with the new command: “Header case (tab) None”. The default is “Head case (tab) proper”. “Upper” and “Lower” are not supported but could be if the need arose.
• The “RunScore Open Interface” for external bib/tag systems, has been extended so RunScore knows if the data being set is chip data or bib data. You use “RSBI” for a bib-tag and “RSCI” for a chip-tag. These improvements came about from working with Thorsten Voegel, Race Result, Germany.
• Fixed a bug that kept the registration_ids from getting uploaded to RunSignUp or RunScore Results.
• Changed the simulate feature so you will no longer get the “Unregistered Runner Number” in the results produced by simulate.
• Doug Cleavenger reported that Importing a CSV file that had CR/LFs within a field caused a problem. This problem had been fixed some time ago for internal imports such as downloads from a registration system. It is now fixed for imports from File/Import.
• The logos on the main page of RSServer and RSClient have been changed to reflect the fact that RunScore Results is part of the module. They now read, respectively:
• RunScore RunScore Results/RSServer Results/RSClient
• When uploading a large custom/external result set, the upload is now done in pieces of 1000 results per piece.
• New command “Output Format” allows you to create the output in any of the following formats: Text (default), XML, JSON, or HTML.
• The new entries.ini command “Modified Field” now works from RSClient. It previously only worked from RSServer.
• If you change a RunSignUp entrant to a different event online, a new registration_id is assigned. On the next incremental download, RunScore will notice that it is a new registration_id. It will then look for the bib number. If the bib number in the new record also exists in the RunScore database, the new record will replace the old but preserve fields that are not in the download.
• “Sync with server” function has been removed because it has not been robust. It is replaced with the, already existing, “Incremental download” in conjunction with the new “Upload modified registrations”.
• New command: “Team Total” can be used in an Event to Database to send the team total for each individual’s team to a field. It can also be used in an overall listing to produce, next to the “Team place” column a “Team Score” column which shows the team score for each individual’s team.
• Improvements have been made to the criteria which determine if a field has changed. This is useful when uploading changed registrations.
• Can now handle USAT (USA Triathlon) and USATF (USA Track and Field) membership numbers when downloaded from RunSignUp.
• Doug Liversidge pointed out that the “Divide” and “Divide By” commands did not work for time fields. Fixed.
• Preliminary support has been added for the DirectAthletics TFRRS-XC site. This will be final once more testing is done. The support allows timers to upload collegiate cross-country results to the DirectAthletics site.

• At the request of Jenna Ginsberg, have extended the Total (to a field) command to handle times. The receiving field must be flagged as a time field.
• At request of Steven Keith, have added a new control “Contains” which tests if a field contains a given string of characters.