OptionsClick - One. Click. Trade. Binary Options Live ...
Best One Click Root Methods in 2020 - xda-developers
Manual ONE CLICK Trader for MT4 - Binary Options Edge
Introducing One-Click-Trading for Binary Options - Online ...
One click binary options - duniyahaigol.com
One click binary options - Pelajaran
anyoption mit neuem One Click Trading Feature
7 Binary Options – One Click Profits
Blacklist - Binäre Optionen Betrüge in 2020
Is the option for non-binary pronouns a conspiracy from the identity politics cult to make save scumming more inconvenient by one click? r/battletech takes a break from talking about stompy shooty robots to discuss
It almost took us the same amount of time this year as it did last year. We think it's worth the wait. The results are in and we can't wait to share them with you! This year we've received a tremendous amount of help from u/gates0fdawn. She designed the whole infographic you'll see linked below, we're super grateful she took the time to create this, we think it looks super good. I would also like to shout out valuable community members who helped us out with both proofreading and giving valuable opinions. One of our Discord Mods: OldWhiskeyGuy from the subreddit discord server helped with proofreading a lot. u/SirBuckeye for valuable input and thoughts as well as industry officials who doesn't want to be named. Super thankful for all the help! Yet again we kept the age gate, so every account created after August 1st were not allowed to participate in the census.
Responses - We had a total of 5957 responses! That's 1977 less than last year's census. We started sticky commenting a link to the census in threads the final few days of the census which saw a large influx of participants taking the census.
Age - The 18-24 age group had the largest percentage of 51.5%. It declined from last years 56.7%. The 25-34 age group was the second largest with 33.4%, it has increased from 30.9% last year. The 13-17 age group increased from 8.7% to 9.9%. Yet again, it seems like we're getting older y'all.
Gender - Following last years gender identity change we've seen more users choosing more varied responses here. This one might be shocking to a few. 51.8% are Female, 43.6% are Male. Non Binary was the third largest with 1.7%.
Gender Part 2 - 91.9% are Cisgender. 1.9% are Transgender and 2.7% is an Other Gender Identity (Please let us know!) 3.5% didn't want to answer.
Sexuality - Last year about 62.5% chose Straight, this year it's lowered to 58%. 17.3% are Bisexual and 9.7% are Gay (6%) / Lesbian (3.7%).
Relationship Status - We kept the same options as last years census. We went from 76% Single to 75.6% Single! Let's keep the trend going! Last year 16.9% of users were in a relationship, this year it's at 16.5%. Married users increased from 4.7% to 5.3%
Ethnicity - 40.5% are White (Non-Hispanic), 16.6% are East Asian, 15.3% are Southeast Asian. 8.1% are Hispanic/Latino. 6% are mixed race.
Education - This question was first asked last year. This year we tried fixing this question because there were so many options that many users felt a little flabbergasted for what to choose. 34.5% are working on, or already have a Bachelor's Degree. 23.9% Are currently in Some College (No Degree) 8.3% are currently in High Scool and 13.1% are High School graduates. 8% have a Master's Degree. 1.3% has a Doctorate and 1% has a PhD.
Employment Status - With the current world situation we included the option "Covid-Related Uncertainty". 7.9% of you voted this. 34.1% are employed, 30% of students are employed and 13.8% of the students are unemployed. 6.8% are unemployed.
Employment Field - New question last year but updated a tiny amount this year. We see a majority of our users working with Computer Science and Maths, Healthcare, Financial Business, Engineering and Arts, Design & Entertainment.
Where Do You Currently Live?
World Region - 56.8% of the participants are based in North America, majority in the US. 22% are in Europe, majority in the UK. 10.3% in Asia, with most users in Philippines, Singapore and India.
Time Zones - Check the infographic for a better overview for this one. Majority of users are in UTC-05 and UTC-06.
K-Pop Engagement Questions
How were you first exposed to K-pop? - This first segment got divided into two questions this year. Most of our users had their first exposure to K-Pop through a friend, co-worker or classmate. A lot also had their first exposure to K-Pop through Youtube videos and recommendations. 10.6% were exposed to K-Pop through Gangnam Style.
What got you into K-pop? - 29.2% said that there were specific artists / groups that made you stay in the genre. 25.7% got into K-Pop from specific songs and MVs. 15.4 were interested in the songs and albums.
When did you start listening to K-Pop? - The users who started listening to K-pop 5-3 years ago was the largest % here at 19.5%. Last year, 7.8% of our users started listening to K-Pop less than a year ago, that's now gone down to 5.2%.
How do you listen to K-Pop? - Paid streaming rose from 62.2% last year to 63.8% this year. Piracy declined from 18.3% to 14.5%.
What other genres do you listen to? - New question this year. The largest three genres were Pop (80.5%), Hip-Hop / Rap (47.1%) and Rock (42.4%)
Do you know Korean? - 75.9% know very little to no Korean. This is roughly the same as last years census at 75.9%. 3.3% can speak conversational Korean.
Are you learning Korean? - 38.1% wants to learn but haven't taken it seriously yet. 13.5% are actively engaged in learning Korean.
Where do you get your K-Pop news? - 98.8% use kpop to get their news. Twitter, group subreddits, Youtube and Instagram also score high.
How often do you visit kpop? - 35.5% visit kpop multiple times a day. while 31.2% visit about once a day. 21.4% visit a few times per week.
What is your primary way to view kpop? - 44.5% use the official mobile app. This has decreased from last years 60%. 18.1% use Desktop Redesign (me included). This has now overtaken Desktop Old Design at 16.9%.
Is this your first kpop census? Not included as a question in the infographic. 50.8% said that this is their first census. 22.5% had their first census last year. 26.7% said that their first census was two or more years ago.
IU (2175 votes)
Chungha (2004 votes)
Sunmi (1782 votes)
Taeyeon (1442 votes)
Taemin (1080 votes)
Agust D / Suga (1046 votes)
Hwasa (1046 votes)
Baekhyun (900 votes)
Hyuna (879 votes)
Zico (700 votes)
IU (1st, 2175) reclaims the 1st place over Chungha (2nd, 2004). Sunmi (3rd, 1782), Taeyeon (4th, 1442) and Taemin (5th, 1080) keep their same position as last years census. Agust D (6th, 1046) has moved from last year's 8th place and moved up to a combined 6th place with newcomer Hwasa (6th, 1046) Hwasa was previously voted 17th place at last years census. Baekhyun (8th, 900) was placed at 16th place at last years census but now climbed up to 8th. Hyuna (9th, 879) was 7th place at last years census but is now at 9th place. Zico (10th, 700) was voted to 23rd place last year, he's now up to 10th place. Artists who dropped out of the top 10: RM (12th, 658), Heize (13th, 637), Dean (14th, 620).
Red Velvet (2857 votes)
TWICE (2410 votes)
BTS (1876 votes)
ITZY (1555 votes)
BLACKPINK (1550 votes)
MAMAMOO (1464 votes)
NCT (All Units) (1382 votes)
LOONA (All Units) (1345 votes)
(G)I-DLE (1334 votes)
EXO (1320 votes)
Red Velvet (1st, 2857) retakes their throne over TWICE (2nd, 2410) this year. BTS (3rd, 1876) is still topping the boy group vote. ITZY (4th, 1555) was placed 12th place last year. They have now moved up and taken the 4th place, they have pushed Girls' Generation (12th, 1155) out of the top 10. LOONA (8th, 1345) was 4th last year but has now been overtaken by NCT (7th, 1382), MAMAMOO (6th, 1464) and Blackpink (5th, 1550). EXO (10th, 1320) went from 8th last year to 10th this year. Artists who dropped out of the top 10: Girls' Generation (12th, 1155). I recommend checking the infographic for this one to see the differences in male and female voting in both favourite groups and favourite soloists.
Thank you all for participating in this years census! Sorry it took a little while for us to upload it, but we tried to do it as fast as possible. If there are any questions you'd like to see altered or improved for next years census then we're all ears. We think more data is better. Cheers, and stay safe during this crazy pandemic. Nish
Hey, it's some weirdo again. Bored on a gloomy day, thought I'd write down some thoughts. I see a lot of my fellow sissy weirdos having a lot of serious struggles with whether to come out, whether to live full time, and what kinds of secrets to have. It can be a very painful thing to struggle with, and for a lot of people it's what leads a harmless kink into some serious depression and anxiety. So I just wanted to share a bit about what I've learned along the way in the hopes that it could be beneficial to someone reading. Now just to start with, I have very little judgement and I don't aspire to be a bummer. The last thing I want to do is make you overthink your love of sucking cock, your desire to have your sensitive little sissy nips played with while you're in a pink tutu, or make you feel bad about your secret panty collection. This should be fun, and you should have fun! I don't think sex is inherently something to be ashamed of, nor do I think eschewing normal gender roles is inherently problematic. So don't worry, sweet little sluts, I have you. That said, we do get a little serious towards the end. I feel like I need to give a disclosure here: I live my life as a cis man, but experience some gender dysphoria and have been having sissy experiences for something like a decade. I'm not a mental health professional, and if you're struggling with serious depression, go find one instead of reading reddit threads. That said, if you want someone to relate to, some of my experiences might help. Definition of Sissy So though a million people have done this in the past, I wanted to start by defining what a sissy is. The fact is that nobody can really make a definition that works for everyone as there is no true authority on the matter. But from reading what others have interpreted and from my own personal life experience, I think that a sissy is a person born male who gets sexual gratification out of the idea of being forced/ coerced/ or seduced into acting feminine, dressing feminine, or taking on a feminine role in sex. This is meant to stand in contrast to a trans woman, who is a person assigned male at birth but who identifies distinctly as female. Trans women can certainly still enjoy sissy play, but not all sissies are trans. What's probably the most important thing to take from this definition of sissy is that it sort of has some inherent discord to the definition: "sissy" describes a person who should have had the OPPORTUNITY to be male and masculine, but who instead chooses or is forced to portray a feminine role. The very existence of sissies is thus in a state of inherent disharmony, a disharmony echoed in most sissy porn that frequently expresses coercion or plays off the idea of being degraded to a point of sexual submission. In essence, it's about being one thing AND another, at the same time. It's no surprise then that the idea of secrets and imbalance are an inherent part of the ideology. You are effectively living your life as one thing and another, so it's normal that people confront this idea of secrets and what to be open with. The Value of Secrets In short, everyone has secrets, and secrets can be a fun thing. We all like to act like we're open books, but the fact of the matter is that everyone you know has something they don't share with the world. More of us than not have unique sexual interests or have had unique sexual experiences, and even outside of sex, we all have things we don't want the world to know about. You shouldn't feel like a freak if you have a fun obsession with sexy sissy stuff. If you day dream about having a mouth full of cum all the time, you shouldn't feel bad about that. Gargle away. Secrets in this case are not inherently a bad thing. By their very nature they express a certain vulnerability: they represent something that you know that you wouldn't want the world to know about, and that can make you feel like there's a moralistic imperative to have less of them. Basically you're afraid of your secret leaking to the world, so you think to yourself that your secret is inherently bad. But it isn't! The way I always think about it is this: does your mom need to know what your favorite sex position is? Does your boss need to know when your first hand job was? These are fundamental experiences we all have that don't need to carry a moral weight to them, but that also don't need to be shared in the world. Your personal fetishes can be the same. And there are, from my personal experience, some benefits to having secrets. I spent a long time in my 20s being pretty closeted about my sexual endeavors. I'd meet up with guys from craigslist and suck their cocks, I would dress in my girlfriends clothes and have two guys over to double end me, I snuck off to gay sex parties where i'd suck cock and get fucked by strangers, and the world didn't know about it. As much as I did feel some vulnerability that my secrets might be exposed, I also felt an ongoing sense of confidence. When you have secrets like that, certain things in the world can't touch you. insults that people might make about you or assumptions about you just roll off your back: you know that they don't know the real you, so how could their opinion about you really matter? Only you know the real you. They just see what you want them to see. their judgments mean nothing. Additionally, going through some of the real scary and intense sort of stuff--having gay sex in a public restroom or glory hole, or going to a strangers house to fuck--can sort of turn down the volume on other things in life. Stuff that used to be scary simply isn't anymore because you've dealt with some REAL scary shit, and survived. Even when your secret is that you love taking it in the ass and guzzling piss and cum, it can be empowering to simply have something for YOURSELF. something that you do, because you want to do it, and you aren't afraid of the world's repercussions. The Cost of Secrets All of that said, there are certainly costs to being a secretive person, and some of those costs can be pretty serious and a real bummer. Some of them can have a drastic effect on your mental health. The first thing to confront for sissies of course is whether or not you're expressing internal homophobia or misogyny. Feeling closeted can be an awful feeling. Watching people be out and proud about being gay or being trans and you yourself having impulses that you don't share can make you see yourself as a coward, or a liar, or a fake. You can feel like you're hurting people who are out, or hiding from people who scare you. There's a lot of nuance in the sissy world about this kind of thing so I won't go at it at length, but I would encourage everyone to try to step away from those classic "is being a sissy gay" or "am i gay if i just wanna suck cock" kind of arguments. These sort of things still put the term "gay" as being this awful, OTHER thing that you don't want to be. It's inherently qualifying gay as being a worst case scenario, something to avoid, something to be afraid of. So i would encourage you to have less fear of it as a sexual identity. maybe you are bisexual, or queer, or curious, or whatever. It doesn't matter. What matters is how you feel about it. If, to you, having a preference to suck cock isn't any different than a slight preference for doggy style, then sure, maybe you don't have an obligation to come out as gay or bi or whatever. Looking at some cock here and there isn't a big deal. But if for you it's causing you to feel ashamed, then consider coming out as queer or bisexual. That's what i did! eventually i started feeling awful about being closeted in a world full of hate and homophobia, so i came out. For me, it was a good decision that ended up having a remarkably small effect on my life, and it separated a lot of the mental baggage i had. I still had my secrets, nobody knew exactly WHAT i was doing with guys, but knowing that the world had an idea made me a lot less afraid to be exposed to the world, a lot less ashamed of who i was as a person. So, to summarize, it's a personal decision, but consider non-binary options. You can identify however you want, to whoever you want. Shades of gray are not only permitted, but inevitable. (quick note: there's nothing cowardly or shameful about not coming out if you're in a scary situation. if you live with your parents and your dad is an awful homophobe, you don't have to feel an obligation to come out that said, you should start the wheels on doing ANYTHING and EVERYTHING you can to get out of that situation, at your own pace. get a job, save money, make a plan to move out and gain your own independence so you can start being yourself.) The next risk of being secretive concerns your partners. Many of you are in straight relationships and you might feel like you've got past the point of no return: if you were going to tell your partner that you sometimes suck cock or that you want to wear her clothes or that you look at weird sissy hypno porn, you feel like you should have done it by now. maybe you feel like she won't love you or respect you anymore. This obviously is going to be very different from relationship to relationship. But I would strongly recommend that you open up to people you're in relationships with, and try to do it early. The longer you're with a person the higher the odds are that they'll somehow find out what you've been up to, and if they find out that you have a whole sexual identity that they weren't aware of when they've been with you for years, this can be a very painful and traumatizing process. It isn't that the things you enjoy are inherently BAD, it's simply that you've shown that you don't trust this person to know the whole you, or to be welcomed in. and that can put a serious dent in a relationship. You certainly don't need to tell your partner every time you jerk off or show them what porn you like (unless you do that in a fun, kinky way). but if it's going to be an increasingly big part of your life, consider opening up to them about your interests. In the end, you deserve to be loved and appreciated for who you really are. \**incoming, important part**** Which leads into the biggest problem with secrets. Secrets are fun at first; as stated above, you get a thrill out of having these secret parts to you, these things that make you unique and special. you feel excited, horny, thrilled, and you have a good time. But there is a consequence to this, and that is that you'll begin to subconsciously feel that the people in your life don't know the REAL you. You'll come to believe that your friends, family, and partners only love the version of you that you PROJECT into the world, that they only love you because of who you fake you are. And when you're in a dark place in your life and you're trying to convince yourself that you are a good person, a person who's life has meaning and value... then a loved one looking you in your eyes and telling you they love you and think you're a good person will begin to feel hollow. You won't be able to take comfort in it, because you'll know that they don't actually know the REAL you. and you'll resent that part of yourself, and the people who don't know the real you, and you'll convince yourself that if they DID know the real you, they would hate you. If it isn't clear, I'm talking a bit from experience here. But fear not, there is a way out. I was a man full of secrets and lies, and eventually i realized that to really enjoy my life the way i wanted to i'd have to just be honest. I worked with my partner to open up about who i am and open up our relationship so that i could get what i needed, i gave my friends loose details about me being into weird kinky stuff (and didn't go into more detail than that) and came out as bisexual. And now, when my partner says she loves me, i can believe it. I know she knows the real me. And I have to tell you, my fellow perverts, having someone know the real you, know your deepest darkest feelings and secrets, and still LOVE you is just... the best feeling there is. Whether it's your partner or your friends or your family, it's a very uplifting feeling. So it takes work to communicate these things. You'll need to go out of your comfort zone. you'll hurt feelings, you'll have a hard time communicating, you'll stumble, you'll have moments of remorse. But if you get to the end of that road, you'll be happier and more free than you thought you could be. Whether to go Full Time Ok again, have to say that I'm not a therapist and i'm not a trans person, so take anything I say here with a grain of salt. But I know that lots and lots of you fine sissies are struggling with whether to go from fantasy to reality and transition. The first and most important thing here is that there isn't anything inherently wrong with being trans! So don't consider it a worst case scenario or anything that you should look at with dread. lots of people transition and live much happier lives, so if that's the path for you, enjoy yourself. That said! As I stated above, there's this inherent idea of being a "sissy" that means that you know that you're a man but believe you should act like or be treated like a woman. So a lot of the porn that goes along with sissy stuff tends to deliver this tempting, taunting message that you should finally take the plunge, take the leap, give in to your true desires, and transition. I guess I'd just say that you should jerk off and then think about it, if i'm being straight with you. We all get pretty ... intense, when we're in the heat of a sexual moment. when i'm horny and desperate you can feed me your ass and piss and spit in my face and i'll beg you desperately for more. I've done some shit. And for me personally, it does make me want to fall headlong into sissy play. I want to shave every inch of me, convert my body, throw away all my boxer shorts and be the sissy cock sucker cum dump i was meant to be. But i guess just keep in mind that real life is, in fact, real life. you can't actually look at the life of a cock sucking sissy as a simple ALTERNATIVE to your hum drum life because the fact is that sissies also need to do things like pay rent, have jobs, see their families on the holidays, raise their kids, see that guy from high school at the mall... all the stuff we have to do every day. The fact is there just aren't all these rich guys who want to pay you to dress pretty and be their slut, and the people who do get close to that, just get a few years out of it before they age out. So just jerk off. get it all out of your head, then go back and ask yourself how transitioning would effect your life goals, your relationships with people, and everything else you have going on. if it meets your goals, then go talk to a therapist and see if it's a good idea! If not, maybe you should just chill out and enjoy that you have this ever tempting fetish that you can enjoy for the rest of your days. In the End, Open Your Mind So that's pretty much it. I'd just want to end on this: a lot of sissies feel anxiety about their personal identity because they're trying to force that identity into boxes other people have defined. Whether you're gay or straight, whether you're a male or female, whether you're full time or part time, passable or not, a slave or a pillow princess, a cum addict or just a fantasizer.... these are all just toys for you to play with. none of them have to define you. none of them have to hurt you. you can use them to build up the identity and routine that gives you a sense of sexual satisfaction while preserving your greater life goals. so have fun with it, and relax. the world is your playground. note: if you liked reading this, i've written about lots of other sissy stuff on reddit. just click on my page and you'll see more, i think, i dunno i don't really know reddit. also, i love talking about sex and sexuality, so feel free to dm me with any questions if you don't like to comment directly.
Recently on the csharp subreddit, the post C# 9.0 records: immutable classes linked to a surprisingly controversial article discussing how C# 9.0's records are, underneath it all, immutable classes. The comments are full of back-&-forth over whether one should use records for ease or structs for performance. The pro-struct argument revolved around the belief that performance should always be a developer's #1 priority, and anything less was the realm of the laggard. Here is a real-world example that shows with stark clarity why that kind of thinking is wrong. Consider the following scenario:
You're working on a game with dozens, maybe hundreds of people on the team; you don't know because when you were cross with facilities about them removing all the fluorescents, you got accused of being against the new energy saving initiative. Now you swim in a malevolent ocean of darkness that on some very late nights alone in the office, you swear is actively trying to consume you.
The team that preceded you inherited an engine that is older than OOP, when source repositories were stacks of 8-inch floppies, and it looked as if Jefferson Starship was going to take over the world. One year ago they bequeathed upon the company this nightmare of broken, undocumented GOTO spaghetti & anti-patterns. You're convinced this was their sadistic revenge for all getting fired post-acquisition.
Management denied your request to get headcount for an additional technical artist, but helpfully supplied you with an overly nervous intern. After several weeks working alongside them, you're beginning to suspect they're pursuing something other than a liberal arts degree.
Despite the many getting started guides you spent countless evenings writing, the endless brownbags nobody attended, and the daily dozen emails you forward to oppressively inquisitive artists comprised of a single passive-aggressive sentence suggesting they scroll down to the part that begins FW: FW: FW: FW: FW: FW: RE: WE BROKE TOOL NEED WORKAROUND ASAP ...
...yes, despite all of that, the engineering team still spent days tracking down why the game kept crashing with Error 107221: У вас ошибка after re-re-re-re-re-throwing an ex_exception when it couldn't (and should never even try to) load a 16K-textured floor mat.
Despite your many attempts to politely excuse yourself, one blissfully unaware artist exhausts 48 minutes of your lunch break explaining how the Pitchfork review for the latest "dope slab" of this TikTok-Instagram-naphouse artist you never heard of was just sooooo unfair.
And then in their hurry to finish up & catch the 2:30 PM bus home, they forget to toggle Compress To CXIFF (Custom Extended Interchange File Format), set the Compression slider 5/6ths of the way between -3 & -2, look to their left, look to their right, click Export As .MA 0.9.3alpha7, and make absolutely, positively, 100% SURE not to be working in prod. And THAT is how the game explodicated.
You know better than anyone the intermediate file format the main game loop passes to Game.dll, memory mapping it as a reverse top-middle Endian binary structure.
You know for 381 of the parameter fields what their 2-7 character names probably mean.
YOU know which 147 fields always have to be included, but with a null value, and that the field ah_xlut must ALWAYS be set to 0 unless it's Thursday, in which case that blackbox from hell requires its internal string equivalent: TRUE.
YOU know that the two tech artists & one rapidly aging intern that report to you would totally overhaul tooling so artists would never "happen" again, but there just aren't enough winters, springs, summers, falls, July 4ths, Christmas breaks, Presidents Days, and wedding anniversaries in a year to properly do so.
And so somehow you do. A blurry evening or two here. A 3:00 AM there. Sometimes just a solitary lunch hour.
Your dog no longer recognizes you.
You miss your wife calling to say she's finally cleaning out the hall closet and if you want to keep this box of old cards & something in plastic that says Underground Sea Beta 9.8 Grade, you better call her back immediately.
And your Aunt Midge, who doesn't understand how SMS works, bombards you one evening: your father is... no longer with us... they found him... 1 week ago... in an abandoned Piggly Wiggly... by an old culvert... split up... he was then... laid down to rest... sent to St. Peter's... and your father... he's in a better place now... don't worry... it's totally okay... we decided we will all go... up to the mountain
You call your sister in a panic and, after a tidal wave of confusion & soul-rending anxiety, learn it was just Hoboken Wireless sending the messages out of order. This causes you to rapidly cycle.
On your bipolar's upswing, you find yourself more productive than you've ever been. Your mind is aglow with whirling, transient nodes of thought careening through a cosmic vapor of invention. It's like your brain is on 200mg of pure grade Adderall.
Your fingers ablaze with records, clean inheritance, beautiful pattern matching, bountiful expression syntax, aircraft carriers of green text that generate the most outstanding CHM for an internal tool the world has ever seen. Readable. PERFECTLY SOLID.
After much effort, you gaze upon the completed GUI of your magnum opus with the kind of pride you imagine one would feel if they hadn't missed the birth of their son. Clean, customer-grade WPF; tooltips for every control; sanity checks left & right; support for plugins & light scripting. It's even integrated with source control!
THOSE GODDAMNED ARTISTS CAN'T FAIL. YOUR PIPELINE TOOL WON'T LET THEM.
All they have to do is drag content into the application window, select an options template or use the one your tool suggests after content analysis, change a few options, click Export, and wait for 3-5 minutes to generate Game.dll-compatible binary.
Your optimism shines through the commit summary, your test plan giddy & carefree. With great anticipation, you await code review.
A week goes by. Then two. Then three. Nothing. The repeated pinging of engineers, unanswered.
Two months in you've begun to lose hope. Three months, the pangs of defeat. Four months, you write a blog post about how fatalism isn't an emotion or outlook, but the TRANSCENDENCE of their sum. Two years pass by. You are become apathy, destroyer of wills.
December 23rd, 2022: the annual Winter Holidays 2-hour work event. The bar is open, the Kokanee & Schmidt's flowing (max: 2 drink tickets). The mood a year-high ambivalent; the social distancing: acceptable. They even have Pabst Blue Ribbon, a beer so good it won an award once.
Standing beside you are your direct reports, Dave "Macroman" Thorgletop and wide-eyed The Intern, the 3 of you forming a triumvirate of who gives a shit. Dave is droning on & on about a recent family trip to Myrtle Beach. You pick up something something "can you believe that's when my daughter Beth scooped up a dead jellyfish? Ain't that something? A dead jellyfish," and "they even had a Ron Jons!"
You barely hear him, lost as you are in thought: "I wishIhad 2 days of vacation." You stare down ruefully at your tallboy.
From the corner of your eye you spot Milbert, index finger pointed upward, face a look of pure excitement.
"Did I tell you about my OpenWinamp project? It's up on SourceForge", he says as he strides over. It's unsettling how fast this man is.
Dave snickers. The Intern keeps staring wide-eyed. You position yourself somewhat close to the studio's 3 young receptionists, hoping they serve as a kind of ritual circle of protection.
It works... kind of. Milbert is now standing uncomfortably close to The Intern, Dave nowhere to be seen.
From across the room you distinctly hear "Think about it, the 1st-person UI could be Lua-driven Electron."
The Intern clearly understands that words are being spoken to them, but does not comprehend their meaning.
You briefly feel sorry for the sacrificial lamb.
You slide across the wall, putting even more distance between you & boredom made man. That's when you spot him, arrogantly aloof in the corner: Glen Glengerry. Core engineering's most senior developer.
Working his way up from a 16-year old game tester making $4.35 an hour plus free Dr. Shasta, to pulling in a cool $120K just 27-years later, plus benefits & Topo Chicos. His coding style guides catechism, his Slack pronouncements ex cathedra; he might as well be CTO.
You feel lucky your team is embedded with the artists. You may have sat through their meetings wondering why the hell you should care about color theory, artistic consistency, & debates about whether HSL or CMYK was the superior color space (spoiler: it's HSL), you were independent and to them, a fucking code wizard, man.
And there he stands, this pseudo-legend, so close you could throw a stapler at him. Thinning grey-blonde tendrils hanging down from his CodeWarrior hat, white tee with This Guy VIMs on the back, tucked into light blue jeans. He's staring out into the lobby at everything and yet... nothing all at.
Maybe it's the 4.8% ABV. Maybe it's the years of crushing down anger into a singularity, waiting for it to undergo rapid fiery expansion, a Big Bang of righteous fury. Maybe it's those sandals with white socks. Maybe it's all three. But whatever it is, it's as if God himself compels you to march over & give him a piece of your mind, seniority be damned.
"Listen, you big dumb bastard..."
That... is maybe a little too aggressive. But Glen Glengerry barely reacts. Pulling a flask out of his back pocket, he doesn't look over as he passes it to you.
Ugh. Apple Pucker.
"I thought bringing in your own alcohol was against company policy", wiping sticky green sludge from your lips. He turns with a look of pure disdain & snorts.
"You think they're going to tell ME what I can & can't bring in?" He grabs the flask back, taking a big swig.
For what feels like an eternity, you both stand in silence. You swallow, speaking softly. "None of you even looked at my code. I worked very, very hard on that. My performance review for that year simply read 'recommend performance improvement plan." The words need no further context.
"I know", Glen² replies. "That was me."
Now you're not a weak man, and maybe in some other circumstance you would have punched him in the goddamn lip. But you feel nothing, just a hollowness inside. "Why?", you ask, wondering if the answer would even matter.
"Because you don't use Bulgarian notation. Because your method names aren't lower camel case. Because good code doesn't require comments. Because you use classes & records over more performant structs, pointlessly burdening the heapstack. BECAUSE. YOUR CODE. IS. SHIT."
You clinch your fists so tightly the knuckles whiten.
He looks away from you, taking another sip of green goo. "You're not a coder. You're an artist masquerading as one" he speaks, as if it were fact.
The only thing artistic about you is the ability to create user-friendly internal tooling using nothing but a UI framework, broken down garbage nobody wants to touch, & sheer willpower. If your son's life depended on you getting accepted into art instruction school, you couldn't even draw a turtle.
He doesn't pause. "I'll champion ruthless micro-optimization until the day I die. But buddy, I'm going to let you in on a little secret: you aren't here to improve workflow. You're here to LOOK like you're doing something NOBODY else can."
He goes on. "What do you think those artists are going to do when they have to stare at a progress bar for 4, 5 minutes? They're going to complain your tool is slow."
"Sure, it may take them 20, 30 minutes to do it the old way, there'll be an error, and either they'll stare at it for 30 minutes before adding that missing semi-colon or they'll come get you. And you'll fix it. And 1 week later, they won't remember how. And you'll stay employed. And every. Body. Wins."
A little bit of the pride, the caring, wells back up inside from somewhere long forgotten.
"You don't think we should care about rapid application development & KISS, quickly getting things out that help our team, instead devoting ourselves to shaving off ticks here & there? What do you think artists are going to do with those 4 minutes you talk about?
You don't stop. "I'll tell you what they'll do. They'll 9GAG for 20 minutes straight. They'll listen to podcasts about dialectical materialism vis-a-vis the neo-feudalism that is a natural extension of the modern world's capitalist prison. They'll Reddit."
His silence gives you the bravery to push the limits.
"Christ, man. Are you only in it for the $120K..."
He corrects you: "...$123K."
"...only in it for the $123K/year? The free snacks from the microkitchen? The adulation? Have you no sense of comraderie?? No desire to push us to something better?! No integrity?!!!"
His eyes sharply narrow, face creases in anger. You clearly have overstepped your bounds.
"You thinkIdon't have integrity? No sense of teamwork? I'm only in it for the cold cash? You think I don't care about you all?", he roars.
A light volley of small green flecks land on your face.
"Why do you think they made a 16-year old tester the lead developer of a 1993 Doom clone?! Because my code was clean & painless to work with?! Because I made coding look easy?! No! IT WAS BECAUSE I WAS A GOD TO THEM.
And from a God, a PANTHEON. We built monuments to over-engineering! We crafted that of 7 weeks onboarding, that of immortal bugs, demonic hosts spawned by legion from the very loins of a fix. It took 2 years before a developer could BEGIN to feel confident they knew what they were doing. And by that time, they were one of US!
You think the team we laid off November '19 was fired because they were bad at their jobs? NO! It was because they worked themselves out of one. They didn't leave us a broken pipeline. They left an internal Wiki, a wealth of tools & example projects, and a completely transparent code base.
We couldn't have THAT, now could we? No, we couldn't. So we got rid of it. ALL OF IT. Poof. Gone. Just like that. Before anyone even knew a THING."
He leans forward, so close his psoriasis almost touches yours. With an intensity that borders on frightening, he whispers "You think they left us Game.dll? I fucking *MADE** Game.dll."*
The words hit hard like a freight train.
And without another word, he turns & leaves. You're left there, alone, coworkers milling about, with only one thought.
Were one to get a hobby, should it be cocaine?
It's these kinds of situations that make me believe there are far more important considerations than a ruthless dedication to performance, even in the game industry as my real-world scenario so clearly demonstrates.
No gods, no kings, only NOPE - or divining the future with options flows. [Part 2: A Random Walk and Price Decoherence]
tl;dr - 1) Stock prices move continuously because different market participants end up having different ideas of the future value of a stock. 2) This difference in valuations is part of the reason we have volatility. 3) IV crush happens as a consequence of future possibilities being extinguished at a binary catalyst like earnings very rapidly, as opposed to the normal slow way. I promise I'm getting to the good parts, but I'm also writing these as a guidebook which I can use later so people never have to talk to me again. In this part I'm going to start veering a bit into the speculation territory (e.g. ideas I believe or have investigated, but aren't necessary well known) but I'm going to make sure those sections are properly marked as speculative (and you can feel free to ignore/dismiss them). Marked as [Lily's Speculation]. As some commenters have pointed out in prior posts, I do not have formal training in mathematical finance/finance (my background is computer science, discrete math, and biology), so often times I may use terms that I've invented which have analogous/existing terms (e.g. the law of surprise is actually the first law of asset pricing applied to derivatives under risk neutral measure, but I didn't know that until I read the papers later). If I mention something wrong, please do feel free to either PM me (not chat) or post a comment, and we can discuss/I can correct it! As always, buyer beware. This is the first section also where you do need to be familiar with the topics I've previously discussed, which I'll add links to shortly (my previous posts: 1) https://www.reddit.com/thecorporation/comments/jck2q6/no_gods_no_kings_only_nope_or_divining_the_future/ 2) https://www.reddit.com/thecorporation/comments/jbzzq4/why_options_trading_sucks_or_the_law_of_surprise/ --- A Random Walk Down Bankruptcy A lot of us have probably seen the term random walk, maybe in the context of A Random Walk Down Wall Street, which seems like a great book I'll add to my list of things to read once I figure out how to control my ADD. It seems obvious, then, what a random walk means - when something is moving, it basically means that the next move is random. So if my stock price is $1 and I can move in $0.01 increments, if the stock price is truly randomly walking, there should be roughly a 50% chance it moves up in the next second (to $1.01) or down (to $0.99). If you've traded for more than a hot minute, this concept should seem obvious, because especially on the intraday, it usually isn't clear why price moves the way it does (despite what chartists want to believe, and I'm sure a ton of people in the comments will tell me why fettucini lines and Batman doji tell them things). For a simple example, we can look at SPY's chart from Friday, Oct 16, 2020: https://preview.redd.it/jgg3kup9dpt51.png?width=1368&format=png&auto=webp&s=bf8e08402ccef20832c96203126b60c23277ccc2 I'm sure again 7 different people can tell me 7 different things about why the chart shape looks the way it does, or how if I delve deeply enough into it I can find out which man I'm going to marry in 2024, but to a rationalist it isn't exactly apparent at why SPY's price declined from 349 to ~348.5 at around 12:30 PM, or why it picked up until about 3 PM and then went into precipitous decline (although I do have theories why it declined EOD, but that's for another post). An extremely clever or bored reader from my previous posts could say, "Is this the price formation you mentioned in the law of surprise post?" and the answer is yes. If we relate it back to the individual buyer or seller, we can explain the concept of a stock price's random walk as such:
Most market participants have an idea of an asset's truevalue (an idealized concept of what an asset is actually worth), which they can derive using models or possibly enough brain damage. However, an asset's value at any given time is not worth one value (usually*), but a spectrum of possible values, usually representing what the asset should be worth in the future. A naive way we can represent this without delving into to much math (because let's face it, most of us fucking hate math) is: Current value of an asset = sum over all (future possible value multiplied by the likelihood of that value)
In actuality, most models aren't that simple, but it does generalize to a ton of more complicated models which you need more than 7th grade math to understand (Black-Scholes, DCF, blah blah blah). While in many cases the first term - future possible value - is well defined (Tesla is worth exactly $420.69 billion in 2021, and maybe we all can agree on that by looking at car sales and Musk tweets), where it gets more interesting is the second term - the likelihood of that value occurring. [In actuality, the price of a stock for instance is way more complicated, because a stock can be sold at any point in the future (versus in my example, just the value in 2021), and needs to account for all values of Tesla at any given point in the future.] How do we estimate the second term - the likelihood of that value occurring? For this class, it actually doesn't matter, because the key concept is this idea: even with all market participants having the same information, we do anticipate that every participant will have a slightly different view of future likelihoods. Why is that? There's many reasons. Some participants may undervalue risk (aka WSB FD/yolos) and therefore weight probabilities of gaining lots of money much more heavily than going bankrupt. Some participants may have alternative data which improves their understanding of what the future values should be, therefore letting them see opportunity. Some participants might overvalue liquidity, and just want to GTFO and thereby accept a haircut on their asset's value to quickly unload it (especially in markets with low liquidity). Some participants may just be yoloing and not even know what Fastly does before putting their account all in weekly puts (god bless you). In the end, it doesn't matter either the why, but the what: because of these diverging interpretations, over time, we can expect the price of an asset to drift from the current value even with no new information added. In most cases, the calculations that market participants use (which I will, as a Lily-ism, call the future expected payoff function, or FEPF) ends up being quite similar in aggregate, and this is why asset prices likely tend to move slightly up and down for no reason (or rather, this is one interpretation of why). At this point, I expect the 20% of you who know what I'm talking about or have a finance background to say, "Oh but blah blah efficient market hypothesis contradicts random walk blah blah blah" and you're correct, but it also legitimately doesn't matter here. In the long run, stock prices are clearly not a random walk, because a stock's value is obviously tied to the company's fundamentals (knock on wood I don't regret saying this in the 2020s). However, intraday, in the absence of new, public information, it becomes a close enough approximation. Also, some of you might wonder what happens when the future expected payoff function (FEPF) I mentioned before ends up wildly diverging for a stock between participants. This could happen because all of us try to short Nikola because it's quite obviously a joke (so our FEPF for Nikola could, let's say, be 0), while the 20 or so remaining bagholders at NikolaCorporation decide that their FEPF of Nikola is $10,000,000 a share). One of the interesting things which intuitively makes sense, is for nearly all stocks, the amount of divergence among market participants in their FEPF increases substantially as you get farther into the future. This intuitively makes sense, even if you've already quit trying to understand what I'm saying. It's quite easy to say, if at 12:51 PM SPY is worth 350.21 that likely at 12:52 PM SPY will be worth 350.10 or 350.30 in all likelihood. Obviously there are cases this doesn't hold, but more likely than not, prices tend to follow each other, and don't gap up/down hard intraday. However, what if I asked you - given SPY is worth 350.21 at 12:51 PM today, what will it be worth in 2022? Many people will then try to half ass some DD about interest rates and Trump fleeing to Ecuador to value SPY at 150, while others will assume bull markets will continue indefinitely and SPY will obviously be 7000 by then. The truth is -- no one actually knows, because if you did, you wouldn't be reading a reddit post on this at 2 AM in your jammies. In fact, if you could somehow figure out the FEPF of all market participants at any given time, assuming no new information occurs, you should be able to roughly predict the true value of an asset infinitely far into the future (hint: this doesn't exactly hold, but again don't @ me). Now if you do have a finance background, I expect gears will have clicked for some of you, and you may see strong analogies between the FEPF divergence I mentioned, and a concept we're all at least partially familiar with - volatility. Volatility and Price Decoherence ("IV Crush") Volatility, just like the Greeks, isn't exactly a real thing. Most of us have some familiarity with implied volatility on options, mostly when we get IV crushed the first time and realize we just lost $3000 on Tesla calls. If we assume that the current price should represent the weighted likelihoods of all future prices (the random walk), volatility implies the following two things:
Volatility reflects the uncertainty of the current price
Volatility reflects the uncertainty of the future price for every point in the future where the asset has value (up to expiry for options)
[Ignore this section if you aren't pedantic] There's obviously more complex mathematics, because I'm sure some of you will argue in the comments that IV doesn't go up monotonically as option expiry date goes longer and longer into the future, and you're correct (this is because asset pricing reflects drift rate and other factors, as well as certain assets like the VIX end up having cost of carry). Volatility in options is interesting as well, because in actuality, it isn't something that can be exactly computed -- it arises as a plug between the idealized value of an option (the modeled price) and the real, market value of an option (the spot price). Additionally, because the makeup of market participants in an asset's market changes over time, and new information also comes in (thereby increasing likelihood of some possibilities and reducing it for others), volatility does not remain constant over time, either. Conceptually, volatility also is pretty easy to understand. But what about our friend, IV crush? I'm sure some of you have bought options to play events, the most common one being earnings reports, which happen quarterly for every company due to regulations. For the more savvy, you might know of expected move, which is a calculation that uses the volatility (and therefore price) increase of at-the-money options about a month out to calculate how much the options market forecasts the underlying stock price to move as a response to ER. Binary Catalyst Events and Price Decoherence Remember what I said about price formation being a gradual, continuous process? In the face of special circumstances, in particularly binary catalyst events - events where the outcome is one of two choices, good (1) or bad (0) - the gradual part gets thrown out the window. Earnings in particular is a common and notable case of a binary event, because the price will go down (assuming the company did not meet the market's expectations) or up (assuming the company exceeded the market's expectations) (it will rarely stay flat, so I'm not going to address that case). Earnings especially is interesting, because unlike other catalytic events, they're pre-scheduled (so the whole market expects them at a certain date/time) and usually have publicly released pre-estimations (guidance, analyst predictions). This separates them from other binary catalysts (e.g. FSLY dipping 30% on guidance update) because the market has ample time to anticipate the event, and participants therefore have time to speculate and hedge on the event. In most binary catalyst events, we see rapid fluctuations in price, usually called a gap up or gap down, which is caused by participants rapidly intaking new information and changing their FEPF accordingly. This is for the most part an anticipated adjustment to the FEPF based on the expectation that earnings is a Very Big Deal (TM), and is the reason why volatility and therefore option premiums increase so dramatically before earnings. What makes earnings so interesting in particular is the dramatic effect it can have on all market participants FEPF, as opposed to let's say a Trump tweet, or more people dying of coronavirus. In lots of cases, especially the FEPF of the short term (3-6 months) rapidly changes in response to updated guidance about a company, causing large portions of the future possibility spectrum to rapidly and spectacularly go to zero. In an instant, your Tesla 10/30 800Cs go from "some value" to "not worth the electrons they're printed on". [Lily's Speculation] This phenomena, I like to call price decoherence, mostly as an analogy to quantum mechanical processes which produce similar results (the collapse of a wavefunction on observation). Price decoherence occurs at a widespread but minor scale continuously, which we normally call price formation (and explains portions of the random walk derivation explained above), but hits a special limit in the face of binary catalyst events, as in an instant rapid portions of the future expected payoff function are extinguished, versus a more gradual process which occurs over time (as an option nears expiration). Price decoherence, mathematically, ends up being a more generalizable case of the phenomenon we all love to hate - IV crush. Price decoherence during earnings collapses the future expected payoff function of a ticker, leading large portions of the option chain to be effectively worthless (IV crush). It has interesting implications, especially in the case of hedged option sellers, our dear Market Makers. This is because given the expectation that they maintain delta-gamma neutral, and now many of the options they have written are now worthless and have 0 delta, what do they now have to do? They have to unwind. [/Lily's Speculation] - Lily
One of the main complaints about QC is the lack of a server browser. In DBT we have a server browser but nobody uses it. I wonder what is the reason: is this feature not really needed or is this feature not exposed enough? I would rather lean towards the 2nd option. I have some random ideas on how to Make Server Browser Great Again:
Server browser doesn't stand out enough. It's hidden under the "Custom games" button:
Rename "Custom games" to "Community servers".
Display the number of custom servers over the "Community servers" button. Use the same UI that indicates the number of new items in the Locker (the yellow thingy). This will encourage people to click on this button.
Alternatively move "Custom Games" to the main screen - put it on the Quick Play screen (not really sure is it a good idea)
Display players list and their ranks in a popup when the mouse cursor is over the custom server name
Display an icon that tells what is the average rank of players that are currently playing on the server
Make it possible to set a rank cap or a minimum/maximum rank
Add presets. At the moment if we want to set up a custom server we have to select a bunch of options. Let's add some thumbnails that, when clicked, would start a server with exactly the same settings that public games have (Wipeout, FFA, MacGuffin, etc). I would even make such a selection to be the primary screen when one clicks a "create a new game" button. So basically starting a new server should be as easy as joining a quick play game.
In the future, when server binaries are available, let private servers "talk" to the master server and let players browse private servers via "Community servers" tab.
I won't add "let us play custom maps" to the list because I know it's on the roadmap.
Wait, some people really actually FEEL LIKE their AGAB?
Shortly after realizing you were trans, did you have a moment of "Oh wait... some people really ARE women/men"? This sounds dumb and I wouldn't have understood what I meant if I read these words like 3 weeks ago. Like, duh, of course. But it never clicked for me that "woman" and "man" really are two different frameworks for BEING in the world. The one I was given fit so poorly I didn't understand how it was supposed to work. And yet it took me 32 years to realize this and actually like, decide to do away with it for myself and try out the other binary option. Just realizing I was Not-Cis was a great step, but trying on the other binary gender and FEELING AT HOME IN IT was a complete surprise. I never in a million years would have thought I was trans but it makes so much sense now. How could I not have seen this for > 3 decades??
What is up Depthians! We are back with another monstrous update as this one incorporates five beta test builds, so we have a lot to cover. If you want to dive straight into the massive changelog/dissertation Click We should probably start with the biggest change to From The Depths in this update and that is the change of fuel and ammo storage. Quoting Nick, our lead developer
The change is quite simple: "remove ammo and fuel as separate resources. Weapons will consume materials directly, fuel engines and CJEs will burn materials directly". Before I dig into why I think this is the right thing for FtD, I'd like to explain a few details. Energy, fuel and ammo are still needed for your constructs. We have changed the "ammo barrels (etc)" and "fuel tanks" so they are just alternative material storage containers, but with the following properties: --"ammo barrels" now increase the maximum possible rate of usage of materials as "ammo" for reloading guns. They still explode. --"fuel tanks" increase the maximum possible rate of use of materials as "fuel" for fuel engines and CJEs, with the future stretch goal of fuel tanks being flammable. --So ammo racking is going to remain a feature of the game- vehicles that need to reload a large amount of materials may need additional ammo barrels Ammo and oil processors are replaced ship-wide with existing material storage containers of the same size. They'll be made decorative blocks so you can still use them decoratively in future if you want to. The oil refinery will be repurposed (described later in the patch notes) There are two main reasons why I think this is the right move. Why it's right for the business and why it's right for the player. Let's start with why I think it's right for the player: Ammo and fuel containers are currently purchasable as either "empty or full". This is confusing when considered in the context of the campaign, story missions, custom battles, multiplayer matches...how do empty and full tanks behave in these modes? I'd need an hour to study the code and a small essay to explain it. That's not good game design. Localised resources, when considering just the moving of material (and energy, if you want), becomes infinitely more manageable. The supply group system and the transit fleet system are not intuitive and for a lot of situations, their usage becomes fiddly and too complicated. We've replaced these systems with a new supply system that is much more intuitive for moving materials and energy around. The UI is less cluttered now that ammo and fuel bars are not shown. This is not a minor point...it'll reduce the amount of data on screen by about 40% in a lot of the different views. It'll be so much easier to know at a glance if a particular fleet is running low on "materials" or doing fine. Is a transport ready to leave, or does it need to pick up more materials? Will a set of vehicles have enough materials for the next fight...this is so much easier with just one main resource type per vehicle. When you or an enemy run out of ammo or fuel in a battle it's just frustrating. By combining fuel, ammo and materials for repairing you can guarantee that if someone runs out, the fight is going to be over quickly. I imagine that deep down the majority of players would rather not have to create, stock and resupply fuel and ammo. I know that personally, the requirement to do this puts me off playing the campaign. By using a single material it still focuses the game on making efficient war machines, maintaining supply lines and growing your economy, but without the extra confusion of mat->ammo and mat-> fuel conversion. Being able to assess weapons, engines and vehicles in terms of material cost and running cost is elegant. Most grand strategy games and RTS games don't have localised resources, and many don't have more than 2 resource types to handle. Very few combine localised materials with multiple types. Why it's right for the business: The ammo and oil processors were created about 8 years ago. Boring single blocks that don't add much to the game. It's been our intention to add something similar to the oil refinery but for ammo creation. That's a lot of work and adds to the complexity of the logistical part of the game, which we feel is already a burden. Making the localised resource supply system more user friendly to make it easy/natural/pleasant to move ammo, fuel and material around the map would require a lot of effort and, quite frankly, I'm not sure we'd ever manage it. The complexity of the UI scares off a lot of our customers. The barriers to getting a gun firing or a boat moving will be lowered if a single material container can theoretically get everything working. Running out of ammo/fuel in combat is a problem for our players. We want to find a solution to that, but it would take a lot of effort to do so. We also want the strategic AI to always enter a battle with enough ammo and fuel for the fight- that's another massive bunch of work. The campaign's strategic AI has to work hard to get materials where it wants them. It's a bundle of work and added complexity to get NPC fleets to restock ammo and fuel as well. We had proposed work to make resource dumps (from dead ships) contain ammo and fuel...again, that's more work, more bugs, more testing. Certain game modes such as story missions, tournament mode, and multiplayer maps should theoretically allow the player to choose the amount of ammo or fuel stocked into their vehicles before the match begins. That's another bundle of work and added complexity we'd like to avoid. Currently out of play units on the map can run out of fuel and will still continue to move "for free". It's exploitable and we don't have a solution to that...but if all the different out of play movement calculations are burning material, there will be no avoiding the cost. The development effort can be much better spent polishing up other features that I actually believe in, rather than flogging the dead horse of logistical complexity in an attempt to make it interesting, approachable and fun for everyone (which I fundamentally don't think it would ever be). Fundamentally I think that by winding back this feature we tie up a large number of loose ends and it results in a far more finished and enjoyable product. And what's-more everyone on the development team agrees that we enjoy the game for fighting, looting and creating...not staring blankly at dozens of resource bars trying to figure out who needs to head back for more fuel and how long we need to wait for ammunition to process. We've also simplified the resource transfer system. "Supply groups" and "Transit Fleets" have been replaced with a simple but comprehensive three-tier system. You can mark a vehicle as a "Creator", a "Cargo" or a "User". Creators fill up Cargos (and Users), Cargos give to Users (up to procurement levels). Users equalise their material with their neighbours, so do Creators, and there are a few handy transfers from Users back to Cargo and Creator to make sure they maintain their procurement levels as well. This system covers 95% of the way people were using the resource system and does it all semi-automatically. This simplification is much more possible now that materials are the only resource, as they invariably just need to flow from the resource zones to the front line, with everyone (Creators and Cargo) keeping what they need and passing the rest on. This new resource system also facilitates the long-range transport of materials from refinery to refinery, which is neat. The system also has an option, for Creator and Cargo types, to set their "supply chain index", so if you want to relay materials from output to output in order to accumulate them at a central location you can set the supply chain index to determine which way along the chain the materials will flow. It's all explained in the game.
After spending a lot of time with this new system from adventure to campaign and designer mode, the gameplay feels a little faster to get going and a little simpler for fleet management. As if you didn’t already know, you can shift+right click (with your supply construct selected) on the target construct / flagship of a fleet to keep supplied, keep holding down shift and right-click where you want to pick the resources up from and once again while not letting go of shift, shift+right click on the target construct/flag ship to finish the loop. This would be done of course after setting up the settings Creator, Cargo and User. Creator as an example is the harvesting construct, Cargo which would be the supply ship, User which would be a single target construct that uses the mats. This will keep the supply ship target waypoint updated and therefore your supply ship will always head to the target construct no matter where it has moved to after setting up the loop. You still need ammo and fuel boxes on your constructs, as these are governing the transfer rate / the speed that stock your turrets and fuel engine with the materials needed for them to run. You can run a construct without fuel or ammo boxes, however, once your APS clips are empty you will see a drop in your rate of fire as the material is not being transferred fast enough, this is the same for fuel engines and CJE. Another change that goes hand in hand with resource management is the changes to fuel refineries. In short:
Refineries on a force with greater than 1 million materials on it will begin refining the material into 'commodities' that are stored centrally. Commodities (AKA centralised materials) can be added by the player to any vehicle in allied territory, at any time.
Steam was previously totally unbalanced and arbitrary. For example, 9 small boilers with 1 small piston was the optimal steam setup, which was more efficient and denser than almost all other engines; and turbine power generation only depended on its pressure, so compact turbines were always optimal.
It lacked many critical info in its UI.
It was hard to control the usage of steam
What's good with new steam:
A bit more of realism and complexity
Larger steam now generally have better efficiency and density than equivalent smaller steam
More useful info such as total power production, performance over time
Possibility to regulate steam usage with valves
Pros of steam compared to injector fuel:
Denser and more efficient
Even denser with turbines
Easier to fit into irregular space
Provides a buffer with flywheels or steam tanks
More efficient when used for propellers
Doesn't require fuel containers, uses material directly from any type of storage
Computationally less intensive
Cons of steam compared to fuel:
Still hard to regulate, so it's only useful when the power usage is constant or there's a buffer energy storage
Turbines waste energy when batteries are full
Crankshafts waste energy when reaching speed limit
More susceptible to damage (injector engines can often still run fine even when half of it is gone, steam can stop working when a single pipe is destroyed)
Why cost of parts is hilariously high: Steam engines have better efficiency and density (many players seem to forget that one) than injector engines. So a higher initial costs makes it less overpowered. (In my opinion, the potential waste of energy is a major drawback of steam and justifies for its high potential power. But iirc Draba said that injector engines would be useless on designs that require a lot of power if steam doesn't have higher initial cost, which also makes sense.) Problem with new steam that can't be fixed:
Many old designs are broken due to low power output
Problems that can probably be fixed but I don't have a solution:
Inefficient steam engines are ridiculously bad (a bad steam engine is like 30 PPM and 50 PPV, while a good one is around 600 PPM and 110 PPV) (I tried to fix this and spent like 40 hours on that, but I only managed to make it easier to build a mediocre engine)
Cannot be simulated to calculate a stable power output, like fuel engines do (actually it's easy but would take a lot of time to do and I don't think it's necessary)
Another massive change is the detection rework which I also left a few questions for Ian AKA Blothorn to explain the system and how it works. Why a change was warranted:
Different types of detection weren't well balanced--for instance, visual components had better accuracy than IR and vastly better range.
Detection autoadjust used an incorrect formula, so optimizing adjustment was both mechanical and tedious.
Trackers having much better detection ranges than search sensors meant that detection was very binary--if you could see something at all you could usually get a precise lock (barring ECM, which was only counterable by large numbers of components).
Needing both sensors and munitions warners made reactive missile defence difficult on small vehicles.
There were a number of other inconsistencies/imbalances, e.g. some visual/IR sensors working through water, steam engines producing no heat, etc.
Overview of the new system: On the offensive side, each sensor type now has a role in which it is optimal, and large vehicles are best using a variety to cover their weaknesses. Visual probably remains the default for above-water detection--it remains impossible to reduce visual signature other than reducing size. IR is better against fast vehicles, as they have trouble avoiding high IR signatures from thrust and drag. Both visual and IR are weak in rangefinding (although coincidence rangefinders are adequate for most purposes); radar is correspondingly strong in range and weak in bearing, although it often offers better detection chances against vehicles that don't pay attention to radar stealth. On the defensive side, there are two approaches. Most obvious is signature reduction--while it is deliberately difficult to avoid detection entirely, reducing signature reduces detection chances and thus degrades opposing accuracy. At short ranges, however, this doesn't work well--detection chances are likely high regardless, and low errors at short range mean even sparse detections can give a good fix. Smoke and chaff can be useful here: they increase detection chance while adding a distance-independent error to opponent's visual and radar sensors, respectively. ECM, buoys, and radar guidance have also been reworked. Buoys are more powerful, becoming more accurate as they get closer to the target. While their base error is high, at long ranges a buoy at close range can beat the accuracy of any onboard sensor. If you worry about opponents’ buoys, ECM can now intermittently jam them--except if they are connected to their parent vehicle by a harpoon cable, in which case they don't need the vulnerable wireless connection. Most blueprints should need no modifications under the new system, although a few may want a few more or less GPP cards. The one exception is water interactions--IR cameras, laser rangefinders, and retroreflection sensors can no longer work through water, so submarines that used them underwater or vehicles that used them to detect submarines will need to replace them (likely with buoys). Vehicles that predominantly used visual detection should also consider adding a greater variety of sensors--in particular, visual camera trackers tied to AA mainframes should likely be replaced with IR cameras. Also, radars and cameras can take over missile and projectile detection (radar is required for projectile detection), so munitions warners can be removed/replaced with additional sensors. Last but not least a sweet little addition to our build menu prefabs. https://preview.redd.it/iqw1ymabu9t51.png?width=1920&format=png&auto=webp&s=aa1e3cdba6e1d62e07aef83caf0acad2a39249ed Please do make sure you go through the changelog as a hell of a lot has changed!
The Challenges of Designing a Modern Skill, Part 3
Okay, Wendy’s or Walgreens or whoever, I don’t care who you are, you’re listening to the rest.
Introduction to Part 3
Welcome back one last time to “The Challenges of Designing a Modern Skill,” a series where we discuss all aspects of skill design and development. In Part 1, we talked about OSRS’s history with skills, and started the lengthy conversation on Skill Design Philosophy, including the concepts of Core, Expansion, and Integration. This latter topic consumed the entirety of Part 2 as well, which covered Rewards and Motivations, Progression, Buyables, as well as Unconstructive Arguments. Which brings us to today, the final part of our discussion. In this Part 3, we’ll finish up Section 3 – Skill Design Philosophy, then move on to chat about the design and blog process. One last time, this discussion was intended to be a single post, but its length outgrew the post character limit twice. Therefore, it may be important to look at the previous two parts for clarity and context with certain terms. The final product, in its purest, aesthetic, and unbroken form, can be found here.
3-C – Skill Design Philosophy, Continued
3-12 - Balancing
What follows from the discussion about XP and costs, of course, is balancing: the bane of every developer. A company like Riot knows better than anyone that having too many factors to account for makes good balance impossible. Balancing new ideas appropriately is extremely challenging and requires a great respect for current content as discussed in Section 3-5 – Integration. Thankfully, in OSRS we only have three major balancing factors: Profit, XP Rate, and Intensity, and two minor factors: Risk and Leniency. These metrics must amount to some sense of balance (besides Leniency, which as we’ll see is the definition of anti-balance) in order for a piece of content to feel like it’s not breaking the system or rendering all your previous efforts meaningless. It’s also worthy to note that there is usually a skill-specific limit to the numerical values of these metrics. For example, Runecrafting will never receive a training method that grants 200k xp/hr, while for Construction that’s easily on the lower end of the scale. A basic model works better than words to describe these factors, and therefore, being the phenomenal artist that I am, I have constructed one, which I’ve dubbed “The Guthix Scale.” But I’ll be cruel and use words anyway.
Profit: how much you gain from a task, or how much you lose. Gain or loss can include resources, cosmetics, specialized currencies, good old gold pieces, or anything on that line.
XP Rate: how fast you gain XP.
Intensity: how much effort (click intensity), attention (reaction intensity), and thought (planning intensity) you need to put into the activity to perform it well.
Risk: how likely is the loss of your revenue and/or resource investment into the activity. Note that one must be careful with risk, as players are very good at abusing systems intended to encourage higher risk levels to minimize how much they’re actually risking.
Leniency: a measure for how imbalanced a piece of content can be before the public and/or Jagex nerfs it. Leniency serves as a simple modulator to help comprehend when the model breaks or bends in unnatural ways, and is usually determined by how enjoyable and abusable an activity is, such that players don’t want to cause an outrage over it. For example, Slayer has a high level of Leniency; people don’t mind that some Slayer tasks grant amazing XP Rates, great Profits, have middling Intensity, and low Risk. On the other hand, Runecrafting has low levels of Leniency; despite low Risk, many Runecrafting activities demand high Intensity for poor XP Rates and middling Profits.
In the end, don’t worry about applying specific numbers during the conceptual phase of your skill design. However, when describing an activity to your reader, it’s always useful if you give approximations, such as “high intensity” or “low risk,” so that they get an idea of the activity’s design goals as well as to guide the actual development of that activity. Don’t comment on the activity’s Leniency though, as that would be pretty pretentious and isn’t for you to determine anyway.
3-13 - Skill Bloat
What do the arts of weaving, tanning, sowing, spinning, pottery, glassmaking, jewellery, engraving, carving, chiselling, carpentry, and even painting have in common? In real life, there’s only so much crossover between these arts, but in Runescape they’re all simply Crafting. The distinction between what deserves to be its own skill or instead tagged along to a current skill is often arbitrary; this is the great challenge of skill bloat. The fundamental question for many skill concepts is: does this skill have enough depth to stand on its own? The developers of 2006 felt that there was sufficient depth in Construction to make it something separate from Crafting, even if the latter could have covered the former. While there’s often no clean cut between these skills (why does making birdhouses use Crafting instead of Construction?), it is easy to see that Construction has found its own solid niche that would’ve been much too big to act as yet another Expansion of Crafting. On the other hand, a skill with extremely limited scope and value perhaps should be thrown under the umbrella of a larger skill. Take Firemaking: it’s often asked why it deserves to be its own skill given how limited its uses are. This is one of those ideas that probably should have just been thrown under Crafting or even Woodcutting. But again, the developers who made early Runescape did not battle with the same ideas as the modern player; they simply felt like Firemaking was a good idea for a skill. Similarly, the number of topics that the Magic skill covers is so often broken down in other games, like Morrowind’s separation between Illusion, Conjuration, Alteration, Destruction, Mysticism, Restoration, Enchant, Alchemy (closer to Herblore), and Unarmored (closer to Strength and Defense). Why does Runescape not break Magic into more skills? The answer is simple: Magic was created with a much more limited scope in Runescape, and there has not been enough content in any specific magical category to justify another skill being born. But perhaps your skill concept seeks to address this; maybe your Enchantment skill takes the enchanting aspects of Magic away, expands the idea to include current imbues and newer content, and fully fleshes the idea out such that the Magic skill alone cannot contain it. Somewhat ironically, Magic used to be separated into Good and Evil Magic skills in Runescape Classic, but that is another topic. So instead of arguments about what could be thrown under another skill’s umbrella, perhaps we should be asking: is there enough substance to this skill concept for it to stand on its own, outside of its current skill categorization? Of course, this leads to a whole other debate about how much content is enough for a skill idea to deserve individuality, but that would get too deep into specifics and is outside the scope of this discussion.
3-14 - Skill Endgame
Runescape has always been a sandbox MMO, but the original Runescape experience was built more or less with a specific endgame in mind: killing players and monsters. Take the Runescape Classic of 2001: you had all your regular combat skills, but even every other skill had an endgame whose goal was helping combat out. Fishing, Firemaking, and Cooking would provide necessary healing. Smithing and Crafting, along with their associated Gathering skill partners, served to gear you up. Combat was the simple endgame and most mechanics existed to serve that end. However, since those first days, the changing endgame goals of players have promoted a vast expansion of the endgame goals of new content. For example, hitting a 99 in any non-combat skill is an endgame goal in itself for many players, completely separate from that skill’s combat relationship (if any). These goals have increased to aspects like cosmetic collections, pets, maxed stats, all quests completed, all diaries completed, all music tracks unlocked, a wealthy bank, the collection log, boss killcounts, and more. Whereas skills used to have a distinct part of a system that ultimately served combat, we now have a vast variety of endgame goals that a skill can be directed towards. You can even see a growth in this perspective as new skills were released up to 2007: Thieving mainly nets you valuable (or once valuable) items which have extremely flexible uses, and Construction has a strong emphasis on cosmetics for your POH. So when designing your new skill, contemplate what the endgame of your skill looks like. For example, if you are proposing a Gathering skill, what is the Production skill tie-in, and what is the endgame goal of that Production skill? Maybe your new skill Spelunking has an endgame in gathering rare collectibles that can be shown off in your POH. Maybe your new skill Necromancy functions like a Support skill, giving you followers that help speed along resource gathering, and letting you move faster to the endgame goal of the respective Production skill. Whatever it is, a proper, clear, and unified view of an endgame goal helps a skill feel like it serves a distinct and valuable purpose. Note that this could mean that you require multiple skills to be released simultaneously for each to feed into each other and form an appropriate endgame. In that case, go for it – don’t make it a repeat of RS3’s Divination, a Gathering skill left hanging without the appropriate Production skill partner of Invention for over 2 years. A good example of a skill with a direct endgame is… most of them. Combat is a well-accepted endgame, and traditionally, most skills are intended to lend a hand in combat whether by supplies or gear. A skill with a poor endgame would be Hunter: Hunter is so scattered in its ultimate endgame goals, trying to touch on small aspects of everything like combat gear, weight reduction, production, niche skilling tools, and food. There’s a very poor sense of identity to Hunter’s endgame, and it doesn’t help that very few of these rewards are actually viable or interesting in the current day. Similarly, while Slayer has a strong endgame goal it is terrible in its methodology, overshadowing other Production skills in their explicit purpose. A better design for Slayer’s endgame would have been to treat it as a secondary Gathering skill, to work almost like a catalyst for other Gathering-Production skill relationships. In this mindset, Slayer is where you gather valuable monster drops, combine it with traditional Gathering resources like ores from Mining, then use a Production skill like Smithing to meld them into the powerful gear that is present today. This would have kept other Gathering and Production skills at the forefront of their specialities, in contrast to today’s situation where Slayer will give fully assembled gear that’s better than anything you could receive from the appropriate skills (barring a few items that need a Production skill to piece together).
3-15 - Alternate Goals
From a game design perspective, skills are so far reaching that it can be tempting to use them to shift major game mechanics to a more favourable position. Construction is an example of this idea in action: Construction was very intentionally designed to be a massive gold sink to help a hyperinflating economy. Everything about it takes gold out of the game, whether through using a sawmill, buying expensive supplies from stores, adding rooms, or a shameless piece of furniture costing 100m that is skinned as, well, 100m on a shameless piece of furniture. If you’re clever about it, skills are a legitimately good opportunity for such change. Sure, the gold sink is definitely a controversial feature of Construction, but for the most part it’s organic and makes sense; fancy houses and fancy cosmetics are justifiably expensive. It is notable that the controversy over Construction’s gold sink mechanism is probably levied more against the cost of training, rather than the cost of all its wonderful aesthetics. Perhaps that should have been better accounted for in its design phase, but now it is quite set in stone. To emphasize that previous point: making large scale changes to the game through a new skill can work, but it must feel organic and secondary to the skill’s main purpose. Some people really disliked Warding because they felt it tried too hard to fix real, underlying game issues with mechanics that didn’t thematically fit or were overshadowing the skill’s Core. While this may or may not be true, if your new skill can improve the game’s integrity without sacrificing its own identity, you could avoid this argument entirely. If your skill Regency has a Core of managing global politics, but also happens to serve as a resource sink to help your failing citizens, then you’ve created a strong Core design while simultaneously improving the profitability of Gathering skills.
3-16 - The Combat No-Touch Rule
So, let’s take a moment to examine the great benefits and rationale of RS2’s Evolution of Combat: This space has been reserved for unintelligible squabbling. With that over, it’s obvious that the OSRS playerbase is not a big fan of making major changes to the combat system. If there’s anything that defines the OSRS experience, it has to be the janky and abusable combat system that we love. So, in the past 7 years of OSRS, how many times have you heard someone pitch a new combat skill? Practically no one ever has; a new combat skill, no matter how miniscule, would feel obtrusive to most players, and likely would not even receive 25% of votes in a poll. This goes right back to Section 3-5 – Integration, and the importance of preserving the fundamentals of OSRS’s design. I know that my intention with this discussion was to be as definitive about skill design as possible, and in that spirit I should be delving into the design philosophy specifically behind combat skills, but I simply don’t see the benefit of me trying, and the conversation really doesn’t interest me that much. It goes without saying that as expansive as this discussion is, it does not cover every facet of skill design, which is a limitation both of my capabilities and desire to do so.
3-17 - Aesthetics
I don’t do aesthetics well. I like them, I want them, but I do not understand them; there are others much better equipped to discuss this topic than I. Nonetheless, here we go. Since the dawn of OSRS, debates over art style and aesthetics have raged across Gielinor. After all, the OSRS Team is filled with modern day artists while OSRS is an ancient game. What were they supposed to do? Keep making dated graphics? Make content with a modernized and easily digestible style? Something in-between? While many players shouted for more dated graphics, they were approached by an interesting predicament: which dated graphics did they want? We had a great selection present right from the start of OSRS: 2002, 2003, 2004, 2005, 2006, and 2007. People hungry for nostalgia chose the era that they grew up in, leading to frequent requests for older models like the dragon or imp, most of which were denied by Jagex (except the old Mining rock models). But which era was OSRS supposed to follow? Jagex elected to carve their own path, but not without heavy criticism especially closer to OSRS’s conception. However, they adapted to player requests and have since gone back and fixed many of the blatant early offenders (like the Kingdom of Kourend) and adopted a more consistent flavour, one that generally respects the art style of 2007. Even though it doesn’t always hit the mark, one has to appreciate the OSRS artists for making their best attempt and listening to feedback, and here’s to hoping that their art style examination mentioned in June 2020’s Gazette bears fruit. But what exactly is the old school art style? There are simple systems by which most players judge it in OSRS, usually by asking questions like, “Would you believe if this existed in 2007?” More informed artists will start pointing out distinct features that permeated most content from back in the day, such as low quality textures, low poly models, low FPS animations, a “low fantasy” or grounded profile that appeals somewhat to realism, reducing cartoonish exaggerations, and keeping within the lore. Compiled with this, music and sound design help that art style come to life; it can be very hard on immersion when these don’t fit. An AGS would sound jarring if its special attack sounded like a weak dagger stab, and having to endure Country Jig while roaming Hosidius suddenly sweeps you off into a different universe. But coming back to skill design, the art, models, and sound design tend to be some of the last features, mostly because the design phase doesn’t demand such a complete picture of a skill. However, simple concept art and models can vastly improve how a skill concept is communicated and comfort players who are concerned about maintaining that “old school feel.” This will be touched on again later in this discussion under Section 5-2 – Presentation and Beta Testing.
3-18 - Afterword
Now we’ve set down the modern standards for a new skill, but the statements that started this section bear repeating: the formula we’ve established does not automatically make a good or interesting skill, as hard as we might have tried. Once again, harken back to the First Great Irony: that we are trying to inject the modern interpretation of what defines a skill upon a game that was not necessarily built to contain it. Therefore, one could just as easily deny each of the components described above, as popular or unpopular as the act might be, and their opinion could be equally valid and all this effort meaningless. Don’t take these guidelines with such stringency as to disregard all other views.
5-0 - The OSRS Team and the Design Process
If you’ve followed me all the way here, you’re likely A) exhausted and fed up of any conversation concerning new skills, or B) excited, because you’ve just struck an incredible skill idea (or perhaps one that’s always hung around your head) that happens to tick off all the above checkboxes. But unfortunately for you B types, it’s about to get pretty grim, because we’re going to go through every aspect of skill design that’s exterior to the game itself. We’ll be touching on larger topics like democracy, presentation, player mindsets, effort, and resource consumption. It’ll induce a fantastic bout of depression, so don’t get left behind.
5-1 - Designing a Skill
Thus far, Jagex has offered three potential skills to OSRS, each of which has been denied. This gives us the advantage of understanding how the skill design process works behind the scenes and lets us examine some of the issues Jagex has faced with presenting a skill to the players. The first problem is the “one strike and you’re out” phenomenon. Simply put, players don’t like applying much effort into reading and learning. They’ll look at a developer blog highlighting a new skill idea, and if you’re lucky they’ll even read the whole thing, but how about the second developer blog? The third? Fourth? Even I find it hard to get that far. In general, people don’t like long detail-heavy essays or blogs, which is why I can invoke the ancient proverb “Ban Emily” into this post and it’ll go (almost) completely unnoticed. No matter how many improvements you make between developer blogs, you will quickly lose players with each new iteration. Similarly, developer blogs don’t have the time to talk about skill design philosophy or meta-analyse their ideas – players would get lost far too fast. This is the Second Great Irony of skill design: the more iterations you have of a lengthy idea, the less players will keep up with you. This was particularly prominent with Warding: Battle Wards were offered in an early developer blog but were quickly cut when Jagex realized how bad the idea was. Yet people would still cite Battle Wards as the reason they voted against Warding, despite the idea having been dropped several blogs before. Similarly, people would often comment that they hated that Warding was being polled multiple times; it felt to them like Jagex was trying to brute-force it into the game. But Warding was only ever polled once, and only after the fourth developer blog - the confusion was drawn from how many times the skill was reiterated and from the length of the public design process. Sure, there are people for whom this runs the opposite way; they keep a close eye on updates and judge a piece of content on the merits of the latest iteration, but this is much less common. You could argue that one should simply disregard the ignorant people as blind comments don't contribute to the overall discussion, but you should remember that these players are also the ones voting for the respective piece of content. You could also suggest re-educating them, which is exactly what Jagex attempts with each developer blog, and still people won’t get the memo. And when it comes to the players themselves, can the playerbase really be relied on to re-educate itself? Overall, the Second Great irony really hurts the development process and is practically an unavoidable issue. What’s the alternative? To remove the developer-player interface that leads to valuable reiterations, or does you simply have to get the skill perfect in the first developer blog? It’s not an optimal idea, but it could help: have a small team of “delegates” – larger names that players can trust, or player influencers – come in to review a new, unannounced skill idea under NDA. If they like it, chances are that other players will too. If they don’t, reiterate or toss out the skill before it’s public. That way, you’ve had a board of experienced players who are willing to share their opinions to the public helping to determine the meat and potatoes of the skill before it is introduced to the casual eye. Now, a more polished and well-accepted product can be presented on the first run of selling a skill to the public, resulting in less reiterations being required, and demanding less effort from the average player to be fully informed over the skill’s final design.
5-2 - Presentation and Beta Testing
So you’ve got a great idea, but how are you going to sell it to the public? Looking at how the OSRS Team has handled it throughout the years, there’s a very obvious learning curve occurring. Artisan had almost nothing but text blogs being thrown to the players, Sailing started introducing some concept art and even a trailer with terrible audio recording, and Warding had concept art, in game models, gifs, and a much fancier trailer with in-game animations. A picture or video is worth a thousand words, and often the only words that players will take out of a developer blog. You might say that presentation is everything, and that would be more true in OSRS than most games. Most activities in OSRS are extremely basic, involve minimal thought, and are incredibly grindy. Take Fishing: you click every 20 seconds on a fishing spot that is randomly placed along a section of water, get rid of your fish, then keep clicking those fishing spots. Boiling it down further, you click several arbitrary parts of your computer screen every 20 seconds. It’s hardly considered engaging, so why do some people enjoy it? Simply put: presentation. You’re given a peaceful riverside environment to chill in, you’re collecting a bunch of pixels shaped like fish, and a number tracking your xp keeps ticking up and telling you that it matters. Now imagine coming to the players with a radical new skill idea: Mining. You describe that Mining is where you gather ores that will feed into Smithing and help create gear for players to use. The audience ponders momentarily, but they’re not quite sure it feels right and ask for a demonstration. You show them some gameplay, but your development resources were thin and instead of rocks, you put trees as placeholders. Instead of ores in your inventory, you put logs as placeholders. Instead of a pickaxe, your character is swinging a woodcutting axe as a placeholder. Sure, the mechanics might act like mining instead of woodcutting, but how well is the skill going to sell if you haven’t presented it correctly or respected it contextually? Again, presentation is everything. Players need to be able to see the task they are to perform, see the tools they’ll use, and see the expected outcomes; otherwise, whatever you’re trying to sell will feel bland and unoriginal. And this leads to the next level of skill presentation that has yet to be employed: Beta Worlds. Part of getting the feel of an activity is not just watching, it but acting it out as well - you’ll never understand the thrill of skydiving unless you’ve actually been skydiving. Beta Worlds are that chance for players to act out a concept without risking the real game’s health. A successful Beta can inspire confidence in players that the skill has a solid Core and interesting Expansions, while a failed Beta will make them glad that they got to try it and be fully informed before putting the skill to a poll (although that might be a little too optimistic for rage culture). Unfortunately, Betas are not without major disadvantages, the most prominent of which we shall investigate next.
5-3 - Development Effort
If you thought that the previous section on Skill Design Philosophy was lengthy and exhausting, imagine having to know all that information and then put it into practice.Mentally designing a skill in your head can be fun, but putting all that down on paper and making it actually work together, feel fully fleshed out, and following all the modern standards that players expect is extremely heavy work, especially when it’s not guaranteed to pay off in the polls like Quest or Slayer content. That’s not even taking into account the potentially immense cost of developing a new skill should it pass a poll. Whenever people complain that Jagex is wasting their resources trying to make that specific skill work, Jagex has been very explicit about the costs to pull together a design blog being pretty minimal. Looking at the previous blogs, Jagex is probably telling the truth. It’s all just a bunch of words, a couple art sketches, and maybe a basic in-game model or gif. Not to downplay the time it takes to write well, design good models, or generate concept art, but it’s nothing like the scale of resources that some players make it out to be. Of course, if a Beta was attempted as suggested last section, this conversation would take a completely new turn, and the level of risk to invested resources would exponentially increase. But this conversation calls to mind an important question: how much effort and resources do skills require to feel complete? Once upon a time, you could release a skill which was more or less unfinished. Take Slayer: it was released in 2005 with a pretty barebones structure. The fundamentals were all there, but the endgame was essentially a couple cool best-in-slot weapons and that was it. Since then, OSRS has updated the skill to include a huge Reward Shop system, feature 50% more monsters to slay, and to become an extremely competitive money-maker. Skills naturally undergo development over time, but it so often comes up during the designing of an OSRS skill that it "doesn't have enough to justify its existence." This was touched on deeply in Section 3-13 – Skill Bloat, but deserves reiterating here. While people recognize that skills continually evolve, the modern standard expects a new skill, upon release, to be fully preassembled before purchase. Whereas once you could get away with releasing just a skill's Core and working on Expansions down the line, that is no longer the case. But perhaps a skill might stand a better chance now than it did last year, given that the OSRS Team has doubled in number since that time. However, judging from the skill design phases that have previously been attempted (as we’ve yet to see a skill development phase), the heaviest cost has been paid in developer mentality and motivational loss. When a developer is passionate about an idea, they spend their every waking hour pouring their mind into how that idea is going to function,especially while they’re not at work. And then they’re obligated to take player feedback and adapt their ideas, sometimes starting from scratch, particularly over something as controversial as a skill. Even if they have tough enough skin to take the heavy criticism that comes with skill design, having to write and rewrite repeatedly over the same idea to make it “perfect” is mentally exhausting. Eventually, their motivation drains as their labour bears little fruit with the audience, and they simply want to push it to the poll and be done with it. Even once all their cards are down, there’s still no guarantee that their efforts will be rewarded, even less so when it comes to skills. With such a high mental cost with a low rate of success, you have to ask, “Was it worth it?” And that’s why new skill proposals are far and few between. A new skill used to be exciting for the development team in the actual days of 2007, as they had the developmental freedom to do whatever they wanted, but in the modern day that is not so much the case.
5-4 - The Problems of Democracy
Ever since the conceptualization of democracy in the real world, people have been very aware of its disadvantages. And while I don’t have the talent, knowledge, or time to discuss every one of these factors, there are a few that are very relevant when it comes to the OSRS Team and the polling process. But first we should recognize the OSRS Team’s relationship with the players. More and more, the Team acts like a government to its citizens, the players, and although this situation was intentionally instated with OSRS’s release, it’s even more prominent now. The Team decides the type of content that gets to go into a poll, and the players get their input over whether that particular piece makes it in. Similarly, players make suggestions to the Team that, in many cases, the Team hadn’t thought of themselves. This synergy is phenomenal and almost unheard of among video games, but the polling system changes the mechanics of this relationship. Polls were introduced to the burned and scarred population of players at OSRS’s release in 2013. Many of these players had just freshly come off RS2 after a series of disastrous updates or had quit long before from other controversies. The Squeal of Fortune, the Evolution of Combat, even the original Wilderness Removal had forced numerous players out and murdered their trust in Jagex. To try and get players to recommit to Runescape, Jagex offered OSRS a polling system by which the players would determine what went into the game, where the players got to hold all the cards. They also asked the players what threshold should be required for polled items to pass, and among the odd 50% or 55% being shouted out, the vast majority of players wanted 70%, 75%, 80%, or even 85%. There was a massive population in favour of a conservative game that would mostly remain untouched, and therefore kept pure from the corruption RS2 had previously endured. Right from the start, players started noticing holes in this system. After all, the OSRS Team was still the sole decider of what would actually be polled in the first place. Long-requested changes took forever to be polled (if ever polled at all) if the OSRS Team didn’t want to deal with that particular problem or didn’t like that idea. Similarly, the Team essentially had desk jobs with a noose kept around their neck – they could perform almost nothing without the players, their slave masters, seeing, criticizing, and tearing out every inch of developmental or visionary freedom they had. Ever hear about the controversy of Erin the duck? Take a look at the wiki or do a search through the subreddit history. It’s pretty fantastic, and a good window into the minds of the early OSRS playerbase. But as the years have gone on, the perspective of the players has shifted. There is now a much healthier and more trusting relationship between them and the Team, much more flexibility in what the players allow the Team to handle, and a much greater tolerance and even love of change. But the challenges of democracy haven’t just fallen away. Everyone having the right to vote is a fundamental tenet of the democratic system, but unfortunately that also means that everyone has the right to vote. For OSRS, that means that every member, whether it’s their first day in game, their ten thousandth hour played, those who have no idea about what the poll’s about, those who haven’t read a single quest (the worst group), those who RWT and bot, those who scam and lure, and every professional armchair developer like myself get to vote. In short, no one will ever be perfectly informed on every aspect of the game, or at least know when to skip when they should. Similarly, people will almost never vote in favour of making their game harder, even at the cost of game integrity, or at least not enough people would vote in such a fashion to reach a 75% majority. These issues are well recognized. The adoption of the controversial “integrity updates” was Jagex’s solution to these problems. In this way, Jagex has become even more like a government to the players. The average citizen of a democratic country cannot and will not make major decisions that favour everyone around themselves if it comes at a personal cost. Rather, that’s one of the major roles of a government: to make decisions for changes for the common good that an individual can’t or won’t make on their own. No one’s going to willingly hand over cash to help repave a road on the opposite side of the city – that’s why taxes are a necessary evil. It’s easy to see that the players don’t always know what’s best for their game and sometimes need to rely on that parent to decide for them, even if it results in some personal loss. But players still generally like the polls, and Jagex still appears to respect them for the most part. Being the government of the game, Jagex could very well choose to ignore them, but would risk the loss of their citizens to other lands. And there are some very strong reasons to keep them: the players still like having at least one hand on the wheel when it comes to new content or ideas. Also, it acts as a nice veto card should Jagex try to push RS3’s abusive tactics on OSRS and therefore prevent such potential damage. But now we come to the topic of today: the introduction of a new skill. Essentially, a new skill must pass a poll in order to enter the game. While it’s easy to say, “If a skill idea is good enough, it’ll pass the threshold,” that’s not entirely true. The only skill that could really pass the 75% mark is not necessarily a well-designed skill, but rather a crowd-pleasing skill. While the two aren’t mutually exclusive, the latter is far easier to make than the former. Take Dungeoneering: if you were to poll it today as an exact replica of RS2’s version, it would likely be the highest scoring skill yet, perhaps even passing, despite every criticism that’s been previously emphasized describing why it has no respect for the current definition of “skill.” Furthermore, a crowd-pleasing skill can easily fall prey to deindividualization of vision and result in a bland “studio skill” (in the same vein as a “studio film”), one that feels manufactured by a board of soulless machines rather than a director’s unique creation. This draws straight back to the afore-mentioned issues with democracy: that people A) don’t always understand what they’re voting for or against, and B) people will never vote for something that makes their game tougher or results in no benefit to oneself. Again, these were not issues in the old days of RS2, but are the problems we face with our modern standards and decision making systems. The reality that must be faced is that the polling system is not an engine of creation nor is it a means of constructive feedback – it’s a system of judgement, binary and oversimplified in its methodology. It’s easy to interact with and requires no more than 10 seconds of a player’s time, a mere mindless moment, to decide the fate of an idea made by an individual or team, regardless of their deep or shallow knowledge of game mechanics, strong or weak vision of design philosophy, great or terrible understanding of the game’s history, and their awareness of blindness towards the modern community. It’s a system which disproportionately boils down the quality of discussion that is necessitated by a skill, which gives it the same significance as the question “Should we allow players to recolour the Rocky pet by feeding it berries?” with the only available answers being a dualistic “This idea is perfect and should be implemented exactly as outlined” or “This idea is terrible and should never be spoken of again.” So what do you do? Let Jagex throw in whatever they want? Reduce the threshold, or reduce it just for skills? Make a poll that lists a bunch of skills and forces the players to choose one of them to enter the game? Simply poll the question, “Should we have a new skill?” then let Jagex decide what it is? Put more options on the scale of “yes” to “no” and weigh each appropriately? All these options sound distasteful because there are obvious weaknesses to each. But that is the Third Great Irony we face: an immense desire for a new skill, but no realistic means to ever get one.
6-0 - Conclusion
I can only imagine that if you’ve truly read everything up to this point, it’s taken you through quite the rollercoaster. We’ve walked through the history of OSRS skill attempts, unconstructive arguments, various aspects of modern skill design philosophy, and the OSRS Team and skill design process. When you take it all together, it’s easy to get overwhelmed by all the thought that needs to go into a modern skill and all the issues that might prevent its success. Complexity, naming conventions, categorizations, integration, rewards and motivations, bankstanding and buyables, the difficulties of skill bloat, balancing, and skill endgames, aesthetics, the design process, public presentation, development effort, democracy and polling - these are the challenges of designing and introducing modern skills. To have to cope with it all is draining and maybe even impossible, and therefore it begs the question: is trying to get a new skill even worth it? Maybe. Thanks for reading. Tl;dr: Designing a modern skill requires acknowledging the vast history of Runescape, understanding why players make certain criticisms and what exactly they’re saying in terms of game mechanics, before finally developing solutions. Only then can you subject your ideas to a polling system that is built to oversimplify them.
Animation Timing for sharpening your edits/overall button pressing
Had to make this since I couldn't see the video anymore or had too much on the other post? https://www.reddit.com/FortniteCompetitive/comments/jr7yl6/character_animation_recognition_to_identify_you Somebody showed me this 14 years ago, which was they key to success in a particular game. and almost/ maybe even/ - nobody is currently using this to increase their skill cap in fortnite. Example: Press gun/pickaxe. do it like you are spam editing. do you ever see the gun come out , or appear that it might come out? it should NOT. it should look like your pickaxe does a swipe . same thing with confirm edit on release, which is tricky to get perfect timing because of how it functions. the trick is to getting the confirm edit on release to go alongside the same timing as edit/select. instead of right after 100% I can guarantee that any pro even the best out there, can utilize this method to raising their skill cap. 100% guarantee with enough practice - the difference will prove itself to be incredible. would you be interested in looking at something if I told you your character animations and which ones occur, speaks volumes about how you press buttons efficiently? This Video Shows when using a pickaxe how to to identify and speed up your ability to press the buttons more effectively/correctly. You may need to re-watch to notice. First notice the pencil - the motion/direction it travels on the first swing is a jabbing/straight motion. the second is a curve upwards motion. there are 6 edits, 4 done correctly and 2 done too slow/bad timing/lost my rhythm. Notice that 3 of the 4 done correctly are consecutively, which is important to note. Had all 6 edits been the same exact upwards curve, this would be about perfect in the overall manner. This animation is similar to having your blueprint out and doing spam edits that way. The reason why it is popular to use builds out is because of the muscle memory for having your buttons pressed ''perfectly together'' which can be discouraging for many people to practice on. Spam edits are a way to practice this precision, consistency, timing, speed, how hard to press the button, how far down the button goes. Your fingers have to learn to work at the same pace so that you can speed up overall, which can be hard to do. Here is the tricky part that doesn't quite make sense though: Notice how many times that the bar changes from 1,298 to 1,277 but both keep the 100,000 right. I find that of little important about the 100,000. However I do want to point out how the 3 edits I did correctly - were in order back-to-back. the numbers change every other time during this clip. 1298 to 1277 to 1298 to 1277 to 1298 to 1277 to 1298. This is because of how input scanning intervals function. So it was 1298 to begin with, which can not be counted out of the 6 edits - this part is from the previous edit that was cut out, its irrelevant to a point. Out of 6 edits, you saw the number change 6 times but in a straight binary form. its the same as 101010 , which is how binary works for sending data. Your computer functions from this binary data transmission and sends it in a certain order. When it scans for that stuff, it has to figure out how to organize the order in which it is sent. When you manipulate your button pressing, you begin to correct yourself to match up to how a computer sends data, so that you yourself will begin to give the hardware inputs at a more computer-like skill level. Video 5 OPTIONAL: I would like to mention 1 method of training this outside of fortnite, which will require you to remap your left click to a letter on the keyboard. Type SAD , pressing sa together will allow the d to show up sooner, which is better. So now you type SAD by using your mouse button as A. This is so you press S (which is hypothetically your edit button, and A is hypothetically your select/confirm edit on release) Remap A to be your left click and your left click to be A. then practice this in the notepad. It isn't as effective, but is an alternative to doing spam edits. You won't actually be able to tell if you are pressing them right but if you use the speed of when D shows up, that is a good start. -- This next video is almost the perfect animation edit speed for a pyramid. The 3rd edit is the best, and is closer to avoiding the sight of blue/grey tile when editing. This means that the timing, precision, and how those buttons are pressed - were almost flawless and perfect similar to how macros can be. https://reddit.com/link/jsa6v8/video/a7ujxwut7oy51/player Look at the best editors in the world and find similar animations, if you don't see consistency then you know that they have room to improve their ability to press buttons.
How to Safely Flash Official One UI 2.5 (DBT) on SM-N960F
Hey Guys! https://youtu.be/hzHzSk5KPUE I will be showing you how to flash Official One UI 2.5 Germany DBT ROM on your device without deleting any data (if OEM is enabled otherwise you will have to backup). 3 Main Requirements before you start.
Make sure your chipset is Exynos (you can find out using CPU-Z app).
Model number must be either SM-N960F or SM-N960F/DS.
Binary Version should be either 6 or lower. (see the video below for better understanding)
1.1. On Phone > Goto Settings > Scroll Down > About Device > Software Information > Tap Build number 7 times > Go back to settings main page > scroll down > you will find new option called Developer options. Click on it > You will than find OEM unlocking (if OEM unlocking is not visible or is already enabled than you can skip to section *1.2*. If OEM unlocking is disabled, make sure you backup your device using SmartSwitch. 1.2. Download the necessary files from the video description. (Odin, Stock ROM (DBT), SmartSwitch, Samsung USB Drivers). 1.3. If you have SmartSwitch and USB Drivers already skip to *1.4*, disconnect cable to your device if connected than once you have installed both software/drivers make sure you reboot your PC. Launch SmartSwitch and simply press backup. 1.5. Once you are done now run Odin as administrator, click BL, AP, CP and CSC one by one and click on file that matches the starting letters located in your stock rom folder. NOTE: You will have 2 CSC files, Home_CSC is to keep data and not to format, CSC is to format the device. Pick the one you desire. 1.6. On your device, power it off, than plug in a usb cable to your PC, hold volume down + bixby button and power button simultaneously once it vibrates leave the power button but keep holding volume down + bixby button until you see warning screen, press volume up once to enter download mode. 1.7. Now you should see a blue highlighted ID:COM on Odin, you can simply press Start and it will do its job. 1.8. After it shows the PASS sign, you may close the odin and enjoy the One UI 2.5! :) If you get to know that your region released the One UI 2.5 you can follow the same step and flash your region rom and you will get the OTA updates with no issues. I also made a video since there isn't a video that explains step by step, I hope you enjoyed and thanks!
AWS, Azure, Google Cloud, Digital Ocean, IBM/RedHat Cloud
and much more! Read release notes for a complete list of improvements: https://www.zabbix.com/rn/rn5.2.0 In order to upgrade you just need to download and install new binaries (server, proxy and Web UI). When you start Zabbix Server it will automatically upgrade your database. Zabbix agents are backward compatible therefore no need to install new agents, you can do it anytime later if needed.
Beginning|Previous Premier Valast felt a tingle. It began at the base of his spine and traveled moved upward, sending warm fuzzy feelings all throughout his body as it made its way to his brain and inserted itself in his conscious thoughts. After all of the misery. After all of the failures. For once, something had gone right. How delightful. How extravagant. How deserved. The Humans had made a mistake. Clearly, they had thought to expand upon their treachery, believing themselves to be invincible. Their monstrosity of a vessel had appeared just as their last one had, within Halcyon's inner perimeter. After their ruse of parlay, their beast had commenced belching out weapons of mass destruction, clearly in an attempt to retrieve the encryption key and the elite assassin-thief they had dispatched under the guise of a Witness. They thought Halcyon weak. Defenseless. Not true! Not true at all! Kinetics. Valast laughed aloud, his rib cage heaving out great guffaws. Accelerated mass! More laughter. The savages thought to bring such inelegance against the might of the Combine? They mistook their prior fortune for competence. Their one-time success for future capability. Alas, poor Humans, the truth of your inadequacies is made manifest! The brief gap in the defenses brought on by the improbable chain of events that had resulted in their arrival had been filled. For all of their destructive potential, their weapons were useless. Valast continued to cackle, his hindclaws scrunching up the soft material of his pillow, as he watched the Humans receive their punishment for their insolence. The Humans had made assumptions. Perhaps assumptions were fine in their backwater corner of the galaxy, but here, among civilization, assumptions could be quite dangerous indeed. It was quite unwise to assume Halcyon would leave the inner perimeter exposed. They must have thought their Evangi co-conspirators would leave the gates open for them, as the traitor Neeria had done when she had given them access to a Combine wormkey in the first place. Sadly for the Humans, their four-armed friends had been exposed for what they were. A great many of the Evangi now lay motionless on the floor of a Halcyon mainway, a fitting end to their perfidy. Halcyon had stood since the beginning, and it would continue to stand long after the Human infestation had been expunged from the Combine Space. Perhaps the Humans should have spent more time pondering the nature of the place before they had meddled with forces they clearly did not understand. Halcyon existed in defiance of the chaotic nature of the neutron star it orbited. Its survival required an solution to the objects such a gravity well attracted. Halcyon had many such solutions, weaved together to maintain a delicate balance. Among them were the inertial dampeners. The screen in Valast's paws bloomed with colors, indicating firings of Halcyon's inertial dampeners. Each blossom of color was an attempt by the Humans to deploy weapons in clear violation War Accords, cementing Humanity's position as a menace to decent civilization. Had Valast not commanded Bo'Bakka'Gah to take the necessary precautions, the devastation would have been significant. Lines of crimson sailed through the blooms of color. Valast's whiskers twitched, his eyes squinting as it tracked one of these lines. The solution was not perfect. The intertial dampeners in close proximity to Halcyon were a final precaution, and their purpose was narrow. They were a fine net, meant to indiscriminately capture any residual high-speed astral particulate that had escaped the outer defenses. Their efficacy diminished at an exponential rate in proportion to the size and mass of the object they acted upon. Thus far, they had been quite successful at preventing the Humans from making use of their weapons, but dampeners had no effect on the Human vessels. Even if the dampeners could be used for such a purpose, their indiscriminate nature would have required the cessation of all space born travel within Halcyon, an unacceptable disruption to the workings of the Combine's capitol. The Humans' small spherical vessels were thus capable of traveling unimpeded throughout Halcyon space, tracing their crimson lines behind them as they did so. Such a thing did not overly worry Valast. They could not fire their weapons, and they were susceptible to electromagnetic disruption, rendering them easy targets for the Peacekeepers. Were Valast not otherwise consumed with the affairs of state, he would perhaps take to the front line and dispatch a few himself. Sadly, his bravery would find no opportunity for direct expression beyond the valor found in the privilege of command competently exercised. The whiskers ceased their twitching and some cheer returned. It would not be long before the meddlesome Human spheres were swatted from the sky and the encryption key recovered. Then they would dispatch the Human warship. Then Humanity. He need only wait. ----------- "Get spread. Get small." Sana called out. Had to buy time. Had to get a handle on the situation. Not her first rodeo, but it was the first time where she had no idea what the hell she was riding. Maybe the aliens were riding her. Maybe it wasn't a rodeo, maybe it was just a slaughter. That was the problem. No one knew anything. The callsigns in her local were dropping like flies. Squaddies getting wiped without so much as a peep. The eggs in Science were saying EMPs, but the balls were supposed to be fixed against that frakkery. Sensors said the balls were still there even after they went dead, so maybe they were right. Couldn't think about that now. Couldn't think about anything but the mission. Captain Sana Bushida had a shit-shuttle to bring to station. She needed to get from A to B. Normally the quickest point-to-point was a line, but the baddies were coming in from all sides. Trying to corral her in. So be it. She could handle a long and squiggly with the juice she had in the four balls attached to the cockpit. Only question was how long they'd be up for. Whatever they were using on the balls wasn't touching her. She was good, but she wasn't that good. Guess they wanted her kicking and screaming. Predators, not scavengers then. Frakk 'em. Right in their stupid alien faces. Sana's brain shunted command signals as fast as her eyes to parse the readouts in her pilot pod. Dodging. Weaving. Diving. Dipping. Half those words didn't even apply to space, but they felt right. Float like a butterfly, run like cheetah on amphetos. She'd sting 'em later. Run run run, fast as you can. You can't catch me, I'm the shit-shuttle can. Swipe. Swipe. Two smaller ships moved in a pincer formation, one cutting off her angle around the larger ship she was skimming around. Sana let out a giggle, as she shoved the shuttle in another direction. "You thought you had me, crapdonkey? You never had me. You're gonna be seeing my ass all day." The giggle somehow transformed into a roar halfway through as a third ship appeared in her view, coming out from its hiding place on the other side of the large ship. "SCREW YOU!" They weren't going to win. Losing wasn't an option. Swipe. Patterns emerged as the ballet played out. Certain ships were the herders. The small annoying frakks that always seemed to be moving around her flanks. Other ships were the receivers. They were the big boys. The ones who just floated there like giant shits in space. Lazy frakks just waiting to be fed some shit-shuttle. Fine then. New info. New tactics. New rule: Get around the herders, never get closer to the receivers. Herders bad. Receivers bad-der-er. As long as she was a step ahead of the herders and two steps away from the receivers, she'd be fine. Problem was they were more agile than her. Problem was there was more of them. Problem was the friendly callsigns on her readouts kept disappearing. Problem was that she was stuck in here instead of out there where she belonged. Ninety-nine problems... Swipe. Swipe. All she needed was a line of sight. A place where she could get a whiff of open space and just gun it. Navigate the maze. Get through it. Light at the end of the tunnel. Glass is half full. Metaphor. Analogy. Idiom. The stream of consciousness flowed out of her, expressing itself in her verbiage and in the desperately navigating shuttle some distance away. Step forward. No steps backward. Okay, maybe one step backward, but it'll be okay. She'd take the step forward soon enough. Just...needed...a...line. Alpha, Beta, Charlie, and Delta was gone. It was just her. Swipe. Swipe. The fate of the world. The shit-shuttle must survive. Swipe. Swipe. The gap opened. She saw it. They didn't. "There it is bitches!" All four balls slammed the thrusters on. It wasn't a direct bee line to the Oppenheimer but it was good enough. She just needed to get out of the hornet's nest and into open space so she could keep pouring on the acceleration. She didn't know how much juice the herders had, but it was all she had going for her at this point. Bitter bile rose up in her throat as the shit-shuttle surged forward, leaving A through D behind. Her squaddies. Her friends. Abandoned. She should be out there. She could be. She just needed to get the mission done. She was so close. She was putting distance between her and the baddies. Just a few more minutes...the link cut off. Her thoughts were shunting into a wall. She swiped, her eyes scanning the readouts. Alcubierre - Shuttle - Cockpit (Ejection)(DISTRESS) no longer appeared. For once, Sana was speechless. --------------------- Kai retched air. There was nothing else to throw up at this point. He'd given everything he had to give, and it was now floating about the cockpit in a viscous cloud. He was fairly certain Neeria was collateral damage in the matter. If she were ever to regain consciousness, she'd find she had been provided with a fresh coat of puke paint. At this point, being blind was something of a boon. Congratulations were owed to the sadist in the pilot's seat though, he hadn't emptied his stomach like this since flight sims. He'd raise his hand in salute if it weren't for the incredible g-force shifts whipping him around like a rag doll as the pilot attempted to avoid whatever was out there. Some of the maneuvers seemed impossibly complex, as if the cockpit was navigating through an impassable morass of enemies. Or perhaps the pilot was just drunk. Either seemed possible. The whipsawing continued. Back. Forth. Round and round. Acceleration never seemed to continue in a single direction for more than a few seconds. They were going in circles. They had to be. Finally, it appeared the pilot had decided on a direction as Kai was slammed back into his chair as the cockpit rocketed forward under sustained acceleration. They must have broken through. Or the pilot had fallen asleep at the controls with the throttle down and they were all doomed. Either way. At this point, Kai was just eager for it to be over. The acceleration continued. He felt like he was being crushed. Like an enormous hand was pressing against him, trying to squeeze all of his organs out through his eyes. Whatever was powering the cockpit now was beyond the parameters of the shuttle's acceleration compensators. His vision began to dim and his joints ached. Pain surged up in his right arm, which was still contorted within the goo. He was fairly certain a bone had just snapped. "Oppenheimer..ETA," Kai managed to gasp out, drawing the breath back into his lungs with some effort. "The shuttle is not currently on course to intercept with the UWDFFOppenheimer." "Joan." Kai wheezed. "Connect. Joan." The acceleration cut off. Kai took a huge gulp of air, the relief immediate. "Comm-link. Fleet Admiral Joan Orléans." No response. Kai tried again. Silence greeted him. Grumbling, he raised his left wrist toward his face. He stuck out his tongue and smeared it along the wrist console's interface. None of the expected beeps and chirps sounded out. It was dead, and, he suspected, so was the cockpit along with whatever had been propelling him. No life support. No way to call out for help. No way to do anything but sit there. For all intents and purposes, they were a hunk of space junk drifting off into the black oblivion. Fair enough. It was a fitting end. Helpless. Hopeless. Kai tried to muster some anger at the situation, if only to distract him from the pain coursing through his body, but found he was up to the task. It was easier to be motivated when there was something to do. Some way he could impact the situation. But there was nothing to do but wait. Maybe he'd live. Probably he'd die. He didn't mind it, that was the same binary he faced every other day. It was a bit more present in his mind than it normally was, but the truth was that he was overdue for demise. He'd given death the slip more times than anyone had a right to. Still. It bothered him. Not the death part. The not doing what he set out to do part. He had run through walls, both literal and figurative, to make it this far. He didn't know what making it back to the Oppenheimer would mean for Humanity, but it had to be better than not making it. The encryption key -- what did it do? What could it do? Would it be doable? Neeria -- could she guide them? Could she help them navigate the treacherous galaxy Humanity was just beginning to play a part in? There were so many questions. The answers could matter. Kai tried to remember how much time they had. Without life support, the supply of oxygen would rapidly begin to deplete. He supposed it didn't matter, since he had no idea whether Neeria breathed, what Neeria she breathed, or the rate she consumed it. His space suit had a few hours of stored supply, but it was designed to work in conjunction with his helmet. Without the wrist console, he'd need to find some way to manually vent it. That was something to do. Small, but perhaps meaningful. Anything to tilt the scales just a little bit more in their direction. Just a few more minutes of air could make a difference. "Seconds matter," Kai wheezed out. His breath was wet and tasted of iron. He'd worry about that later. Air first. It wasn't much of a plan, but it was better than nothing. He hoped Joan's plans were faring better. ------------------- The Admiral's Bridge was awash in a sea of red. Multiple views vied for primacy as the situation continued to deteriorate. So far, the Oppenheimer itself had withstood the sustained EMP assault directed its way, but the same could not be said for the battle balls. Callsigns continued to blink out of existence with every passing second. The Oppenheimer had immediately attempted to provide supporting fire, but its kinetic weaponry was similarly disabled. Whatever the circumstances had been that had allowed the Alcubierre to destroy an alien vessel, they were clearly no longer relevant to the situation at hand. Without kinetics, the vast majority of Humanity's space-born projective power was effectively nullified. Science was looking into explanations and alternatives, but it would take time. The Oppenheimer's EMP arrays had succeeded in firing, but the alien vessels appeared to be impervious to that form of assault. It was unclear whether they possessed EMP hardening around core processes similar to the Oppenheimer or they had other means of deflecting attacks of that nature. In the absence of an alternative, the Oppenheimer was continuously discharging the EMP arrays as they became available, attempting to test for weaknesses. The energy drain from the sustained fire was easily accommodated by the altered physics of local space, but it was unclear whether alien defenses could be worn down by continuous assault. Other oddities were appearing as the situation unfolded. The aliens did not field any tactical fighters that their sensors could identify. There were ships of different sizes, but, thus far, no vessels had moved to directly engage the balls. Kai's cockpit was being corralled by a series of smaller ships working in conjunction with the larger ones, but that was it. Joan considered it, trying to parse out deeper meanings from the absence. Human conflict, both Earthside and in space, had always heavily relied on tactical fighters. They had numerous advantages in terms of firepower projection and significantly increased tactical dynamism in a battle zone. Either the aliens had never considered the approach, or it was considered suboptimal within this environment. Joan squinted, watching as the battle ball's callsigns dropped from the battle status view. She tilted her head. "This environment," she muttered to herself, her eyes drawn to the EMP array firing status. The recharge bars filled and expended. Filled and expended. Each cycle representing an incredibly powerful pulse of electromagnetic energy at the speed of light. Speed of light. Speed. The answer struck her. The ramifications of the answer were displeasing. Plans must be altered. Contingencies reconsidered. The Black Fork was too optimistic. Their position was considerably worse than hoped for, but not entirely beyond anticipated outcomes, which had included their immediate destruction upon arrival in the system. They simply had fewer tools than she desired. Tactical fighters had low utility when combat operated at the speed of light. There was no yield on agility, because no thruster could move faster than light could travel. There was no evading a lightspeed weapon at these distances. Unless a tactical fighter could retain functionality under fire, which the death balls so far could not, they were a pointless extravagance. At best, they could serve as a momentary distraction, particularly when their weapons were inoperable. The unique characteristics of Humanity's birthplace were a hindrance here. Kinetics were the logical path for weaponry to take in an environment where destructive output was a matter of maximizing scarce energy resources. They were also the easiest, most natural extension from their Earthside forebears. Humanity had begun development of lightspeed weapons, the EMP and the Griggs pulse among them, but they placed tremendous strain on ship systems. The Oppenheimer, as a dreadcarrier, was among the few Earth spaceships that contained a full battery of EMP arrays. Due to the extremely demanding specifications, only a Pulser class ship could make use of a Griggs pulse. Had Humanity known what it faced just beyond its doorstep, it would have invested its research and development resources differently. Too late now. The game was not lost yet, they simply must play the hand they were dealt to its greatest effect. A display flashed from green to red and moved toward the center of the wall, increasing in size. Simultaneously, three other displays shifted in color, position and size, in a chain reaction. Joan frowned. Or perhaps the game was lost, and she was only just realizing it. The shuttle cockpit's callsign, along with the four balls that had attached to it, had disappeared. Her hands darted up and began a series of gestures, swiping North to South as she removed some filters from the local space scan and South to North as she applied others. She exhaled. The shuttle had not been destroyed, only incapacitated. It was careening through space away from the cluster of alien ships closest to Halcyon, though a few were in rapid pursuit. The pursuers had acceleration in their favor, but the shuttle's current course brought them toward the Oppenheimer. Joan flicked a few fingers, pulling the course data from the local scan and pushing it into the timer view.
Pursuers to Shuttle: 1m6s
Tactical Fighter to Shuttle: 38s
Oppenheimer to Shuttle: 53s
G4 Fleet First Arrival: 1m42s
Oppenheimer to Exit: 3m0s
Before Joan could issue the order, the nearest balls peeled off and immediately began an intercept course with the shuttle. Joan pulled up the command-chain, it appeared that Captain Bushida had decided to be proactive. Very well, but it would not be enough. The balls were more likely than not to be incapacitated before they could be used in any rescue effort. This required a more substantial intervention if the outcome were to be changed. Joan pushed a new course heading into her comm-link with Ragnar. "Captain, I am moving us off of the Black Fork standing orders." Ragnar glanced at the course heading. "That's even further in." Joan nodded, "It's the only way we'll recover the cockpit. The balls can't get the job done." "There's a risk the Oppenheimer won't get it done either. They're holding back," Ragnar replied, his eyes scanned off screen, bouncing between the various readouts and inbound requests. "Doesn't make any sense they'd only have EMPs. They've got more." "Likely. My current belief is that they will refrain from further escalation until they have either secured the cockpit or believe they can no longer retrieve it. Each moment of escalation from them has been in response to an action on our part directed at the cockpit." Ragnar wiped the back of his sleeve against his brow, mopping up the sweat. "Must be something important." "Must be. The prize is likely worth the pain here, Ragnar. Retrieving the cockpit is the top priority. Preservation of ourselves is an ancillary concern." "G4 is only a few out. We can hold that long," Ragnar said. "Get the job done, Captain," Joan ordered and then cut the comm. Ragnar was a sophisticated battlefield tactician. The overlap between them was significant, and the differences between them were accretive to both. They both knew there was another card to be played, it was just a matter of whether Humanity could adapt to it. Joan opened another comm-link. "Chief Adeyemi." The Chief blinked a few times as the interjection, as if being pulled from a daze. "Idara!" Joan exclaimed. "Where's Science at?" Idara wet her lips, "We've gathered the data and mapped it to a few different explanations...but we need more--" "You don't have it. Best guess, go." "Some sort of inertial dampening field. Effects smaller objects. Weakens as the objects get larger. Only affects objects moving a certain speed. Only affects objects in space. Our kinetics are getting caught. Bigger objects, like the fighters, like the Oppenheimer, are fine. Bullets fired inside of the Oppenheimer are fine. "Any sense on source?" Idara shook her head. "But it doesn't effect the fighters. Doesn't effect energy based weapons." "From what we can see, that's right." Joan's eyes drifted toward the tracker on Kai's cockpit. Hurtling through space. "Idara, when the Alcubierre was heading for Proxima Barrier, your modeling said the ship would survive the impact, correct?" "Yes, Admiral. There isn't an equal an opposite reaction. Actor has primacy in these physics." Joan stared at Idara, lost in thought. The Chief shifted uncomfortably, "Is there something else--" "I have what I need," Joan replied, cutting the comm. She pulled up the status tracker on the balls. Over eight-five percent of launched fighters had already been incapacitated. The Oppenheimer still retained a final wing in its hangers, numbering approximately a hundred and twenty additional balls. Joan watched the timers ticking down. They needed to go on the offensive. To find a way to tilt the situation in their favor. Even if they retrieved the cockpit, it was a long way back to the wormhole, and a long time to survive before G4 appeared. If the aliens had an ace up their sleeve, that would be the time to play it, when they had nothing to lose, and everything to gain. She re-opened the comm with Ragnar. "Captain, I think we can even the odds a bit." "I'm all ears, Admiral." Joan pushed a series of orders to Ragnar. He glanced at them and then glared at her, "You want-- "Yes, Captain, that's what I want." "But they'll be destroyed," Ragnar responded. "Not if they're moving fast enough. Get whoever we can get back into the hangers, launch the rest without the pilots. Target the ships. Target Halcyon." Ragnar stared at her, "Halcyon? That's a civilian--" "Captain, I want those balls dumped and under full steam at the designated targets. That's an order." Ragnar opened his mouth and then shut it. A hand came off screen and formed a salute. The comm was dropped shortly after. Almost immediately, the tactical fighters shifted flight plans and began their retreat toward the Oppenheimer. Simultaneously, the wing residing within the *Oppenheimer'*s hangers shifted from stand-by to active. Soon they would be launched, pushing top acceleration toward Halcyon. No EMP would be able to stop them. If the aliens had another card to play, Joan hoped this would force it out and maybe, just maybe, buy enough time for G4 to make an appearance. She just needed a little time. Just needed to survive long enough for the Pulsers to arrive. Seconds mattered. Next. Be sure to leave a comment or an upvote if you're enjoying Alcubierre. If you want a sense of how much it matters to me,here's a very emo journal entry documenting it. Click this linkor reply withSubscribeMe!to get notified of updates to THE PLATYPUS NEST. I have been conducting a strange experiment on myTwitterwhich people seem to be enjoying. I found an AI bot that randomly posts impactful images every few minutes. I've decided to craft a narrative on top of these random images called "The Human Archives."
One Click Trading: anyoption mit neuem Feature. Mit einem einzigen Klick bis zu 80 Prozent Profit erzielen: Das ist das erklärte Ziel des neuen One Click Trading Features von anyoption. Das zukunftsweisende Tool funktioniert denkbar einfach. Nach der Auswahl des Basiswerts heißt es nur noch, auf steigende oder fallende Kurse zu setzen. Para aqueles que querem duplicar o seu investimento ou tentar a sua mão na negociação de opções binárias, One Click Profits afirma que pode ajudá-lo a atingir seu objetivo. É totalmente automatizado para que você não tem que ser um especialista para o comércio com este sistema. Anthony DeRuiz, o criador de One Click Profits, The promotions offered by the site are highly speculative and their execution can lead to the loss of your entire capital. You just have to invest the amount you can afford to lose. Trading is not suitable for all investors, so Bin Options.com is not responsible for possible losses. OptionsClick - One. Click. Trade. Binary Options Live Trading OptionClick Binary Options. Oil, Silver, Currencies, indices, CFDs, Stocks, Commodities. For those who want to double their investment or try their hand at binary options trading, One Click Profits claims it can help you reach your goal. It is fully automated so you do not have to be an expert to trade with this system. Anthony DeRuiz, the creator of One Click Profits, promises you Trade Binary Options as quick as one click! Access our binary options trading platform and try this great feature, which makes trading a lot easier. You can nwt choose preferred way of trading yourself. One-Click-Trading saves your time and as we all know – time is money! Page 1 of 3 - Manual ONE CLICK Trader for MT4 - posted in Metatrader 4 Indicators (MT4): Hey Traders Have been busy making a Binary Options Manual One Click Trader for MT4.You can use it in combination with your indicators, on any TimeframeHas a 4 level investment input.Check it out. One Click Binary Options ( CL ) is currently trading at $64.75 Steps to set opening item by single click or double clicks on Windows 10: Step 1: Access one click binary options File Explorer Options Tip: File Explorer Options is also referred to Folder Options Step 2: Select a clicking option In the General settings, under Click items as follows, choose Single-click …. One Click Binary Options. At Our Options we guarantee instant execution at the best available price. 7. It is risk-free trading. In this example we’ve clicked “Binary options”, “Indices”, and then “Weekly” under “US 500”. With one click you can change between Binary Options trading and Forex/CFD trading. Binary options are generally various options you can trade one click ... Some devices can be rooted with "one-click" methods. As the name implies, this makes the process very easy. We'll show you the best one-click root methods available today.
Binary Options Trade With 100% Accuracy How to Hack ...
Broker für binäre Optionen haben ihren Sitz außerhalb von Deutschland. Aus diesem Grund sind im Vergleich nur diejenigen Broker gelistet, die eine deutschsprachige Webseite anbieten. The road to success through trading IQ option Best Bot Reviews Iq Option 2020 ,We make videos using this softwhere bot which aims to make it easier for you t... good Your real way to EARN BIG PROFIT - ITS EASY! I EARN 975 in week HERE))) http://goo.gl/AzaS9q /// You will earn more at 1 minutes binary options Strategy Earn... http://eurooptionen.club 1 Klick. 60 Sekunden. 91% Gewinn binäre optionen hütchen strategie tag 1 - mehr informationen zu dieser und weiterer strategien zum ... http://eurooptionen.club 1 Klick. 60 Sekunden. 91% Gewinn binäre optionen 60 sekunden broker - binäre optionen strategie 60 sekunden. binäre optionen 60 seku... With OneClickBinary no need to install a binary options plugin. Just place the expert advisor to your MT4 broker platform and start trading. OneClickBinary can also be used for people trading with ... Contact Telegram ️ https://t.me/Crtrading12. Join Binary,com and Get Profit Every Day ️ https://bit.ly/3gmtkMP ... Published on Jun 1, 2020 Choose this single setting for your order tickets and you can click the buy or sell button to submit an order without the extra step of a confirmation screen. Comments are ...