Yup, 65535 is the unsigned short int limit. Had the creator used a long int instead the limit would be 4,294,967,295 or more than anyone could ever need.

So essentially CB is hard coded at that limit. Not sure why, as it could have been a long int, even back in the Win 95 days. Could be for memory reasons, or the developer just really didn't think more than 65,535 would ever be needed.

By Steve Zamboni (Szamboni) on Sunday, October 13, 2019 - 01:33 am: Edit

Blizzard used to have 32-bit limits on some of data fields on their World of Warcraft characters, although I never did figure out why one of the limits was 2^31-2.

(We suspected that the in-game mailboxes had a similar limit, but stopped poking at it after crashing all of the NA servers and waiting a week for them to restore the mailboxes from tape. Oops.)

By Lawrence Bergen (Lar) on Saturday, October 19, 2019 - 07:04 pm: Edit

I added some fun maps today for yet unwritten scenarios Chuck and I discussed two years ago.

One is a Romulan Western Empire scenario where the Roms somehow took the Klingon empire down.
Its only a territory color shift ATM from the Klingon Eastern Marches scenario. No suggested rules, Fleets, timelines or schedules have been devised.

The Other one is a wholesale swap of the Kzinti and Hydrans, moving the Hydrans North and the Kzinti into the corner.
("No one puts Kzinti in the corner.")

I think when we discussed it there were all sorts of variations in the 2nd swap scenario.
Who should get attacked first, the Hydran special rules (maybe some remain with the Kzinti, depending on the scenario). Either way it was just fun to speculate and the map was a quick swap.

By Ted Fay (Catwhoeatsphoto) on Monday, October 21, 2019 - 10:56 am: Edit

This may have already been dealt with, but I encountered it again just now, so I thought I'd mention it just in case.

The current gamebox has no Klingon E3As. We'll need at least as many counters as are called for in the FO update.

Thanks!

By Thomas Mathews (Turtle) on Monday, October 21, 2019 - 01:06 pm: Edit

It is being addressed. There are other missing units to be added as well.

By Thomas Mathews (Turtle) on Monday, October 21, 2019 - 06:30 pm: Edit

Ted, off the top of your head do you know if 20 E3As will be enough? No one is really going to build any more, but we will have a couple of extra just in case another scenario needs some extras.

By Ted Fay (Catwhoeatsphoto) on Monday, October 21, 2019 - 07:22 pm: Edit

Thomas, FO 2016 lists the following E3 class vessels:

Mothball: 3*E3, 6*E3A

Eastern fleet: 3*E3, 2*E3A

Western fleet: 2*E3A

That is a total of 6 E3s and 10 E3As.

For the General War scenario, this is all you will need.

The Revised Four Powers war has 18*E3 among all the fleets listed (no E3A). However, the Klingon build schedule for that scenario includes another 6 E3s (plus the possibility of downgrade substitution).


From these numbers, and given that no one in the right mind builds another E3 class hull, I would say that 30 E3s would be plenty. Honestly, you could get away with 24 (the total number expected for the 4PW).

As for E3As, I would say 10 is probably OK, but 15 is likely more than enough.

YMMV. I've just provided the data you might find useful.

By Lawrence Bergen (Lar) on Monday, October 21, 2019 - 09:30 pm: Edit

How about in EB, would you guys build these over E4s? That might be the tipping point.

By Thomas Mathews (Turtle) on Monday, October 21, 2019 - 09:31 pm: Edit

I wouldn't build E3s in EB. They are not cost effective. Also, unless the schedule forced you to build E3s in a given scenario, I would only build the minimum number required. The E4, as bad as it is, is a better buy.

By Mike Curtis (Nashvillen) on Tuesday, October 22, 2019 - 08:47 am: Edit

Agreed, the number for the published scenarios should be enough. The E4 is a better purchase for the Klingons in EB.

By Lawrence Bergen (Lar) on Wednesday, October 30, 2019 - 07:10 pm: Edit

Ted: it is possible to make the tug counters with backs as Mission M for easy use and separate Crippled Tugs that flip back to Mission M once repaired.

By Ted Fay (Catwhoeatsphoto) on Thursday, October 31, 2019 - 11:04 am: Edit

Lawrence, that would be *awesome*. It would make tracking tug missions from turn to turn *much* easier!!!

By Ted Fay (Catwhoeatsphoto) on Thursday, October 31, 2019 - 11:07 am: Edit

I am DROOLING for the new Cyberboard game box!

By Thomas Mathews (Turtle) on Thursday, October 31, 2019 - 01:51 pm: Edit

The issue of making them comes back to the number of counters available. I for one am loath to cut to far into remaining 4000 or so after the auxiliary counts are "standardized".

By Ted Fay (Catwhoeatsphoto) on Thursday, October 31, 2019 - 03:26 pm: Edit

I can't remember if this has been addressed already, but the Hydran SA unit (fusion FF leader) has an error on it's crippled side. It should have a crippled defpot of 3, not 2.

-T

By Richard B. Eitzen (Rbeitzen) on Thursday, October 31, 2019 - 04:37 pm: Edit

I've brought this up but the result stands as 3, even so.

By Ted Fay (Catwhoeatsphoto) on Thursday, October 31, 2019 - 04:43 pm: Edit

@Richard, yeah, I know the result stands at 3. I'm just pointing out that the SA counters in the CB gamebox needs to be updated accordingly.

By Thomas Mathews (Turtle) on Thursday, October 31, 2019 - 07:27 pm: Edit

The SAR in the forthcoming gamebox matches the 2017 SIT for factors. So, unless the SIT changes, no changes will be made to that counter.

By Richard B. Eitzen (Rbeitzen) on Thursday, October 31, 2019 - 11:47 pm: Edit

The current Hydran SIT on THIS website shows the SAR as 4-5/2-3, so that's what it should be in Cyberboard.

By William Jockusch (Verybadcat2) on Tuesday, November 19, 2019 - 11:23 am: Edit

I would love more FRD parks for like everyone. I like to put my crips into such fleets.

By Ted Fay (Catwhoeatsphoto) on Tuesday, November 19, 2019 - 12:28 pm: Edit

Concur with William. Would be nice to have, say, 4 FRD park counters for each empire, maybe 5 or 6 for Klingons and Feds.

By Rob Padilla (Zargan) on Wednesday, December 04, 2019 - 08:34 am: Edit

Just caught an error on the Map itself. In Tholian Space, the map labels for the 2nd and 3rd Fleet are swapped.

The 3rd Fleet should be on 2918.
The 2nd Fleet should be on 3019, 3018 and 3119.
The 1st Fleet (correct) is 2819, 2818 and 2719.

By Ted Fay (Catwhoeatsphoto) on Wednesday, December 04, 2019 - 11:01 am: Edit

Should also check for a missing Tholian SAS in Home.

By Rob Padilla (Zargan) on Thursday, December 05, 2019 - 09:19 am: Edit

Well, that's a scenario issue. The map itself resides in the gamebox and would affect all scenarios across the board.

By Ted Fay (Catwhoeatsphoto) on Thursday, December 05, 2019 - 09:26 am: Edit

True, but they're also working on the scenarios as needed (especially the WIND scenario), 'cause I know they're fixing things like the fact that the Klingon North Fleet counter is currently out of place.