Fyni

I am very much in favor of this. I believe 516 has made the lobby actually whoose by faster. Additionally while we are plagued by the DDoS and reconnects on restarts not been smooth I'd like to see it perhaps extended even further.

This comes after lengthy discussions with multiple people, and I believe now it's best to draw on the wider community. Currently, canonicity in Ody works as follows: Maps are screened by the lore team. Any which contain elements which may be none canonical (the cyro section of cyro outpost, or the ICBM bunker of artic valley) will always be none canon. Ody is voted in round. A map is selected at random. If it is not one which is forced to be none canon, it is randomized if it is canon or not with a 50/50 coinflip. Note this heavily favours none canon from an RNG stand point, as it needs to both roll the few maps with canon chance then roll canon on that map too. The round plays out based on that, with guidelines in place on the wiki to ensure canon Odys do not go "overboard Ody is still fairly new, and Aurora is, I'm sure we have all noticed, dying, helped along by the DDoS. We've not had a glut of STs (it's intimidating), and the majority of Ody rounds (every single one?) over the past month have been run by me or Sadkermit. These rounds very often happen to be the high pop rounds, as it were, and this is due to the fact we drum up intrest in Discord as best we can before a round. People are excited for Ody rounds. ST can be hard. You need to think of ideas ideally in advance - and I know a lot of people do, I have DMs of people comign to me with their ideas - but this can easily be scuppered by canon RNG, map RNG, pop and crew dsitributions not been as you hope or a lack or overabundance of actors. We can't control all of these (though we can help on the actor front by adding an actor to ready ratio and a ghost role actor spawn that STs can use, but that's a story for another time) but we can on canonicity. I have had this happen to me. I have managed to DM Mel in the past to give a round a nod. "Oh yeah, this is canon." These rounds have often come out wonderfully - a highlight been our lost G2s round. The canonicity of the round provided more reason to engage with it, and allowed for it's fun to continue even into other rounds and onto the relay. I believe there should be power invested somewhere to allow a choice to be made. These are my preferred solutions: The Complicated Solution: Remove Ody from the game mode vote. Add instead "canon ody", "none-canon ody" and "random ody". This allows the whole server to decide - and since Ody is often voted for because a ST speaks up in advance, they can ask for their preference. The Double Vote Solution: Add a canonicity voting round after Ody is voted for. Simpler, but may annoy people who will play one but not the other (do they exsist? I'm not convinced but eh) The Nuclear Solution: Allow STs to flick a switch to decide canon/none canon. The Slightly Less Nuclear Solution: Allow STs to flick a switch only if the map is approved for canonicity. The Sensible Solution: Power should be invested in someone like Kermit, who is active on the server and a member of the lore team, to make the call based on their knowledge of the ST, their plans and the map. (her activity makes it far easier instead of explaining at length what a round is to Mel or similiar), perhaps with restriction in place. My preference is for the complicated solution, or the sensible solution. Of course, there may be a reason for canonicity been as it is. Matt has commented on the past about it, but the reasoning is spread out and I feel having it in one place will be helpful as reference.

Run Canary Run

Perhaps true - but I don't think removing it and adding stowaway should be in the same discussion.

Make hearing it an optional preference and I'm all aboard. Forced - and I'm not

I don't think visitor needs to be replaced - it can be fun in itself - but I think having stowaway be a semi rare ghost role would be fun.

I've seen you play a lot since then - both on ship and as off ships. This sort of ban isn't about the quality of roleplay, but potentially taking limited job slots from people just because you didn't roll antag. I'm happy to lift this ban since you've shown you're happy ot play through a round in a rolled slot even without the antag slot.

Reporting Personnel: Z.I. Circe Job Title of Reporting Personnel: Investigator Game ID: cze-dxu9 Personnel Involved: Z.I. Circe, Investigator - Witness / Victim Vera Lockheart, Paramedic - Offender DAAU-51K, Executive Officer - Witness IRU-Yama, Investigator - Witness Time of Incident: 23:30 Real Time: 23:30GMT 22/4/25 Location of Incident: Medical Lobby Nature of Incident: [ ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [ ] - Neglect of Duty [x] - Harassment [ ] - Assault [ ] - Misconduct [x] - Other: Potential breakage of i222 Overview of the Incident: Over the common comms, Vera Lockheart stated they were a synthetic, a claim they repeated after been questioned. I moved to verify this claim, but was prevented from doing so by lack of access. They later repeated that they were "sneaky" and after a medical scansaid they had a device which would fool such scans. They never rescinded these claims, despite questioning. I have also been informed that if their claims are lies, then this is a case of anti shell IPC speciesism. Submitted Evidence: N/A - Command on shift prevented further ivnestigation. Would you like to be personally interviewed? [x] - Yes [ ] - No Did you report it to a Head of Staff or a superior? If so, who? If not, why? Yes - DAAU-51K, Executive Officer Actions taken: DAAU-51K ordered no investigation take place. Additional Notes: Multiple crew members attempted to prevent further investigation, so no conclusion could be found.

We actually have a "massive moving meteor is on inbound to the Horizon in the overmap" event, however it seem to be extremely bugged that I do not think I have seen it genuinely fire in the 6 months or so it has been in the code. Additionally, security does not need any more gameplay. Ideas for loading and operating guns should be within the purview of Operations - as it currently is.

I see both those boothes used semi regually, and both holodecks not as much - but again, they are used. They are prime roleplay spaces, and if something was to be taken out it should not be them. I agree that more space is good, though there *does* already exsist multi spaces which beg to be converted and in the rare instance where such works are done, are. These include the secret D2 bar, both nacelles, the massive empty space behind D2 sec, the former crew arm, the former RUST(?) engine space. Additionally, there is nothing stopping convertion of a holodeck right now anyway.

You are required to use the format found below for all species applications and not a downloadable file. It should be a simple matter to copy paste - presuming it is correctly formatted. Please edit you post.

It ain't easy been pink.

The ultimate answer to this is always - will you be playing them all in 3 real life years time? If yes, will all the characters you built those relationships still be around? Add in that even if there isn't a timeskip, there is likely to be a new ship / station / colony / MAP which will effect them and the people around them too. The shift from the NSS Aurora to the SCCV Horizon saw many just make new characters to exploit the new freedom they had in character creation, and today years later you hardly see any of those who were transferred. Aurora can't stay on the Horizon forever.

Your own diagram shows 1 to 6 going down. There are no minus decks. Per wikipedia: It numbers from 1 to 4 for the superstructure - something which the Horizon lacks (but these diagrams do not) Again we see "the main deck", the uppermost one which covers most of the space, numbering down as you go lower. The US Navy seems to distinguish the "levels" as the things above the main deck, and decks as the maint structure of the bridge. Some cruise ships use the numbering system of buildings (1 or ground is bottom, moving up), but that's purely because they are cruise ships, and designed for the majority of the people aboard to not be use to life aboard a boat, unlike the Horizon where the crew live aboard sometimes for years at a time. Been fun to research all this lol. I propose we do a Polaris and email Nasa to see what they would do.

Some good ideas if the Horizon was ever remapped. All I want is for the decks to be numbered correctly (I.E. like every single real life boat/ship, and the majority of fictional ones). Bridge/top should be 1. If we assume there are residential decks on the bottom of the Horizon, they go from 0 to -5 or something???

Loorey and I have reviewed the logs and both testimonies. To cover the important points: 1. It is expected that command members do give room for antags to do their thing - this is a key part of getting the whitelist. Accepting bribes and been corrupt is generally acceptable to a point, but command players should keep in mind the flow of a round. Once an antag "goes loud", so to speak, the action of command charcter should reflect this. 2. Having a character permabrigged is almost on the same level as killing said character - it often removes them from the round, away from any action and roleplay. Care should be taken when pushing for such. I know in a way Cam intended for them to be obviously innocent, but again the chaos of a fully escalated round was in action and the flow should have been obvious - security will likely not question this. Command members should be aware and concious of this. 3. Headset removal. While it seems the full removal of the headset was a miscommunication, we would like to stress that security should not be removing headsets and PDAs from people in the brig unless they have a good reason to (which amounts to them been shown to abuse this priveledge by shouting insults or similiar). In part, this is because uplinks for antags can be hidden in these things, but also because without any way to communicate with the outside world, once in the permabrig this completely cuts them off from the round. Loorey and I have discussed this matter, and the appropriate action will be taken. This complaint is now closed, but the thread will be open for 24 hours if anyone else would like to comment

Alternative opnion: do not give them a new office but make them share one office. Let the resentment foster.

Ckey/BYOND Username: Fyni Position Being Applied For: Wiki Maintainer Have you read the Lore Team Rules and Regulations wiki page?: I read the wiki maintainer rules Past Experiences/Knowledge: When I was younger, I made several wikis for self made fantasy worlds on wikia (now fandoms) (ew yes I know). More recently, I've contributes to a niche wiki based on Mediawiki before it went down. Examples of Past Work: Sadly, I am either too embrassed by the wikis I made in the youth or the more recent have gone down. Additional Comments: I had a talk with Trio about the wiki just the other day. I'm someone who likes to make many quick and small edits where needed just to make sure things are upto date, but also have an unreasonable passion for standadization and templates, something which the wiki formats greatly help with.

Average Hazel round working in the kitchen

I have fun interacting with all of Max's characters, but more importantly I know him to understand the dynamics required of HRP and have no doubt they will excel in pushing this understanding into command where it can really allow rounds to flourish.