Jump to content

GreeningGalaxy's Flavor Text - Need fun descriptions written for your awesome mod? Have GG do it!


Recommended Posts

-- November 2015: Ack! I forgot I still had this open. Flavor text requests haven't been responded to in a while, and this service is pretty much on hold at the moment due to my constant preoccupation with that "real life" thing. December looks pretty good, though, so if you still have something you want me to look at, poke me at the end of the month. Sorry for going dark on you all. :blush: --

I've noticed a number of very nice mods lately which, despite adding great content, are lacking when it comes to in-game descriptions and documentation for their new additions. This is completely understandable, of course - Maybe English is not the native language of the modder, or maybe they just don't like writing sentences nearly as much as they like writing code. As I said, I don't hold anyone in lower esteem for not writing descriptions for their mod parts, but I do think that mods with complete and in-character descriptions fit into the game a lot better than ones that do not.

As such, I'm hereby offering my services as your on-call flavor text writer. Do you have a mod full of fancy new parts, planets, and features, but not know where to start on the documentation? I can help!

Things I'll write:

-In-game part descriptions

-In-game planet descriptions

-Science blurbs for planets

-Explanations of mod features (for forum threads, in-game manuals, et al.)

-Tutorials and other documentation for using those features

-Pretty much anything else, within reason, that involves KSP and English.

Things I won't write:

-Code (I don't know a lot about programming; if you're a modder, you're pretty much guaranteed to be better at code than I am)

-Comments on code (I probably won't be able to read your code and tell what it does, so it would be pointless for me to try to do this)

-Stuff in languages besides English, or translations of other languages (I only speak English, unfortunately. :( ) If you're desperate, I'm willing to feed whatever you give me through Google Translate and convert the results into grammatically-correct and sensical English as best I can, but I kinda doubt that that's going to end well.

-Your term papers, birthday cards, business emails, or other things not related to KSP

How to Request:

1) PM me. That's the most reliable way.

2) Post in this thread. I might take longer to see it, but if you want it to be public for whatever reason, that works.

3) Find me on IRC. I'm on #KSPOfficial on EsperNet rather a lot these days, so you'll probably be able to find me there if you want to talk in real-time about something.

In-game descriptions, particularly part descriptions, are mainly there to tell the player how to use the thing in question. In addition to that, the best descriptions are often written 'in-character,' or at least, 'in-universe,' often written in the tone of someone who lives in the Kerbal universe explaining it to you. In the case of the stock parts' descriptions written by Squad, these are usually rather humorous.

I can write your documentation in whatever style or character you need. I'm probably best at the more humorous and in-character ones, but I can also cut to the chase and write simple, out-of-character documentation to maximize clarity.

In general, I'll need the following from you before I can write anything good:

1) A good idea of what I'm writing about. If the mod is already released, great - just link me to it and tell me what you want documented, and I'll play around with it and get right back to you. If your mod is in some stage of earlier development, give me what you can - videos, screenshots, unfinished models, sketches, or even textual descriptions - I'll do my best with whatever you can give me. For tutorials, it would probably be best if you gave me a functional copy of your mod to mess with, but I can still try to make do with whatever. However, I can't guarantee that you'll get what you're looking for if you don't give me much information to work with.

2) The tone you're looking for. If you don't specify, I'll just give your parts and planets stock-similar in-character descriptions, and tutorials in simple out-of-character terms. If that's what you're after, great; if not, you'll need to let me know.

3) How soon you want it done. I don't imagine that this kind of thing will have very many rush jobs, but we can also talk about prioritizing your project over others if yours has any particular deadlines attached to it. Expedient delivery is not something that I can necessarily guarantee, but if business is as slow as I expect it to be, this shouldn't be a problem.

FAQ:

Can I get a sample of your writing?

Yes, you can check the bottom of this post, under "contributed projects," for everything I've written for projects so far. Content for each mod will be included in spoiler tags for your perusal. Those spoilers will be long; you've been warned.

Your writing sucks! I can totally do better!

Great! I never claimed to be better at it than you or anyone else. I just happen to really like doing it, particularly in this context, which is why I'm offering my services. If you think you can do better, you probably can, and you don't need me at all.

What's this, you just want to write the descriptions for mods and not have to bother with the code/models/other hard work? That's not helpful, you're just selfish!

If writing the descriptions is the fun part for you, then it sounds like you enjoy writing as much as I do, and therefore probably don't have any need for my services. :)

What's the most you're willing to do for one project?

I won't set a hard limit on that at the moment. For part and planet descriptions, I'll probably be able to do as many as you can give me - they're only a few sentences each anyway. If you have a very big documentation project that needs a lot of writing - well, first of all, I'd be flattered if you wanted little old me to handle that - then we might run into problems depending on how much time I can devote away from my real-world life to work on it. Since most mod projects involve a lot of modelling, texturing, and coding, and not a lot of flavor-text writing, I don't expect to see very many insurmountably-large goals tossed my way. Tutorials and other in-depth documentation will take the longest, since they'll necessarily involve some actual gameplay, so just be aware of that before you ask me to make you a whole MechJeb manual from the beginning. I'm not saying I won't do that, just that it could take me a considerable amount of time.

What are you currently working on?

Nothing at the moment. There will be a "pending jobs" list at the bottom of this post for that.

What projects have your written for so far?

Check the bottom of this post for a list!

Do I need to credit you if I use your writing in my mod?

Nope! While I do appreciate contributor's credit, I don't require it. It might annoy me a little if you keep our interaction totally secret and claim to have written the stuff you got from me yourself, but I won't raise a fuss. I do reserve the right to add your mod and everything I've written for it to my "contributed projects" list, though.

Pending Jobs:

Contributed Projects:

>>>Bacon Labs--

Spoiler


--Auriga Multi-Purpose Crew Vehicle--

Description: Designed with comfort, reliability, and survivability in mind, the Auriga MPCV is a great habitat for deep-space missions. It features an integrated heat shield, a limited reaction control system, four seats, and plenty of cabinets for snacks - so far, our only real problem with this pod has been convincing the crew to come back out at the end of the mission.

--ESV Core Module--

Description: A little self-contained cargo craft for when you need to deliver fuel and supplies to your outposts in space. Engines, RCS, and other fiddly bits sold separately.

--Space Launch System Fairing Base/Instrument Unit--

Description: Using an old hubcap we found lying around in the parking lot, someone's phone, and some spare fairings, we managed to make a nice little rocket topper to provide shielding and control to mid-sized payloads. Warranty not included, may void warranty of other parts if used on the same vehicle.

--Juno V Core Stage (3.75m)--

Description: Our Health and Safety committee told us that we'd reached the safe limit on fuel tank size long ago, sometime before the Jumbo-64 came into mass-production. They were pretty irate when we showed them the first production model of this tank - some called it "absurd," others said it was "patently ludicrous," and one even felt strongly enough to name it "an obelisk to the flaming death gods." Whatever you choose to call it, it can't be denied that a tank this size provides a fantastic amount of up-going juice for those big heavy launch vehicles.

--Space Launch System Extender Tank--

Description: The Space Launch System core stage is a truly colossal piece of rocketry. However, if it's still too small for you, our engineers have thoughtfully included an expandability option to make it as tall and heavy as you like.

--Ares I--

Description: The Ares I is a good little engine, best suited for upper stages and light booster stages. We're told it also makes a great heatshield, but the manufacturers have insisted that using it as one is not recommended or covered under warranty.

--Ares II--

Description: With a slightly heavier and more robust nozzle, the Ares II can put out a bit more thrust than its predecessor, and has thus been deemed a huge success by everyone involved. Despite the sturdier design, the manufacturer emphasizes that this engine is NOT a bell and should NOT be rung to celebrate important design or construction milestones.

Notes: The Ares engines don't really look finished to me (they're pretty similar in power and function, and seem like they're going to be a little weak for first-stage 3.75m engines) so their descriptions aren't as informed as I'd like them to be. Feel free to come back and have me make whatever changes you require.

--Auriga BPC--

Description: This Booster-equipped Protective Cover is an all-in-one safety kit. Not only does it provide a nice solid shield against the atmosphere on the way up, but it also comes with a great big rocket thing on top to yank a crewed Auriga pod clear of an exploding launch vehicle. Requests that this part be omitted from vehicle designs because it "blocks the view" are hereby preemptively denied.

--Auriga Service Module--

Description: The Auriga pod went over great with space programs everywhere, but the inevitable complaints rolled in immediately: "It doesn't have engines!" they said. "It's RCS isn't balanced!" "How are we supposed to power it?" Accordingly, the manufacturer quickly released this Service Module expansion to address those problems, converting the Auriga capsule into a full-featured and capable mini-spacecraft. Now everyone's complaining that they split the Auriga's command and service modules into two separate products just to make more money, but you can't please everyone.

--Circe Upper Stage--

Description: A nifty self-contained insertion stage designed to finish moving payloads into the target orbit. Crews are warned that although this engine may appear shiny and glowy right after use, direct contact with its metal surfaces is likely to burn through spacesuit gloves very quickly and is to be avoided.

--Hephaestus Upper Stage--

Description: All-in-one stages are all the rage these days, so we made sure to get lots of variety to choose from in the latest shipment. The Hephaestus stage is a great choice for tossing payloads towards geostationary orbit, but the manufacturer warns that this part is pretty small and you'll probably want something bulkier if you're shifting something really big.

--Hyacinthus IX--

Description: Intended as the bottom stage for the acclaimed Hestia launch vehicle, the Hyacinthus IX has been described as a "very solid booster" by our engineers. We aren't sure if they were talking about the fuel or the reliability characteristics, but the manufacturer says that statement can be applied to both.

--Hyacinthus X--

Description: "Not enough thrust" is the most commonly-cited problem with new launch vehicles. Fortunately, the folks in the Juno Project saw that coming, and provided us with this excellent radial-attachable booster to augment the central stack. The Hyacinthus X has been well liked among our engineering staff - not just because it's powerful, but also because it's cheap.

--Hyacinthus XX--

Description: After much deliberation, it was decided that a slightly smaller version of the Hyacinthus IX was in order for the Hestia launch vehicle's second stage. It makes the first stage a little less sluggish getting off the pad, and also, according to one interviewed engineer, "makes it look spiffier."

--Interrim Cryogenic Propulsion Stage--

Description: Big rockets are great and all, but when it comes to the largest ones available, one starts to expect a little more than just "more thrust" and "more fuel." This self-contained cryogenic rocket stage provides the rare and highly prized "more specific impulse" aspect of bigger rockets, at the slight disadvantage of burning the infamously lightweight hydrogen fuel. In spite of this, it manages to be a very capable upper stage, particularly well-suited for boosting the Auriga command and service modules to wherever they're needed.

--Juno V SRB--

Description: Dwarfing even the most aggressive and dangerous SRBs previously on the market, the Juno V pushes the limits in size, power, and cheapness of the solid rocket booster world. Some flight crews have started to object to the use of this booster after learning that it can't be shut down once lit; we've found that the simplest solution is just not to tell them.

--Juno VI Core Stage (Solid)--

Description: This solid booster is a bit of an oddity in that, despite its colossal size, it doesn't really put out all that much thrust. We're told that this is intended to maximize its burn time and make it more controllable, but nobody can resist strapping some Juno Vs to it whenever it's used on a rocket - life is too short for low thrust-to-weight ratios.

--Juno VI Core Stage (Liquid)--

Description: This booster's introduction into the stockpiles stirred up considerable friction between the solid- and liquid-fuel enthusiasts at the space center. The solid fuel folks argue that they've been sidelined for too long and making a liquid version of every booster that comes along just isn't fair, while the liquid proponents are making their same old cases about "controllability" and "improved vacuum performance," whatever that means.

--ORANGE--

Description: The only liquid-fueled part of the Hestia launch vehicle, the committee responsible for ORANGE has seen a bit of heckling from the other teams on the project. No one likes a tiny engine, but ORANGE's development team is adamant that a controllable, lightweight, and low-cost propulsion system is absolutely essential for the final insertion burn on any orbital ascent, and that ORANGE provides all of that. Whatever you choose to do with it, we recommend not using this engine where thrust-to-weight ratio is a major concern.

--Space Launch System Lower Stage--

Description: A truly thunderous piece of overengineering, the SLS Lower Stage is absolutely the biggest and best booster anyone has ever seen. Allegations that it is actually a farming silo that we stole and attached engines to are totally unfounded - those events definitely did not happen in that order.

--Space Launch System SRB--

Description: The team behind the Juno V SRB was very angry indeed when this booster first hit the market. Not only does it totally smash all previously-held records for largest solid booster, but it even looks like it might be more cost-effective for its size. Fortunately for the Juno team, the price is still prohibitive, and most saner payloads won't need boosters this big to get off the ground.

--Z-50--

Description: Designed as a highly-capable third stage for the Hestia launch vehicle, the Z-50 manages to pack a huge amount of oomph into a small package. Its relatively high thrust and inability to be deactivated or throttled once lit can make it difficult to control at times, but almost all pilots to use this booster have survived the experience.

--Auriga Service Adapter--

Description: Bridges the difference in sizes between a shrouded Auriga service module and a cryogenic upper stage. Decoupler sold separately.

--Auriga Service Shroud and Adapter--

Description: The Auriga service module is notorious for its unsightly and un-aerodynamic fiddly bits. This shroud provides welcome concealment for them during ascent, and with the help of an adapter, it connects smoothly to a cryogenic upper stage. Explosive bolts are included to separate the shrouds and adapter once the stage below it finishes burning.

--Hestia Decoadapter--

Description: Bridges the size difference between the Hyacinthus IX and XX booster stages, and contains an explosive decoupling mechanism to separate the lower one once spent.

--Hestia Decoupler--

Description: Unlike the other decouplers this size, this part neatly matches the exterior diameter and appearance of the Hestia Hyacinthus XX and Z-50 boosters. We're told this makes the rocket more aerodynamic, but we rather suspect the project engineers of caring about aesthetics.

--Hestia Fairing Base--

Description: The Hestia launch vehicle has some nice sleek lines, but the same cannot be said for most payloads. To keep the rocket's nose pointy, the project has delivered this attachment base for custom-buildable fairings.

--Juno V Decoupler--

Description: Developed after complaints that there weren't enough large decouplers available, this decoupler is best suited to the larger bits of the Juno V launch vehicle.

--Juno V Fairing Base--

Description: A large base for custom fairings. Can be somewhat heavy when surrounding a large payload, but everyone agrees that fairings pull their own weight with their superior aerodynamic properties.

--Juno VI Decoupler--

Description: A specialized decoupler for the 3.125-meter Juno VI rocket stacks.

--Juno VI Fairing Base--

Description: Our engineers were initially skeptical of whether or not we actually needed yet another fairing base. However, it was quickly shown that fairings don't work very well when they don't match the rocket stack they're attached to. Accordingly, a base for custom fairings was quickly commissioned for the 3.125-meter Juno VI launch vehicle.

--5-Segment SRB Nose Cone--

Description: The idea of combining the Sepratron motor with a nose cone seemed obvious enough, and we were impressed by how well it worked. Although it's designed mainly for the unusual 2.25-meter boosters, it does a great job in preventing separating radial boosters from striking the center stack.

--Bacon Docking System--

Description: After many complaints about the Clamp-O-Tron series docking ports, we came up with this innovative new device. Its connections are slightly stronger than the older ports, and it has a much lower profile. Better yet, it's backwards-compatible with Clamp-O-Trons of similar size.

--Bacon Docking System (Parachute)--

Description: Nobody is sure how the Bacon Docking System's designers managed to cram three whole parachutes into a docking port while leaving the crew hatch unobstructed, but that's exactly what they've done - no longer will you need to worry about all those silly radial chutes for your docking craft!

 

 

 

Edited by GreeningGalaxy
Link to comment
Share on other sites

  • 2 weeks later...
  • 3 months later...

Hi,

My request isn't mod related but it is English and KSP related so here goes:

I am desirious to spend a few weeks to try and organize the dozens of craft I have built and released all over the forums and elsewhere since January when I started playing KSP "seriously". I have an existing craft directory but it's kind of ultra technical and thus boring and no one will ever read it so I will someday redo it and categorize them into different mock companies developing different flavors of craft.

For instance, I have a 'kitten space program' which endeavours to seek out space tuna and unravel the secrets of intergalactic yarn.

A terrestrial rover program alternates spontaneously between huge American SUVs and tiny compact cars based on need.

An airplane design program seems to always want to finish projects that real world aerospace engineers run away from, make videos of them then move on to something even more impractical and never-flown.

I'm quite alright at writing fluff text for the first category above, because it's a one-liner description, but I could use help to write equally catchy summaries for the other programs and perhaps overhaul my YouTube channel description too (which was written while I was a complete and utter noob).

Let me know if anything above could lead to generation of fun descriptions :3

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...