Missing Ship Specifications

[Cholmondely]

Sixth stab.

Generation Ships (shiplibrary.plist)

Code: Select all

(
	{
	class = ship;
	description = "The largest ship in the galaxy. These immense vessels are encountered only rarely in the vast tracts of Thargoid-haunted interstellar space between inhabited systems, so seeing one may be a once in a lifetime occurrance for many commanders. Few who have reported seeing these vessels have ever been unchanged by the experience, to be dwarfed by the sheer magnitude and awed by the stately grace these ships exhibit is something that remains with the viewer forever. It is illegal to interfere with these.";
	ship = "generation-ship";
	// summary = "Generation ship"; - not sure that this is needed at all at all!
    }
)

Not bothered with the summary. It merely repeats the name of the ship and seems utterly redundant.

[Cholmondely]

Seventh stab.

Commies (shiplibrary.plist)

Code: Select all

(
	{
	class = station;
	description = "Of all the penal institutions in the galaxy, saving GalPen One, the Asteroid Mines controlled by the Communist systems are the most feared. The Astro-Gulags are Rock Hermits that have been worked out and then rebuilt to house convicts in a near-escape-proof prison, forcing them to contribute to the Communist ideal. Most Astro-Gulags are located a fair distance away from the planet, within the Witchspace beacon to planet spacelane, and are a usual sight in most medium to high TL systems. Inside, thousands of convicts live and toil amongst noisy, dusty and incredibly dangerous ore processing machines.";
	ship = "astromine";
	summary = "[oolite-ship-library-summary-SM]";
    },
	{
	class = station;
	description = "With the minimalist design defining most Communist equipment these early Zero-Gravity Factories have been reduced to the most basic functions: air & water recycling, heating and power systems for the machines in the station. 'Luxury details' like artificial gravity & recreation facilities were ignored, since either would burden the primitive power converters. In systems with powerful suns CZGF's have enhanced thermal shielding & heat dissipaters to counter the dangerous levels of thermal radiation. Thus, no matter what, productivity and Communism can continue unimpeded.";
	ship = "comfactory";
	summary = "Station";
    },
	{
	class = station;
	description = "Solar Laboratory & Production Units are a major advance on the older CZGF's. They have 4 sectors. Sector Green is primarily concerned with power allocation to the SLAPU, production of electronics & ship-board technologies and docking facilities. Sector Yellow, is allocated to bio-technological and bio-medical research and is the centre of hydroponic food production. Sector Red is concerned with theoretical & experimental physics and Witchspace research. Sector Black's function is wholly taken up with propulsion technologies.";
	ship = "slapu";
	summary = "Station";
    },
	{
	class = ship;
	description = "Like great lumbering predators, the Giant Rays trawl the outermost regions of Communist systems and inter planetary space, seeking out Thargoids and other enemies of the State that exist in the trackless regions of Witchspace.";
	ship = "comgrc";
	summary = "[oolite-ship-library-summary-HF]";
    },
	{	
	class = ship;
	description = "Sweeping majestically along the spacelanes of Communist systems, the Sturgeon Mark I is known as the Commissar's Limousine (or by cynical outsiders as 'The Party Liners'). It function is carrying the political and People's Commissars into and out of Communist systems, to attend meetings with other systems' heads of state or, it is rumoured, simply to visit pleasure-worlds for rest and relaxation from the high-pressure world of administrating the People's government or overseeing the great Red War Machine.";
	ship = "comlim";
	// summary = "Yacht"; - I do not think that this is needed
    },
	{	
	class = ship;
	description = "Mining pods commonly travel in formations of four or five, blasting asteroids at close range, before peeling off to allow Scavenger Rays to scoop the debris. These vessels redefine the term 'basic'. They are literally an engine with a laser and a pilot’s seat; all other systems are pared down to the minimum required to maintain life. Air is supplied via an oxygen recycler with an operational lifespan of 12 hours, heating requires firing the pod’s mining laser to allow heat to leach through into the pilot’s compartment. The main purpose of this is to prevent convicts from escaping.";
	ship = "comminer";
	summary = "Mining Pod";
    },
	{	
	class = ship;
	description = "Scavenger Rays go by a gamut of names: Convict Rays, Scoopers, Scavengers or ‘Orange Eyesores’. They are completely unarmed, devoid even of mountings. Instead, they have a Fuel Scoop and a cargo bay that quadruples the capacity of other Rays. They follow the Mining Pods and scoop the minerals extracted from asteroids. Once filled, they return to the Gulag to transfer their cargo to the ore processors in the Pits. With depleted energy reserves and crawling speed, an escapee would have a long and perilous flight to a safe haven.";
	ship = "comminer2";
	summary = "Scavenger Ray";
    },
	{	
	class = ship;
	description = "The People's Police are tasked with protecting the spacelanes from those seeking to destabilise their ordered society. GalCop, seeing a greater erosion of their power, lodged bitter complaints against the Communist Governments, but hastily withdrew them when the Communists threatened to withdraw from GalCop and form their own Communist superstate. With their spacelanes secure, the Communists began to exploit their systems' resources, building Asteroid Mines, CZGF's and the advanced SLAPU's to take advantage of solar power. ";
	ship = "comviper";
	// summary = "People's Police";
    },
	{	
	class = ship;
	description = "The thought police are the backbone of the Communist system, stepping in to maintain the rule of the party elite, whether by interrogating infiltrators in the SLAPU's Sector Black or by escorting the Commissar's Limousine & Worker's Commuters in times of need. ";
	ship = "politicop";
	// summary = "Thought Police";
    },
	{	
	class = ship;
	description = "Big, blocky, unlovely - for outsiders. Large, cost-effective, efficient - for the Communist Commissars responding to the commercialistically-corrupted. These immense transport ships carry hundreds of citizens between their home planets and the stations where they work for the greater glory of the People. They are built around a massive open cargo bay with floor upon floor of metal benches. The rudimentary drive occupies a tiny part of the aft section, while the crew work in a tiny 'bubble' cockpit.";
	ship = "workcom";
	summary = "[oolite-ship-library-summary-HT]"; 
    },
	{
	class = ship;
	description = "The Communist Military use the ubiquitous Ray, patrolling extra-systemic space to counter the threat of Thargoid attack. Their Rays tend to be upgraded with advanced weapons and systems. Crewed by highly-trained Spetsnaz pilots, they are more than a match for most experienced pilots and, when deployed in numbers, are a dangerous proposition for even Elite-rated spacers.";
	ship = "commilray";
	summary = "[oolite-ship-library-summary-MF]";
    }
)

Can people please check this over? Long and complex. I caught all the mistakes I caught, but there are bound to be more! Blurb is adapted from Captain Hesperus's excellent wikipages.

I'm not happy with using the ship names for the summaries for the Mining Pod and the Scavenger Ray, but the names chosen by the shipdata.plist for those ships left me little option.

[Old Murgh]

Can people please check this over?

Is commercialistically an actual word?
"The Astro-Gulags are Rock Hermits that have been worked out and then.. " maybe me not getting it, but could this be phrased another way?
SLAPUs instead of possessive pronoun SLAPU's and other similar cases..

[Cholmondely]

Eighth stab.

Galactic Navy (shiplibrary.plist)

Behemoth:

Code: Select all

(
	{
	class = "galactic_navy";
	description = "The Behemoth is GalCop's mainstay battleship. It has 8 ball turrets and a belly full of Navy Vipers & Asps. Most Behemoths are assigned to planetary patrol/search and rescue. During peacetime, they accept docking civilians - the military provide the best (expensive) overhaul/repair facilities to be found. There are four different designs for this massive monster.";
	ship = "behemoth-argus"; // "behemoth-type1" & "Colossus" flubbed the dub
	summary = "Behemoth";
	},
	{
	class = "galactic_navy";
	description = "The Navy-class carrier is a monster of a ship. Primarily a carrier rather than a battleship.  Like the Behemoth it will accept civilian traffic at times of peace.";
	ship = "ncc_carrier-antiphates"; // "ncc-carrier" was a bust
	summary = "GNSS Navy-class carrier";
	},
	{
	class = "galactic_navy";
	description = "The Navy employs its own collectors to scoop up thargons after a battle to that they can be used for research";
	ship = "ncc_thargon_collector";

	summary = "GNSS Collector";
	},
)

Galactic Navy Facelift:

Code: Select all

(
	{
	class = "galactic_navy";
	description = "The Frigate is a multipurpose, medium-class capital ship. Envisioned by Admiral Matthews' forward-thinking and sweeping reforms, it was primarily designed to support the Behemoth as a fighter screen in the Navy's formidable carrier group. It was then quickly moved into additional planet patrol and picket duties. Several ships have been captured or salvaged by various rogue forces.
The Frigate is essentially a mobile weapons platform. Each ship bristles with twenty turrets and can unleash a devastating fusillade in any direction. An enemy fighter caught in a Frigate's broadside is quickly vaporized in a wave of plasma - larger ships seldom fair any better. ";
	ship = "navy-frigate";
	summary = "Frigate";
	},
	{
	class = "galactic_navy";
	description = "A transport capable of landing marines into hostile environments.  ";
	ship = "navy-lander";
	summary = "Transport";
	},
	{
	class = "galactic_navy";
	description = "Superseded by the Behemoth with a bellyful of Vipers not many Asp Mark II were left in the fleet. This changed when Admiral Matthews took over command. His vision included a Navy version of this military machines again. With the license sold to Zorgon Petterson Group an older design was reactivated first and modified to the first Navy Asp Mark II. While successful, this model wasn't able to live up to the expectations.
At the end a deal with Zorgon Petterson Group was struck, modifying an Asp Mark II Special to a new prototype. The first tests were impressive, so at the end the new member of the Neo-Asp family went into mass-production. . ";
	ship = "navy-asp";
	summary = "Heavy fighter";
	},
	{
	class = "galactic_navy";
	description = "The Navy Minesweeper serves a crucial function in the Galactic Navy. They prevent a single Q-mine from destroying an entire fleet. Adapted from the Viper Cruiser, these minesweepers can be found protecting every carrier group and Sec Com Station throughout the eight galaxies. ";
	ship = "navy-minesweeper";
	summary = "Minesweeper";
	},
	{
	class = "galactic_navy";
	description = "The Navy Medical Ship performs two essential duties in the Galactic Navy. Its primary role is battle-zone search and rescue. Secondarily, the Navy Medical Ship operates as an ambulance, transferring the untreatable to the nearest hospital for expert care. In addition to the usual naval upgrades, they are also outfitted with the latest emergency medical technology, including cryo-suspension systems, auto-docs and drug synthesisers. These ships are capable of scooping escape pods as well as docking directly with damaged ships via soft seal technology. To further facilitate access to badly damaged ships, the interior of the docking ring sports a high precision plasma cutter which can rip though the toughest hulls to access the interior. ";
	ship = "navy-medship";
	summary = "Medical Ship";
	},
	{
	class = "galactic_navy";
	description = "The Galactic Navy High Command decided upon the budget Worm to fulfil the task of ship-to-surface and ship-to-ship transit. The ubiquitous nature of the Worm meant that a single vessel could transport some 10-12 Navy personnel (in somewhat cramped conditions) to a planet's spaceport, then within a half hour transport more than ten times that weight in supplies back to the ship by the simple expedient of folding away the seating. As a concession to the whinging officers, one Worm per Navy ship was outfitted with much more than the spartan transports as was befitting a Captain's Barge.  ";
	ship = "navy-shuttle";
	summary = "Shuttle";
	},
	{
	class = "galactic_navy";
	description = "The Navy Transport is the logistical centerpiece of the Galactic Navy, transferring men and materials across all eight galaxies. Whether operating in a convoy or as part of a carrier group the Navy Transport is an indispensable part of any fleet. Each transport began as an ordinary anaconda trader. Before being commissioned into military service every ship is extensively re-fitted with the latest navy hardware and software. The final product is a model of military efficiency.  ";
	ship = "navy-transport";
	summary = "Transport";
	},
	{
	class = "galactic_navy";
	description = "The Galactic Navy is organized into regional Sector Commands (SecComs). SecComs operate autonomously but are ultimately answerable to the Navy Commander-in-Chief. Each Galaxy is divided into 14 Sectors, and each Sector has a home system within its command. These home systems are highly militarized and are never based in anarchy or feudal systems. At least one Carrier Group is assigned to each Sector Command.";
	ship = "navystat";
	summary = "Station";
	},
)

Light Destroyer
This one could do with a bit more description...

Code: Select all

(
	{
	class = "galactic_navy";
	description = "Light Destroyer is a light capital ship employed by the Navy. ";
	ship = "gn_light-destroyer";
	summary = "Light Destroyer";
	},
)

ADCK's Navy Destroyer (needs railgun oxp)

Code: Select all

(
	{
	class = "galactic_navy";
	description = "The Destroyer is a multipurpose, light-class capital ship. It is equipped with a railgun and special naval torpedoes. ";
	ship = "adck_navy-destroyer";
	summary = "Destroyer";
	},
)

And, somewhere, in a descriptions.plist (mine is in GN Facelift)

Code: Select all

(
	{
	class = "galactic_navy";
	description = "Light Destroyer is a light capital ship employed by the Navy. ";
	ship = "gn_light-destroyer";
	summary = "Light Destroyer";
	},
)

Edited to add in SecCom station (to Facelift) - and the Shipdata.plists for the two destroyer types & Behemoths/Navy-class carriers needed their names changed to GNSS Destroyer/GNSS Light Destroyer etc. to cohere with the GN.oxp names.

Behemoth .plist re-edited to add in navy-class carriers & thargon collectors.

[Switeck]

Can people please check this over?

Is commercialistically an actual word?
"The Astro-Gulags are Rock Hermits that have been worked out and then.. " maybe me not getting it, but could this be phrased another way?
SLAPUs instead of possessive pronoun SLAPU's and other similar cases..

"Worked out" in this context is a mining term...meaning mined out/hollowed out. They're no longer circular because so much material has been removed. Still have a bit of a rough surface texture to them though.

Yes, SLAPUs makes more sense than SLAPU's...in almost every instance imaginable.

[RockDoctor]

I'm not suggesting that we do all of the ship oxp's - just the most popular ones.

Is there a mechanism for that to be known? I could see that the download statistics for each OXP could be known - but is there a mechanism for knowing which OXPs remain in use after their download?

Or is there a need for a straw poll - to answer the question of which ships are most popular amongst users of the forum.

[Cholmondely]

I'm not suggesting that we do all of the ship oxp's - just the most popular ones.

Is there a mechanism for that to be known? I could see that the download statistics for each OXP could be known - but is there a mechanism for knowing which OXPs remain in use after their download?

Or is there a need for a straw poll - to answer the question of which ships are most popular amongst users of the forum.

Alas, O great and glorious geologist, I believe that we are well and truly stuffed in this regard.
1) Even before considering your critique, the wiki download statistics stopped working some years ago and are thus outdated.
2) The more recent straw polls have evinced a paltry response (16-17 voters):
Survey: What is your Oolite playing style? & How did you start playing Oolite?

I fear that only the Witchspace Lobster is in a position to comment knowledgeably on the matter, and since he normally devours any questioners who evade his perfervid worshippers...

[Cody]

... the wiki download statistics stopped working some years ago and are thus outdated.

And Box stopped showing download stats years ago too. They've just recently stopped Updates, so one has no idea whether something has been downloaded at all. Probably different for paid accounts, I expect.

[RockDoctor]

I believe that we are well and truly stuffed in this regard.
1) Even before considering your critique,

It wasn't a critique. It was a question.
I am actually trying to help. Before my previous employer went "software only", from of a field staff of 60-odd users and several thousands client seats, I managed to generate a significant percentage of the company's bug reports just myself, and I only reported things I couldn't work around myself. Developers can't fix bugs they don't know about.

So, previous methods of monitoring have, for reasons variously internal to the project and external, failed. Problematic for all sorts of "prioritise" type questions. If usage stats for ships, stations, small furry Lavian OXPs etc are worthwhile (and this thread suggests they are), what available techniques would provide a reasonable sampling of usage?

Here's 0.02€ worth : modify the code that downloads the (updated) list of expansion packs so that it (optionally, user choice) uploads the contents of ... is it "latest.log" - the last loading log for the installation? to {some friendly location}. Then, the user has elected to have some internet traffic ; the log file is something people seem happy to upload here for debugging ; there might even be a sort-of-unique ID in the log ($ship_name+$commander_name).
How much other "junk" data would that generate? Are the contents of "latest.log" managed by SDL, Oolite code, or a witches brew of the two. In the latter case, would generating "stats.log" from the next (major) version of Oolite be useful, and what data would it need?

I wouldn't be surprised to find the topic has already been flogged to death several times over - but with hundreds of threads and tens of thousands of posts on the forum, I could get a lot older and still fail to find the threads.

A plan "B" - send all forum users a monthly email (I get these from all sorts of mailing lists on the 1st of the month ; probably everyone does), requesting they mail "latest.log" to {someone who is interested} who can parse them to produce whatever statistics are being requested from the "developers" sandpit. Whether that would attract a wider spread than the sesquidozen that other polling gets ... well, one can hope.

[Cholmondely]

I believe that we are well and truly stuffed in this regard.
1) Even before considering your critique,

It wasn't a critique. It was a question.
I am actually trying to help. Before my previous employer went "software only", from of a field staff of 60-odd users and several thousands client seats, I managed to generate a significant percentage of the company's bug reports just myself, and I only reported things I couldn't work around myself. Developers can't fix bugs they don't know about.

So, previous methods of monitoring have, for reasons variously internal to the project and external, failed. Problematic for all sorts of "prioritise" type questions. If usage stats for ships, stations, small furry Lavian OXPs etc are worthwhile (and this thread suggests they are), what available techniques would provide a reasonable sampling of usage?

Here's 0.02€ worth : modify the code that downloads the (updated) list of expansion packs so that it (optionally, user choice) uploads the contents of ... is it "latest.log" - the last loading log for the installation? to {some friendly location}. Then, the user has elected to have some internet traffic ; the log file is something people seem happy to upload here for debugging ; there might even be a sort-of-unique ID in the log ($ship_name+$commander_name).
How much other "junk" data would that generate? Are the contents of "latest.log" managed by SDL, Oolite code, or a witches brew of the two. In the latter case, would generating "stats.log" from the next (major) version of Oolite be useful, and what data would it need?

I wouldn't be surprised to find the topic has already been flogged to death several times over - but with hundreds of threads and tens of thousands of posts on the forum, I could get a lot older and still fail to find the threads.

A plan "B" - send all forum users a monthly email (I get these from all sorts of mailing lists on the 1st of the month ; probably everyone does), requesting they mail "latest.log" to {someone who is interested} who can parse them to produce whatever statistics are being requested from the "developers" sandpit. Whether that would attract a wider spread than the sesquidozen that other polling gets ... well, one can hope.

Jolly helpful, thank you!

Cody (or another) might well remember previous discussions, if such exited. My search just now for "download stats" proved unavailing, and I can't recall noticing anything in my scouring of the boards.

I suppose another method might be to peruse the lists of "included oxp's" from the latest.log posting of people with problems. Less perfect, I know.

[Cholmondely]

Ninth stab.

Superhub (shiplibrary.plist)

Superhub:

Code: Select all

(
	{
	class = station;
	description = "The GASEC Superhub is the first station that is capable of transporting itself to its destination, two engine bays allow the GASEC SR-GD-S (Space Rotary Galactic Drive S) to be fitted. At the destination these engines can be taken out for re-use in other transport missions. The luxury apartments in the habitat rings near the entrances are renowned for their elegance and taste.";
	ship = "pagroove_superhub_station_mainhull";
	summary = "Massive Orbital Station";
	},
)

[Cholmondely]

Tenth stab.

Torus station (shiplibrary.plist)

Torus:

Code: Select all

(
	{
	class = station;
	description = "Colossal and majestic, Torus stations can be spotted at a great distance in space, and serve as a reminder that one is approaching the cream of technological advancement. Capable of containing vast resources and unorthodox space accommodation, they are usually lucrative centers of commerce. When the first Torus station was unveiled in orbit of Onrira in 3129, it marked an event of political promise. Needless to say, things went downhill from there, but Onrira eventually benefited.";
	ship = "toriA";
	summary = "Massive Orbital Station";
	},
)

[Nite Owl]

These "descriptions" fit into the larger scheme of things if the player is using Stations for Extra Planets and Super Hubs for Extra Planets but please feel free to use whatever bits and pieces you may deem worthy.

Super Hubs
description = "These stations were designed to handle the docking of very large ships with ease. They have double the living and commerce space of the more standard stations. There are four identical variations each with a different numerical attachment to their names; 1, 2, 3, and 4. This allows more than one of these stations to appear in the same system. They are mobile but it is extremely rare for them to move and inconvenience the station's population.";

Torus A
description = "The M-T1 Torus Station is enormous yet is remarkably easy to assemble. The prefab segments are easily transported to the building site where they are finalized according to specific needs and budget. There is no limit to the amount of rings a Torus Station can have although few have requested more than two. Torus stations are generally found in high tech systems. This single ring Torus Station can support eight times the population of a standard station. Corporate opportunity dwells at the very heart of the design.;

Torus B
description = "The M-T2 Torus Station is enormous yet is remarkably easy to assemble. The prefab segments are easily transported to the building site where they are finalized according to specific needs and budget. There is no limit to the amount of rings a Torus Station can have although few have requested more than two. Torus stations are generally found in high tech systems. This double ring Torus Station can support sixteen times the population of a standard station. Corporate opportunity dwells at the very heart of the design.;

[Cholmondely]

One can always edit in a description if it becomes an eyesore. I imagine a copy-paste DIY update will added to the relevant threads on the forum for OXPs that won't be updated.

Pluisje, do you prefer the Torus station description 2 posts above, or the two immediately above?