naut

So recently I was part of a discussion talking about the status of in-character Incident Reports (IRs) done by CCIA staff, particularly regarding the way they were handled, how they apply, their process of information gathering/interviewing, and the roleplay element they contribute to, if any. I'd like to use this thread as feedback and discussion for potentially overhauling the way some IRs work, rather than shouting into the wind and complaining about problems. Some suggestions from the masses (I don't necessarily support any of these but I just want to throw in what's been talked about so far): Denying IRs that clearly are of little consequence to anyone and seemingly don't deserve HR's time to investigate. Encouraging Discord interviews either through the relay or through Discord messaging. Current stigma is that Discord interviews are a "last resort" and discouraged. Being more transparent in punitive action given to individuals, even if it's only available OOCly. Making CCIA interviews less "boring" and more proactive discussions, possibly by involving multiple people in the same interview.

Stellar Corporate Conglomerate - After Action Report SCCV Horizon Izulikh Humanitarian Mission - 29 June 2466 Class II Clearance - SCC Personnel Only (Not for Public Consumption) Overview The Izilukh Humanitarian Mission (henceforth known as the “Mission”) undertaken by the SCCV Horizon was designed to deliver relief aid to the village of Izilukh in the Northern Zazalai Mountains of Moghes. The mission was authorized on 25 June 2466, following reports of severe shortages of food, water, and medical supplies, aimed to alleviate the suffering caused by the Contact War and the ensuing Wasteland conditions and open the area for future developments and revitalization. Partway through the Mission, however, the Horizon crew was betrayed by the very people they were supposed to be aiding - the retinue and soldiers under Lord Izaku of Mudki - and had to abandon valuable equipment and evacuate. Some crew were tragically killed or lost in the process. Objectives Land in Izilukh via shuttle SCCV Apollo. Deliver 20 tons of food supplies. Provide medical aid and establish a temporary clinic. Conduct infrastructure maintenance and repairs. Survey and analyze the local environment. Distribute food aid to the local population. Notes Nralakk Federation personnel have set up a field outpost prior to the Horizon crew’s arrival and were planning to coordinate activities alongside. The field outpost was approx. 140 meters east of SCCV Apollo. No radio contact was made from SCCV Horizon to this outpost beforehand while SCCV Apollo was in transit. Frequent sandstorms approx. 30 minutes after touchdown of SCCV Apollo made travel difficult but were ultimately minor. The weather cleared afterward. The village was walled on three sides and against a mountain on the western end. Abandoned buildings were present outside the walls. The village was governed by Hegemony noble Lord Juyzi Izaku, Lord of Mudki. Locals noted bandits and a figure named “The Old One” that attacked people in the south of the village. The village aquifer was contaminated with a toxin that the research team believed to be small amounts of phoron, presumably from traces of Vaurca blood also found inside the aquifer. Locals and Horizon crew that attempted to drink the water fell ill. The Vaurca blood presence in the well was never further investigated before the flashpoint. Leadership Captain - Helena Artigas Executive Officer - Alsina Tau’ha’nor Chief Engineer - Felix Fleeter Chief Medical Officer - Seoyeon Park Head of Security - Cornelius Huizhong Operations Manager - Casey Wildkins Research Director - Sasha Kaiser Security, Blue Leader - Suvek Tokash Security, Red Leader - Keeh Rasi Timeline Times are approximate and indicated in Moghes Central Wasteland Time (CWT). 0940: SCCV Apollo arrives from SCCV Horizon in a clearing outside the village. 1005: Crew briefed by local soldiers. Minor altercation; guns are drawn. 1022: Crew begins to leave 1028-1031: First sandstorm. 1035: Paramedic informs of dead Federation personnel in the Federation outpost. 1040-1045: Second sandstorm. 1100: Crew arrives in the village after several members were standing by outside the gate, awaiting entry. Departments set up their respective areas. 1121: Negotiations are complicated by the entry of Horizon personnel into the Federation outpost without Lord Izaku’s permission. 1130: Locals and some Horizon crew receive medical care after falling ill from contaminated water. 1135: Skrell crewmembers discover a Federation official is still alive. Rescue attempts are made. 1155 (Flashpoint): Diplomacy breaks down. Lord Izaku orders his soldiers to attack the Horizon crew. 1155-1215: Gunfights commence inside the town. Many personnel are injured; several hostiles are killed by Horizon security. 1210: Research team finds Federation survivors captured in a suspected Pre-Contact War underground bunker. Following negotiations, they were released to the Horizon crew. 1215: SCCV Horizon in orbit picks up an armed convoy en route to the village. 1225: Evacuation order is given to Horizon crew. Mining personnel clear a tunnel for the crew to go through. 1235-1240: SCCV Apollo launches with most crew. Some leave the shuttle before takeoff and are abandoned on the surface; see MIA and KIA personnel. Description of Events Throughout the duration of the Mission to the village, the Horizon crew encountered consistently belligerent and unfriendly behavior from the guards and soldiers assigned to them by Lord Izaku. Despite this, the crew remained to set up aid facilities such as a clinic for medical care and a canteen for food distribution, both of which were used by the local villagers, albeit lightly. Shortly after touching down, Horizon crew discovered the Federation outpost and its inhabitants to be dead; violently killed in some capacity. This was initially blamed on bandits; however Horizon crew began to suspect the guards after attempting to press for more information. Horizon leadership had been negotiating with ground forces for a long time, especially in regards to requesting intelligence for troubling matters such as the Outpost, as well as the medical staff's discovery of dead bodies of villagers inside the clinic. At the flashpoint (see Timeline above), Lord Izaku's soldiers betray the Horizon and attack personnel, presumably under the order of Izaku himself. Soldiers are declared hostile (mistakenly identified as "Hegemony" soldiers) and they attack the village, after which gunfire is exchanged inside the village walls between the hostile soldiers and Horizon security. Several hostiles are killed (see below) before hostiles receive a reinforcement via armed convoy. The convoy is picked up by the SCCV Horizon in orbit and, following an exchange of orders, an evacuation order is given to leave the village and the planet before the reinforcements arrive. The operations team excavates a path through the mountain for Horizon crew to exit the village through and enter the SCCV Apollo. A trail is marked by flares and personnel are escorted out by security, with medical personnel being among the last to leave due to having patients in tow. The SCCV Apollo takes off approx. 11 minutes after evacuation, leaving 4 crewmembers behind. Prior to the evacuation, Horizon crew rescued one Federation worker from the outpost, Qixqil Xuqzix, who was successfully extracted and returned to the Horizon. Casualties 3 SCCV Horizon crew killed, 1 missing, 15+ wounded Clarity Beck, Security Officer (PMCG), deceased Chandler Kovacevic, Scientist (Nanotrasen), deceased Zofia Warzyszczak, Machinist (Hephaestus) , deceased Eris Wyvis, Xenoarchaeologist (Zeng-Hu), missing in action 4+ Izaku soldiers KIA 7+ Nralakk Federation aid personnel KIA 12+ local villagers found dead, unknown cause Hegemony intelligence confirmed visuals on the bodies of Kovacevic, Warzyszczak, and Beck onsite at the cave the Horizon crew used to evacuate from the village. A body was never found for Wyvis; presumed missing. Damage Assessment Near 90% loss of delivered supplies. Significant damage to village infrastructure. Approx. 31.5 million BSC in lost investments. Catastrophic failure of humanitarian mission. Personnel Investigation Central Command Internal Affairs: CCIA found no egregious issues with the handling and decision-making of the leadership personnel present at the time, at least with the intelligence they were provided. The betrayal by local forces was unprecedented and CCIA commends the Horizon crew for responding accordingly. We believe that the decision to press and investigate the Nralakk Federation outpost was the breaking point that led to casualties. While this situation could have had a better outcome, CCIA stands with the decision to press on investigating the reasons behind the outpost’s fate. Investigations for the evacuation found that communication during the latter stages and before the SCCV Apollo's takeoff could have been better. All SCC employee losses occurred during the chaotic evacuation. No losses were observed during the attack on the village or other flashpoints during the mission. Clarity Beck and Chandler Kovacevic were killed fighting the hostiles during the evacuation. Eris Wyvis vanished inside the evacuation tunnel. Radio contact was lost and no body was found. Zofia Warzyszczak was lost and later found dead after leaving the SCCV Apollo as it was about to take off. Liaison Recommendations Liaisons and representatives from the main SCC corporations most involved in the Mission have put forward recommendations to minimize the likelihood of similar incidents occurring again over the course of the humanitarian aid program to Moghes. SCC Central Command Reps. Cyrine Utsubeyoshi & Rowan Atagrande, SCC Tau Ceti More comprehensive intelligence analyses of away sites for SCCV Horizon. More thorough evaluation of assigned foreign security personnel groundside. Hephaestus Industries Reps. Zsuka Tsa’kalar & Jovin Sinclair, Hephaestus Skalamar Overall humanitarian program remains unchanged. Details must be revised. Reevaluation of the Moghes humanitarian mission strategies and planning. More thorough assessment of local leadership and loyalty to Hegemony / friendliness with SCC. Advance teams by Hephaestus-aligned Unathi guild members to scout prospective areas. Comprehensive reevaluation of sites selected for humanitarian programs. Zeng-Hu Pharmaceuticals Rep. Wrukshel Jruzhrl, Zeng-Hu Nralakk Division SCC must establish more advance contact with Nralakk Division personnel sent as forward teams in away sites. Enhanced security and communication for personnel. Conclusion The Izilukh Humanitarian Mission resulted in a tragic loss of life and complete failure to deliver much-needed aid to Izilukh, the Village instead being severely damaged during the fight between Horizon personnel and Izaku's soldiers. Affiliated groups must address identified shortcomings to prevent future incidents and ensure the safety of the Horizon's personnel and the success of its missions. Thorough assessment of local leadership is necessary to gauge loyalty and relationships with SCC personnel. Immediate review and implementation of recommendations are imperative to restore operational integrity and trust in humanitarian efforts from both the international community and from stakeholders. ===

The SCC/KAF joint assault operation on the Kaneyama Power Plant will take place in on March 23, 2466. The SCCV Horizon and her crew are once again asked to partake in the operation alongside personnel from the Konyang Armed Forces to secure the power plant and destroy the Hivebot presence within. This is an all-hands effort. Department-level objectives and goals remain similar to the operation of the Xiangtong Warehouse approx. two weeks ago. The crew's joint task is to deliver the SCC-manufactured Electronic Countermeasures Device, or ECD, to the power plant's core, and activate it -- doing so will disable Hivebot and rampancy virus presence in the area and, if the analysis is correct, the whole planet. The Konyang Rampancy Joint Task Force (KRJTF), consisting of leadership from the Konyang government and military, the Konyang Robotics Company (KRC), Einstein Engines (EE), and the Stellar Corporate Conglomerate (SCC), are in the process of collecting as much intel as ascertainable from sources such as blueprints, maps, and area scans, and are currently locating and interviewing former GON-ENE employees of the Kaneyama Power Plant. The following intelligence has so far been made available to us: (edited) The layout of the facility consists mostly of tight rooms and narrow corridors. Expect heavy presence and usage of CQC (close-quarters combat). While the power plant has been deactivated, dormant volatile elements such as nuclear fuel and waste remain that may cause a meltdown if subject to damage, such as explosions. This, combined with the Hivebots' established countermeasures and the power plant's own shielding and reinforcements, unfortunately, renders large-scale aerial bombardment infeasible without catastrophic collateral damage. As above, radioactive nuclear waste and fuel are present and stored in the facility. Care should be advised to read the labels of rooms before entry and to immediately see a medical professional if one experiences symptoms indicative of radiation poisoning. In addition, extreme care should be taken to avoid usage of explosive or incendiary weaponry in close proximity of the reactor cores, due to the risk of meltdown. Satellite scans are having difficulty penetrating the power plants' radiation shielding; however, it is planned that a map be drawn and provided to all participating crew and KAF servicemembers as soon as possible that provide important locations and details. This is being done using a combination of exterior scans, building plans, and employee interviews. Equipment After consultancy with strategic advisors from the KAF and PMCG, additional equipment has been requisitioned and procured for usage by Horizon crewmembers. It is believed that having more equipment and weapons issued to personnel will greatly increase the odds of mission success, or at least a desirable outcome. The following equipment has been procured to be issued at least 1 to each participating crew member: 1x Nanotrasen "Everyman Mk1" 10mm pistol and ammunition 1x Zavodskoi Interstellar "Terrier" 5.56mm bullpup assault carbine and ammunition 1x Hephaestus Industries G40E laser carbine 1x SCC-issue plate carrier w/ helmet 1x maglight MREs, provided by the Konyang government In addition, security will be receiving the following additional equipment available to them: 1x SCC-issue heavy plate carrier w/ helmet Choice of the following: Nanotrasen LR-6 laser rifle Zavodskoi Interstellar "Terrier" 5.56mm bullpup assault carbine and ammunition NT/KA Jingya A-1 5.56mm burst rifle Hephaestus Industries KS-40 12ga combat shotgun and ammunition 1x Nanotrasen Mk58 .45 pistol w/ ammunition Standard issue security equipment such as stunbatons and flashes Single PEAC (point-entry anti-materiel cannon) w/ ammunition, for usage by one individual Additional equipment will be available in more limited requisition: Stabilization medical kits for frontline first aid, containing emergency pouches for trauma, burns, radiation, toxins, and oxygen deprivation. Recharger backpacks. These function as mobile rechargers and are designed to accept laser weaponry and other rechargeable items. Additionally, after consultancy with Horizon's medical department, additional medical bay retrofits and equipment have been provided to the KRJTF Forward Operating Base (FOB) to facilitate more efficient medical treatment by onsite personnel. Good luck to those who volunteer. The KRJTF will be providing additional aid and intelligence as necessary when we receive updates.

Reporting Personnel: Alessia Marino Job Title of Reporting Personnel: Captain Personnel in Question: Rick Towl Job Title of Personnel in Question: Passenger Reason for Review: [ X ] - Extended Arrest History [ ] - Grievous Infraction on Record [ ] - Other Notes: Passenger Rick Towl has an extremely concerning arrest history of multiple felonies. After his release from his latest sentence, he arrives to the Horizon under questionable circumstances, and immediately gets himself into trouble (see security incident report #7463 on record). On a recent shift, as well, he was found to have trespassed into security. Security on-shift attempted to get him to pay a simple fine, of which he gave 4 credits (of the 300 required) and proceeded to run away; he was later caught and apprehended for resisting arrest and trespassing; this was handled appropriately by security staff on shift. It should be noted that he had insulated gloves on his person when searched. However, he has also seemed to have acquired the schematics for "wiring" - likely airlock wiring to allow illicit access into areas - and was selling them for a price over the common radio. Below are transcripts of such messages obtained from the messaging server: This behavior is extremely concerning for a passenger and not that of a person I would like on this ship. I would request that this person be immediately looked over both by SCC authorities and law enforcement personnel to determine if he is fit to stay on this ship, given his criminal nature and recent incidents.

I did love your style of commanding as HOS, being very clear to what you expect from your officers and giving them concise orders on what to do in the event of an emergency, like teaming up. While it seems simple, it stuck out to me as something that makes you appear really competent at your job. You were interesting to have an RP discussion with too, even if only for a brief period of time - your character was very well fleshed out in terms of background. +1 from me!

Basic Information Byond key: Nauticall Character names: Leslie Asoya, Alessia Marino, Seoyeon Park (+ several other one-offs) Age: 21 Timezone: UTC+8 / Beijing Time What times are you most available?: 8PM - 12AM EST (reliably on weekends, unreliable on weekdays), 4AM - 12PM EST every day Experience How long have you played SS13?: Since about late 2019 now, so going on 4 years. How long have you played on Aurora?: Since June 2023. How active on the forums, discord and/or server are you?: I'm active on Discord on almost a daily basis. Forums much less so, but on the server proper I play about 1-3 rounds every other day. Have you ever been banned, and if so, how long and why?: I've not been banned. Have you ever volunteered as moderation staff for any other servers, SS13 or otherwise?: I have; I've modded for a handful of non-SS13 games, even becoming head admin for one at one point, as well as CM-SS13 in the past. I'm also currently a whitelist maintainer on CM-SS13. Do you have any other experience that you believe would be relevant to a position in the CCIA?: I have a lot of experience from both my moderation and also a little bit of non-professional management in handling complaints, running investigations, and making interviews. It's something I'm intimately familiar with and have developed experience in arbitrating with customers as well. I additionally took a year of business management in college and know the basics of handling human resources. Personality Why do you want to join the CCIA?: I'd like to join because the role of CCIA in handling disputes is fascinating to me. Aurora is the only server I know of that has such a system for resolving disputes in an IC manner without OOC intervention getting involved, and I think I can very much contribute to such a unique system. What do you think are the most important qualities for a CCIA Agent to possess?: I think the important ones are the ability to see the big picture, neutrality, communication, and also recognizing that this is a game and we're here to have fun. These would allow investigations to be carried out truthfully but also in a way that doesn't kill other peoples' enjoyment of the game. Big picture: It's important, in my opinion, to recognize both sides and the overarching goal of whatever job someone is doing, such as handling an IR. Getting tunnel vision by only focusing on what a single side did, for example, can be detrimental, and it also helps tremendously to remember and reflect on why you, and anyone involved, is performing a job. Is it because someone is actually concerned, or because of revenge, for example? Neutrality: As said above, it's important to take all sides into account when doing an investigation, even if it seems very cut-and-dry otherwise. Personal biases should also not factor into an investigation that one is handling for obvious reasons, and it should be noted that every witness can have a different recollection of what happened during an incident. Communication: Talking to people is one of the core aspects of being CCIA, and without good communication skills will be effectively left in the dust. Knowing what to say, when to say it, and who to say it to can make the difference between an hour-long session fo small talk and a fifteen-minute efficient interview. OOC, communicating with other CCIA members is also vital as it allows for arbitration and getting external perspectives. Asking other people for their opinions is a skill I've found to be vital in my decision-making over the years, and it's because communication makes it possible. It's just a game: I've admittedly been guilty of not recognizing this myself a handful of times, but I've come to recognize that in the grand scheme of things we're all here just to have fun. This isn't our actual job and we shouldn't be held to absolutely rigid standards that must never be broken like a real company. No customers are getting screwed over because of peoples' actions here; this is just another tool to help move the train along and promote the roleplay idea that we play as members of a real company. In the end, though, we shouldn't dogpile on someone to the point where they lose enjoyment altogether, even if it seems like the right thing to do. What do you think the purpose of a CCIA Agent is in an ongoing round?: I think this would be to represent the in-game bureaucracy that is SCC's central command. Playing the role of the higher-ups gives the sense that this is a believable setting, and that the Conglomerate does take incidents seriously and attempts to investigate. It lets characters know that even if only for the sake of minimizing losses, their employer does oversee affairs and look out for their staff. It's a stark contrast to, say, there being no central command at all. What do you think the purpose of a CCIA Agent is outside of the server?: I think their role outside the server is to handle investigations and overall make sure people are still having fun. IRs, to me, happen primarily because someone ICly is behaving or treating someone so poorly that it affects the believability or sensibility of the setting and also might hamper someone's enjoyment of the game. As a result, CCIA should help keep that immersion going by representing the SCC saying, "no, this is where we draw the line", and handling a situation that crosses it. How do you handle stress?: When stressed by something (for example, schoolwork), I put whatever is stressing me down (for an indefinite duration of time, admittedly) and turn my attention to working on some kind of chore or task, typically on the computer but also in real life, to help "cool down" my mind. I like to think of it as my form of meditation since I think about myself and the things I do while I focus on idle tasks. These can be games, or they can be game development, like spriting/mapping for SS13 or some other game entirely. How well do you work autonomously?: If I'm not in a leadership position I'll usually need someone giving orders to tell me to do something; however, once the executive order is given I like to think I can work very autonomously in how I do things, laying out the workflow and, if necessary, communicating with people and setting up jobs for me to do.

Reporting Personnel: Alessia Marino Job Title of Reporting Personnel: Captain Game ID: crv-aFUT Personnel Involved: Ilhe Razsaross, Shaman: Offender. Alessia Marino, Captain: Witness & reporting party. Suvek Tokash, Head of Security: Witness. Arrested the shaman for failure to execute an order, as they were ordered to the XO's office and refused. Ismet Al-Barghouti, Executive Officer: Witness. Suspended the shaman and ordered their initial arrest. -- Secondary Witnesses: Aayun Kaiser, Chief Engineer. Coordinated the initial firefighting efforts. Felix Fleeter, Engineer: Witness. Extinguished the fire in the chapel. Time of Incident: ~03:30 Ship Time Real Time: ~11:05 PM EST / 4:05 AM GMT, 12/28/2023 Location of Incident: Chapel, SCCV Horizon Nature of Incident: [ X ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [ ] - Neglect of Duty [ ] - Harassment [ ] - Assault [ X ] - Misconduct [ ] - Other _____ (Place an x in the box that applies. If other, replace line and specify.) Overview of the Incident: Shaman Ilhe Razsaross was reported for lighting a bonfire in the chapel, posing a fire hazard. About a month ago on 11/13/2465, he had done a similar incident of lighting a fire in the chapel, which was also extinguished - such an incident additionally led to a brawl; however, details of the aftermath are irrelevant here. During the first incident, I had ordered the shaman to stop, following which he said he was exercising religious freedom and was within his rights to do so. In doubt, I faxed CCIA, who returned a reply (Exhibit B) stating it was not legal. I showed this to him, and he complied. No further incidents occurred afterward. The second occurrence took place today, 12/28. Shaman Razsaross repeated his previous actions and demands, insisting on official confirmation from the CCIA regarding his activities. This time, he was instructed to report to the XO's office for negotiations, an order that he refused. Consequently, the XO ordered his detention for failing to execute an order and subsequently suspended him. Upon his release from the brig, the XO stated that Razsaross told him that he would re-offend, saying that he would "start a fire again, regardless of his status as a chaplain." Razsaross went to residential shortly afterward. -- Submitted Evidence: Exhibit A & B: - CCIA fax messages from Mr. Greyswandir and Mr. Talponar, respectively, detailing CCIA's rulings on the matter. Exhibit C - Snapshot of the aftermath of the fire in the chapel caught by CCTV timestamp ~11:20. Bonfire and remains were cleaned up by engineering personnel. Exhibit D - XO's suspension form on Razsaross, following the latter's violation of i111. 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?: As I was the captain, this was reported to CCIA via fax (see exhibits A and B), and issued a cease and desist warning as per captain's orders. Actions taken: Shaman was arrested by security and suspended by the XO following my order to have him extinguish the fire, which he refused.

BYOND key: Nauticall Discord name/id: sammy (@nauticall) Borg / AI names: R4NGER (Robot) / Maverick (matriarch drone) / Oswin (planned AI name) Have you read the Aurora wiki page about the AI?: Yep, I have! Why do you wish to be on the whitelist?: In the past in other servers, I've really loved playing AI as like this helpful, robotic assistant who oversees the ship and plays out like the sort of "caretaker" for the whole ship/station. It's an interesting departure from the standard round flow of playing someone on two legs, and I found it to be quite fun and just satisfying to me to be helpful in whatever way I could. I also loved playing AI on Baystation before it was removed (rip) because the interactions between AI and the crew were much more than just "LAW 2 OPEN DOOR". I'm hopeful the experience will be good, if not better, on Aurora and I look forward to it as a result. Have you received any administrative actions? And how serious were they? Nope. Do you understand your whitelist is not permanent, and may be stripped following continuous administrative action? I do. (Copy-paste from the last AI app I made and fumbled. Let's try this again.)

BYOND Key: nauticall Discord Username: nauticall Character Name: Alessia Marino Item Name: Voidwarder Sphere Item Function(s): It's a religious good luck charm, so nothing, except glowing brighter and bluer than a standard warding sphere. Item Description: A special variant of a warding sphere that shines even brighter and for far longer than a traditional sphere. These Voidwarders are given especially to Luceian explorers, first responders, and crew of starships that cross the boundary of Light's Edge into the suffocating blackness of the Lemurian Sea - Assunzione's version of Hell. Those said to venture into the Sea with a Voidwarder and the Church's blessing are said to have narrowly survived their encounters with certain death in the Sea and emerged from the darkness a changed, more faithful individual. The Church allows explorers who have been given these spheres to keep them after their travels, as a reminder of what they had accomplished: marching into the gates of Hell and living to tell the tale. Why is your character bringing this item to work?: Warding spheres are a traditional item owned by Assunzioniis, and Alessia is no exception. It's a sort of good luck charm to her, a beacon of light that she, and her religion, believe will guide her through the stars. How did your character obtain this item?: The Voidwarder sphere was gifted to her by the Luceian Church pending her expedition into the Lemurian Sea. What value does this item have to your character, and what story does it tell?: The sphere is a testament to Alessia's past as one of the explorers who ventured into the highly-feared Lemurian Sea, surviving narrow brushes with death while traveling inside the region for research and managed to survive. To her, her Voidwarder, as well as the Voidwarder spheres of every Assunzionii on her ship, were what helped guide them through to safety, saving them from the dangers that lurk in the dark. As a result, she places a great amount of faith in the item and believes it contributed to keeping her well and will continue to do so until its light burns out. Sprites: The purple case is a placeholder, but the sphere is the final-ish design. The intention is to make the 'star' around the sphere's eye rotate around in 3D. Additional Comments: This item bases a lot of its lore on the Luceism rework I made, which I have also put up an application for on the canon app section. Just an FYI in case that gets shot down for some reason.

Lore Impact (Small/Medium/Large): Medium Species: (Skrell, Tajara, Human, Vaurca, Dionae, Unathi, Synth, General): Human, with a touch of Dionae Short Description: Overhauls and expands on Luceism as a religion, adding details like its afterlife, core beliefs, and prayers. How will this be reflected on-station?: Hopefully more consistency with Assunzionii characters and how they portray their religion, as well as possibly more Luceian clergy. Does this addition do anything not achieved by what already exists?: Yes, it expands on the existing Luceism page and overhauls certain aspects. 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: https://docs.google.com/document/d/1BnG3ABl8JXsYov4i1l2ndaXbitKd7Fs_A25wkYqyL6o/edit?usp=sharing May light guide you on your journey.