Scorinators (OOC Discussion)

[Darmen]

Hey I'm new to Xkorinate and I was trying to do a group -> knockout tournament and ran into some trouble, and wasn't able to find answers on the NSwiki. 1) Is it possible to setup multi-step tournaments like the one I described? 2) Are knockout tournaments possible? Thnaks to whoever answers and sorry if I seem stupid.

Absolutely not a stupid question. Unfortunately it is not possible to setup multi-step tournaments in either xkoranate or NSFS, nor is it possible to setup a knockout tournament in xkoranate. It is however possible to set up both single-legged and double-legged knockout tournaments in NSFS. You can still use xkoranate to scorinate your group -> knockout tournament, but the group stage and knockout stage will need to be two separate events and you'll have to manually remove teams which have been eliminated during the knockout stages.

[Shokpos]

Absolutely not a stupid question. Unfortunately it is not possible to setup multi-step tournaments in either xkoranate or NSFS, nor is it possible to setup a knockout tournament in xkoranate. It is however possible to set up both single-legged and double-legged knockout tournaments in NSFS. You can still use xkoranate to scorinate your group -> knockout tournament, but the group stage and knockout stage will need to be two separate events and you'll have to manually remove teams which have been eliminated during the knockout stages.

Ah, that is unfortunate, thanks for the the help though, Darmen.

[Boda]

Is there an official guide to xkornate anywhere? I want to be able to use it.

[Recuecn]

viewtopic.php?p=7631203&sid=ba984e9d90bb28c6881deadc8c321951#p7631203

I think that post is the best option there is right now (from the xkoranate help thread which I don't think sees much use). If that doesn't explain it well enough (it's pretty complicated, obviously), feel free to shoot a telegram or hop on the nss discord, where there's now a dedicated xkoranate/tech channel.

[Darmen]

Starblaydia also wrote xkoranate for Dummies.

[Mantovanian]

Is there a way to export all matchdays in one file on Xkoranate? I know that NSFS does this, but I created a personalized formula for football and because of that I need to use Xkoranate. The problem is that when I go to the last matchday and export, all I get are the results of that specific matchday...

Also, I downloaded the source code and I'm making some experiments with the code. The thing is: how do I apply these changes to the program itself? I have a separate folder for this Xkoranate experiments

[Free Republics]

Is there a way to export all matchdays in one file on Xkoranate? I know that NSFS does this, but I created a personalized formula for football and because of that I need to use Xkoranate. The problem is that when I go to the last matchday and export, all I get are the results of that specific matchday...

Also, I downloaded the source code and I'm making some experiments with the code. The thing is: how do I apply these changes to the program itself? I have a separate folder for this Xkoranate experiments

I don't think there is any way to export all results. There probably should be.

In terms of changing the source code, you need to compile it again with your changes. Since xkoranate is written with the QT graphics library, I used QT Creator (QT's IDE) to compile the version I use on Linux. Once you've compiled it, you just run your new version's executable (after copying over any sports files you want to use with it).

If you make any changes that could be of general use, you're welcome to submit them as a pull request to the Xkoranate-CE repository. Currently, that's just the same source code on CH's site plus some changes I made around 3 years ago to get it to compile on Linux under a newer QT version. At some point, I'll be adding further enhancements to the repository and releasing actual versions of Xkoranate-CE (which is a fork/continuation of xkoranate).

[Mantovanian]

Is there a way to export all matchdays in one file on Xkoranate? I know that NSFS does this, but I created a personalized formula for football and because of that I need to use Xkoranate. The problem is that when I go to the last matchday and export, all I get are the results of that specific matchday...

Also, I downloaded the source code and I'm making some experiments with the code. The thing is: how do I apply these changes to the program itself? I have a separate folder for this Xkoranate experiments

I don't think there is any way to export all results. There probably should be.

In terms of changing the source code, you need to compile it again with your changes. Since xkoranate is written with the QT graphics library, I used QT Creator (QT's IDE) to compile the version I use on Linux. Once you've compiled it, you just run your new version's executable (after copying over any sports files you want to use with it).

If you make any changes that could be of general use, you're welcome to submit them as a pull request to the Xkoranate-CE repository. Currently, that's just the same source code on CH's site plus some changes I made around 3 years ago to get it to compile on Linux under a newer QT version. At some point, I'll be adding further enhancements to the repository and releasing actual versions of Xkoranate-CE (which is a fork/continuation of xkoranate).

I have only a basic knowledge of C++, because I studied a little bit of it in college. But I'm in for testing some things. Is it hard to compile everything? I used to write the program and run in the Dev-Cpp itself, never did it with multiple files. If you can help me with this I would really appreciate.
By the way, I've been looking through the files and I found the "src\eventeditor\scorinatewidget.cpp" one. Around the line 160, there's a comment about "showing only the current matchday results"... I don't know if it would solve the problem but I deleted that specific command, just haven't tested it because of my first paragraph problem

[Free Republics]

I don't think there is any way to export all results. There probably should be.

In terms of changing the source code, you need to compile it again with your changes. Since xkoranate is written with the QT graphics library, I used QT Creator (QT's IDE) to compile the version I use on Linux. Once you've compiled it, you just run your new version's executable (after copying over any sports files you want to use with it).

If you make any changes that could be of general use, you're welcome to submit them as a pull request to the Xkoranate-CE repository. Currently, that's just the same source code on CH's site plus some changes I made around 3 years ago to get it to compile on Linux under a newer QT version. At some point, I'll be adding further enhancements to the repository and releasing actual versions of Xkoranate-CE (which is a fork/continuation of xkoranate).

I have only a basic knowledge of C++, because I studied a little bit of it in college. But I'm in for testing some things. Is it hard to compile everything? I used to write the program and run in the Dev-Cpp itself, never did it with multiple files. If you can help me with this I would really appreciate.
By the way, I've been looking through the files and I found the "src\eventeditor\scorinatewidget.cpp" one. Around the line 160, there's a comment about "showing only the current matchday results"... I don't know if it would solve the problem but I deleted that specific command, just haven't tested it because of my first paragraph problem

I haven't done an xkoranate build in a few years so I don't remember how hard it was. Qt has Windows instructions on their web site. I found these instructions for Ubuntu which are probably quite similar to what you'd do to build xkoranate on a Mac or some other Linux distro. It might also be possible to compile directly from within Qt Creator.

With more complicated programs, the normal practice is to use makefiles which are text files that tell the compiler what to do. In the case of xkoranate, you almost certainly don't need to edit any makefiles.

[Mantovanian]

I have only a basic knowledge of C++, because I studied a little bit of it in college. But I'm in for testing some things. Is it hard to compile everything? I used to write the program and run in the Dev-Cpp itself, never did it with multiple files. If you can help me with this I would really appreciate.
By the way, I've been looking through the files and I found the "src\eventeditor\scorinatewidget.cpp" one. Around the line 160, there's a comment about "showing only the current matchday results"... I don't know if it would solve the problem but I deleted that specific command, just haven't tested it because of my first paragraph problem

I haven't done an xkoranate build in a few years so I don't remember how hard it was. Qt has Windows instructions on their web site. I found these instructions for Ubuntu which are probably quite similar to what you'd do to build xkoranate on a Mac or some other Linux distro. It might also be possible to compile directly from within Qt Creator.

With more complicated programs, the normal practice is to use makefiles which are text files that tell the compiler what to do. In the case of xkoranate, you almost certainly don't need to edit any makefiles.

I though that recompiling was just a matter of opening the .exe file on the program, opening the .cpp files and compile everything.
This process is extremely harder than I thought. Editing the code is fast and easy, but I still can't compile everything up. The official guides do not help at all with Xkoranate. I had already edited several files but I can't seem to find a way to apply them.
For this reason I'm giving up on my experiment and going back to NSFS.

[Osarius]

Is there a way to export all matchdays in one file on Xkoranate?

The league xml file contains all results.

[Mantovanian]

Is there a way to export all matchdays in one file on Xkoranate?

The league xml file contains all results.

For some reason I never tried this, always thought it was just a way to save table sort criterias and things like that for specific sports. Thanks man!

[Highton Islands]

Xkoronate doesn't work on Mac Catalina, it says that the app needs to be updated!

I believe this is because it is a 32-bit program and Catalina doesn't run them anymore. Will Xkoronate be updating to suit this update?

[Free Republics]

Xkoronate doesn't work on Mac Catalina, it says that the app needs to be updated!

I believe this is because it is a 32-bit program and Catalina doesn't run them anymore. Will Xkoronate be updating to suit this update?

As Xkoranate was released under the GNU General Public License (GPL), which makes it free and open source software that anybody can modify (with that caveat that, if you distribute modified versions of Xkoranate, you are required to release your source code), and as its now been around 2 months since a MacOS update broke compatibility with the most recent version of Xkoranate with no sign of a new version from Commerce Heights, I have started a GitHub repository for Xkoranate Community Edition, a collaborative project to continue development on Xkoranate.

So far, I haven't had time to get a 64 bit Mac build together. I prioritized RPing for the World Cup and now I'm emergency hosting the World Bowl because nobody else was going to bid for it so that's eaten up the vast majority of my NS time of late. Once the World Bowl's out of the way, I should hopefully be able to put some time into the xkoranate continuation.

If you've already upgraded to Catalina, your best option is probably to try and run the Windows version through Wine. I haven't tested that but it'll probably work since xkoranate doesn't seem to use anything too exotic within the Windows API.

The other option right now to run xkoranate would be to download Qt Creator and compile the current commit of xkoranate-CE which is the same code I've been running on Linux for the past few years (0.3.3 with a few minor changes to replace deprecated function calls that were removed from Qt since the last xkoranate version).

[Zwangzug]

So um, twelve years ago this month (shush) I did some simulations with NSFS2 on Jolt. Turns out they were illustrative, so I wanted to have an easy way to link to them as a point of reference.

In words: when using multiplicative style modifiers, attacking styles tend to inflate the margin of victory for good teams, while defensive styles keep things closer. This is especially an issue when goal difference is used as a tiebreaker, but even in terms of total points accumulated.

All teams style 0:

Pos Team P W D L GF GA GD Pts
1 60-pointers 60 41 9 10 157 51 106 132
2 50-pointers 60 41 7 12 133 62 71 130
3 40-pointers 60 33 8 19 109 77 32 107
4 30-pointers 60 33 7 20 109 75 34 106
5 20-pointers 60 15 10 35 70 123 -53 55
6 10-pointers 60 14 11 35 59 116 -57 53
7 Imdilan n00bs 60 3 8 49 38 171 -133 17

Here the 0-point team had a style modifier of -5.

Pos Team P W D L GF GA GD Pts
1 60-pointers 60 45 6 9 152 50 102 141
2 50-pointers 60 38 10 12 110 55 55 124
3 30-pointers 60 29 15 16 99 87 12 102
4 40-pointers 60 23 11 26 85 89 -4 80
5 20-pointers 60 19 12 29 64 90 -26 69
6 10-pointers 60 16 12 32 59 108 -49 60
7 Karelan n00bs 60 4 6 50 22 112 -90 18

Here it had one of +5.

Pos Team P W D L GF GA GD Pts
1 60-pointers 60 47 9 4 179 51 128 150
2 50-pointers 60 42 9 9 170 62 108 135
3 40-pointers 60 35 8 17 132 75 57 113
4 30-pointers 60 22 15 23 107 102 5 81
5 20-pointers 60 21 8 31 92 99 -7 71
6 10-pointers 60 8 15 37 56 132 -76 39
7 Takilan n00bs 60 1 4 55 47 262 -215 7

What if the top seeds change their style? Here it's +5:

Pos Team P W D L GF GA GD Pts
1 Takilan 60-pointers 60 50 5 5 221 62 159 155
2 50-pointers 60 38 10 12 143 60 83 124
3 40-pointers 60 38 7 15 119 70 49 121
4 30-pointers 60 22 10 28 92 104 -12 76
5 20-pointers 60 17 13 30 74 113 -39 64
6 10-pointers 60 11 9 40 57 129 -72 42
7 0-pointers 60 4 6 50 32 200 -168 18

and here it's -5:

Pos Team P W D L GF GA GD Pts
1 50-pointers 60 42 11 7 136 45 91 137
2 Karelan 60-pointers 60 34 19 7 99 37 62 121
3 40-pointers 60 35 11 14 113 64 49 116
4 30-pointers 60 23 16 21 85 75 10 85
5 20-pointers 60 15 16 29 73 95 -22 61
6 10-pointers 60 11 9 40 49 125 -76 42
7 0-pointers 60 4 10 46 41 155 -114 22

(When using additive style modifiers, this effect is much less drastic--it is possible with shutouts to have the margins of victory decrease (what would have been a 2-0 win reduces to 1-0), but otherwise, if a 3-1 game becomes 2-0 or 4-2, it doesn't change either team's GD.)

[Mantovanian]

Did anyone ever find out about the config file for Autoracing on XKoranate? I'm trying to do a fictional race championship using real tracks. The code is:

Code: Select all

<sport version="0.3">
   <name>Auto racing—Qualifying</name>
   <alphabetizedName>Auto racing—Round 1</alphabetizedName>
   <discipline>Auto racing</discipline>
   <event>Qualifying</event>
   <scorinator />
   <paradigm>autoracing</paradigm>
   <paradigmOptions>
      <double type="randCoeff">0.6</double>
      <double type="randOffset">0.6</double>
      <double type="skillCoeff">0.5</double>
      <double type="reliabilityCoeff">0</double>
      <double type="startingGridPenalty">2</double>
      <int type="displayDigits">3</int>
      <int type="tiebreakerDigits">5</int>
      <int type="resultWidth">6</int>
      <string type="totalType">best</string>

Does anyone know what each thing means? randCoeff, randOffset, skillCoeff, reliabilityCoeff, startingGridPenalty, displayDigits, tiebreakerDigits, resultWidth, string type?

[Northwest Kalactin]

Hello all,
After trying to play around with some different scorinaters I found out that you can use the Vilitan Soccer Scorinater on almost any mobile device (IPhone, Android, IPad). So this seems to be a very helpful scorinater to just throw together some results if you need to quickly simulate a domestic cup or an event like that. Apologies if I made this post and this was already known but just throwing this out there.

[Highton Islands]

[...]

So far, I haven't had time to get a 64 bit Mac build together. I prioritized RPing for the World Cup and now I'm emergency hosting the World Bowl because nobody else was going to bid for it so that's eaten up the vast majority of my NS time of late. Once the World Bowl's out of the way, I should hopefully be able to put some time into the xkoranate continuation.

[...]

Hello again, just checking in to see if you have been able to work on upgrading the program. My apologies if I may have missed it as I rarely use the NS forums. If not, there is no pressure, take your time. I am just not very good at these things

[Former Citizens of the Nimbus System]

The Racing Scorinator V2.4
(as used in WGP2 III)

Save to your own Google Drive (recommended) or download and run in Excel (has been known to have problems in the past)
See an error? Leave a comment on the file, make a post on this thread, or drop a telegram to me or Audio!

Previous Version

The latest version of The Racing Scorinator was the one used in WGP2 III; it makes tyre manufacturer stats more easily understandable and integrates them into the RP bonus system, as well as providing customisation for the effects that different variables have on overall car stats. It also slightly rearranges the individual sheets to make it easy to proceed through them sequentially when scorinating!

When you open the scorinator, you’ll see a lot of numbers and formulas all firing at once. Don’t panic! You needn’t concern yourself with any of the formulas. All you have to do is follow the instructions below.

Let me know if anything needs to be added, or is confusing in any way.

Setting up the Scorinator

ENTERING DRIVERS
- Go to the 'Input' tab. Find the orange boxes on the left.
- Insert the information for each driver. Nationality should be in the form of a trigram. 'DRV' is the trigram of the driver's family name. Make sure no two drivers have the same number. Make sure no drivers have the same DRV trigram.
- Enter the driver's RATE abilities.
= 'R' stands for 'Reliability'. Enter a number between 2 and 5.
= 'A' stands for 'Aggression'. Enter a number between 2 and 5.
= 'T' stands for 'Technique'. Enter a number between 2 and 5.
= When the above abilities are added together they should be equal to, or less than, 12. Examples: R4 A4 T4 / R5 A3 T4 / R3.05 A4.1 T4.85
= 'E' stands for 'Experience'. Here you should enter a number between 0 and 20.
- The information should automatically appear on all the relevant sheets.

ENTERING TEAMS
- Go to the 'Input' tab. Find the blue boxes in the middle.
- Enter the team name and nationality. The nationality should be in the form of a trigram.
- If desired, enter one symbol for the team’s tyre manufacturer (more on that later). This is optional. Leaving this blank is fine.
- If desired, enter a hexadecimal code (a # followed by six numbers/letters) for the team’s colour. For example, #ff0000 is bright red. This is optional. Leaving this blank is fine.
- Enter the team's RATE abilities.
= 'R' stands for 'Reliability'. Enter a number between 2 and 5.
= 'A' stands for 'Acceleration'. Enter a number between 2 and 5.
= 'T' stands for 'Turning'. Enter a number between 2 and 5.
= When the above abilities are added together they should be equal to, or less than, 12. EG R4 A4 T4 / R5 A3 T4 / R3.05 A4.1 T4.85
= 'E' stands for 'Experience'. Here you should enter a number between 0 and 5.

ENTERING TYRE MANUFACTURERS
- Using Tyre Manufacturers is optional. You may skip this step entirely if you prefer.
- Go to the 'Input' tab. Find the purple boxes in the middle.
- Enter the name of each tyre manufacturer and a single letter monogram to represent the team. For example, ‘Bridgestone’ would be represented by a ‘B’, Goodyear by a ‘G’ etc.
- Enter the team's RATE abilities. These have changed from the last version.
= Under ‘Reliability’, enter a number between -1 and 1.
= Under ‘Traction’, enter a number between -1 and 1.
= When the above abilities are added together they should be equal to 0. E.G. (R5 T5, R3.5 T6.5, R8 E2)

ENTERING CIRCUITS
- Go to the 'Input' tab. Find the green boxes on the right.
- Enter each circuit's nationality (in the form of a trigram), Circuit Name, Grand Prix Name and a url for the track image.
- Under ‘Type’, leave this section blank unless you’re using the circuit for a non-race event - IE pre-season testing, mid-season testing or a non-championship race (one that won’t count towards the final points total for teams or drivers).
- The greyed 'fastest expected laptime' columns are automated. Ignore these.
- Enter the track's lap record. This should be for a WGPC-speed car.
- Enter the length of the track in kilometres.
- Ignore the '# of laps' column. This is automatic.
- For the circuit's Aggressiveness rating, enter a number in the 'A' column. This number should be between 1 and 9.
- For the circuit's Technical Difficulty, enter a number between 1 and 9. The A and T numbers should add up to ten.
- If the qualifying type is 'Traditional', enter 'Trad'. If it's two-tiered, enter 'TT'. If qualification type is 'One Shot', put 'OS'. For elimination qualifying, enter ‘E’
- Under 'Chance of Rain (%)' enter the percentage chance of an event being wet. This number should be between 1 and 20. 1 means there will be a 1% chance of a wet race and 1.5% chance of a 'changeable' race. 20% means there will be a 20% chance of a wet race and a 30% chance of a 'changeable' race. Use 5% as an average.
- Enter the 'overtaking difficulty' stat for each circuit. This should be a number between 0.1 and 5, with 5 being difficult to overtake (narrow circuit / street circuit) and 0.1 being easy (wide circuit / fast circuit). 2.5 is average.
- Enter the 'Margin for Error' stat for each circuit. This should be a number between 0.1 and 5, with 5 meaning mistakes are punished severely (narrow circuit / street circuit / large gravel traps) and 0.1 meaning driver errors are less costly (wide circuit / circuit with large tarmac runoff areas). 2.5 is average.


GENERAL SEASON INFO
- Just to the right of the circuits you'll see some boxes for general info about the season.
- Enter the 'kilometres per race' on the right hand side. This is 305 for the WGPC. It will probably be lower for WGP2 and lower again for most types of racing. Have a look on wikipedia if you aren't sure.
- For 'Speed of Cars' put '100' if the cars are Formula 1 standard, '90' if the cars are GP2 standard or 85 if they're WGPT3 standard. You would put 45 or so for touring cars, 60 for Formula E cars etc. Again, have a google if you aren't sure.
- If you’d like a team’s colour to be put next to their name, enter a ‘Y’ next to ‘Show Team Colours, else put an ’N’.
- Enter the amount of points awarded per race on the right-hand-side of the yellow fields. If these aren't in descending order then you're doing something very wrong. At the bottom of this list there is an option to allocate points for the driver who is fastest in qualifying.
- There is the option to have limited spots in the race compared to the amount of registered drivers, meaning, for example, that up to thirty different drivers can contest qualifying but with only, say, 24 making the starting grid. Set the amount of drivers to start the race by altering the number next to 'drivers on grid'. For the maximum possible, this should be set to thirty (an uncommonly large number for top-tier open wheel racing)
- To the right of these green and gold boxes there are some red boxes. It's not a good idea to edit these unless you know exactly what you're doing. It's probably okay to lower the 'spin constant' or 'crash constant' numbers if you find races are a little incident-heavy for your liking, but I wouldn't raise or lower any of them by more than a couple of points.

STAT INFLUENCE MODIFIERS
- Below and to the right of the 'General Season Info' boxes you'll find the 'Stat Influence Modifiers' chart, which allows you to adjustments the impact that the different stats that a car's tyres, team and drivers have on its performance.
- The first row, labelled 'RATing', determines the influence that a driver, team and tyre manufacturer have on a car's overall 'R', 'A' and 'T' statistics by multiplying the inputted values of each. Note that a tyre manufacturer's stats are intentionally smaller than a team's, so equal numbers in their boxes will not make their effects equivalent.
- The second row, labelled 'RP bonus', determines the influence that a driver's, team's or tyre manufacturer's user's RP bonus will have on the car's overall RP bonus by multiplying the calculated value of each.
- The third row, labelled 'Experience', determines the influence that a driver's, team's or tyre manufacturer's Experience will have on the car's overall RP bonus by multiplying the inputted value of each.

Scorinating


SCORINATING PRACTICE EVENTS
- Sort out RP bonuses first.
- Go to the 'Scorinate' tab. In the B1 field next to 'raceweek' you should put the current week of the season. For the first event this number would be '1'.
- Enter 'P' (meaning 'Practice') in field B2.
- The results for that practice event should then be displayed. This may take a minute.
- Copy and paste the information displayed into notepad (or similar) and neaten it up.
- Paste into thread in PRE tags.

SCORINATING QUALIFYING EVENTS
- Sort out RP bonuses.
- Go to the 'Scorinate' tab. In the B1 field next to 'raceweek' you should put the week. For the first event, this number should be '1'.
- Enter 'Q' (for 'Qualifying') in field B2.
- Results for qualifying should appear. These will be in the yellow box for most types of qualifying, or the blue box below for Elimination qualifying
- If you’re doing cutoffs, you can copy and paste the orange ‘cutoff text’(cells E2 and F2) directly into a post.
- Copy and paste the information displayed in the yellow boxes into notepad (or similar) and neaten it up.
- Paste into thread
- You'll see a row of purple cells to the left of the yellow box. Highlight these and hit ctrl+c
- Go to the 'Standings' tab and look for the purple fields under the heading 'Starting Grid'. Select the top blank cell (IE for race one this would be cell Q4). Right-click and in the 'paste special' submenu select 'paste values only'. This will set up the starting grid for Sunday's race. It will also set the random number generator back in motion, so your results are now lost in the scorinator. This is why you copy and paste the yellow boxes into notepad first.

SCORINATING RACE EVENTS
- Sort out RP bonuses.
- Go to the 'Starting Grid' tab and check that the cars are in the correct order on the grid by checking the 'Starting Grid' section. If it's race one, then you should find a list of numbers in fields Q4 to Q33.
- Go to the 'Scorinate' tab. In the C1 field next to 'raceweek' you should put the week. For the first event, this number should be '1'.
- Put an 'R' (for 'race') in field C2. Wait a few moments (likely a minute) and the race results should appear in the big cyan and green boxes in columns K to Q.
- Copy and paste the information displayed into notepad (or similar) and neaten it up.
- You'll notice a row of yellow numbers in blue boxes next to the big yellow box. Select all the blue boxes and hit 'ctrl+c'.
- Go to the 'Standings' tab and select the first blank box in the rows of blue boxes. Select the top blank cell (IE for race one this would be cell AM4). Right-click and in the 'paste special' submenu select 'paste values only'. This sets the spreadsheet's random number generator back into motion, so the race's results will be replaced. This is why you copy and paste into notepad first.
- Go back to the 'Scorinate' tab and copy and paste the updated drivers and constructors' championship standings into notepad.
- Neaten up and post in PRE tabs.

GRADING RP BONUS
- Go to the 'RP bonus' tab
- Write the trigram of every RPer in the leftmost column.
- The first column, headed '1' is for all RPs written before the first race. The maximum RP bonus is 10.
- The scorinator runs on a multiplicative/degrading system. RPs graded for the current race are multiplied by 5. Previous races are multiplied by smaller and smaller numbers until they approach '1', in which case they stay the same.
- If you'd prefer to use an additive RP bonus system, then you can simply replace all of the numbers at the top with a '1' in each field.

New for Version 2
The 'Experience' Metric'
The figure entered into the ‘Experience’ field works as a multiplier for RP bonuses. It only affects a driver's performance if they roleplay during the season. A driver with an Experience score of 2.5 would have their RP bonus mulitplied by 1.025. A driver with an experience score of 25 would have their RP bonus multiplied by 1.25.

ELIMINATION QUALIFYING

Elimination qualifying takes place over four sessions. In the first thirty-minute session, each driver tries to record a fast lap. The drivers with the slowest times are eliminated. How many drivers get eliminated depends on how big the grid is. A 20-team grid would see 15 drivers progress to round two, a 26 team grid would see 20 drivers progress. It’s set at 75% of the starting grid.

More drivers are eliminated with each round, until the final round sees the top 25% of the grid duke it out for top spot.

USING IMAGES

In the 'images' tab you can ignore columns A and B, which are automatic.

On the top right there are optional images for posting to the forum. These appear automatically in the 'scorinate' tab in the event's information box.

If you want some cutoff music, enter it below. If you don’t know what a cutoff is, ignore this.

SAFETY CAR OPTIONS
Putting a ‘V’ in cell AV8 in the Input tab will enable the Virtual Safety Car, whereas putting an ‘R’ in the cell will enable the Real Safety Car. Here are the differences between the two:

THE VIRTUAL SAFETY CAR
In the event of a bad crash, a virtual safety car is deployed, during which time all drivers must keep to a slow laptime (at minimum about 120% of the circuit's fastest lap, meaning drivers would be forced to complete laps at 75 seconds per lap for a circuit which has a fastest lap of 60 seconds. This will be slower for wet races)

THE REAL SAFETY CAR
In the event of a bad crash, a safety car is deployed. All drivers will queue up behind the safety car. Lapped drivers will begin to un-lap themselves so they can join on to the back of the train[/pre]

Signups Templates
These templates contain the minimum information required. You can add various RP stuff to this if you want.

DRIVER SIGNUPS

Driver Name:
Name Trigram:
Nationality Trigram:
Preferred Number:
Reliability (Between 2 and 5):
Aggression (Between 2 and 5):
Technique (Between 2 and 5):
R/A/T ratings should add up to a maximum of 12.
Experience (Between 0 and 25):

TEAM SIGNUPS

Team Name:
Team Nationality (Trigram):
Reliability (Between 2 and 5):
Acceleration (Between 2 and 5):
Turning:  (Between 2 and 5):
R/A/T ratings should add up to a maximum of 12.
Experience: (Between 0 and 10)

TYRE MANUFACTURER SIGNUPS (Optional)

Manufacturer Name:
Monogram:
Reliability (Between -1 and 1)
Traction (Between -1 and 1)

Reliability and Traction ratings should add up to no more than 0

CIRCUIT SIGNUPS

Circuit Name:
Grand Prix Name:
Track Image:
Lap Record (F1/WGPC Car):
Track Length (km):
Qualifying Type (Elimination, Traditional, One-Shot or Two-Tiered):
Chance of being a wet race (1%-20%)
Overtaking difficulty (0.1 - 5. 0.1 is easy, 5 is difficult):
Margin for Error (0.1 - 5. 0.1 is forgiving, 5 is treacherous):

Aggressiveness (1-10):
Technical Difficulty (1-10):
(Both these numbers should add up to 10)

Limitations

Thing that might break the scorinator				Workaround
A driver or team's 'experience' rating goes to more		Don't put a driver or team's 'experience' rating to more than three
than three decimal places.					decimal places.

Drivers appear to be racing despite not qualifying, or		When copying the starting grid to the Standings tab,
drivers with blank names are shown in the results.		make sure you copy *ALL* the purple fields over, and
								remember to right-click and 'paste special->paste values only

Removing a driver during the season				You will need to copy and [paste special]>[paste values only]
								THE ENTIRE ROW of driver info on the Standings and Bonus 
								sheet to one of the empty rows below the roster of drivers on that
								sheet. This should ensure their points still show up in
								the drivers/teams championship standings.

Drivers switching teams during the season			This is a fart. I recommend you instigate a 'one team per season'
								rule for drivers.

A race having more than 98 laps					Don't have races that last for more than 98 laps.

Having more than 30 drivers on the grid.			Don't have more than 30 drivers on the grid.

Lots of 'N/A' fields in the yellow boxes 			It might be because you have a driver or team with a very long name.
in the 'scorinate' tab 						Try putting a larger number in the 'character limit' box in the
								'scorinate' tab.

Accidentally deleting or overwriting a cell			Good luck!
and not being able to find which one it was

Everything just says ‘#REF’					Make sure the team names are spelled correctly, both next to the driver
										and in the ’Teams’ box.

Lots of 'N/A' fields or lots of ERROR! fields.			Could be anything. Contact me.

FAQ
Q: Is this the WGPC scorinator?
A: More or less. The WGPC17 scorinator was very similar.

Q: Is this scorinator as buggy as previous editions?
A: Probably. There will be bugs. Let me know if you see one.

Q: Is this scorinator balanced?
A: I can imagine no situation wherein someone could properly balance the 'R' metric with the 'A' and 'T' metrics. 'A' and 'T' compliment each other, so they're fine, but 'R' used to be a little under-powered. It might be over-powered in this version or it might still be under-powered. I don't know. If you're doing some sort of statistics or maths thesis at university and have a spare couple of years you might want to have a look at it.

Q: This is a bit overwhelming...
A: It is a little, yes, I suppose. You can make it easier by ignoring anything that's in a grey box. The bits that you'll need to enter data into are generally colourful.

Q: Can I make changes to the formulas?
A: Sure, go ahead.

Q: SHOULD I make changes to this sheet?
A: If you know what you're doing then sure, why not?

Q: I haven't used any spreadsheets before, actually.
A: Then no. You should probably change nothing.

Q: I found an error in the sheet...
A: Awesome! Please TG me and leave a note in the scorinators thread

Q: What do the 'RATE' things do?
A: Drivers take their 'A' skills from their own Aggression stats, their car's Acceleration stats and half of their tyre's Traction stats and multiply them by the course's Aggressiveness stats. It's the same with the Technique/Turning/half of Traction again/Technical Difficulty stats. The reliability stat controls how often they crash or spin or destroy their car, how well they do in the wet and also governs things like how many flying laps they can attempt in practice and qualifying.

Q: In previous editions of WGPC the winner was always a driver and/or team that min-maxed their ACR/RATE/Whatever you’re calling it these days. Does that still happen?
A: Maybe? I don’t know. Here’s what I know:

Advantages of Low R and High A/T Builds (eg R/A/T skills of 2/5/5)
Your car will be faster than other cars
Your peak performance in qualifying will be faster than everyone else’s
If you’re a little lucky, you’ll be very, very fast.

Disadvantages of Low R and High A/T Builds (eg R/A/T skills of 2/5/5)
Your chances of having a minor accident during the race increase.
When you have a minor accident, you’ll lose more time than other drivers
Your pit-stops are longer
Your chances of retiring from a race increase
You get fewer attempts at qualifying.
Your chances of not setting a time at all in qualifying increase
In general, your results may seem to be random.
Your chances of crashing on wet tracks increase

Q: You've only just released this scorinator. Barely anyone else has used it. How is it possible that you have 'frequently asked questions'
A: How is it possible that your face has frequently asked questions, you mean.

Q: I pressed a button and all the results changed and it's messed everything up!
A: Don't press a button. The moment you scorinate you should:
(a) Immediately copy and paste the results into notepad.
(b) After qualifying you should immediately C+P the final qualifying positions into the racegrid and, after the race, you should immediately copy and paste the results into the results grid.
If you do anything between (a) and (b) then you will lose your data.

Q: I’m getting a load of errors. What did I do wrong?
A: The most common mistake people have made is that there’s a difference between the name of a team as listed next to the driver and as listed in the ‘Teams’ section. Check that.

Next, check you haven’t accidentally deleted or overwritten a cell. This happens from time to time.

If results aren’t showing up, try increasing the character limits (C12, D12 and D11 in the Scorinate tab.

Q: Can a team change drivers in the middle of a seasons?
A: Yes, that's not too much of a problem. Simply go to their row in the Standings tab, highlight the entirety of a driver's row, hit Ctrl+C, and then go to the first free spot and right click > paste special > paste values only. Then enter the new driver's information where the old driver's info used to be in the 'Input' tab. All that's changed is that you'll have to manually add the old driver's points-scored into the constructor's championship thing when you post it.

Q: Can a driver drive for two teams during a season.
A: If you don't mind that you'd have to do the standings manually then sure.

[Former Citizens of the Nimbus System]

The Racing Scorinator V2.5.6

V2.5.5
V2.5.4
V2.5.3
V2.5.2
V2.5.1
V2.5

Save to your own Google Drive (recommended) or download and run in Excel (has been known to have problems in the past)
See an error? Leave a comment on the file, make a post on this thread, or drop a telegram to me or Audio!

Previous Version

The latest version of the Racing Scorinator adds a plethora of new features, including separate engine manufacturers, options to turn tyres and engines on and off, entities run by two users and, by popular demand, the option to not output positions at quarter-race distances.

When you open the scorinator, you’ll see a lot of numbers and formulas all firing at once. Don’t panic! You needn’t concern yourself with any of the formulae. All you have to do is follow the instructions below.

Let me know if anything needs to be added or is confusing in any way.

Setting up the Scorinator

ENTERING DRIVERS
- Go to the 'Input' tab. Find the orange boxes on the left.
- Insert the information for each driver. Nationality should be in the form of a trigram; if a driver is being RPed by two users, enter their shared trigram instead (see 'Grading RP Bonus'). 'DRV' is the trigram of the driver's family name. Make sure no two drivers have the same number. Make sure no drivers have the same DRV trigram.
- Enter the driver's RATE abilities.
= 'R' stands for 'Reliability'. Enter a number between 2 and 5.
= 'A' stands for 'Aggression'. Enter a number between 2 and 5.
= 'T' stands for 'Technique'. Enter a number between 2 and 5.
= When the above abilities are added together they should be equal to, or less than, 12. Examples: R4 A4 T4 / R5 A3 T4 / R3.05 A4.1 T4.85
= 'E' stands for 'Experience'. Here you should enter a number between 0 and 20.
- The information should automatically appear on all the relevant sheets.

ENTERING TEAMS
- Go to the 'Input' tab. Find the blue boxes in the middle.
- Enter the team name and nationality. The nationality should be in the form of a trigram. If a team is being RPed by two users, enter their shared trigram instead (see 'Grading RP Bonus').
- If desired, enter one symbol for the team’s tyre manufacturer and another for the team’s engine manufacturer (more on that later). These are optional; leaving them blank is fine.
- If desired, enter a hexadecimal code (a # followed by six numbers/letters) for the team’s colour. For example, #ff0000 is bright red. This is optional. Leaving this blank is fine.
- Enter the team's RATE abilities.
= 'R' stands for 'Reliability'. Enter a number between 2 and 5.
= 'A' stands for 'Acceleration'. Enter a number between 2 and 5.
= 'T' stands for 'Turning'. Enter a number between 2 and 5.
= When the above abilities are added together they should be equal to, or less than, 12. EG R4 A4 T4 / R5 A3 T4 / R3.05 A4.1 T4.85
= 'E' stands for 'Experience'. Here you should enter a number between 0 and 5.

ENTERING TYRE MANUFACTURERS
- Using Tyre Manufacturers is optional. If you’d prefer not to use Tyre Manufacturers, head to the right of the 'Input' tab and enter 'N' next to the cell reading 'Use Tyres? (Y/N)'.
- Go to the 'Input' tab. Find the purple boxes in the middle.
- Enter the name of each tyre manufacturer.
- Enter the tyre manufacturer name and nationality. The nationality should be in the form of a trigram. If a tyre manufacturer is being RPed by two users, enter their shared trigram instead (see 'Grading RP Bonus').
- Enter a single letter monogram to represent the tyre manufacturer. For example, ‘Bridgestone’ would be represented by a ‘B’, Goodyear by a ‘G’ etc.
- Enter the tyre manufacturer's RATE abilities.
= Under ‘Reliability’, enter a number between -1 and 1.
= Under ‘Traction’, enter a number between -1 and 1.
= When the above abilities are added together they should be equal to 0. E.G. (R1 T-1, R-0.5 T0.5, R0.83 E-0.83)

ENTERING ENGINE MANUFACTURERS
- Using Engine Manufacturers is optional. If you’d prefer not to use Engine Manufacturers, head to the right of the 'Input' tab and enter 'N' next to the cell reading 'Use Engines? (Y/N)'.
- Go to the 'Input' tab. Find the yellow boxes in the middle.
- Enter the name of each engine manufacturer.
- Enter the tyre manufacturer name and nationality. The nationality should be in the form of a trigram. If an engine manufacturer is being RPed by two users, enter their shared trigram instead (see 'Grading RP Bonus').
- Enter a single letter monogram to represent the engine manufacturer. For example, ‘Mercedes’ would be represented by an ‘M’, Honda by an ‘H’ etc.
- Enter the team's RATE abilities.
= Under ‘Reliability’, enter a number between -1 and 1.
= Under ‘Actuation’, enter a number between -1 and 1.
= Under ‘Tare’, enter a number between -1 and 1.
= When the above abilities are added together they should be equal to 0. E.G. (R1 A-0.5 T-0.5, R-0.2 A0.4 T-0.2)

ENTERING CIRCUITS
- Go to the 'Input' tab. Find the green boxes on the right.
- Enter each circuit's nationality (in the form of a trigram), Circuit Name, Grand Prix Name and a url for the track image.
- Under ‘Type’, leave this section blank unless you’re using the circuit for a non-race event - IE pre-season testing, mid-season testing or a non-championship race (one that won’t count towards the final points total for teams or drivers).
- The greyed 'fastest expected laptime' columns are automated. Ignore these.
- Enter the track's lap record. This should be for a WGPC-speed car.
- Enter the length of the track in kilometres.
- Ignore the '# of laps' column. This is automatic.
- For the circuit's Aggressiveness rating, enter a number in the 'A' column. This number should be between 1 and 9.
- For the circuit's Technicality, enter a number between 1 and 9. The A and T numbers should add up to 10.
- If the qualifying type is 'Traditional', enter 'Trad'. If it's two-tiered, enter 'TT'. If qualification type is 'One Shot', put 'OS'. For elimination qualifying, enter ‘E’
- Under 'Chance of Rain (%)' enter the percentage chance of an event being wet. This number should be between 1 and 20. 1 means there will be a 1% chance of a wet race and 1.5% chance of a 'changeable' race. 20% means there will be a 20% chance of a wet race and a 30% chance of a 'changeable' race. Use 5% as an average.
- Enter the 'Overtaking Difficulty' stat for each circuit. This should be a number between 0.1 and 5, with 5 being difficult to overtake (narrow circuit / street circuit) and 0.1 being easy (wide circuit / fast circuit). 2.5 is average.
- Enter the 'Error Punishment' stat for each circuit. This should be a number between 0.1 and 5, with 5 meaning mistakes are punished severely (narrow circuit / street circuit / large gravel traps) and 0.1 meaning driver errors are less costly (wide circuit / circuit with large tarmac runoff areas). 2.5 is average.


GENERAL SEASON INFO
- Just to the right of the circuits you'll see some boxes for general info about the season.
- Enter the 'kilometres per race' on the right hand side. This is 305 for the WGPC. It will probably be lower for WGP2 and lower again for most types of racing. Have a look on Wikipedia if you aren't sure.
- For 'Speed of Cars' put '100' if the cars are Formula 1 standard, '90' if the cars are GP2 standard or 85 if they're WGPT3 standard. You would put 45 or so for touring cars, 60 for Formula E cars etc. Again, have a google if you aren't sure.
- If you’d like team’s colours to be included in race results and championship standings, enter a ‘Y’ next to ‘Show Team Colours, else put an ’N’.
- Enter the amount of points awarded per race on the right-hand-side of the yellow fields. If these aren't in descending order then you're doing something very wrong. At the bottom of this list there is an option to allocate points for the driver who is fastest in qualifying.
- There is the option to have limited spots in the race compared to the amount of registered drivers, meaning, for example, that up to thirty different drivers can contest qualifying but with only, say, 24 making the starting grid. Set the amount of drivers to start the race by altering the number next to 'drivers on grid'. For the maximum possible, this should be set to thirty (an uncommonly large number for top-tier open wheel racing)
- To the right of these green and gold boxes there are some red boxes. It's not a good idea to edit these unless you know exactly what you're doing. It's probably okay to lower the 'spin constant' or 'crash constant' numbers if you find races are a little incident-heavy for your liking, but I wouldn't raise or lower any of them by more than a couple of points.

ENABLING/DISABLING QUARTER-RACE POSITIONS
- Below the 'General Season Info' boxes you'll see a grey box entitled 'Show positions at 1/4 race distances? (Y/N)'. The box next to it (in which, predictably, you may enter either 'Y' or 'N') allows you to determine whether the overall positions of cars are shown at points 1/4, 1/2 and 3/4 of the way through the race.
- Showing these shifts in position can provide some extra inspiration for roleplaying, help to align the roleplay of different users and inspire collaborations as drivers and teams battle throughout the race. On the other hand, not doing so can help to smooth over some of the less plausible aspects of the scorination and give roleplayers more creative freedom. In the end, it's your choice!

ENABLING/DISABLING TYRES AND ENGINES
- Below the 'Show positions at 1/4 race distances? (Y/N)' boxes you'll see a purple box and a yellow box. These boxes allow you to turn the scorinator's use of tyre and engine manufacturers on and off.
- The first box, in purple and labelled 'Use Tyres? (Y/N)' allows you to turn on and off tyre manufacturers. Enter 'Y' if you want the scorinator to use them and 'N' if you don't.
- The first box, in yellow and labelled 'Use Engines? (Y/N)' allows you to turn on and off engine manufacturers. Enter 'Y' if you want the scorinator to use them and 'N' if you don't.


STAT INFLUENCE MODIFIERS
- Below and to the right of the 'General Season Info' boxes you'll see the 'Stat Influence Modifiers' chart, which allows you to adjust the impact that the different stats that a car's engine, tyres, team and driver have on its performance.
- The first row, labelled 'RATing', determines the influence that a driver, team, tyre manufacturer or engine manufacturer will have on a car's overall 'R', 'A' and 'T' statistics by multiplying the inputted values of each. Note that a tyre or an engine manufacturers' stats are intentionally smaller than a team's, so equal numbers in their boxes will not make their effects equivalent.
- The second row, labelled 'RP bonus', determines the influence that a driver's, team's, tyre manufacturer or engine manufacturer's user's RP bonus will have on the car's overall RP bonus by multiplying the calculated value of each.
- The third row, labelled 'Experience', determines the influence that a driver's, team's, tyre manufacturer or engine manufacturer's Experience will have on the car's overall RP bonus by multiplying the inputted value of each.

Scorinating


SCORINATING PRACTICE EVENTS
- Sort out RP bonuses first.
- Go to the 'Scorinate' tab. In the B1 field next to 'raceweek' you should put the current week of the season. For the first event this number would be '1'.
- Enter 'P' (meaning 'Practice') in field B2.
- The results for that practice event should then be displayed. This may take a minute.
- Copy and paste the information displayed into notepad (or similar) and neaten it up.
- Paste into thread in PRE tags.

SCORINATING QUALIFYING EVENTS
- Sort out RP bonuses.
- Go to the 'Scorinate' tab. In the B1 field next to 'raceweek' you should put the week. For the first event, this number should be '1'.
- Enter 'Q' (for 'Qualifying') in field B2.
- Results for qualifying should appear. These will be in the yellow box for most types of qualifying, or the blue box below for Elimination qualifying
- If you’re doing cutoffs, you can copy and paste the orange ‘cutoff text’(cells E2 and F2) directly into a post.
- Copy and paste the information displayed in the yellow boxes into notepad (or similar) and neaten it up.
- Paste into thread.
- You'll see a row of purple cells to the left of the yellow box. Highlight these and hit ctrl+c
- Go to the 'Standings' tab and look for the purple fields under the heading 'Starting Grid'. Select the top blank cell (IE for race one this would be cell Q4). Right-click and in the 'paste special' submenu select 'paste values only'. This will set up the starting grid for Sunday's race. It will also set the random number generator back in motion, so your results are now lost in the scorinator. This is why you copy and paste the yellow boxes into notepad first.

SCORINATING RACE EVENTS
- Sort out RP bonuses.
- Go to the 'Standings' tab and check that the cars are in the correct order on the grid by checking the 'Starting Grid' section. If it's race one, then you should find a list of numbers in fields U4 to U33.
- Go to the 'Scorinate' tab. In the C1 field next to 'raceweek' you should put the week. For the first event, this number should be '1'.
- Put an 'R' (for 'race') in field C2. Wait a few moments (likely a minute) and the race results should appear in the big cyan and green boxes in columns K to Q.
- Copy and paste the information displayed into notepad (or similar) and neaten it up.
- You'll notice a row of yellow numbers in blue boxes next to the big yellow box. Select all the blue boxes and hit 'ctrl+c'.
- Go to the 'Standings' tab and select the first blank box in the rows of blue boxes. Select the top blank cell (IE for race one this would be cell AM4). Right-click and in the 'paste special' submenu select 'paste values only'. This sets the spreadsheet's random number generator back into motion, so the race's results will be replaced. This is why you copy and paste into notepad first.
- Go back to the 'Scorinate' tab and copy and paste the updated drivers and constructors' championship standings into notepad.
- Neaten up and post.

GRADING RP BONUS
- Go to the 'RP bonus' tab
- Write the trigram of every RPer in the column labelled 'Trigram'.
- If two RPers would like to RP for a single driver, team, tyre manufacturer and/or engine manufacturer, write their trigrams in a row of the 'User 1' and 'User 2' columns under 'Bi-National Entities' and then add a new trigram next to them in the column labelled 'Trigram'. Make sure you also enter the users' trigrams separately, even if they aren't RPing for anything else. Then enter the new trigram in the 'Input' tab for drivers, teams, tyre manufacturers and/or engine manufacturers that they are RPing together. The scorinator will average their RP bonuses and apply them to entities under the new trigram without you needing to do anything else.
- The first column, headed '1' is for all RPs written before the first race. The maximum RP bonus is 10.
- The scorinator runs on a multiplicative/degrading system. RPs graded for the current race are multiplied by 5. Previous races are multiplied by smaller and smaller numbers until they approach '1', in which case they stay the same.
- If you'd prefer to use an additive RP bonus system, then you can simply replace all of the numbers at the top with a '1' in each field.

New for Version 2
The 'Experience' Metric'
The figure entered into the ‘Experience’ field works as a multiplier for RP bonuses. It only affects a driver's performance if they roleplay during the season. A driver with an Experience score of 2.5 would have their RP bonus mulitplied by 1.025. A driver with an experience score of 25 would have their RP bonus multiplied by 1.25.

ELIMINATION QUALIFYING

Elimination qualifying takes place over four sessions. In the first thirty-minute session, each driver tries to record a fast lap. The drivers with the slowest times are eliminated. How many drivers get eliminated depends on how big the grid is. A 20-team grid would see 15 drivers progress to round two, a 26 team grid would see 20 drivers progress. It’s set at 75% of the starting grid.

More drivers are eliminated with each round, until the final round sees the top 25% of the grid duke it out for top spot.

Elimination qualifying results are visible in the blue box below the regular box used for qualifying.

USING IMAGES

In the 'images' tab you can ignore columns A and B, which are automatic.

On the top right there are optional images for posting to the forum. These appear automatically in the 'scorinate' tab in the event's information box.

If you want some cutoff music, enter it below. If you don’t know what a cutoff is, ignore this.

SAFETY CAR OPTIONS
Putting a ‘V’ in cell AV8 in the Input tab will enable the Virtual Safety Car, whereas putting an ‘R’ in the cell will enable the Real Safety Car. Here are the differences between the two:

THE VIRTUAL SAFETY CAR
In the event of a bad crash, a virtual safety car is deployed, during which time all drivers must keep to a slow laptime (at minimum about 120% of the circuit's fastest lap, meaning drivers would be forced to complete laps at 75 seconds per lap for a circuit which has a fastest lap of 60 seconds. This will be slower for wet races)

THE REAL SAFETY CAR
In the event of a bad crash, a safety car is deployed. All drivers will queue up behind the safety car. Lapped drivers will begin to un-lap themselves so they can join on to the back of the train.

Signups Templates
These templates contain the minimum information required. You can add various RP stuff to this if you want.

DRIVER SIGNUPS

Driver Name:
Name Trigram:
Nationality Trigram:
Preferred Number:
Reliability (Between 2 and 5):
Aggression (Between 2 and 5):
Technique (Between 2 and 5):
R/A/T ratings should add up to a maximum of 12.
Experience (Between 0 and 25):

TEAM SIGNUPS

Team Name:
Team Nationality (Trigram):
Reliability (Between 2 and 5):
Acceleration (Between 2 and 5):
Turning (Between 2 and 5):
R/A/T ratings should add up to a maximum of 12.
Experience: (Between 0 and 10)

TYRE MANUFACTURER SIGNUPS (Optional)

Manufacturer Name:
Manufacturer Nationality (Trigram):
Monogram:
Reliability (Between -1 and 1):
Traction (Between -1 and 1):
R & T ratings should add up to no more than 0.
Experience: (Between 0 and 10)

ENGINE MANUFACTURER SIGNUPS (Optional)

Manufacturer Name:
Manufacturer Nationality (Trigram):
Monogram:
Reliability (Between -1 and 1):
Actuation (Between -1 and 1):
Tare (Between -1 and 1):
R/A/T ratings should add up to no more than 0.
Experience: (Between 0 and 10)

CIRCUIT SIGNUPS

Circuit Name:
Grand Prix Name:
Circuit Nationality (Trigram):
Track Image:
Lap Record (F1/WGPC Car):
Track Length (km):
Qualifying Type (Elimination, Traditional, One-Shot or Two-Tiered):
Chance of being a wet race (1%-20%)
Overtaking Difficulty (0.1 - 5. 0.1 is easy, 5 is difficult):
Error Punishment (0.1 - 5. 0.1 is forgiving, 5 is treacherous):

Aggressiveness (1-10):
Technicality (1-10):
(Both these numbers should add up to 10)

Limitations

Thing that might break the scorinator				Workaround
A driver or team's 'experience' rating goes to more		Don't put a driver or team's 'experience' rating to more than three
than three decimal places.					decimal places.

Drivers appear to be racing despite not qualifying, or		When copying the starting grid to the Standings tab,
drivers with blank names are shown in the results.		make sure you copy *ALL* the purple fields over, and
								remember to right-click and 'paste special->paste values only

Removing a driver during the season				You will need to copy and [paste special]>[paste values only]
								THE ENTIRE ROW of driver info on the Standings and Bonus 
								sheet to one of the empty rows below the roster of drivers on that
								sheet. This should ensure their points still show up in
								the drivers/teams championship standings.

Drivers switching teams during the season			This is a fart. I recommend you instigate a 'one team per season'
								rule for drivers.

A race having more than 98 laps					Don't have races that last for more than 98 laps.

Having more than 30 drivers on the grid.			Don't have more than 30 drivers on the grid.

Lots of 'N/A' fields in the yellow boxes 			It might be because you have a driver or team with a very long name.
in the 'scorinate' tab 						Try putting a larger number in the 'character limit' box in the
								'scorinate' tab.

Accidentally deleting or overwriting a cell			Good luck!
and not being able to find which one it was

Everything just says ‘#REF’					Make sure the team names are spelled correctly, both next to the driver
								and in the ’Teams’ box.

Certain races aren't scorinating properly			Make sure to enter the trigrams for all of your circuits into the RP Bonus
								sheet.

Lots of 'N/A' fields or lots of ERROR! fields.			Could be anything. Contact me.

FAQ
Q: Is this the WGPC scorinator?
A: More or less. The WGPC17 scorinator was very similar.

Q: Is this scorinator as buggy as previous editions?
A: Probably. There will be bugs. Let me know if you see one.

Q: Is this scorinator balanced?
A: I can imagine no situation wherein someone could properly balance the 'R' metric with the 'A' and 'T' metrics. 'A' and 'T' complement each other, so they're fine, but 'R' used to be a little under-powered. It might be over-powered in this version or it might still be under-powered. I don't know. If you're doing some sort of statistics or maths thesis at university and have a spare couple of years you might want to have a look at it.

Q: This is a bit overwhelming...
A: It is a little, yes, I suppose. You can make it easier by ignoring anything that's in a grey box. The bits that you'll need to enter data into are generally colourful.

Q: Can I make changes to the formulas?
A: Sure, go ahead.

Q: SHOULD I make changes to this sheet?
A: If you know what you're doing then sure, why not?

Q: I haven't used any spreadsheets before, actually.
A: Then no. You should probably change nothing.

Q: I found an error in the sheet...
A: Awesome! Please TG me and leave a note in the scorinators thread

Q: What do the 'RATE' things do?
A: Drivers take their 'A' skills from their own Aggression stat, their car's Acceleration stat, half of their tyres' Traction stat and their engine's Actuation stat and multiply them by the course's Aggressiveness stat. It's the same with the Technique/Turning/half of Traction again/Tare/Technicality stat. The reliability stat controls how often they crash or spin or destroy their car, how well they do in the wet and also governs things like how many flying laps they can attempt in practice and qualifying.

Q: In previous editions of WGPC the winner was always a driver and/or team that min-maxed their ACR/RATE/Whatever you’re calling it these days. Does that still happen?
A: Maybe? I don’t know. Here’s what I know:

Advantages of Low R and High A/T Builds (eg R/A/T skills of 2/5/5)
Your car will be faster than other cars
Your peak performance in qualifying will be faster than everyone else’s
If you’re a little lucky, you’ll be very, very fast.

Disadvantages of Low R and High A/T Builds (eg R/A/T skills of 2/5/5)
Your chances of having a minor accident during the race increase.
When you have a minor accident, you’ll lose more time than other drivers
Your pit-stops are longer
Your chances of retiring from a race increase
You get fewer attempts at qualifying.
Your chances of not setting a time at all in qualifying increase
In general, your results may seem to be random.
Your chances of crashing on wet tracks increase

Q: You've only just released this scorinator. Barely anyone else has used it. How is it possible that you have 'frequently asked questions'
A: How is it possible that your face has frequently asked questions, you mean.

Q: I pressed a button and all the results changed and it's messed everything up!
A: Don't press a button. The moment you scorinate you should:
(a) Immediately copy and paste the results into notepad.
(b) After qualifying you should immediately C+P the final qualifying positions into the racegrid and, after the race, you should immediately copy and paste the results into the results grid.
If you do anything between (a) and (b) then you will lose your data.

Q: I’m getting a load of errors. What did I do wrong?
A: The most common mistake people have made is that there’s a difference between the name of a team as listed next to the driver and as listed in the ‘Teams’ section. Check that.

Next, check you haven’t accidentally deleted or overwritten a cell. This happens from time to time.

If results aren’t showing up, try increasing the character limits (C12, D12 and D11 in the Scorinate tab.

Q: Can a team change drivers in the middle of a seasons?
A: Yes, that's not too much of a problem. Simply go to their row in the Standings tab, highlight the entirety of a driver's row, hit Ctrl+C, and then go to the first free spot and right click > paste special > paste values only. Then enter the new driver's information where the old driver's info used to be in the 'Input' tab. All that's changed is that you'll have to manually add the old driver's points-scored into the constructor's championship thing when you post it.

Q: Can a driver drive for two teams during a season.
A: If you don't mind that you'd have to do the standings manually then sure.

- Fixed a display issue by which positional points would show in race results for non-finishing drivers.
- Fixed a display issue by which the safety car readout would list laps after the end of the race.

Thank you to Northwest Kalactin for bringing these issues to our attention!

- Adjusted some formulae to make Qualifying times more consistent.

- Fixed an issue by which some of the cells in the 'Total' columns on the Input sheet were previously adding Experience to their sums. Thank you to Filindostan for bringing this issue to our attention!
- Adjusted some formatting for consistency and clarity; in particular, moved the 'Total' columns on the Input sheet to the left of the 'Experience' columns and added a 'Total' column for combined track Aggressiveness and Technicality.

- Fixed an issue by which Practice and Qualifying results were showing team names rather than driver names. Thank you to Vdara for bringing this issue to our attention!
- Adjusted some formatting in the Scorinate sheet for standardisation and to make results easier to copy and read.

- Added interaction between dual-national entities and single-nation entities for home race bonusses.
-- Bi-national drivers and teams now receive a home race bonus of half the regular influence when racing at a circuit in one of their nations.
-- Bi-national circuits now confer a home race bonus of half the regular influence on drivers and teams attached to one of their nations.

- Fixed an issue by which Tyre and Engine stats were being applied even if they were turned off. Thank you to Vilita and Turori for bringing this issue to our attention!

[Tioguldos]

Hi all. I'm new to NS and of course also to NS Sports. I'm designing my Association Football league and decided to create my own Scorinator using MS Office Excel. I've been working for the past two days and I've managed to create something that works. I guess. But I have a lot of questions:

* I'm using binomial distribution to simulate each team's goals. Should I be using Poisson? Would it be ok to scorinate an international match with binomial distribution? Also,

* Would it be ok if I hosted a tournament using my own scorinator?

* If yes, what do you think about my probability modifiers? Should I change them?

Here you have the file:
https://drive.google.com/file/d/1R8qQPNezDOzlOcrk_BmpzpHc8YN8muNp/view?usp=sharing

I've explained everything in there, but if something is not clear, feel free to ask me.

My priority is to improve it as much as possible. Any criticism is welcome. I can gather statistics and publish graphs for different variables if that helps you draw better conclusions.

Thanks for your time.

[Zwangzug]

Hi, welcome! I'm interested in checking your code out but I got the "Access Denied" link from Google Drive--could you change it so anyone with the link can view?

[Tioguldos]

It should work. Please let me know if you are still denied access, in that case I can upload it to another site.

[Zwangzug]

It should work. Please let me know if you are still denied access, in that case I can upload it to another site.

It works now, thanks. I'm playing around with it!

Where are the results supposed to output? I'm getting "VALUE!" errors in rows 9 and 11.

[Tioguldos]

Where are the results supposed to output?

The results output in K9 and K11. K9 is the amount of goals of the local team and K11 the away team.

I'm getting "VALUE!" errors in rows 9 and 11.

Oops. It was an error caused by the format change. It should work normally now. Sorry!