• The UDF must be written as one or more lines.
  
• The UDF is expected to finish in a reasonable time, e.g. if it gets started when the challenge opens, it's expected to be finished by the
  time the challenge closes even on a somewhat slow computer. The UDF has to be valid during the period that the challenge runs.
  
• You can submit scores as often as you want until the deadline, there's no reason to wait until the last minute for a score submission. In
  fact, other people want to see the score to beat. So don't be a spoilsport by hoarding your score. Submit early and often.
  
• The UDF may only use the KiXtart/KiXforms commands/functions/macros, no other code fragments are allowed. Calls to COM components that
  are part of a standard default Windows installation are allowed.
  
• Calls to other executables, as long as they are part of a standard default Windows installation are allowed.
  
• The use of the KiXforms DLL is also permitted as the KiXforms DLL can now be considered an integral part of KiXtart scripting.
  
• The UDF should be self-contained (except for any I/O mentioned in the challenge). In particular, you may not do things like fetching
  extra data from a remote site or file.
  
• You may assume ASCII as character set.
  
• You may not use block comments as the KiXgolf Scoring Engine does not support block comments
  
• You are not allowed to use additional code that is external to the KiXgolf UDF Collection. All code must be contained within the KiXgolf UDF Collection.
  
• You are allowed to only use publicly available versions of KiXtart and KiXforms, private builds or alpha builds are NOT allowed
  
• Your submitted score must include the KiXart/KiXforms version used.
  
• All variables must be properly declared as SETOPTION('Explicit','ON') has been coded into the main script
  
• Other script-wide restrictions, e.g. NoVarsInStrings=ON, are not in effect
  
• The KiXgolf UDF Collection as enclosed by the ';!' and ';!;!' tags can be modified to e.g. rename the parameter variables, add additional
  optional parameters or add additional sub-UDFs.
  
• Maximum runtime for the code solution is one hour
  
• Tokenizing the UDF, script, or portions thereof is not allowed
  

• 01) The goal of KiXtart Golf is to score the lowest strokes.
  
• 02) Strokes are all characters in a piece of code except whitespace characters, unless the whitespace character is necessary
  for the line of code to work. Therefore, carriage returns and line feeds do not count or spaces in between the '=' sign when
  assigning variables, e.g. '$a = $b' scores 5.
  
• 03) Code can be constructed any way you like, as long as it is syntactically correct with KiXtart, i.e. the KiXgolf engine
  does not throw a syntax or other error.
  
• 04) The final solution MUST pass all test scripts that accompagny the KiXtart golf challenge.
  
• 05) The use of '$' as a variable is allowed.
  
• 06) In case of questions about a particular way to count the KiXtart Golf Challenge organizer
  has the last call.
  
• 07) During the private coding phase, no code is allowed to be posted. Violations result in disqualification of said player.
  
• 08) During the public coding phase, code should be posted, reused, and borrowed from other players.
  
• 09) The test script contains the official KiXgolf scoring engine
  
• 10) Only the person posting a particular score will be recognized for the score, unless the KiXtart Golf Challenge
  organizer or another delegate posts code on behalf of a player
  

Quote:

---

The UDF is expected to finish in a reasonable time, e.g. if it gets started when the challenge opens, it's expected to be finished by the
time the challenge closes even on a somewhat slow computer. The UDF has to be valid during the period that the challenge runs.
...
Maximum runtime for the code solution is one hour

---

Quote:

---

The KiXgolf solution is expected to run for no more than one hour in order to run through all public test cases that are part of the KiXgolf package

---

Quote:

---

So, since this is a community process, here's my condensed version, maybesomebody can golf this rule down further

Quote:

---

The KiXgolf solution is expected to run for no more than one hour in order to run through all public test cases that are part of the KiXgolf package

---

---

1. KiXtart Golf (a.k.a KiXgolf) codes must be written inside the KiXgolf UDF collection tags, ';!' and ';!;!'
2. Parameter names of the UDF's can be changed and additional optional parameters can be added.
3. Additional helper UDF's can be written as long as they reside inside the ';!' and ';!;!' tags.
4. The UDF layout is up to coder.
5. The UDF is expected to finish in a reasonable time, that is, on modern computers inside 1 hour timeframe.
6. You can submit scores as often as you want.
7. If you reach leading score, you are oblicated to post your score immediately so others can try to compete with you.
8. The UDF may only use the KiXtart commands/functions/macros, no other code fragments are allowed.
9. Calls to COM components that are part of a standard default Windows installation are allowed.
10. The use of the KiXforms DLL is also permitted as the KiXforms DLL can now be considered an integral part of KiXtart scripting.
11. Calls to other executables, as long as they are part of a standard default Windows installation are allowed.
12. The UDF should be self-contained (except for any I/O mentioned in the challenge). In particular, you may not do things like fetching extra data from a remote site or file.
13. You may assume ASCII as character set.
14. You may not use block comments as the KiXgolf Scoring Engine does not support block comments.
15. You are allowed to only use publicly available versions of KiXtart and KiXforms, private builds or alpha builds are NOT allowed.
16. Your submitted score must include the result print of the KiXgolf test-engine.
17. All variables must be properly declared.
18. You may not use variables or macros inside strings.
19. Case-Sensitivity is forced.
20. Tokenizing the UDF, script, or portions thereof is not allowed.

Quote:

---

8. The UDF may only use the KiXtart commands/functions/macros, no other code fragments are allowed.

11. Calls to other executables, as long as they are part of a standard default Windows installation are allowed.

---