LordFowl

Flamethrowers are actually moderately effective if you fiddle with the gas contents with gas coolers.

On the new planetmap the janitor closet is 1x1 tile large, with all items on that tile.

Aurora is mallcops = god is dead, apparently.

A security whitelist is not likely going to happen any time in the future. Sorry for breaking the bad news, but discussing it on this thread isn't exactly pertinent. That said, if we were to entertain 'realism' in arming our security personnel, the most sensible side-arm for them to be equipped with is not a ballistic pistol at all, but rather an energy pistol. It has the capability to both stun and kill, and possesses sufficient means to accomplish both without being excessively lethal. It is also the more suited for space combat, and is the more technological appealing. To be perfectly honest, I wouldn't mind phasing out separate taser and pistol sidearms and consolidating both functions into an energy pistol - its the logical step.

There've been rounds where radio has been down due to 'ionospheric disturbances' than it has been up. Baycode bandage to their rubbish round longevity isn't needed on Aurora, as we are clearly the superior server.

Legend goes that once, in the long forgotten land of Auroracode circa 2015, there were clearly outlined station directives. But then the Baycode came, and the world changed as we knew it. Amidst the flurry and noise, the rumour of new maps, the screams of 'wag your tails' and 'baycode is ghey', we lost a great deal. When the dust finally settled, they say that station directives ranked among the casualties. But this is not a tale of tragedy, for the legend goes that the features of Auroracode and Baycode will be reconciled again one day, and harmony bestowed upon the NSS Exod- Aurora. NSS Aurora.

I will never consider characters that break the lore to any excessive point to be canon in any fashion. Furthermore, non-canon events cannot be punished with canon punishments. Following your example, if security were to start executing people regularly, but only on non-extended rounds, then they CANNOT be punished ICly (Except in that round), for example by DOs. They can only be punished by OoC means such as player complaints and ban requests. Removing Vaurca from security is at this point being masked as an IC decision, and thus cannot be based off of non-canon or even roughly canon occurences. That there are players disrupting the canon with their lorebreaking characters is an issue that needs to be resolved through OoC means. As for your point, Dreamix, I agree that the Vaurca lore is rubbish in terms of why they're employed. But restricting each Vaurca to janitor because that's logically the only role they could fill is not particularly fun for Vaurca players. The lifeblood of this game is is diverse pool of occupations, and scenarios that derive from those occupations. Restricting Vaurca arbitrarily from those occupations will only make people less inclined to play Vaurca, favouring other races and debasing the unique opportunities that Vaurca could experience. Ultimately, the solution for this circumstance is abundantly clear; 1) Strip the whitelists of bad-apple Vaurca players, and restore balance to the canon. 2) Rework the Vaurca lore. Covert0ddity's lore is fundamentally flawed, and we should not be adverse to changing and fixing it.

It also wouldn't be hard to say "If we can't trust these damn insectoids to manage crew, what makes us thing we can trust them to make sure our space station's engine doesn't EXPLODE/research WEAPONS and BOMBS/perform SURGERY on living crewmembers/cook us FOOD!!!" This logic could've applied to any race when we had a lot more restrictive Head of Staff roles, not too long ago. But we never did that. Why in God's name would we start now? Because of a handful of rubbish Vaurca players? I think not. You exaggerate greatly. There's a major difference in not trusting a group of aliens who are acting retardedly and aggressively in Security roles, than ones who calmly contribute to research, or cook food. I exaggerate little, and no more than those who want to see Vaurca banned from security, jumping from poorly constructed and excused IC platforms. People seem to fail to realize that the bad apple Vaurca players will act aggressive and retarded no matter what role they are in. Banning them from security won't make your problems go away. Also, if their aggressiveness was canon (Which it isn't) then what would stop them from being aggressive in science or other departments? The fallacious argument that Vaurca should be banned from security is a misdirection of our efforts, and is a gap in logic.

It also wouldn't be hard to say "If we can't trust these damn insectoids to manage crew, what makes us thing we can trust them to make sure our space station's engine doesn't EXPLODE/research WEAPONS and BOMBS/perform SURGERY on living crewmembers/cook us FOOD!!!" This logic could've applied to any race when we had a lot more restrictive Head of Staff roles, not too long ago. But we never did that. Why in God's name would we start now? Because of a handful of rubbish Vaurca players? I think not.

This is a terrible idea, and it was to me a terrible idea when it was first posted, and in that interim nothing has changed. Station security is a general staff position. It holds no greater importance compared to any other role, and thus banning Vaurca only from security makes no sense, especially if you're masking your actions under the guise of IC considerations. Banning Vaurca from every role except for a select few makes sense ICly, but OoCly is unbearable and something I would not stand for. The pattern for race blacklists has always been abundantly clear; roles that already require a whitelist, and thus demand more tolerance and consideration from their holder, experience race blacklists. If security were to be a whitelisted role (Which is an idea I also oppose, coincidentally), then this decision would have merit. There can of course be implied blacklists. Someone brought up Dionaea being banned from EMT (Which is untrue), and while the reasoning for it makes sense, I could hop onto the server right now and roll a Dionaea EMT and be very surprised if anyone took administrative action against me. Now, this thread diverges from the previous thread in one key circumstance; it uses SilverTalisman's official post as some sort of platform to present its idea. Ultimately, this is a ridiculous notion when you consider the following: If you ban Vaurca from security roles and justify it as NanoTrasen recognizing that Vaurca are not suitable for security because there are shitty Vaurca players who play security poorly, then what you are really saying is that we should take IC actions based off of OoC failures. The failures of sub-par Vaurca players are not intrinsic to the Vaurca race, but rather their failure to roleplay the race properly, to take the cultural considerations to heart. IC punishment based off of OoC considerations is violating a core tenet of this server, and makes little sense once you realize the very important fact that shitty Vaurca players will be shitty Vaurca players no matter what role they are in. This thread marginalizes the fact that there are shitty Vaurca players in all roles, and really I'm inclined to believe there are more in engineering even than in security, from what I've seen. IC punishment systems are all fine and good, and they give DOs something to do, and they make a comprehensive universe and all that. But at a certain point they cannot fix the core issue of a player. OoC failures require OoC administration efforts, not hair-brained schemes and IC contrivances to "punish" them 'damn bugs'. The whitelist system is ingenious because it gives us power over players; the power to strip their whitelist. It is time to start exerting that power. IC punishments and DO reports and company decisions no longer stand tall enough to conquer the problem. When Jamison Stamos was fired by the DOs, it did little to stop his player from creating Za'Akaix'Ghul Zo'ra. I reiterate, in case that my previous words fell upon deaf ears: It is time to start stripping whitelists. Altogether, while I can support some elements of this suggestion, in its current state I can give it little more than a very heavy '-1'.

Baycode already provides us with more clothing options than we could use. Why exactly do we need more 32x32 sprites, except for your stated reason of 'blue jeans'.

>implying security officer's don't already stun to coma.

But we do, as is indicated by the sprite.

Since SoundScopes no longer exists, bumping this might be relevant. So I will.

Its all your fault, Alberyk. Thanks a lot.

Thank you very much for the feedback. I found the Unathi lore you wrote to be extremely interesting and compelling, and could not help but integrate it into my application. I'm sorry that I did not abide by the two paragraph rule, but I was rather tired when I wrote this and forgot about it.

IPCs, Cyborgs, and AIs can interface with the archives and download books to their memory drive, to be called up at any moment.

http://aurorastation.org/forums/viewtopic.php?f=28&t=4730 You do not need to have feedback for an application to be accepted, and a moderator of applications should not require feedback to make a decision. That would be utterly ridiculous.

BYOND Key: Lord Fowl Character Names: Zultar Karjei, Maximus Crane, Ka'Akaix'Krull K'lax, Two Birds Beaks Together, HI-47 MkI, various cyborgs and AIs. Species you are applying to play: Unathi What color do you plan on making your first alien character (Dionaea & IPCs exempt): Sandy brown. Have you read our lore section's page on this species?: Affirmative. Please provide well articulated answers to the following questions in a paragraph format. One paragraph minimum per question Why do you wish to play this specific race: tabtabtabtabtabtabtabtabtabtabtabtabIt is my utmost desire to experience the full extent of racial diversity that our server presents, and Unathi are the natural progression in this regards. Originally I disregarded Unathi and Tajara as little more than furry races, but upon reading Unathi lore I found a complexity that I did not expect. The Unathi strikes a most particular character that is most distinct in its nature. This is a culmination of their culture and history. Identify what makes role-playing this species different than role-playing a Human: tabtabtabtabtabtabtabtabtabtabtabtabThe Unathi is to me singular in the nature of their history. While their culture serves as the typical spartan offshoot, the nature of their history suits me quite well. They come from a homeworld that is at its very base destroyed, perhaps even beyond repair. Their situation is at its most base quite fucked. This provides a most unique situation to base your character off of. The biological distinctions of the Unathi are ultimately inconsequential compared to the stark contrast of their nature versus their situation. A proud race of culture forced to live in utter destitution inspired by nuclear warfare. While not an uncommon archetype, I find it to be very compelling still. Character Name: tabtabtabtabtabtabtabtabtabtabtabtabK'orzga Rakhir Please provide a short backstory for this character, approximately 2 paragraphs tabtabtabtabtabtabtabtabtabtabtabtabThe nature of clan dominance in Unathi culture is always one of military supremacy - the most dominant clan is the most pervasive and capable in terms of combat. Theirs is the clan of honour and acclaim. However, this accepted, it becomes clear that not every clan can be this most dominant. The very nature of this system of dominance mandates that some clans will inevitably be menial in nature. That is not to say that their disposition is that of service, nor is it to say that their warriors do not act with honour and lethality. Rather, it is acceptance of inevitable fact; the machine of war needs be fed constantly in both literal and a-literal terms. Ever since the conclusion of the civil war that preceded the domination of the Third Hegemony, the clan Rakhir has satisfied this role. Once the smoke from the feud between the Honoured Alliance and the Izweski nation cleared, the Rakhir clan dutifully filled the gap of resources caused by the desolation of the war, acting as a conduit in the growing nerve system of the Third Hegemony, distributing their tithes to their clanlords and doing their service in building the glory of the Izweski nation. Upon the culmination of this Moghes-spanning glory, they settled firmly into the trade of aquaculture, producing massive quantities of fish for their liegelords.. Under these conditions, in the year 2421, the one known as K'orzga Rakhir, son of his father, was borne under favourable conditions - clearly indicative of the good-will the ancestors bore for him. With his brethren he oversaw the operations of his clan, under his father. The hatchling Rakhir had grown to the formidable age of twelve by the time the first alien crafts probed onto the Moghes surface, and while the Rakhir clan did not directly encounter the foreign intrusion, the ripples that alien presence caused were still felt. The tide of foreign technology eventually passed over the Rakhir clan - passed over because these staunch traditionalists refused the breach of custom that these energy devices threatened - and for a short time the Rakhir clan experienced a period of normalcy, despite alien intrusion. This normalcy was shattered when K'orzga's father became terminally ill, and passed on to the ancestors. His eldest brother took the seat of Rakhir, and the care of his father's mate. This shift of power was interruped by the explosion of tension that would develop shortly after the first colonist launch's failure. K'orzga's brother, his clan-master, allied his perspective with the other staunch traditionalists. After the success of the colonial endeavour in 2438, he joined them in their Coalition, seceding from the Izweski Hegemony through force of arms. tabtabtabtabtabtabtabtabtabtabtabtabAs fighting escalated, it become inevitable that the Rakhir clan would need to deploy its forces to assist the coalition. K'orzga and his kin were distributed across the fighting force of the Coalition. K'orzga himself was assigned to a bomber team, performing navigational duties for strikes on Izweski supply lines. By June of the first year of conflict his squadron was performing bombing runs on supply lines as distant as S'th. While Coalition ground forces were decimated by Izweski breacher troops armed with energy weapons, K'orzga and other bombers faced difficulty mostly only in anti-air weaponry which typically defended entrenched positions. As the war progressed the air-front shifted back and forth. While K'orzga's operations in the later war typically centered around supply lines outputting from the city of S'th, his duty involved his squadron in two distinct pushes for the city of Ma'ha'rem; however both operations ultimately failed. K'orzga's bomber vessels typically employed high density incendiary explosives, designed to irreparably damage ordinance and to indiscriminately clear auxiliary settlements that could possibly be providing support for Izweski forces. tabtabtabtabtabtabtabtabtabtabtabtabIt came to be then that on a fateful January morning in the year 2439 that K'orzga experienced the latter wave of the first round of nuclear demolition. Unaware of the destruction of Da'ha'den, his squadron was flying reconnaissance over Baandr when K'orzgr witnessed what he would later describe as a 'bright flash over the horizon, followed by a massive explosion singular in that it was completely without noise.'. For a long moment, his bomber flight continued along a normal flightpath, before suddenly being hit with sudden extreme turbulence. As a wave of sound washed over the aircraft the turbulent wave caused the bomber to flip over mid-air. Within a mere moment they were plunged into a rapid downward spiral, accompanied by stark cacophony accentuated by the previous moment of soundlessness. The sudden change in altitude caused K'orzgr to black-out before he could reach respiratory gear. tabtabtabtabtabtabtabtabtabtabtabtabAwakening among the debris of his broken aircraft, K'orzgr stumbled to his feet. The air around him was filled with thick smoke and burning embers. The scent of incinerating fuel was distinct. Ultimately, the crash would have been totally fatal had they been operating a bombing run - the payload would've detonated within the bomb-bay, causing the entire plane to be destroyed. Even so, K'orzgr was unable to locate his fellow sky warriors amidst the debris, and was forced to quickly egress from the crashsite. Perched on the foothills of the long coastal mountains, K'orzgr could see nothing of what would in later years be named "The Wasteland". Even so, he felt a slight tingle to his skin that penetrated beneath his scales. Turning his back to the mountains, and facing the debris once again, K'orzgr had little choice but to move on. Despite the calamity that had just occurred, the full extent of which he did not yet realize, he had to face the fact that there was a war going on. In these contested zones the destruction of his squadron would have been noticed, and hostile forces could very well be inbound. It was imperative that he arrive at Baandr, for from there he could path across the mountainrange and arrive at Coalition territory - in particular an airfield some distance West of the Baandr gap. Traveling quickly under the brush, he stayed away from the rather empty roads. Despite the recent disasters, the entire world seemed perfectly still. As day began to break, K'orzgr took shelter in a shallow alcove in the rocks, peering outward suspiciously, gaining no rest throughout the long day. By the time night fell once again he was already traveling, and by morning he had arrived at the outskirts of Baandr. The city was crawling with displaced Unathi. Hordes of shattered clans surged at the city's walls, possessing nothing but the clothes on their backs. More than K'orzgr had ever seen, and even more were pouring in from the gap, fleeing from whatever lay beyond those skypiercing mountains. He hesitated for a moment as he saw Izweski soldiers filter the horde, rejecting far more than they accepted. He then scampered through the brush, entering into the mountaingap. As he approached the western plains, dust began to fill the air. At first only in moderate amounts, but soon blinding waves of dust scoured across the rockfaces, and against his scales. He ripped a piece of cloth from his robes, and tied it across his snout, and another around his eyes. Bursting at last from the wave of refugees he finally arrived at the western plains, a fertile region where much of Izweski herding and been done before the war. Gazing upon this once verdant scape, he saw only desolation. Dust and wind scoured at bare rocks which had once been adorned by layers of sod and grass. The burnt husks of trees stood weakly against the ravaging winds. Far in the distance thunderclouds rolled, distinct in their sickly green colouring. For a moment K'orzgr faltered, before proceeding towards the location of the Coalition airfield, some miles west of his position. When he arrived it was completely empty. He made his way to the command post, where the transistor radio was still barking orders, garbled by radioactive wind. "Arr-bzzzt-eld Baandr, r-bzzt-loy to Res'ka-bzzt-. Airfield Baandr, redep-bzzt- Res'karum". Res'karum was miles to the northwest, and nestled deep in another range of mountains. It was not a trip K'orzgr could make alone. Departing the command center, he looked around for any supplies or ordinance, and was sorely disappointed. As he prepared to leave once more, he reached a conclusion. Whatever had happened, it was clear the war was over in its traditional sense. The Coalition was completely abandoning the S'th front, the push for Ma'ha'rem and from there Scalamar. It was more imperative to him then that he find his clanhome, Rakhir. It lay to the northwest too, but far from the mountainranges. It was somewhere across that burning plain, where once stood mighty forests and ran glorious rivers. tabtabtabtabtabtabtabtabtabtabtabtabHe traveled for days, resting during the heat of the day and traveling amidst the cool of the night. Some days he could not travel a foot because of the scouring dust storms, and some days it was clear as glass, though the horizon was always shadowed by the ominous thunderclouds. Some days the roads were empty, and some days they were packed with surges of refugees. He passed by abandoned villages, their huts still warm with the pulse of life, but completely devoid of any inhabitants. By the week's end vehicles began to appear. They patrolled the roads, impeding bands of refugees, stealing them away at gunpoint. As time passed the villages K'orzgr began to pass stopped being simply abandoned, but looted also, stripped of valuables by foreign hands. Corpses began to be a more common sight, some stricken down by that strange tingling radiation that permeated the air, but more and more stricken down by bullets and knives. Still, he traveled forwards, until he reached the river Ka'zzir, where once his clanfather had taken him to hunt the forest-killer, dreaded beast of wild lands. Once mighty and great, the river was reduced to nothing more than a trickle. Debris both natural and artificial dammed the river. Shattered cliff-faces and huts swept away by the raging winds ensured the river would never run again. On its distant banks there was no life. Where once had been verdant canopies and deep forests, there was nothing more than burnt stumps, continuing for miles and miles. The bridge that lead across the water was shattered, its stone edifice crushed by overwhelming force. Of the city beyond, he could see no trace. The horizon appeared to disappear. Crossing through the charred riverbed, he climbed the bank and looked for a way to progress, through the incinerated brambles. After many hours of circumnavigation, he arrived at a lofty hilltop, which ascended above the torn brush. He ascended, and at its peak saw before him nothing but destruction. Where once his clanhome had been, the many villages which pulsed around massive aquaculture pods, there was nothing. Rather, there was something, but that something was defined by its lack of anything. The entire city had been wiped away, and in its place stood a simple crater. It was smaller than K'orzgr would have expected. Turning away, he departed from the tomb of his ancestral home. tabtabtabtabtabtabtabtabtabtabtabtabTry as he might, he could not set himself upon the path of Guwandi, for though his clan-honour had been wiped and his home destroyed, he felt a strange optimism. Though his kin had passed from the mortal world, they had not passed from existence - surely they now safeguarded him amongst his spirit ancestors. Even so, he began to face the realization that he could not stay in Moghes. There was no thing left for him here, nor any thing left at all in most cases. While the shattered remains of the Coalition he had once honourably served scavenged for even the barest morsel of sustainable land, K'orzgr sought egress from Moghes altogether, an opportunity which was granted in the summer of 2441. He became a planetary navigator for a bluespace shuttle service, and from there escaped into the wide galaxy. Working on their shuttles, it was inevitable that K'orzgr would come into contact with NanoTrasen. He worked upon various vessels and stations, running navigation, communication, supply, and etcetera. In the year 2444 he was given an opportunity he could not refuse - selected as part of one of NanoTrasen's 'diversity programs' publicity stunts, he and hundreds of others were given the opportunity to receive advanced schooling. Halfway through this process, in the year 2448, the remaining students were given in-depth medical screening. It was there that K'orzgr discovered that due to large buildups of radiation in his system it became likely he would develop a terminal concentration of cancerous cells in the near years. Despite this impediment, he concluded his schooling in 2452, and returned to NanoTrasen work in the year 2454 in positions of elevated authority. What do you like about this character? tabtabtabtabtabtabtabtabtabtabtabtabThe character resounds with me. I feel inspired to play as him. There is little else to say on the matter - his nature suits me well. How would you rate your role-playing ability? tabtabtabtabtabtabtabtabtabtabtabtab10/10 would roleplay agaib Notes:

He means a literal blob. Big green smashy thing that eats walls, weak to emitters.

The voice shouldn't be like ol' Baldie, as cool as he is. It should be neutral, emotionless, and without intonation. Think like the black mesa Vox system in half life 1. This makes it more dynamic, as a plus.

Is the coalition just pooling together for one president?

The most simple and sensible tool I feel would be a PDA with a special datajack implant.

You're putting far too much stock into this nebulous region of emotions, and that line of thinking bears two significant errors; 1: That current AI iterations don't display or utilize emotive response. Canon or noncanon, it is inevitable when you have a human controlling them. B: That people care if the AI has emotions. Emotions will not change malf-meta. Ultimately, a mobile AI will bear similarities to a cyborg, regardless of whether it 'breathes and has emotions' or not. Tacking on emotions and two additional but ultimately meaningless laws (Unless the AI is an antagonist, but even then they're still meaningless because AI's that are antagonists are assumed to be malfunctioning and thus the player can bullshit their way through explaining their emotions as achieving greater sentiency anyways), only belabours the suggestion. Looking at the facts, we reach the following conclusions: People will metagame malfunction rounds, no matter what. People will never sympathize the AI, no matter how much you tell them 'dude it totally has feelings and stuff!' People will gladly gun down the AI if it makes itself vulnerable under the slightest suspicion. Hell, people break into the core and kill the AI over innocuous ion laws already. People will still think of the AI as nothing more than a tool. The AI will still crack fucking awful jokes that no one invited them to make.

Countering the hallway spam would be adding an activation message, so that everyone knows who the dickweed changeling is that's trying to turn everyone into a kawaii lesbay scientist with floor length hair. Perhaps make it un-activatable when bound? I too like Delta's strategy, but the strategies mentioned by Sue are very irritating.