Skull132

Gonna need this ckey to figure out what's got you banned. Could you either PM it to me or send it? Your CID is one of the unfortunately common ones, so it's most likely invalid.

Unfortunately, none of these are applicable. Your IP that time was unique, but you were paired up with the ban according to another set of fingerprints. Which, while can be altered, are quite hard to force a conflict out of. (Only know of 2 cases in my 4 years of dealing with these shenanigans.) I'll flag Alberyk over, see what he wants to do, as the ban is his.

Okay, umm, why are my logs showing that this happened on 25MAR2017 then? This is the cherry atop all of these other mirrors, btw: (A mirror being a ban bypass attempt that we've automatically identified and blocked.)

Aaand PR's up. https://github.com/Aurorastation/Aurora.3/pull/2452

There are two schools of thought, generally. One is that, "Default is yes, this allows you to blaze through stupid menus that you see a million times while adminning/doing shit. Just don't fuck up, and you'll be fine." The other is, "Well. We gotta make sure people don't fuck up!" SS13 was originally made with the former mindset. With the two recent Baymemes, our codebase is split 50/50.

Started working on this. Observations: Explosion code was never removed or disabled. The power cap was just so stupidly high that reaching it would take hours. Regardless, I've moved to make them more fun. They now cause a surge, which will: Cause all APCs within a certain range (on that same power net, mind you) to have their lights burst Cause all machinery connected to that powernet by wire to have EMP act called on them Cause a random chance for an explosion to occur on those powernet items. (small, 1, 1 explosion, as can be observed.) Radius of affect atm is 28 tiles. EMP effect is scaled accordingly. As is light popping. Demo: https://kama.skullnet.me/index.php/s/AE6ejFJghToXjmG Feedback welcome.

Coders are currently busy building up ZLevel code and executing already planned projects. Can't promise much until new map meme ends.

Application accepted, 24MAY2017, following the trial period.

Git it. Old map has this, it's an oversight/mapping error.

Actually, the contrast in the lift shafts might be harder to see, yes. Because both levels are lit. It's quite fine in the asteroid turfs, though.

Not like we've had jobs with widely varying duties lopped under the same banner before. Though custodian has two definitions, and is probably not the best option. Custodial engineer or sanitation technician or whatever else would most likely be better.

The two slot thing was either cryo being amazing, people having transferred out, or admins running tests. Lowering the amount of doctors is a bad meme that should not be listened to, as it will never happen.

This is already a thing. Healtscanners separately shouldn't be needed on spawn, IMO. Voting for dismissal.

I figured I'd roll this guide out of the Development subforum and into public view, because it can only really help. So, What is this about. Quite simply put, DreamMaker (DM from now on) is not really the best editor for large, spanning projects. Like SS13! It lacks things like proper, full project search (it sorta has this now, but it doesn't have a good readout of all results. Instead, it just jumps you from file to file.), Git integration, and the ability to interact with non-DM file types that still reside in the project folder. So basically, if you're touching SS13 for long enough, you will eventually have to do something that requires you quickly use another editor (like Notepad++). And it can get a bit annoying to have do that. There also exist very well maintained and fleshed out general editors, which allow you to integrate any toolchain into them. Prime examples being Sublime, Atom.io, Visual Studio Code. In the dev staff, we started using Atom back in 2015 (if memory serves). And lately, a few of us, notably me and Lohikar, have swapped to VSCode. Which you prefer is up to you. In short, VSCode is more limited in terms of how much you can customize it, but it has a lot more MicroSoft supported toolchains, which are better than what Atom can provide. Atom, on the other hand, is way more customizeable and can potentially pull off more niche shit. Since I have the resources to explain the setup of both, we'll just go through them both! One thing to note before proceeding! There exist some downsides to not using DreamMaker. Specifically, you cannot map edit without it, you cannot icon edit without it or some other tools, and you have to edit the .dme file manually if you want to add/remove files! In practice, though, as a coder, I've still found the other editors to be worth their salt. Visual Studio Code To set up VSCode, just download it from here and install it. Press ctrl-P and paste this into the prompt: ext install byond-dm-language-support It'll open the extensions menu and give you the ability to download the BYOND DM Language Support extension. It's pretty good, and handles syntax highlighting for us. After that's done, open the project directory with ctrl-K ctrl-O. Make a new folder in the root called .vscode (the . is important!) and in there, create tasks.json. Paste the following into tasks.json: { "version": "2.0.0", "presentation": { "echo": true, "reveal": "always", "focus": false, "panel": "shared", "showReuseMessage": true, "clear": true }, "tasks": [ { "label": "Build Release", "type": "process", "group": "build", "command": "C:/Program Files (x86)/BYOND/bin/dm.exe", "args": [ "${workspaceRoot}/aurorastation.dme" ], "problemMatcher": { "owner": "dm", "fileLocation": [ "relative", "${workspaceRoot}" ], "pattern": { "regexp": "^(.+):(\\d+):(warning|error): (.*)$", "file": 1, "line": 2, "severity": 3, "message": 4 } } }, { "label": "Run Server", "type": "process", "group": "test", "command": "C:/Program Files (x86)/BYOND/bin/dreamdaemon.exe", "args": [ "${workspaceRoot}/aurorastation.dmb", "-trusted", "-invisible", "-close" ] } ] } Save it, close it. You're now set! Every time you want to compile the code, just press ctrl-shift-B. Or ctrl-P, type in "task", press spacebar, and select "Build Release". You can also host the server by attaching VSCode to DreamDaemon via "Run Server". The server process will autoclose once the world is destroyed. And there's also a changelog generation command here, for my comfort, really. The compilation will automatically highlight errors as it encounters them. That's it for VSCode. Atom.io The process is similar to Atom.io. Note that this guide may be a little out of date, but I did check to see if all of the dependencies are still being actively worked on. (They are!) So hopefully it's still relevant. Download and install Atom.io Download and install the "Build" package by navigating to File->Settings->Install, and typing "Build" into the search there and pressing enter. The package is by "noseglid", for better identification. Download and install the language-DM pack from the same menu (author is "stuicey"), or use my own, more custom version that can be grabbed from here. If you're using the custom version, then shove the contents of the zip into C:Users\Yournamehere\.atom\packages\language-dm. Copy the code below this list and place it into a file called .atom-build.json in your Aurora folder (the same folder where your baystation12.dme is located). Make sure to change the two paths there! Now, navigate to your Aurora folder, right click, open with Atom. It'll open the project and should also say that 1 build target is parsed! This is success! .atom-build.json contents: { "cmd": "C:/path/to/BYOND/bin/dm.exe", "args": [ "C:/path/to/git/and/fork/baystation12.dme" ], "sh": false, "errorMatch": [ "\n(?<file>[\\\\\/0-9a-zA-Z\\._ -]+)?<line>\\d+):error: (?<message>.*)" ], "warningMatch": [ "\n(?<file>[\\\\\/0-9a-zA-Z\\._ -]+)?<line>\\d+):warning: (?<message>.*)" ] } Useful Tips: Ctrl-F searches the opened file, Ctrl-Shift-F will search all the files in the opened project (starting from the one you have active). Regex is supported! Ctrl-Alt-B to start compiling the code. Note that with the correct .atom-build/tasks.json setup, it will automatically parse build errors and warnings into usable links, just like with DM! Ctrl-Alt-V to look at the last compile results. (Only applies to Atom.io.) This thing links to your Git files, and showcases git differences, enabling you to find your edits and so on. Any questions, feel free to post.

Project update. Pull request merged. Awaiting playtesting and push to master along with new map meme 2017.

For ref. Thine cries have been heard and a coder has been assigned. PR for reference: https://github.com/Aurorastation/Aurora.3/pull/2193

Marked as complete.

It might be worth having a list of common contraband items and in what situations. But yes, a definite list is impossible to make, because what is and isn't contraband can depend on the circumstances.

Have you played on this server under any other ckey/username? Please do answer truthfully.

As some grade of mod admin person with ban panel access. Will confirm, there are no exceptions to the standard naming scheme outside of these cases: Species exception (see: IPC, Vaurca, Diona, naming schemes) Special character (merc, heist, event char, etcetera) Borg/AI The rule exists to make the gameplay setting a bit more believable, and to cut down on obvious shenanigans. Nothing stops you from insisting and otherwise roleplaying that your character prefers to be referred to as "Brother X", though! (So basically, everything Synnono said.)

Here's the more fun part of this. Means you get space drugs out of ambrosia when ground up and inspected. Mechanical confirmation that ambrosia == space drugs, just with a very low concentration. And with the latter most certainly remaining outlawed, it makes you thunk.

Holy shit, ban is old. fammable - VikingPingvin - 2015-08-27 09:16:50 - Banned from Warden, Detective, Forensic Technician, Security Officer, Security Cadet - Hit and tasered an afk Diona multiple times. Logged before being able to question the act. Permanent Sec ban. Viking's no longer an admin. I'll wave someone else your way.

Shit, my apologies! I had a stupidly busy Monday and Tuesday, and this slipped my mind. The ban's lifted, you are good to join. Again, apologies! Also, please don't attempt to doge bans in the future. Here's a list of ckeys our system identified as belonging to you: 2016-09-29 - cjruss32 2016-10-28 - potato45 2016-11-17 - squenix 2016-12-22 - junior456 2016-12-25 - junior456 2017-02-02 - junior456 I'd suggest sticking to just one.

Application entered into trial, currently assigned to work on TComms code for the new map.

Checked your notes, you were give a warning a few days before for the same reason. But I'm up for giving you another chance. If no one says anything negative by the time I wake up tomorrow, I'll unban ya.