hmm...
ok, the rules are different... not sure about the section names still.
anyways, came up with something like this.
if someone can spot it, I removed at least one rule that actually hasn't been true for quite some time.
- KiXtart Golf (a.k.a KiXgolf) codes must be written inside the KiXgolf UDF collection tags, ';!' and ';!;!'
- Parameter names of the UDF's can be changed and additional optional parameters can be added.
- Additional helper UDF's can be written as long as they reside inside the ';!' and ';!;!' tags.
- The UDF layout is up to coder.
- The UDF is expected to finish in a reasonable time, that is, on modern computers inside 1 hour timeframe.
- You can submit scores as often as you want.
- If you reach leading score, you are oblicated to post your score immediately so others can try to compete with you.
- The UDF may only use the KiXtart commands/functions/macros, no other code fragments are allowed.
- Calls to COM components that 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.
- Calls to other executables, as long as they are part of a standard default Windows installation are allowed.
- 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 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 result print of the KiXgolf test-engine.
- All variables must be properly declared.
- You may not use variables or macros inside strings.
- Case-Sensitivity is forced.
- Tokenizing the UDF, script, or portions thereof is not allowed.
_________________________
!download
KiXnet
