There’s Syntax errors in this

Gotcha. The “syntax errors” aren’t really bugs in the code logic—they’re artifacts from copying code out of the PDF. Three things in the PDF will break Apps Script/JS if pasted as-is:

1. Encoding garbage (e.g. stray Â, smart quotes, fancy dashes) inside comments/strings
   You can see those right at the top: “clamp to ±0.005” and odd hyphen/quote sequences later (e.g. return‑oriented). (script.free.pdf) (script.free.pdf)

2. Injected page markers right in the middle of functions
   Lines like <PARSED TEXT FOR PAGE: …> and [L123] get spliced into the code—any one of those will cause a syntax error. Example: a pushPick(...) call is split by a page marker mid-function. (script.free.pdf)

3. Truncated chunks that make braces/parentheses look “unbalanced”
   The source actually defines REASON_TABLE(...) correctly; but if you copy a region that includes a page splice, your pasted snippet will be missing a closing )/}. (script.free.pdf)

Quick fix (safe cleanup steps)

Do these find-and-replace passes before pasting into Apps Script:

• Remove page artifacts
  • Find: ^<PARSED TEXT FOR PAGE:.*$ → Replace: (empty) (Regex, multiline)
  • Find: ^$$L\d+$$\s* → Replace: (empty) (Regex, multiline)
• Normalize quotes/dashes
  • Find: [\u2018\u2019] → '
  • Find: [\u201C\u201D] → "
  • Find: [\u2010\u2011\u2012\u2013\u2014\u2212] → -
  • Find: Â → (empty)
  • Optionally: replace ± with +/- if you prefer pure ASCII
• After cleaning, use your editor’s “Format Document” and run a bracket-matching check to confirm balanced { } ( ).

If you want a one-shot script (run locally)

In VS Code’s Replace panel (Regex on):

1. Remove page lines:
   • Find: ^<PARSED TEXT FOR PAGE:.*\r?\n? → Replace: (empty)
2. Strip [L123] counters:
   • Find: ^$$L\d+$$\s* → Replace: (empty)
3. Quote/dash fixes as above.

After this, the file should parse. For reference, the REASON_TABLE(...) signature you want to keep starts like this (don’t let any page markers cut through it):

js
function REASON_TABLE(nameA, nameB, oddsA, oddsB, serverFirst){
  try {
    var validation = validateBothPlayersData('', '');
    if (!validation.valid) {
      return [
        ['ERROR', validation.errorMsg],
        // ...
      ];
    }
    // ...

…and it should end with matching } for the try {} and the function itself (if your paste is missing one, it’s because a page splice ate lines). (script.free.pdf)

If you hit a specific line/column error even after cleanup, drop me the exact message and I’ll pinpoint the single offending character and give you the patched line.