Leaderboard

Safety inspector! We need more of them in this spess-age

In this guide, you will learn various ways of finding, editing and uploading or updating images to the wiki. For this guide, it is recommended but not required to have: A GIthub Account. Local download of the Paradise station repository with the private server setup. 1. Checking for duplicates. Before you think of adding any additional files to the wiki, you should check if that file already exists on it. To do that, you need to go to the search page with Multimedia selected. This will allow you to search for files and files only. Simply type in a few keywords that might relate to the desired file. If you have found the file you were looking for, you can skip over to "6. Adding the file to an article" or if you were looking to update, "5. Uploading/Updating the image". Even if you get nothing out of a search, you should know that the search page is well...a little finicky at best and back-stabbing at worst. The way to tame it is with the * wildcard. It will search for all files that begin with a prefix before the *. Here's an example of how it can help: Searching sunflower only gets me "Sunflower Crown.png", while I want to find the file of a Sunflower, not a crown. What do I do? I search for sunflower* and suddenly, the search page smartens up and shows me all possible files starting with sunflower. Great! 2. Finding the .dmi file. You were unable to to find the image on the wiki? Don't worry, this just means you can contribute even more by finding and uploading it yourself! 2.a. Using GIthub. Log onto your Github account and head over to the Paradise Station repository. From there, you can begin searching by pressing / or hovering over the search bar in the top right corner. Search for keywords of the item and find a the most fitting file containing it, and press CTRL+F to search for .dmi. If there isn't one inside, you can try searching by copy and pasting the subtypes of the item into the search bar and adding AND .dmi to find it. 2.b Using a private server. Assuming you have already launched your private server and logged into it, join in or observe and go into the Debug tab on the top right corner, under which you will find the Spawn verb. It will open a window which will let you type the path to the item you want to spawn, but with most short named items you can just type in a keyword and search for it under the paths given to you, or get the path from the Github. After spawning your desired item, right click it and choose View Variables. It will open a window and give you a search bar. Search for .dmi. 2.BONUS. Using the Icon Search. Simply go onto https://scrubby.melonmesa.com/icon/search/organ_extractor?codebase=paradise and search for the icon_state of the file you want to get. You can get the icon_state from the Github. With this method you can save the images provided and skip over to "4. Resizing". WARNING: THIS METHOD MIGHT NOT WORK IN THE FUTURE AND THE WEBSITE IS SLOW TO UPDATE. 3. Exporting the file. Now that you have found the .dmi file, you can either find it on the Github or on your own local repository under the icons folder and it's relevant subfolders. Open it, and you will be presented with the GLORIOUS DreamMaker. Here you can look for the sprite you want to add, and double click it to open it. Now click Icon on the top left corner and choose Export. It will open a window letting you choose the file extension and location. Choose .PNG for the best quality. Make sure to name your files in Headline Case, where every word is capitalized and separated by a space! 4. Resizing to 64x64. You now have your file, but the wiki is way past the age of 32 by 32 files. This means we need to resize it! Normally programs aren't made for resizing pixel art, as they provide some interpolation or compression to the images with every resize, so you will need to tweak the settings a little. 4.a Using GIMP. Open the image you would want to resize then go into Image and choose Scale Image. In the window that shows up, choose 64 width and 64 height with Interpolation set to None. 4.b Using Paint.net. Open the image you want to resize and press CTRL+R to open a window letting you resize it. Set Resampling to Nearest Neighbor and width and height both to 64 pixels. 4.BONUS. Mass resizing images with ImageMagick. Have to upload or update tens of files due to a new pull request or old files? Free and Open Source Software comes to help. Putting all of the images into one folder and running "mogrify -filter point -resize 200% *" will resize all of the images to 64x64. Download ImageMagick here. 5. Uploading/Updating the image. Head over to the wiki and on the side panel you should see "Upload file". Click on it to be transported to the file uploading page. Now that you are on the file uploading page, simply click Browse, choose the file you wish to upload, add a short summary if it's something complex, add proper licensing and you can click Upload. Now your file is on the wiki! Lets add it to an article! Legend: Destination filename - Set automatically to the filename on your system when adding a file through the Browse button. Summary - Short summary of the file. Useful for adding keywords to make it easier to search for in the future! Licensing - The licensing of the file uploaded. They have short descriptions of when to use them, but you can ask on #wiki-development on the Discord if you are unsure. Watch this file - Notifies you whenever the file is updated. Ignore any warnings - Ignores warnings of filenames not matching. DON'T USE THIS. If you wish to update an image instead, go into the image's page and select Upload a new version of this file on the bottom of the page. It will redirect you to a shorter version of the file uploading page, which will let you update the file and add a short description of the changes. Please be aware that the files on the wiki take a while to update to their new state, so it's recommended to clear your browser cache and wait out a bit for it to change. 6. Adding the image to an article. To add an image to an article, simply put [[File:FILENAME.png]] anywhere in your article with FILENAME representing the filename of your desired image. Make sure to follow the style of which previous files have been added onto the article to keep the editing smooth for the future! Congratulations on reading through the guide! I hope it will be helpful to you, future Wiki Contributor!

So we all tend to play command roles or have to step up as acting whenever we play but there is no true guide to command! Except there is now. For the past few weeks, I have been picking up from where a previous wiki contributor has started and finished their goal. Inside you can find command expectations, how to deal with unruly staff, some things you do as heads of staff, and specific mini-guides for each head of staff + the captain and how they interact with their department. Now this is not a guide to specific command roles but general command to give a push in the right direction. Please submit any feedback here or in #wiki-development on the discord as it is still a WIP until I finish review with the other wiki contributors. Guide to Command Have a fun read!

Welcome to week two of AJC's weekly paradise challenges, where you can choose to complete challenges for... well... extra challenge incase regular space stationing is too easy Yes, this is no longer weekly... Bitch, you thought! Kill or arrest a traitor that killed you(With admin approval if you aren't a valid role) A little Duct Tape Seal a breach using... unconventional means Passport? As a security guard, ask 15 crewmembers for their ID on any security level I'M A VAMPIRE, I'M A VAMPIRE! As a vampire, balatantly kidnap 3 people out in the open Peace was always an option As a traitor, changeling, or vampire, help the crew fend off a high-danger antag (Xenos, terrors, blob, cult, etc)

hello forum dwellers you know how this goes by now, there isnt as much as i would like on here since i haven't been playing as much but i thought since today is my anniversary of my birth ill get this out of the way and make the next one far later. press the heart button or leave a reaction plz this takes forever if you haven't seen previous instalments, view them here Atez, the lore so far. Atez, the Second Saga

Warning - This is going to get incredibly nerd in places and I apologise. If you want clarifications in places, let me know. Chapter 1 - The warning shots For the past month or so, the server has been slightly unstable. As you can see here, theres server Watch Dog warnings about a server crash. This isn't good, but I chalked it up to BYOND for the longest time as that was the status quo, with everything recovering fine afterwards. Little did I know of the storm that was brewing. Chapter 2 - The first outage As a lot of you probably remember, we had an outage on the 15th of August 2023. Before making this announcement, I assumed it to just be the game VM itself crashing due to windows kicking up the ghost, with the only real indication being that Corn was unable to login to the management VPN. (For context - the management VPN is what gives access to all the Paradise virtual machines, similar to a work-from-home VPN you might have at your company). The fact that Corn couldn't even connect to this is what made me go "oh fuck its bad", especially with the hypervisor just not responding to stop commands, but after 6 hours and a full machine reboot (which it did itself), I assumed it was just a blip, and we moved on. However, this was indeed the calm before the storm. Chapter 3 - The real catastrophe Picture this. Its 10AM on a Monday morning (28th August 2023). You're lay in bed, enjoying a bank holiday (for the non UK people, we have bank holidays on random days in the year, which is basically a government mandated "ok its not a national holiday but you dont have to work" day), when I get the following message. Unbeknownst to Adri, the entire server had just shat itself, hardcore. A bit of background. Paradise is made up of 8 virtual machines running on the hypervisor (the server that runs the VMs). These consist of: A router for managing internal IPs and a management VPN (Own VM because pfsense + stability requirements) The core server with the database, ALICE, and about 10 internal automation tools (Own VM because its everything else) The webserver with the wiki, forums, and all the backend stuff (Own VM because its such a huge vector) The game server itself (Own VM because it needs windows) A server dedicated to Elasticsearch + Kibana for log & metric analysis (own VM so I can give Denghis the keys and leave him to it) An internal GitLab (Own VM to confine the fuck out of it) A PRTG runner for network monitoring (Own VM because it needs windows and its not going on the gameserver) A VM for Corn to make his stats thing Anyway, I proceed to get out of bed and go to login to the server panel, only to be hit with a page timeout. So my next assumption is "oh its networking", but then I dig further and realise how fucked we are. For those unfamiliar, a segmentation fault is when a program tries to read RAM it isn't allowed to. But thats not all! My next mentality is to try reinstall the Proxmox packages, so we can use the hypervisor again. Thats when I got a kernel error trying to merely run apt update. So as you can see, its already running bad. But wait. It gets worse! I ran the same command (a version check) twice within the same second. One worked, one died instantly. The same also happened with a check script. And trying to list VMs again, it worked half the time. And above all, straight up corruption So at this point, I establish there is something up, and do the logical thing of a memtest. Which it somehow passed. So my next assumption is "Oh the OS is corrupt somehow, lets move the VMs off to get it fixed". This then unearthed a whole other pile of problems. Paradise has ~1.2TB of data, and all that has to go somewhere if you are wiping the disk, and the only backup I had on hand big enough was a storage share in germany, so I started backing up VMs to that. If you do the maths, you can see that this will take a long time. So I then went to provision storage in eastern US, and at this point you can tell I was out of cares to give. I needed fast, dependable storage, so I went to Azure. This helped. Considerably. However, we were now 8 hours in, and the "oh god this is bad" mentality was setting in, especially with the server getting more and more unstable by the second. This dragged on, and we started to run low on time, which is when the "I ain't getting this done in a day" mentality set in, however I had all the VMs backed up, some in Germany, some in the US, and I was ready to reinstall the OS. So I grabbed a fresh copy of debian, the most stable thing I can get, and booted into the hardware console for the server, ready to reinstall. That's when the debian installer segfaulted on me. I rebooted, it got past that, then died in a separate place. The RAM was fine, and neither of these segfaults were at point where a disk write was required, which led to finally point a finger at the CPU being fucked. It would line up with everything else, however at this point it was 1AM, I had work the following day, so I had to throw in the towel and go at it the following day. Chapter 4 - The next day I get home from work, and immediately get shopping for another server. There's another 13900K in stock, and I grab it. OS installs without a hitch, and notice the board is a new revision compared to our outgoing server (not just a different BIOS, a straight up different hardware revision). The main "oh this one is better" point was that I didn't have to blacklist half the motherboard modules this time. For context server motherboards have extra features on them to help with management, such as a virtual monitor+keyboard+mouse so you can control it remote-desktop style remotely without an OS loaded. Its bloody neat. However, to get this board working on the old server, I had to make the OS completely ignore all these modules, otherwise it would hard lock whenever it tried to interface with it, which clearly isn't desirable behaviour. Anyway, I get proxmox installed, setup a basic bit of networking so I have a management VPN again, and then get to deploying the VMs. Which turned out to be a very, very slow restore process. Half of the VMs were stuck in Germany at this point, with a 1 megabyte restore speed, so I then went to move them from Germany to US-E to restore them faster. However: This would take 8 hours. I dont have time for that. However, we have more Azure regions. This helped. Considerably. The final step was to get it moved from EU-W to US-E, which can easily be done with AzCopy, going via Microsoft's backbone instead of my own upload speed. Anyway, enough backup talk, by this point it was restoring onto the new box, and I thought we had the light at the end of the tunnel. I even threw up the gameserver before everything else was ready because people had been patient and not bugged me, not to mention the support thrown my way (bless all of you who pitched in). I launched the server, stability checked it, then went to bed. Chapter 5 - The light? Day 3, I wake up, spin the last VMs up that I had left to restore overnight, did some quick validation, and all looked fine. No pings of downtime overnight, and I think we are finally sorted, so I leave for work and pretend all is fine. I get home, and notice that TD is worse off than before. Like, 15% TD with 80 people, that is not a good amount when we can normally handle 150 people with about 1% TD, so I go to investigate clocks, and notice we are running at 3.4Ghz. Our target is 5.8Ghz, so theres a lot of performance missing here. Fast forward 3 hours of fucking with various power limits both in the OS and the BIOS, and I throw in the towel. I am beat. The server is running, but she isn't running optimally. Shes basically a car in limp mode. Upon investigation, the CPU voltage fluctuates from as high as 1.08V all the way down to 0.72V, which for a 13900KF is very low. With little time to figure this out since I cant change BIOS settings without taking the server down, I bit the bullet and decided we can run on gimped performance now. Chapter 6 - What now? So we are running, but far from optimally. We are missing out on performance, but it runs, and I am in 2 minds of whether to investigate it. Intel 14th gen is rumoured to come out in September/October time, which lines up well with out upgrade schedule given its only a month or two away. There's also the option of RYZEN on the table still, with a 7950X not only being affordable on a better config for us ($200 instead of $300, and with more storage), so I guess we wait for what the tide brings us. People have also mentioned that on kernel 6.2, the intel power state governer was modified, which may be the cause for this, since we were on 5.10 before. I also want to take this to handle some points of criticism that came up during this "Why is it down for 24 hours why arent you fixing it?" Contrary to the stereotype, some of us have jobs, including me. Given I dont get paid for doing anything regarding hosting on paradise, theres a clear priority here to do actual work over para. Remember, I am a volunteer here, as are the headcoders, the admins, and everyone else. No one is paid here "Why dont you have a team of people doing this?" We dont really have an infrastructure team on this scale because its never really been required. I have Corn as a subordinate to manage stuff on the VMs themselves, and Denghis to handle the log analytics stack, but thats where 99% of it goes. Hypervisor management never really comes into play, nor does the hardware itself, hence why I never rolled out a team for it, and probably never will. "Why dont you have a high availability setup?" Simple - cost. Our server costs $300 a month. We are not doubling our monthly outlay for a box thats going to get maybe a days use over an entire year. "Why dont you use cloud?" This is a point I will actually expand upon. SS13 is not designed for cloud hosting, simple as. Most cloud PaaS offerings are for generic business things (See: Azure Logic Apps), and any PaaS hosting is always for webapps with 80+443 being your only exports. Theres also the issue with performance. No cloud provider will outfit machines with 13900K CPUs, its not viable for a multitude of reasons, and the single-core performance on xeon (which is what BYOND needs remember) is laughable compared to a standard Core-SKU CPU. The other big hitter is bandwidth. We use 5TB of outbound bandwidth a month. On Azure this is $426 a month. On AWS this is $460 a month. And no, that doesn't include the server or any other resources. Cloud makes sense for businesses. We are not a business. Chapter 7 - Closing notes I just want to take a moment to thank everyone for sticking through this with me. This is undoubtedly the worst outage in Paradise history, and I do feel responsible since it rests on me, however you lot have been supportive through the entire thing and that has really helped me mentally wise. Thank you to all of you. - aa07 EDIT - Forgot to mention We've been through three of these boxes now.

More things

I will never understand how you manage to be front and center for so much of this stuff lmfao

Frosted donut galore

Name: CRUNCH (formerly Harry Justinson) Age: 38 DOB: 3 March 2530 Gender: Male Race: Cyborg (Human) Blood Type: O+ General Occupational Role(s): Engineering cyborg Flavour text: Qualifications: Engineering Construction Qualification Engine Operator Certification Atmospherics Technician Certification Firefighting and Prevention Training Basic Marksmanship Training Zero-Gravity EVA (Hostile Environments) Training Combat Fortifications Specialisation Training Sabotage and Sapping Training Combat First Aid (Basic) Training Accolades: Employment Records: [FOR COMPANY USE ONLY - seek HoP approval before viewing.] Security Records: [CONFIDENTIAL: AUTHORISED SECURITY PERSONNEL OR COMMAND CREW ONLY.] Medical Records: [CONFIDENTIAL: AUTHORISED MEDICAL PERSONNEL ONLY.] Personnel Photo: Contents - Footage of CRUNCH, archived TSF service photograph of Harry Justinson.

must give borgo headpats at all times

Actually amazing.

3 dumb admins

I think Aurora station has this exact feature. Click click.

The chef IPC in the picture 'we killed god' was me that round!

This is the stupidest photo collection I have ever seen and I love it By the way, how many goats does one need?

I was the red lizard that walked you to brig over the cargo trespass/fight lol. I figured you were a cling of some sort especially from the PDA messages but we had no hard proof. I would’ve stuck around but I got a call of 2 clings killing Ambrosine in engineering maint so that kinda took precedence. Nice gimmick, I didn’t realize it was you who started the rumble in brig until I read your Reddit post lol.

Not quite. Guiding on game mechanics is one thing, and Paradise has allowed many people use voice chat and other methods to do just that over the years. However, let's say that in the midst of building said droid, an antagonist runs in and abducts you into maintenance--you and the other party would not be permitted to share details of that incident with each other. IE where they took you, their name, what they're doing, etc.. Those are all in character events presently happening in round, and sharing those details/ acting on OOC information ruins the round for everyone around you. If you plan to have someone guide you through basic mechanics ingame through OOC means (voice or text chats on discord or other out of game communication services), you need to press f1 and file an adminhelp to get permission from currently online admins to proceed. That said, if you already have the basic grasp of the easiest game mechanics (walking, talking, interacting with objects and the inventory HUD, the intent system, etc.) I might suggest doing as most other players do and use more common resources to learn, as using OOC voice chats can still be a bit of a dangerous slope that I'd recommend avoiding. Either asking ICly for assistance, pressing F1 and filing a mentor help, or looking through the wiki can often be enough for a wide variety of tasks. Your question of constructing an android is very well covered on the wiki, for example. This isn't to say that there aren't daunting game mechanics a newer player will be worried about interacting with; the supermatter engine would definitely have something to say about that. But even in those cases, there are either alternatives (setting up the solar arrays, for example) or other nearby players who will gladly walk you through the process in-game when asked. Part of the game's charm to many is the learning curve, and even veterans of the game learn new things about it nearly every day due to new features being put in at a semi regular rate.

Whoops

another reason to remove automenders how difficult would it be to actually code that behavior?

Bluey already gets a full on sec kit and lethal laser at round start, as well as a ton of access, oftentimes all access depending on captain. I think a martial art would be overkill, and encourage “redshield” behavior. As for CQC, my opinion would be a hard no. CQC is VERY strong situationally and would be massive overkill. It is an undroppable stamina based brawling machine of a martial art WITH A PARRY on top of round start sec kit. Way too much. The most I’d argue a bluey should get is a roundstart corp judo belt in the locker. I’ve really never felt underpowered as a blueshield, honestly quite the opposite. The most I’ve ever really felt the need to grab is a tele shield for confirmed violent eoc, or an IK30 for biohazards.

The TRIUMPHANT return of the Drakearts. This time for @Qwertytoforty's Kicha. Gosh. What a nostalgic time running though this thread to get here... I love space station.

You can deploy parts of the suit manually to allow for a no-helmet look, but unfortunately you can only do so with the suit powered off, so you have to suffer a heavy movespeed debuff

Inspired by Alphonse Munch's art

Star Gazing spot on the AI connected via telepad to bar.

HoS, syndie Gygax, and captain as prisoner being dragged by hop, fighting griefsky head on

Story in 2 pictures Clown asked if I wanted to suffer as captain, and I did

The Modern Comedian

Daut me Daut Werner me I love alot of things but mostly i love banjo, ducks, camels, wait i think i also love station in spaces yeah Since chaplain is the best role i play mostly chaplain because chaplain is cool and yes i love Basically im cool and i also love my hat because its cool and its having protection of 100% to any hits (Daut(Daut Werner apropopproved)_+;' Also my friends are cool because im cool and that makes them also cool

Yes, this is a threat.

Do it, coward

I always kinda saw it as an SMG or short barreled carbine. You wouldn’t see me complaining about a new sprite for the WT, and quite honestly eguns and laser rifles as well. I always thought the WT looked extremely weird for a gun. Don’t even get me started on the AEG… that thing has a sprite only a mother could love lol.

Honestly the WT sprite looks more akin to a pistol anyways, iirc. Regardless; if you add a ballistic pistol option it might be more interesting (at least in terms of aesthetics) to make it more ss13-ish. Something Sci fi and unique rather than a simple M1911.

oh lawd she comin with the goat

Tori and Dalton!

Just a quick thought that I want to post before I forget about it. Why not add a kit to the traitor's uplink that will give you a red laser tag chest and helmet that act as actual armor, as well as a blue and red laser tag gun, each one being a lethal and disabler respectively, will not charge themselves of course as we don't want to make a buyable antique gun.

I've done stealth wizard. I teleported into mime office, became mime, got an ID from HoP, danced and was silly in front of bridge, whereupon the captain let me in. I ei'nathed him, yes, and misted away. During scry orb, ghosts tell me captain brain is being transplanted, but crew still doesnt know what happened, and thats where I finally figured out what I'm doing. I make my way into medical, steal the brain just before CMO is placing it into the new body, then as CMO chases me into the middle of medical, I ei'nath them too, somehow with no witnesses again, and take the brain. I then get the head of security in the halls, and the HoP in command, just as crew figures it out. My plan was to only kill command, then inform the crew they are free of their shackles, but the CE and a wily sec officer with a shotgun (old shotgun with slugs etc) got me before my plan could be realized.

IRL, if you took a tazer off a cop and shot them with it - you could expect to get shot with real bullets. Do this in a airport, even more so. Do it in a research base with nuclear, biological, and chemical weapons on it that's a known target of terrorists, and well...you see where I'm going. This is also simply solved by not attacking the person armed with a lethal weapon. If you attack a dude wielding a shotgun, you should expect to get shotgunned. Or lasered. Or whatever. This is also all acting under the assumption that people getting killed is a bad thing that we should try to avoid. The risk of death when you mess with sec heightens tensions and adds to the adrenaline of the game. People getting murdered in violent conflicts with sec is a good thing.

nukierounds.mp4

Hello! This is my Roleplaying guide based on my time on paradise combined with a lot of tabletop roleplaying experience. I hope it can give some interesting ideas. If it doesn't, I'm still happy you took the time to check it out. This guide doesn't dwell a lot on what you SHOULD do but rather HOW you do it. It's easy to tell someone to roleplay. It's harder to tell someone how to roleplay. This guide tries to amend this by providing traditional roleplaying and improv techniques. It also gives a lot of examples on how you could accomplish the three steps detailed below. The guide in 4 words: Build, do not destroy. The three things that make you a good roleplayer in this game are the following, in order of priority: Create interesting situations Be Interested Be Interesting Creating interesting situations Difficulty: Hard Note: As always, any interesting situations you create should follow the servers rules. The hardest, but also the most interesting part. It's hard to define an interesting situation but it's something that involves player characters somehow interacting with something. The classic example is an antagonist trying to kill you. It is immediately interesting because it's your character being hunted by a threat. You wanting to survive versus the antagonist wanting to take you down. However, interesting situations can be bigger than this. The bartender can throw a date night for the lonely hearts, the librarian could have a poetry competition, a civilian could try to get a permit to build something in the maints. The possibilities are endless, it just requires imagination. They also require initiative and work. Creating something means you have to try and risking failure. This is, combined witht he imagination required to come up with interesting ideas, is what makes this the hardest thing in this guide. Push yourself and go for it. Examples of creating interesting situations Here are some suggestions for different jobs to initiate interesting situations. Note: This skill depends heavily on the round and whats going on. If you're currently to busy doing your job to initiate interesting situations, do your duties first, then start getting creative. If you got skills, you might be able to do both. Captain: HOP: Sec Officer: Detective: Therapist: Civilian: Be interested Difficulty: Easy Be interested in other characters. Ask them about stuff. Ask them about their backgrounds and whatever else comes to mind. This is appreciated by everyone who has made a Character. They want people to know about their character. Let them show it off. By being interested, you can also show off your character. I've heard SS13 being called a "glorified chatroom" and it struck quite a cord with me. Talk to people. Ask them about their day. Being able to smalltalk as a made up character is a pretty high level of roleplay. The 4 techniques used to be interested are: "I heard a rumour" Yes/Yes And/ Yes But Have an excuse to start a conversation Join in on the action "I heard a rumour" One of the easiest and best conversation techniques to use in this game. As long its harmless, you can make stuff up about OTHER player characters like rumours or facts. Bonus points if you make this flattering or interesting tailored to their personality. They could play along using yes/yes and/ yes but or just say you're totally wrong. Either way, they get a chance to small talk about a possible previous event. Maybe even add something to their backstory. Try it. Examples About a Badass: About a Captain: About a Detective: About a Quartermaster About a Clown: About a Mime: Fill in the blank examples: Yes/ Yes and/ Yes But: This is a classic Improv technique. Someone comes to you for something. Clown wants all access, the chaplain wants to bless you, Sec wants to arrest you, Captain wants you for a special mission. In most cases, you should avoid saying no (Unless you really don't want to do it). It's better to say Yes/Yes and/ Yes but. All these answers will lead to MORE roleplaying and MORE interactions. A No will in most cases lead to less roleplaying. However, you should obviously still follow the server rules and apply common sense to the situations. Examples below. HOP example: Chaplain Blessing you example: Sec Arresting you example: Captain wants you example: Have an excuse to start an interaction When you make your character, consider how they interact with certain people. Different people want different things out of an interaction. What would your character be interested in finding out? Some are focused on the job/personal life/love life/interests. More detail on how to create excuses for your character is in the character creator in the next post. Examples, based on types that can be found on the station.: The young CentCom goldenboy/girl The Gossipy Grandmother The Naive Newcomer The Flirt The Badass The Preacher Join in on the action If you see someone announcing something, like a private investigator, a fun religion or a scientific experiment being announced, interact with it in some way. Just stopping by is good but if you can contribute, taking it in a different direction or building upon what's already there, it's even better. Create interaction. By talking with someone, you can start a series of events that could make someones round a lot better. Don't be afraid to ask people for things or ask about things. Be Interesting Difficulty: Medium. To be interesting means you have a character people are curious about and want to interact with. Your character changes you from just your job to an actual person. This step also happens before you've actually started playing the game. In my next post I'll post a character creator, designed specifically for Paradise, to help you create an interesting character. Some shortcuts to be interesting are the following: Have a unique or odd style/appereance. Speak in a distinct manner. Off hand mentions to previous events in your life. If you came this far, thanks for reading. I truly hope it gave you one or two ideas!

YET another commission! Gosh I'm so happy people feel my art is worth paying for! This is for the wonderful KAM!! They're a neat Vulp, who is feeling pretty wistful at the moment.