Lord Scrimm | |||
I know it's a pretty minor thing to work on, but the occaisional typo creeps into the reporting and it might be a good idea to have the players report them so they can be corrected when time permits ![]() For instance: An encrypted transmission was intercepted from inide the starbase. Picking nits I'm sure, and something WAAAYYYY down the priority list. Cheers, Rich Fanning aka ![]() Lord Lawrence Scrimm CIA Director of Regional Operations | |||
David Bethel | |||
Add any typos here and i will fix them as they are dead easy to do. | |||
kilanuman | |||
And here comes another typo when setting boarding options: >Date 24.1: Boarding Options {Auto Board - Yes} {Ground Combat - Yes} Docking enemy ships will be automatcially boarded. If boarding fails, the strabse will ground assault the ship. Cheers, Peter Norberg | |||
Frabby | |||
A few more spelling issue which I found over time: - 'Rail Mortor mkII' (misspelling in the blueprint name) - 'Rail Gun mkIIV' (misspelling in the blueprint name) - Jammers help against spanish gentlemen according to their TM (Senor deflection) (Didn't somebody else mention this already?) - 'EMF Dampng mkII' (misspelling in the technique name) - Starbase report misspelling: 'Insufficeint training capacity, no troops trained.' - Political report misspelling: Issue to 'Break allience' - 'Requires Blueprint' on TMs for Blueprints? It shows the item number of the item that can be produced with the blueprint so the text should really be: 'Allows to build item' - In the trade report section on starbase printouts it should read 'Value Multiplier' instead of 'Value (stellars)' - Starbase descriptions are printed on the starbase printout, but nobody except the player running the starbase is ever going to read this. They should be given to docking positions and perhaps also when scanning the starbase. - Can we please have a carriage return inserted after jumps/system messages and SA results to improve readability? - Finally, in the database for the order editor, item type 40 is misspelled as 'Technbique' (you may want to correct this in the next version of the orders file) - It still reads 'strabse' on the boarding report of starbase printouts (as Peter pointed out above) Now for some real nitpicking: - Structural modules (the only module item where 'module' is spelled with a downcase 'm') - Fighterbay mkIII (the only fighter bay written as one word, all other versions insert a space between the words 'Fighter' and 'Bay') | |||
Mica Goldstone | |||
These external data typos have been sorted. The rest are hard code typos. | |||
Darrenworthy | |||
This is a really, really (!) insignificant point but I just got the following note on a new turn: You picked up 1 Human Crew (10505) from CIA XXXXXX (XXXX). Upon first glance I thought I had actually picked up 1 human crew (my first thought being 'Doh! Another incorrectly typed order) rather than a human crew blueprint. Is there anyway to easily flag up blueprints so we don't have to really on their item number as an indicator of what they are? Cheers, Darren | |||
Clay | |||
If you have a mini panic, just look in your cargo report. If it's a 100mu item then you either have a BluePrint or one major diet contender! ![]() | |||
Nik | |||
here's another: | If boarding fails, the strabse will ground assault the ship. | | |||
Rich Farry | |||
Civillian instead of civilian. Spotted this for human, wimble, feline and naplians. | |||
Darrenworthy | |||
Here's another! ![]() There is a political order that is called 'create officier' Darren | |||
finalstryke | |||
Insufficient employees, runing at 98% efficiency. | |||
Rich Farry | |||
On the website, for 800*600 resoloution (http://cgi.kjcgames.com/800/main.php) the link for for the Space Combat rules is written as Sapce Combat. Fixed - 22/6/2004 | |||
Rich Farry | |||
>Date 24.5: Transfer Position {xxxx} {xxxx} Transferred Some Ship (xxxxx) to the owner of Sean Mcgovern (xxxx). This action cost you 100 stellars Not a typo as such, but when transferring to a political this should read ".. transferred ... to the ownership..", or something similar. | |||
Rich Farry | |||
Should say something like Does not fire or Is not firing | |||
gordon | |||
Destoyed *** ******* (*****) - 1836 [2100] Damage Here's another one Gord | |||
Steve-Law | |||
IF you want to get technical it's actually firing ![]() | |||
MasterTrader | |||
Should be research laboratories. Richard AFT | |||
Nik | |||
>Date 48.2: Market Buy {4728} {5000} {0.91} {private - No} {Add to Market - No} You do not know about item 4728 if it exists Doesn't really make sense. Perhaps: You do not know about item 4728 or if it exists or You do not know whether item 4728 exists or not etc. Nik | |||
Nik | |||
More a reporting bug, but there's no point in creating a new topic for it: I used the wrong position number for building the ship: >Date 48.2: Build Ship {25001} {yyy} {Priority - No} {Use Best - No} Warning - Your starbase is affiliation owned You can only build ships for affiliation members. Building Surveyor (1) for position yyy. - 20 Heavy Hulls (80). But in the ship yard report it is correct as it coverts to the starbase position: | Surveyor(1) 3 No zzzz | So the building <ship> for position <no> needs to be corrected. Nik | |||
Steve-Law | |||
It could make sense e.g. You do not know about item 4728, if it exists. You do not know about item 4728 (if it exists). But it depends on the meaning... | |||
Archangel | |||
How about something simpler like: What is item 4278? | |||
Rich Farry | |||
Should be construction | |||
gordon | |||
Date 2.4: Train Troops {537} {10} Error - Insufficeint training capacity, no troops trained. Gord | |||
Frabby | |||
Cypiran Crystal Art (30089) | |||
Rich Farry | |||
Find quantity of item type: Technbique (40) | |||
ptb | |||
Should be 'at least 10'. Even though techincally you can have less by deactivating factories. | |||
Duckworth-Lewis | |||
Tech manual for Jammers - they appear to be particularly useful when discouraging Spanish men... Item Type: Jammer Senor Deflection: 4 Required Crew Factors: 1 Build Requirement: 10 Metals (1) |