Page 9 of 11

Re: ULTRA Rules Typo Reporting

PostPosted: Thu 17 Feb 2011 08:11
by Elminster
ApxEE_Tables
The Rapid Fire Weapons are missing in the following entries:

Table Precision Energy Beams (Needle Beam)
Ephs

Table Precision Force Beams (Primary Beam)
Fpcw

Table Laser Beam
Lhw

Table Precision Laser Beam
Lpcw

Table Plasma Gun
Pgkb

Comment by Cralis: Actually we've redone the tables, but I'll make sure we don't make the same mistakes.

Re: ULTRA Rules Typo Reporting

PostPosted: Sat 19 Feb 2011 13:05
by Elminster
Two more:

ApxAA Variable Weapons Twig
In the Note at the end: "...the availability of rapid weapons."
A Copy&Paste error from Rapid Fire Weapons Twig. ;)

A very small one in the table of Y3.02 NPR Government Types at the second line (Capitalist):
The RC Modifier for Trd states "--20". I know it's a trifle :) , but mathematically this would result in +20. :ugeek:

Comment by Cralis: that would be -(-20). A literal --20 is not considered a proper mathematical convention and would be considered, essentially, a syntax error :)

Re: ULTRA Rules Typo Reporting

PostPosted: Sat 19 Feb 2011 15:55
by Club
not really a typo, but why the heck are the "actively at war" rules in R&D? Admittedly some of the rules pertain to R&D, but it seems a really odd place for them.

Comment by Cralis: we already have plans to move them to another section.

Re: ULTRA Rules Typo Reporting

PostPosted: Sat 19 Feb 2011 18:57
by Cralis
PS. I'm commenting in the actual typo reports using red so I don't have to clutter this topic with additional comments. If there is a question or some other response-needed comment, I'll do a regular comment. But just saying "no problem done" I'm going to do inside the reports. Thanks!

Re: ULTRA Rules Typo Reporting

PostPosted: Thu 10 Mar 2011 04:52
by Elminster
In EE.04 Construction Tables and AA Con - Construction the EL information for the Super Monitor and the Leviathan differ.
EE says SM = 15 and LN = 18 while AA lists them in 14 and 16 respectively.

I think the EE table is correct as it is smoother with the gaps between hulls. In this case the fast variants must be corrected, too.

Re: ULTRA Rules Typo Reporting

PostPosted: Thu 10 Mar 2011 20:42
by PracticalM
Not sure if this really qualifies:
Set the pdf to 100% instead of 81% It's very annoying to have to keep changing it.
You have a link to the next section at the end of each file but not to the previous section at the beginning of each file. (might be harder to do with formatting).

Re: ULTRA Rules Typo Reporting

PostPosted: Mon 04 Apr 2011 05:26
by BillW
Not really a typo, but in Appendix AA section S it says "Shields are actually generators that create a magnetic bubble...." I don't think we should define shields a simply a magnetic field.

Re: ULTRA Rules Typo Reporting

PostPosted: Thu 07 Apr 2011 01:18
by Elminster
I think table "L4.11.1 In-system shipping costs and capacity" needs to be clarified.

While the header of the columns on the right says "Capacity Used" there is the possibility they cover, in fact, the cost of shipping. But in this case the first two entries for In-System CFN ("Unlimited") doesn't make sense. In fact they suggest that it is indeed the capacity which is meant here.

Re: ULTRA Rules Typo Reporting

PostPosted: Fri 20 May 2011 14:19
by Taluron
Ultra_4_2009_Part2.zip
_ApxAA_Tech.pdf

Jc - Anti-Matter Drive Tree

The generational codes all start with {h}
example: {h} Jca

The opening SL 22 also has this {h}.

Should those be in the SL column as h making each level a Hazardous project?

Otherwise I can find no explantion for the {h} in the SL 22 entry and personally find them extraneous in the Code field.

Or am I missing something? Are you marking on the control sheet the drives as hazardous?

Re: ULTRA Rules Typo Reporting

PostPosted: Fri 20 May 2011 15:04
by Cralis
Taluron wrote:Ultra_4_2009_Part2.zip
_ApxAA_Tech.pdf

Jc - Anti-Matter Drive Tree

The generational codes all start with {h}
example: {h} Jca

The opening SL 22 also has this {h}.

Should those be in the SL column as h making each level a Hazardous project?

Otherwise I can find no explantion for the {h} in the SL 22 entry and personally find them extraneous in the Code field.

Or am I missing something? Are you marking on the control sheet the drives as hazardous?


What this means is that both the SL project AND the tech project are hazardous projects. Since Jc is anti-matter technology, there is a hazard in both the scientific breakthrough to each SL, and to the actual development of the technology.