diff --git a/markdown.html b/markdown.html
index 3b583eff3..e4c05fb47 100644
--- a/markdown.html
+++ b/markdown.html
@@ -470,8 +470,8 @@ See the FAQ on “remarks.md submission file
Nevertheless, the IOCCC does have certain practices that we ask authors to
follow. Some of these relate to use of markdown directly and others relate
to injecting HTML into the markdown file.
-In the sections below, examples will mark by ❌ for the incorrect method
-and ✔ for preferred correct one.
+In the sections below, examples will mark by ❌ for the incorrect method
+and ✔ for preferred correct one.
diff --git a/markdown.md b/markdown.md
index e870bf167..0b279d631 100644
--- a/markdown.md
+++ b/markdown.md
@@ -25,8 +25,8 @@ Nevertheless, the IOCCC does have certain practices that we ask authors to
follow. Some of these relate to use of markdown directly and others relate
to injecting HTML into the markdown file.
-In the sections below, examples will mark by ❌ for the incorrect method
-and ✔ for preferred correct one.
+In the sections below, examples will mark by ❌ for the incorrect method
+and ✔ for preferred correct one.
diff --git a/next/guidelines.html b/next/guidelines.html
index 6c0fb86b4..53fb9d128 100644
--- a/next/guidelines.html
+++ b/next/guidelines.html
@@ -478,6 +478,13 @@ Because the IOCCC29 guidelines was a substantial rewrite, only
+
+
+
+
+
+
+
You should pay attention to our observations on
code size and Rule 2 remarks for IOCCC28.
@@ -488,6 +495,9 @@ You should pay attention to our observations on
Rule 2b Net Size rules.
To check your code against
Rule 2 - Size restrictions, use the iocccentry(1) tool.
+Your submission must satisfy BOTH the maximum size Rule 2a Gross Size
+AND the Rule 2b Net Size.
+To check your code against Rule 2 - Size, use the iocccentry(1) tool.
For example:
iocccsize prog.c
The IOCCC size tool algorithm can be summarized as follows:
@@ -509,7 +519,11 @@ judges.
There a much less need to #define C reserved words in an effort
to get around the size limits of
Rule 2 - Size restrictions
-because of the iocccsize(1) algorithm.
+because of the iocccsize(1) algorithm.
+by the current version of iocccsize(1) is preferred by the IOCCC judges.
+Make sure iocccsize(1) does not flag any issues with your prog.c.
+There a much less need to #define C reserved words in an effort to get
+around the size limits of Rule 2 - Size because of the iocccsize(1) algorithm.
Yes Virginia, the previous guideline sentence is an important hint!
Jump to: top
@@ -517,6 +531,13 @@ because of the
iocccsize(1) algorithm.
+
+
+
+
+
+
See FAQ on “What is an author handle?”.
Jump to: top
@@ -524,6 +545,13 @@ because of the
iocccsize(1) algorithm.
+
+
+
+
+
+
While it is NOT required, you are allowed to use tools or services such as:
- Code generators
@@ -546,12 +574,20 @@ describe how you used such tools in your remarks.md file.<
+
+
+
+
+
+
We do realize that there are holes in the IOCCC rules, and invite
submitters to attempt to apply creative rule interpretation. A rule abuse though, even
if not rewarded, may result in a subsequent rule change for future contests.
We sometime award ‘Best abuse of the rules’ or ‘Worst abuse of the rules’,
or some variation, to a submission that creatively attempts to exploit a holes in the
+We sometimes award ‘Best abuse of the rules’ or ‘Worst abuse of the rules’,
+or some variation to a submission that creatively attempts to exploit a holes in the
IOCCC rules.
When we do need to plug a hole in the IOCCC rules
or IOCCC guidelines, we will attempt to use a very small plug,
@@ -560,11 +596,14 @@ if not smaller.
Legal rule abuse may involve, but is not limited to, doing things that are
technically allowed by the IOCCC rules and yet do not fit the spirit of what
we intended to be submitted.
-Legal abuse of the IOCCC rules is NOT an invitation to violate
-the IOCCC rules (especailly Rule 17 -
-Packaging ). A submission that violates the
-rules in the opinion of the IOCCC judges,
-WILL be disqualified. RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK!
+Legal abuse of the IOCCC rules is NOT an invitation to violate the
+IOCCC rules (especailly Rule 17 - Packaging ). A submission that violates the rules in the
+opinion of the IOCCC judges, WILL be
+disqualified. RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK! If you
+have a submission that might otherwise be interesting, you might want to
+submit two versions; one that does not abuse the IOCCC rules and one that
+does, making sure to note in the one that does not abuse the rules that this is
+another version, so that the judges do not assume you uploaded it by mistake.
If you intend to abuse the IOCCC rules,
indicate so in your remarks.md file. You MUST try to justify, plead, beg,
why you consider your rule abuse to be allowed under the
@@ -581,6 +620,9 @@ mistake.
Rule 2a - Gross Size
and/or about
Rule 2b - Net Size
+Rule 2a Gross Size
+or about
+Rule 2b Net Size
or any other
rule and submit a submission anyway, you MUST try to justify why the IOCCC
IOCCC judges should not reject your submission due to a rule
@@ -611,6 +653,12 @@ This is one of the reasons why the IOCCC rules and
+
+
+
+
+
+
You may use git, or services such as GitHub
to develop and maintain your submission. However, we DISLIKE
@@ -634,6 +682,13 @@ course.
+
+
+
+
+
+
+
We STRONGLY recommend you do install the most recent release of
mkiocccentry toolkit
As use of using older versions of the mkiocccentry toolkit to are HIGHLY LIKELY to be REJECTED!
@@ -653,6 +708,9 @@ The non-extra files (prog.c, prog.alt.c,
are considered free files, and to not count towards the
Rule 17 - Use mkiocccentry
limit of 31 extra files.
+These files (prog.c, prog.alt.c, try.sh, try.alt.sh, remarks.md,
+Makefile, .auth.json and .info.json) do not count towards the
+Rule 17 - Packaging limit of 31 extra files.
If you use an optional filename for something other than their intended use
in order to get past the file limit, we will consider that an abuse of rules.
@@ -758,7 +816,9 @@ to proceed with a default, however make sure the default is the CORRECT<
answer.
The mkiocccentry(1) tool will use code from iocccsize(1) which detects a number of
issues (such as Rule 2 - Size) that you may ignore,
-however ignoring such issues comes with a significant level of risk!
+however ignoring such issues comes with a significant level of risk!
+issues (such as Rule 2 - Size) that you may ignore,
+however ignoring such issues comes with a significant level of risk as noted else where.
Once the tarball is packaged it will
run txzchk(1), which will also run fnamchk(1), as part of its algorithm.
The use of mkiocccentry -W .... is highly discouraged as this may ignore
diff --git a/next/guidelines.md b/next/guidelines.md
index 061ef30a8..943308171 100644
--- a/next/guidelines.md
+++ b/next/guidelines.md
@@ -35,6 +35,10 @@ Be sure to read the [IOCCC rules](rules.html).
+
+
+
+# Guidelines for [Rule 2 - Size](rules.html#rule2-size)
You should pay attention to our observations on
@@ -48,6 +52,10 @@ Your submission must satisfy **BOTH** the
To check your code against
[Rule 2 - Size restrictions](rules.html#rule2-size), use the `iocccentry(1)` tool.
+Your submission must satisfy **BOTH** the maximum size [Rule 2a Gross Size](rules.html#rule-2a-gross-size)
+**AND** the [Rule 2b Net Size](rules.html#rule-2b-net-size).
+
+To check your code against [Rule 2 - Size](rules.html#rule-2---size), use the `iocccentry(1)` tool.
For example:
```
@@ -78,6 +86,11 @@ There a much less need to `#define` C reserved words in an effort
to get around the size limits of
[Rule 2 - Size restrictions](rules.html#rule2-size)
because of the `iocccsize(1)` algorithm.
+by the current version of `iocccsize(1)` is preferred by the [IOCCC judges](../judges.html).
+Make sure `iocccsize(1)` does not flag any issues with your `prog.c`.
+
+There a much less need to `#define` C reserved words in an effort to get
+around the size limits of [Rule 2 - Size](rules.html#rule-2---size) because of the `iocccsize(1)` algorithm.
Yes Virginia, **the previous guideline sentence is an important hint**!
@@ -90,6 +103,10 @@ Jump to: [top](#)
# Guidelines for [Rule 3 - Register for the IOCCC](rules.html#rule3-register)
+
+
+
+# Guidelines for [Rule 3 - Register](rules.html#rule-3---register)
See FAQ on "[What is an author handle?](../faq.html#author_handle_faq)".
@@ -102,6 +119,10 @@ Jump to: [top](#)
# Guidelines for [Rule 7 - Original Work](rules.html#rule7-original-work)
+
+
+
+# Guidelines for [Rule 7 - Original Work](rules.html#rule-7---original-work)
While it is **NOT** required, you are allowed to use tools or services such as:
@@ -132,6 +153,8 @@ Jump to: [top](#)
# Guidelines for [Rule 11 - Legal rule abuse](rules.html#rule11-legal-rule-abuse)
+
+
We do realize that there are holes in the [IOCCC rules](rules.html), and invite
submitters to attempt to apply creative rule interpretation. A rule abuse though, even
@@ -139,6 +162,8 @@ if not rewarded, may result in a subsequent rule change for future contests.
We sometime award '**Best abuse of the rules**' or '**Worst abuse of the rules**',
or some variation, to a submission that creatively attempts to exploit a holes in the
+We sometimes award '**Best abuse of the rules**' or '**Worst abuse of the rules**',
+or some variation to a submission that creatively attempts to exploit a holes in the
[IOCCC rules](rules.html).
When we do need to plug a hole in the [IOCCC rules](rules.html)
@@ -151,11 +176,14 @@ Legal rule abuse may involve, but is not limited to, doing things that are
technically allowed by the [IOCCC rules](rules.html) and yet do not fit the spirit of what
we intended to be submitted.
-Legal abuse of the [IOCCC rules](rules.html) is **NOT** an invitation to violate
-the [IOCCC rules](rules.html) (especailly [Rule 17 -
-Packaging](./rules.html#rule-17---packaging) ). A submission that violates the
-[rules](rules.html) in the opinion of the [IOCCC judges](../judges.html),
-**WILL** be disqualified. **_RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK!_**
+Legal abuse of the [IOCCC rules](rules.html) is **NOT** an invitation to violate the
+[IOCCC rules](rules.html) (especailly [Rule 17 - Packaging](./rules.html#rule-17---packaging) ). A submission that violates the [rules](rules.html) in the
+opinion of the [IOCCC judges](../judges.html), **WILL** be
+disqualified. **_RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK!_** If you
+have a submission that might otherwise be interesting, you might want to
+submit two versions; one that does not abuse the [IOCCC rules](rules.html) and one that
+does, making sure to note in the one that does not abuse the rules that this is
+another version, so that the judges do not assume you uploaded it by mistake.
If you intend to abuse the [IOCCC rules](rules.html),
indicate so in your `remarks.md` file. You **MUST** try to justify, plead, beg,
@@ -175,6 +203,9 @@ If you do bypass the `mkiocccentry(1)` warnings about
[Rule 2a - Gross Size](rules.html#rule-2a-gross-size)
and/or about
[Rule 2b - Net Size](rules.html#rule-2b-net-size)
+[Rule 2a Gross Size](rules.html#rule-2a-gross-size)
+or about
+[Rule 2b Net Size](rules.html#rule-2b-net-size)
or any other
rule and submit a submission anyway, you **MUST** try to justify why the IOCCC
[IOCCC judges](../judges.html) should not reject your submission due to a rule
@@ -213,6 +244,8 @@ Jump to: [top](#)
# Guidelines for [Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile)
+
+
You may use `git,` or services such as [GitHub](https://www.github.com)
to develop and maintain your submission. However, we **DISLIKE**
@@ -243,6 +276,10 @@ Jump to: [top](#)
+
+
+
+# Guidelines for [Rule 17 - Packaging](rules.html#rule-17---packaging)
We **STRONGLY** recommend you **do** install the most recent release of
@@ -268,6 +305,9 @@ The non-extra files (`prog.c`, `prog.alt.c`,
are considered _free files_, and to not count towards the
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)
limit of **31** _extra files_.
+These files (`prog.c`, `prog.alt.c`, `try.sh`, `try.alt.sh`, `remarks.md`,
+`Makefile`, `.auth.json` and `.info.json`) do _not_ count towards the
+[Rule 17 - Packaging](rules.html#rule-17---packaging) limit of **31** _extra files_.
If you use an optional filename for something other than their intended use
@@ -415,6 +455,8 @@ answer.
The `mkiocccentry(1)` tool will use code from `iocccsize(1)` which detects a number of
issues (such as [Rule 2 - Size](rules.html#rule2-size)) that you may ignore,
however ignoring such issues **comes with a significant level of risk!**
+issues (such as [Rule 2 - Size](rules.html#rule-2---size)) that you may ignore,
+however ignoring such issues **comes with a significant level of risk** as noted else where.
Once the tarball is packaged it will
run `txzchk(1)`, which will also run `fnamchk(1)`, as part of its algorithm.
diff --git a/sitemap.xml b/sitemap.xml
index ac85cfafb..2823095bb 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -16810,11 +16810,11 @@
https://www.ioccc.org/markdown.html
- 2025-11-29T04:28:46+00:00
+ 2025-11-29T17:10:20+00:00
https://www.ioccc.org/markdown.md
- 2025-11-29T04:30:44+00:00
+ 2025-11-29T17:09:30+00:00
https://www.ioccc.org/news.html
@@ -16826,11 +16826,11 @@
https://www.ioccc.org/next/guidelines.html
- 2025-11-29T07:45:34+00:00
+ 2025-11-29T17:10:42+00:00
https://www.ioccc.org/next/guidelines.md
- 2025-11-29T07:45:29+00:00
+ 2025-11-29T17:09:30+00:00
https://www.ioccc.org/next/index.html