wowzewow

Yeah, basically. Other servers have the curator role. Which is kind of weird we don't have something like this. For all the arcs and adventures the server's been on, we don't have much to show for it. They're just collecting dust in the codebase. Would be interesting to have a Silversun shirt in a display case or something, and then like, an Artillery shell from one of the Tajaran arcs.

The crux of the issue is that hydroponics is entirely dependent on the Kitchen for any roleplay whatsoever. Which is bad. It's also bad faith to believe that it will take away RP from the chef, which it shouldn't - it's at most going to be an extension of the kitchen. The same argument could be said about the bar, but the matter of the fact is that it's all going to be localised into one area anyway, and they all have their own specialites to justify their existence. You aren't going to see the hydroponicist cooking food, nor the bartender mixing up drinks, usually. Tables in front of the window or public garden are fixed to the issue, sure, but it's all the more reason to officiate it.

cool fucking image of a skull i found

i come from the future yeah i got nothing

So the other day I finally was face-to-face with an actual salad bar. I don't know why I haven't actually been to one all this time, but that's besides the point. Hey, this is fun, I thought. People ask, soup or salad. Well I made a super salad. I rather...*specially* combined everything. Every sauce, every oil. I came back with a plate of vegetables. It was pretty good actually. Well, it tasted like the inside of a Subway (the crappy sandwich fast food chain) but I guess I'm more healthy now. Basically, add a little alcove for the Hydroponicist to lay out their vegetables and whatnot. Should probably add in some bins, trays, salad tongs too. And maybe some sauces like Thousand Island and Italian vinagarette or whatever. Makes their lives a lot less dependent on chef. Hell, doesn't need to be a salad bar. Can be a lemonade stand, a vegetable store, whatever.

The High Inteference Jammer and Comms Killer. Originally a standard surplus C-UAS gun, co-opted by guerilla millitias with some rather creative illicit aftermarket modifications. A portable cherynobl of common transmission waves, it requires a large back-mounted battery to support its immense power consumption. When it is in use, it generates a wide cone in which communication devices are bombarded with inteference. Anyone unwise enough to continue wearing their headsets will experience a deafening screech, and mild nausea. Stationbounds and Synthetics will experience a gravely disorienting bout of confusion, unable to walk properly or form coherent sentences. Computers, PDAs and suit sensors will struggle to function - sending their data into a sea of gibberish. Note that this doesn't do damage at all, even EMP. Just some mild radiation. It's an utility weapon, after all. I'm just spitballing here, I just think another pacifistic alternative would be interesting.

Ckey/BYOND Username: Wowzewow Position Being Applied For: (Wiki Maintainer, Lore Developer, Deputy Lore developer): Wiki Majnt Have you read the Lore Team Rules and Regulations wiki page? Yes Past Experiences/Knowledge: Wikipedia, Rimworld Official Wiki Examples of Past Work: I made a majority of Peter Barakan's wikipedia page. I honestly cannot give you a good explanation of why I did this, but it's a pretty good showcase of my skills. Additional Comments: I'm mostly going to add infoboxes and fiddle with navboxes. Maybe add more hyperlinks. Seperate and sort out pages so they aren't PARAGRAPHS long. Spring cleaning. This app is mostly so I can get access to the channels to communicate with the existing wikimaints without flooding the general chats, because I'm going to be more particular about things and I want to have absolute clarity.

Well, I agree with you. However, stasis beds do need a nerf, that's for sure. As of now, it's a jack of all trades, and a pretty good one at that. But it will not be too drastic - I agree that there needs to be a bonus to getting someone all the way to medical, it's always disappointing to lose someone even though you put in all that effort in. It definitely should not be a "100% survival chance", there still should be stakes, after all. I'll look into the balance where it stops metabolism for stasis beds, so it'll have a proper "niche", either that or tweaking the stasis potency. I'll also see if I can add mild bonuses to rollerbeds and whatnot - it's a lot more preferable to bleeding out on the ground, a "better than nothing" bonus.

Well, I feel that Tau Ceti Basic is already implied to be a spiritual successor to English - being the lingua franca of the whole setting, and derivation from Esperanto, which has germanic roots.

Well, the problem here is that with a chemist, they practically are a superior sleeper in every way, because you can practically hook them up non-stop with some of the more powerful medication which is balanced around the normal metabolism rate.

Well, considering how large the scope of our lore has grown, having a language tied down to a single planet seems stifling in comparison. Speaking of which, Freespeak can still be used in the very same way, as a "martian rebel-language" by simply just using it in conjunction with a Martian Accent. So nothing is really lost here, you just need to roleplay it out more.

Some suggestions for additions : These are how I'd name the languages. Tau Ceti Basic (unchanged) Elyran Standard (unchanged) Solarian Hanyu (Sol-Yǔ [Translated : Sol-Speak]) Frontier Tongyong / Coalition Common ( [Translated : Tongyong = Common] Col. Com.) Soviet Interslavic (Interslav) Occidental Romantique (Romantique/Romantisch) Other than that, the languages themselves are pretty well thought out. I think they would fit in fine with our current lore, and definitely balance out the rather numerous accents across more languages. In addition to Coalition Common, I would also like to see added : Tenggara Asiatic (Asiatic) Lore Reasoning

Stasis beds are from /tg/. We use Baymed. I think it's safe to say that it's unbalanced, for the fact that stasis beds are used for completely different codebases. From what I've gleaned : Stasis beds... - take away the role of sleepers by providing the exact same stasis effect (and by extension, stasis *bags*) (Infinite chems from sleepers are essentially a non-issue once a single chemist is onboard anyway.) - take away the role of cryotubes for critical patient chemical injection... - and (formerly) operating tables. They were so good, ORs were literally abandoned in favor of stasis beds. There was an emergency patch simply just to rectify this issue. They have nearly outclassed every other piece of machinery in medical. They don't belong in this codebase because it's made for an entirely different medical system.

Personally I think it'd fit more with the rest of the uniforms. I only really left the job specific backpacks default as a holdover. KEEP IN MIND I'M NOT REMOVING THEM!!!! I'M JUST CHANGING THE DEFAULT FOR NEW PLAYERS!!!

Lore Impact (Small/Medium/Large): Small Species: (Skrell, Tajara, Human, Vaurca, Dionae, Unathi, Synth, General) General Short Description: Renaming Konyang How will this be reflected on-station?: Not much? Accents, I guess. Does this addition do anything not achieved by what already exists?: I don't think so. Do you understand that the project may change over time in ways you may not foresee once it is handed over to the Lore Team? Yes. Long Description: I'm making this for many reasons, so I'll try to articulate it as well as possible from my possibly undiagnosed ADHD brain. 0. Reasoning As of now, Konyang is just a name of a random Korean university, which isn't very good, seeing the unspoken rule that we should avoid any real life references if possible. Speaking of which, Konyang as a planet - in lore, stated to have a sizable diaspora of Chinese, Japanese and Korean settlers. (Despite this, Konyang lore leans HEAVILY korean, which I'm reworking it to be more balanced but that's a can of worms for another time.) Hence, it would be a lot more representative to have a phonetically ambiguous name. Not to mention Kai-Yong is already rather close in pronounciation and abbreviation to Konyang. 1. Pronounciation Kai-Yong is a romanized bastardization (like Peking from Beijing) of the word "Ocean" translated from the 3 languages, Korean "Dae-yang", Chinese "Hǎi-yáng", Japanese "Kai-yō". "Yáng" sounds like "Young", so it makes sense. Also to make life easier for the significant majority of the playerbase which is *not* asian. 2. Meaning As again, Konyang is an Ocean planet, and some names can just be literal. It also just so happens to be a Chinese name. Perhaps one of the original settlers? Not like it matters, the origin of the name is supposed to be ambiguous. 3. On Konyang Hell, we don't even need to do away with "Konyang", we can keep it as an old-fashioned romanization, like how "Peking" still exists. But for most official intents and purposes, Kai-Yong should be used. 4. Rule Of Cool It's cool. Hong Kong is a cool name. Hyphens are cool too. Makes it really *pop* from all the rest.

My two cents is that this is a wonderful idea of solving the mechanical issues that plague Cyborgs. Even if this does not solve the lore or roleplay implications, it is definitely a step up from what we have currently. Personally I feel it is too much to ask for ONE PERSON to solve a major roleplay issue, which probably requires a lot more input from lore devs. So, I'm up for implementing this.

I sure hope reactions are disabled for sections such as ban appeals...

On Contained Sprites 1. Abolishing contained_sprites as a folder altogether. Contained sprites is going to be our de-facto way we do sprites going forward. Therefore, as the default, it shouldn't be put aside into one folder since it's our new standard. Custom items are an obvious exception to this. 2. Try to match the OG path as much as possible. This'll save time digging around in .dmis looking for their paths when you simply can copy paste the in-code path. Works both ways. 3. Try to sort similar categories together As above, easier to search up. Plus, might as well use BYOND's inheritance thing. Good example is the sweater accessories. Thus, we can knock out the contained_sprite = TRUE out in one shot rather than manually setting each and every one. 4. If it is an image or overlay, put it with the object it is supposed to be overlaid with. If not possible, use path of object overlaid with instead. For example, the Skrell projector, the overlay effect is in the same .dmi for convenience reasons.

Looking to contribute to Aurora's sprites? Look here on our priority list to see what needs to be done. https://docs.google.com/document/d/1WUfDqmGtLbu1POlZJOqxo7ncC6Q7OUDCJ0arBD7orRM/edit?usp=sharing

Rules and useful guides! Please start here! https://docs.google.com/document/d/1ksUvJ98vDFJUZO0nQlotcDkmkHBCwaIoKDZWcDrIEFE/edit?usp=sharing

Above looks great honestly. Finally, crayons will be an essential kit for all EVA missions

Hold up, got a pic for this.

I guess you could re-use some of my ideas from here. Some new ones : Departmental Exchange Program (self explanatory) Musical Chairs (I've implemented picking up chair code and there's plenty of jukeboxes...) Spin-The-Bottle