PROCESSED Ryan and Turtle spent time going through all of the official published and playtest materials so could speak to the why this was done.

Overall the idea was to source the scenario rules into the (650-early 660s range). The 659 number proposed in CL44 was a notional number often as CL publications are and would get a real number as we add it to another product in the near future. SVC NOTES THAT THIS CONCEPT IS PURE MYTH. IF SOMETHING IS GIVEN A REAL NUMBER, LIKE THIS, IT KEEPS THAT NUMBER. YOU COULD ARGUE THAT CAPLOG STUFF SHOULD GET ONLY PLACEHOLDER NUMBERS, BUT THE REALITY IS THAT 659 IS A HARD NUMBER AND WON'T BE CHANGED. SAME FOR 658 AND 660. NOTIONAL NUMBERS ARE PLACEHOLDERS LIKE 6SL4 OR 6WC1. 659 IS IN FORMAT AND IS A REAL NUMBER. THIS MYTH NEEDS TO DIE.

Ryan and Turtle (or possibly Chuck) can discuss to the other two numbers as we did have a plan that was discussed with SVC in Amarillo last fall when all the numbers were laid out.

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 04:43 pm: Edit

PROCESSED I don't remember such a discussion (which doesn't mean there wasn't one) but numbered rules in Captain's Log almost always (99.9% of the time) keep those numbers forever. There seems to be a lot of myth and guesswork about stuff in Captain's Log, which is complicated by the fact that sometimes it's a final draft and sometimes it's just an idea, but I don't recall ever saying that CapLog rule numbers were fluid. A number like 6TR5 is obviously a placeholder. A number like 660 is a hard number that should never be changed, at least not without a heck of a fight.

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 04:49 pm: Edit

PROCESSED

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 04:53 pm: Edit

PROCESSED F&E 2010, page 123, scenario 659 is a hard published number, not a notional number.

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 04:56 pm: Edit

PROCESSED

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 05:02 pm: Edit

PROCESSED

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 05:10 pm: Edit

PROCESSED

By Lawrence Bergen (Lar) on Wednesday, August 05, 2026 - 07:52 pm: Edit

PROCESSED

By Steve Cole (Stevecole) on Wednesday, August 05, 2026 - 08:46 pm: Edit

PROCESSED We do not change published numbers. If we did we would have to revise previous products. That way lies madness.

In Amarillo we discussed which of the rules was first, second, and third. No one told me you were reusing published numbers or I would have said NO. To be sure, I am technically deaf and at the time my health was much worse than now.

Thanks for the rule numbers but did you not grok that I was deliberately not listening stand in numbers?
6EW is a placeholder. This is obvious because it has letters.
659 is a live number that cannot be changed. This is obvious because all three digits are Numerals.
Capiche?

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 08:08 am: Edit

PROCESSED ]
Exceptional work, Ken!

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 08:37 am: Edit

PROCESSED
THIS HAS BEEN DONE 10 AUG 2026
I propose to renumber 658-661 as 641-644.

Staff?

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 02:09 pm: Edit

PROCESSED CIVIL WARS HARD COPY EDITION - LINE ITEMS

DONE (115.2) TABLE OF CONTENTS:; Add listing for rule (661.0) WYN IN OTHER SCENARIOS to list. (At this moment its Page 40, SVC may change that location, this rule though should align to whatever page number it comes to rest on.) RATIONALE: Missing. - L. Bergen 5 AUG 2026

NOT DONE, NO SPACE (115.7) DEFINITIONS LIST:; Add listing: 'WYN Barrier Movement: 209.0'. RATIONALE: Missing from section. - L. Bergen 5 AUG 2026 Not needed, on table of contents.

NOT DONE, NO SPACE (115.7) DEFINITIONS LIST:; Add listing: 'Robot-controlled Combat: 331.0'. RATIONALE: Missing from section. - L. Bergen 5 AUG 2026 not needed, on table of contents.

DONE, (115.7) DEFINITIONS LIST:; Add listing: ' "WYN Fish ship production: 555.5" RATIONALE: Listing reflects the rule more accurately. - L. Bergen 5 AUG 2026

DONE, NO SPACE (115.7) DEFINITIONS LIST:; Correct listing: "Fish ships: 555.5" should be 'Fish ships, WYN production: 555.5' RATIONALE: Listing reflects the rule more accurately. - L. Bergen 5 AUG 2026

DONE, (115.7) DEFINITIONS LIST:; Correct listing: "WYN Special rules: 554.0" should reflect the change made in the section 'WYN Specific rules: 554.0' RATIONALE: Section name was changed before early edition was published. - L. Bergen 5 AUG 2026

NOT DONE, NEEDS TO BE THERE (115.7) DEFINITIONS LIST:; drop listing: "Special rules for Middle Years: 657.0". RATIONALE: Not needed here or in the 900 Index. - L. Bergen 5 AUG 2026

NOT DONE, NEEEDS TO BE THERE (115.7) DEFINITIONS LIST:; drop listing: "Special rules for WYN: 554.0". RATIONALE: Not needed here or in the 900 Index. - L. Bergen 5 AUG 2026

DONE (115.8) (SPECIAL NOTE ON EARLY ACCESS PDF): This 'unnumbered' section (appearing after 115.7) can be removed for the hard copy edition. RATIONALE: No longer needed in final product. - L. Bergen 5 AUG 2026

A FOOLISH CONSISTENCY IS THE HOB GOBLIN OF SMALL MINDS. (331.0) END (331.0) Title block at the end of the section on bottom of the page shows title block as 'END (331.0)' should be "END OF (331.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

IS THIS REALLY WORTH MY TIME (332.0) END (332.0) Title block at the end of the section on bottom of the page shows title block as 'END (332.0)' should be "END OF (332.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

DONE (506.0) YELLOW BOX on bottom of the page shows rule number as '506.0 OFF-MAP' should be "506 OFF-MAP" with no parentheses or decimal spaces. RATIONALE: Consistency with rulebook formatting. - L. Bergen 5 AUG 2026

LIKE IT MATTERS (506.0) END (506.0) Title block at the end of the section on bottom of the page shows title block as 'END (506.0)' should be "END OF (506.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

FIXED (554.0) Page 14-15 formatting shows last two words of page 14 'the Cluster.' have moved to page 15 pushing this page down and causing the END OF (554) to cover the YELLOW BOX. RATIONALE: Consistency with rulebook formatting. - L. Bergen 5 AUG 2026

SHOULD HAVE BEEN NOTED A YEAR AGO WHEN IT WOULD HAVE BEEN LESS TROUBLE (554.0) END OF (554) Title block at the end of the section on bottom of the page shows title block as 'END OF (554)' should be "END OF (554.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

ALREADY HAD DECIMAL AND PARENS SO WHY WAS YOUR TIME AND MINE REPORTING SOMETHING THAT ISN'T WRONG? (555.0) END (634) Title block at the end of the section on bottom of the page shows title block as 'END (555.0)' should be "END OF (555.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

I ACTUALLY PREFER THE OTHER WAY BUT IT DOESN' T MATTER
YOU ARE JUST PLAYING "MAKE THE DESIGNER TO EXTRA WORK FOR NOTHING"
I HOPE YOU ENJOYED IT.
HOSEA 8:7
(634.0) END (634) Title block at the end of the section on bottom of the page shows title block as 'END (634)' should be "END OF (634.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

IBID (635.0) END OF (635) Title block at the end of the section on bottom of the page shows rule number as 'END OF (635)' should be "END OF (635.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG IBID 2026

(636.0) END (636) Title block at the end of the section on bottom of the page shows title block as 'END (636)' should be "END OF (636.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

QUOTH GRETA; BLAH BLAH BLAH (637.0) END OF (637) Title block at the end of the section on bottom of the page shows rule number as 'END OF (637)' should be "END OF (637.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

HOSEA 8:7 (661.0) END OF (661) Title block at the end of the section on bottom of the page shows rule number as 'END OF (661)' should be "END OF (661.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

DONE DESPITE REPORT BEING MONTHS LATE (661.0) Perform a global review of (661.0) for phrase 'the cluster' and replace with "the Cluster" as necessary. RATIONALE: Consistency with the previous CW: Early Edition review. Plus we don't want Jean to 'whanng' the staff or SVC. - L. Bergen 5 AUG 2026

WILL NO ONE RELIEVE ME OF THIS ANNOYING PRIEST? (661.0) YELLOW BOX on bottom of the page shows rule number as (661.0) should be "661 WYN IN SCNEARIOS" with no parentheses or decimal spaces. RATIONALE: Consistency with rulebook formatting. - L. Bergen 5 AUG 2026

SIGH (661.0) Last line in introduction "Understanding this may greatly upset the scenario's balance (a warning from SVC himself) players would do this at their own risk." Add comma after parenthetical. RATIONALE: Grammar.- L. Bergen 5 AUG 2026

OK (661.11) Last line in paragraph; "The sanctions of rule (554.5) covering the loss of trade rights, would apply to the attacking empire and their allies for a minimum of four years and potentially the rest of the scenario." Remove comma after trade rights as it is not necessary and incorrect. RATIONALE: Grammar. - L. Bergen 5 AUG 2026

(661.121): WHEN DECLARED: Remove extra colon after rule number. RATIONALE: Formatting. - L. Bergen 5 AUG 2026

IT WAS IN YOUR ORIGINAL TEXT, SO I LEFT IT (661.122) Replace this rule text with the following; 'If the WYN declare war, they must declare war on the empire(s) or faction(s) that invaded the Cluster. They may also declare war on the invaders' allies. The WYN may not declare war on any other empire or faction unless that empire or faction subsequently invades the Cluster. The sanctions of (554.5) would then apply to those additional invaders.' RATIONALE: Slightly shorter and more direct. Original created a clarity issue between empires and factions that could only be resolved by adding more words to a page that doesn't need more. - L. Bergen 5 AUG 2026

YOUR ORIGINAL TEXT (661.131) LONE DECLARATION: Change first line start from "If the WYN chose to stand alone, then..." to 'If the WYN stand alone, then...' RATIONALE: Eliminates conditional tense issue between (661.13) and (661.131) 'may choose' vs 'chose', the choice is assumed to have been made. - L. Bergen 5 AUG 2026

YOUR ORIGINAL TEXT, I DID FIX YOUR OTHER TYPOS IN THT ONE (661.22) COMBAT: 'barrier combat' should be replaced with "barrier-disabled combat". RATIONALE: Consistency with the previous review for the early edition book. - L. Bergen 5 AUG 2026

YOUR ORIGINAL TEXT. (661.23) EXAMPLE: Drop this rule number and make the example part of (661.22). RATIONALE: Examples do not usually receive rule numbers. Consistency with rulebook formatting. - L. Bergen 5 AUG 2026

SIGH (704.IF) END (704.IF) Title block at the end of the section on bottom of the page shows title block as 'END (704.IF)' should be "END OF (704.IF)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

SIGH (704.R) END (704.R) Title block at the end of the section on bottom of the page shows title block as 'END (704.R)' should be "END OF (704.R)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

HOSEA 8:7 (712.0) END (712.0) WYN OB Title block at the end of the section on bottom of last page shows title block as 'END (712.0) WYN OB' should be "END OF (712.0)" with parentheses and decimal space. RATIONALE: Consistency with rulebook formatting. All 'END OF (###.#)' title blocks should match. - L. Bergen 5 AUG 2026

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 02:11 pm: Edit

PROCESSED Steve if you prefer I can post the line items here. Or I can stick with the email system we have been using.

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 02:14 pm: Edit

PROCESSED I need them to be here for me to process them since this computer cannot get them to the computer with the rulebook on it. Any report I received by email has to be reposted here by me.

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 02:14 pm: Edit

PROCESSED Ken K: when this is over I want that chart in excel form if you have it that way. Don't spend time creating it there if it's not there. Let me know what format it is in.

KEN SENT IT, REMIND ME TO FORWARD TO STAFF

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 02:15 pm: Edit

PROCESSED Typo correction to above:
(661.0) YELLOW BOX on bottom of the page shows rule number as (661.0) should be "661 WYN IN SCENARIOS" with no parentheses or decimal spaces. RATIONALE: Consistency with rulebook formatting. - L. Bergen 5 AUG 2026

By Steve Cole (Stevecole) on Thursday, August 06, 2026 - 03:25 pm: Edit

PROCESSED Lar, just about everything in your last huge report could and should have been sent to me two months ago.

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 03:29 pm: Edit

PROCESSED Ken's Chart is good...this is a good resource to have to double check things.
For instance:
631.0 In TacOps and 698.0 CL21 are the same scenario 'The War that Almost Was'
660.0 Eastern Sunrise in TacOps used the same number originally given to 660.0 The Kaltic Freestates from P1

Kind of impressive when you stand back and look at it to see just how many scenarios have been created in 40 years from the handful of original 1986 Grand Campaign GW Scenarios.

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 07:22 pm: Edit

PROCESSED (555.15) SPECIFIC CASES; there is an extra carriage return (line space) between (555.15) and (555.151) that seems unnecessary. Suggest remove extra space. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

(555.53) SPECIFIED FISH SHIPS; there is an extra carriage return (line space) between (555.53) and (555.531) that seems unnecessary. Suggest remove extra space. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 07:29 pm: Edit

PROCESSED MISTAKES FROM YOUR ORIGINAL TEXT
(661.12) DECLARING WAR:; there is an unnecessary colon here. Suggest remove extra colon. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

(661.3) ECONOMIC CONSIDERATIONS:; there is an unnecessary colon here. Suggest remove extra colon. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

By Ken Kazinski (Kjkazinski) on Thursday, August 06, 2026 - 08:11 pm: Edit

PROCESSED Steve - scenario files emailed.

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 08:16 pm: Edit

PROCESSED
(506.621) Impassable Zones: should be bolded as (506.621) Impassable Zones: RATIONALE: Formatting consistency. - L. Bergen 6 AUG 2026 DONE

(506.622) Limited Entry: should be bolded as (506.622) Limited Entry: RATIONALE: Formatting consistency. - L. Bergen 6 AUG 2026 DONE

(661.0) end of line 8 the words "grand campaign' is lower case as compared to "Grand Campaign" found on the last line of the (661.132) EXAMPLE (at the bottom of the page). Suggest review for consistency and correctness. RATIONALE: Format and grammar. - L. Bergen 6 AUG 2026 DONE

(661.131) LONE DECLARATION: should be replaced with (661.131) Lone Declaration:. RATIONALE: Formatting. Staff misrepresented this in the initial delivery, three decimal rule numbers are formatted at a lower case and may be or may not be bold (these should be lower case and bold). - L. Bergen 6 AUG 2026 DONE

(661.132) JOINING AN ALLIANCE: should be replaced with (661.132) Joining an Alliance:. RATIONALE: Formatting. Staff misrepresented this in the initial delivery, three decimal rule numbers are formatted at a lower case and may be or may not be bold (these should be lower case and bold). - L. Bergen 6 AUG 2026 DONE

HOW FAR I HAVE MADE IT SO FAR, OUT OF ANTACID PILLS AND ZANAX AND VALIUM

(661.132); start of new paragraph EXAMPLE: should not be bolded and read as 'EXAMPLE:'. RATIONALE: Formatting. Staff misrepresented this in the initial delivery, three decimal rule numbers EXAMPLES may or may not be formatted at a UPPER case (this one should be UPPER) and are typically not bold (this one should not be bold). - L. Bergen 6 AUG 2026

(661.133) JOINING AS A CO-BELLIGERENT:; was not properly bold but should also be replaced with (661.132) Joining as a Co-belligerent:. RATIONALE: Formatting. Staff misrepresented this in the initial delivery, three decimal rule numbers are formatted at a lower case and may be or may not be bold (these should be lower case and bold). - L. Bergen 6 AUG 2026

(661.132) - EXAMPLE 2nd and 3rd sentence, replace with "The WYN declare war on the Klingons and their allies, the Lyrans. The WYN join the Alliance (i.e., the Kzinti, Hydran, Federation, and Gorn), and their actions become part of the Alliance Phasing Turn." RATIONALE: Cleans up some language for clarity while keeping the intent. - L. Bergen 6 AUG 2026

(661.2) DECLARING WAR ON THE WYN:; Typically when we see a rule section change from (###.1) to (###.2) we format with a black bar and white lettering. Was this not done to save space and keep this rule on one page? If not, suggest removal of colon and place into Title block bar format. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

(661.3) ECONOMIC CONSIDERATIONS; Typically when we see a rule section change from (###.2) to (###.3) we format with a black bar and white lettering. Was this not done to save space and keep this rule on one page? If not, suggest Title block bar format be used. RATIONALE: Consistency with rulebook formatting. - L. Bergen 6 AUG 2026

By Stewart Frazier (Frazikar3) on Thursday, August 06, 2026 - 08:18 pm: Edit

PROCESSED
'I propose to renumber 658-661 as 641-644. '

Main problem is that leaves only 639 and 640 for the next scenarios (Andro War?) before jumping to … 645, 661, or 676.

Putting in 661-664 could mean leaving 665-670 for future 'campaign rulings', leaving scenarios in the 639-650 before it jumps to 676 (following Maelstrom) …

By Lawrence Bergen (Lar) on Thursday, August 06, 2026 - 08:23 pm: Edit

PRIMORDIAL INDEED
I realize as I go through (661.0) again that it was in early primordial draft stage where as the other portions of the book had had several round (you guys have no idea how many time we collaborated with SVC on these pages) of honing to get it ready for early draft release. For that you all have my apologies and my appreciation as I help to get it up to par.