It's that time of year again, and we've got a new version of macOS on our hands! This year we've finally jumped off the 10.xx naming scheme and now going to 11! And with that, a lot has changed under the hood in macOS. As with previous years, we'll be going over what's changed in macOS and what you should be aware of as a macOS and Hackintosh enthusiast.
Has Nvidia Support finally arrived?
What has changed on the surface
A whole new iOS-like UI
Broken Kexts in Big Sur
What has changed under the hood
New Kernel cache system: KernelCollections!
New Kernel Requirements
Secure Boot Changes
No more symbols required
Broken Kexts in Big Sur
MSI Navi installer Bug Resolved
New AMD OS X Kernel Patches
Other notable Hackintosh issues
Several SMBIOS have been dropped
Extra long install process
X79 and X99 Boot issues
New RTC requirements
Legacy GPU Patches currently unavailable
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
Dortania's Build Repo
True legacy macOS Support!
Intel Wireless: More native than ever!
Clover's revival? A frankenstein of a bootloader
Death of x86 and the future of Hackintoshing
Getting ready for macOS 11, Big Sur
Has Nvidia Support finally arrived?
Sadly every year I have to answer the obligatory question, no there is no new Nvidia support. Currently Nvidia's Kepler line is the only natively supported gen. However macOS 11 makes some interesting changes to the boot process, specifically moving GPU drivers into stage 2 of booting. Why this is relevant is due to Apple's initial reason for killing off Web Drivers: Secure boot. What I mean is that secure boot cannot work with Nvidia's Web Drivers due to how early Nvidia's drivers have to initialize at, and thus Apple refused to sign the binaries. With Big Sur, there could be 3rd party GPUs however the chances are still super slim but slightly higher than with 10.14 and 10.15.
What has changed on the surface
A whole new iOS-like UI
Love it or hate it, we've got a new UI more reminiscent of iOS 14 with hints of skeuomorphism(A somewhat subtle call back to previous mac UIs which have neat details in the icons) You can check out Apple's site to get a better idea:
A feature initially baked into APFS back in 2017 with the release of macOS 10.13, High Sierra, now macOS's main System volume has become both read-only and snapshotted. What this means is:
3rd parties have a much more difficult time modifying the system volume, allowing for greater security
OS updates can now be installed while you're using the OS, similar to how iOS handles updates
Time Machine can now more easily perform backups, without file inconsistencies with HFS Plus while you were using the machines
However there are a few things to note with this new enforcement of snapshotting:
OS snapshots are not calculated as used space, instead being labeled as purgeable space
Disabling macOS snapshots for the root volume with break software updates, and can corrupt data if one is applied
What has changed under the hood
Quite a few things actually! Both in good and bad ways unfortunately.
New Kernel Cache system: KernelCollections!
So for the past 15 years, macOS has been using the Prelinked Kernel as a form of Kernel and Kext caching. And with macOS Big Sur's new Read-only, snapshot based system volume, a new version of caching has be developed: KernelCollections! How this differs to previous OSes:
Kexts can no longer be hot-loaded, instead requiring a reboot to load with kmutil
OS Snapshots are now verified on each boot to ensure no system volume modifications occurred
apfs.kext and AppleImage4.kext verify the integrity of these snapshots
While technically these security features are optional and can be disabled after installation, many features including OS updates will no longer work reliably once disabled. This is due to the heavy reliance of snapshots for OS updates, as mentioned above and so we highly encourage all users to ensure at minimum SecureBootModel is set to Default or higher.
Note: ApECID is not required for functionality, and can be skipped if so desired.
Note 2: OpenCore 0.6.3 or newer is required for Secure Boot in Big Sur.
No more symbols required
This point is the most important part, as this is what we use for kext injection in OpenCore. Currently Apple has left symbols in place seemingly for debugging purposes however this is a bit worrying as Apple could outright remove symbols in later versions of macOS. But for Big Sur's cycle, we'll be good on that end however we'll be keeping an eye on future releases of macOS.
New Kernel Requirements
With this update, the AvoidRuntimeDefrag Booter quirk in OpenCore broke. Because of this, the macOS kernel will fall flat when trying to boot. Reason for this is due to cpu_count_enabled_logical_processors requiring the MADT (APIC) table, and so OpenCore will now ensure this table is made accessible to the kernel. Users will however need a build of OpenCore 0.6.0 with commit bb12f5for newer to resolve this issue. Additionally, both Kernel Allocation requirements and Secure Boot have also broken with Big Sur due to the new caching system discussed above. Thankfully these have also been resolved in OpenCore 0.6.3. To check your OpenCore version, run the following in terminal: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version If you're not up-to-date and running OpenCore 0.6.3+, see here on how to upgrade OpenCore: Updating OpenCore, Kexts and macOS
Broken Kexts in Big Sur
Unfortunately with the aforementioned KernelCollections, some kexts have unfortunately broken or have been hindered in some way. The main kexts that currently have issues are anything relying on Lilu's userspace patching functionality:
Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:
iMac14,3 and older
Note iMac14,4 is still supported
MacPro5,1 and older
MacMini6,x and older
MacBook7,1 and older
MacBookAir5,x and older
MacBookPro10,x and older
If your SMBIOS was supported in Catalina and isn't included above, you're good to go! We also have a more in-depth page here: Choosing the right SMBIOS For those wanting a simple translation for their Ivy and Haswell Machines:
iMac13,1 should transition over to using iMac14,4
iMac13,2 should transition over to using iMac15,1
iMac14,2 and iMac14,3 should transition over to using iMac15,1
Note: AMD CPUs users should transition over to MacPro7,1
iMac14,1 should transition over to iMac14,4
Currently only certain hardware has been officially dropped:
"Official" Consumer Ivy Bridge Support(U, H and S series)
These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
Ivy Bridge iGPUs slated for removal
HD 4000 and HD 2500, however currently these drivers are still present in 11.0.1
Similar to Mojave and Nvidia's Tesla drivers, we expect Apple to forget about them and only remove them in the next major OS update next year
Due to the new snapshot-based OS, installation now takes some extra time with sealing. If you get stuck at Forcing CS_RUNTIME for entitlement, do not shutdown. This will corrupt your install and break the sealing process, so please be patient.
X79 and X99 Boot issues
With Big Sur, IOPCIFamily went through a decent rewriting causing many X79 and X99 boards to fail to boot as well as panic on IOPCIFamily. To resolve this issue, you'll need to disable the unused uncore bridge:
With macOS Big Sur, AppleRTC has become much more picky on making sure your OEM correctly mapped the RTC regions in your ACPI tables. This is mainly relevant on Intel's HEDT series boards, I documented how to patch said RTC regions in OpenCorePkg:
For those having boot issues on X99 and X299, this section is super important; you'll likely get stuck at PCI Configuration Begin. You can also find prebuilts here for those who do not wish to compile the file themselves:
For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others. * A partial fix is to block Big Sur's AppleAHCIPort.kext and inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext * This will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want. However we recommend setting the MinKernel value to 20.0.0 to avoid any potential issues.
Legacy GPU Patches currently unavailable
Due to major changes in many frameworks around GPUs, those using ASentientBot's legacy GPU patches are currently out of luck. We either recommend users with these older GPUs stay on Catalina until further developments arise or buy an officially supported GPU
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
As many of you have probably noticed, a new organization focusing on documenting the hackintoshing process has appeared. Originally under my alias, Khronokernel, I started to transition my guides over to this new family as a way to concentrate the vast amount of information around Hackintoshes to both ease users and give a single trusted source for information. We work quite closely with the community and developers to ensure information's correct, up-to-date and of the best standards. While not perfect in every way, we hope to be the go-to resource for reliable Hackintosh information. And for the times our information is either outdated, missing context or generally needs improving, we have our bug tracker to allow the community to more easily bring attention to issues and speak directly with the authors:
Kexts here are built right after commit, and currently supports most of Acidanthera's kexts and some 3rd party devs as well. If you'd like to add support for more kexts, feel free to PR: Build Repo source
True legacy macOS Support!
As of OpenCore's latest versioning, 0.6.2, you can now boot every version of x86-based builds of OS X/macOS! A huge achievement on @Goldfish64's part, we now support every major version of kernel cache both 32 and 64-bit wise. This means machines like Yonah and newer should work great with OpenCore and you can even relive the old days of OS X like OS X 10.4! And Dortania guides have been updated accordingly to accommodate for builds of those eras, we hope you get as much enjoyment going back as we did working on this project!
Intel Wireless: More native than ever!
Another amazing step forward in the Hackintosh community, near-native Intel Wifi support! Thanks to the endless work on many contributors of the OpenIntelWireless project, we can now use Apple's built-in IO80211 framework to have near identical support to those of Broadcom wireless cards including features like network access in recovery and control center support. For more info on the developments, please see the itlwm project on GitHub: itlwm
Note, native support requires the AirportItlwm.kext and SecureBootModel enabled on OpenCore. Alternatively you can force IO80211Family.kext to ensure AirportItlwm works correctly.
Airdrop support currently is also not implemented, however is actively being worked on.
Clover's revival? A frankestien of a bootloader
As many in the community have seen, a new bootloader popped up back in April of 2019 called OpenCore. This bootloader was made by the same people behind projects such as Lilu, WhateverGreen, AppleALC and many other extremely important utilities for both the Mac and Hackintosh community. OpenCore's design had been properly thought out with security auditing and proper road mapping laid down, it was clear that this was to be the next stage of hackintoshing for the years we have left with x86. And now lets bring this back to the old crowd favorite, Clover. Clover has been having a rough time of recent both with the community and stability wise, with many devs jumping ship to OpenCore and Clover's stability breaking more and more with C++ rewrites, it was clear Clover was on its last legs. Interestingly enough, the community didn't want Clover to die, similarly to how Chameleon lived on through Enoch. And thus, we now have the Clover OpenCore integration project(Now merged into Master with r5123+). The goal is to combine OpenCore into Clover allowing the project to live a bit longer, as Clover's current state can no longer boot macOS Big Sur or older versions of OS X such as 10.6. As of writing, this project seems to be a bit confusing as there seems to be little reason to actually support Clover. Many of Clover's properties have feature-parity in OpenCore and trying to combine both C++ and C ruins many of the features and benefits either languages provide. The main feature OpenCore does not support is macOS-only ACPI injection, however the reasoning is covered here: Does OpenCore always inject SMBIOS and ACPI data into other OSes?
Death of x86 and the future of Hackintoshing
With macOS Big Sur, a big turning point is about to happen with Apple and their Macs. As we know it, Apple will be shifting to in-house designed Apple Silicon Macs(Really just ARM) and thus x86 machines will slowly be phased out of their lineup within 2 years. What does this mean for both x86 based Macs and Hackintoshing in general? Well we can expect about 5 years of proper OS support for the iMac20,x series which released earlier this year with an extra 2 years of security updates. After this, Apple will most likely stop shipping x86 builds of macOS and hackintoshing as we know it will have passed away. For those still in denial and hope something like ARM Hackintoshes will arrive, please consider the following:
We have yet to see a true iPhone "Hackintosh" and thus the likely hood of an ARM Hackintosh is unlikely as well
There have been successful attempts to get the iOS kernel running in virtual machines, however much work is still to be done
Apple's use of "Apple Silicon" hints that ARM is not actually what future Macs will be running, instead we'll see highly customized chips based off ARM
For example, Apple will be heavily relying on hardware features such as WX, kernel memory protection, Pointer Auth, etc for security and thus both macOS and Applications will be dependant on it. This means hackintoshing on bare-metal(without a VM) will become extremely difficult without copious amounts of work
Also keep in mind Apple Silicon will no longer be UEFI-based like Intel Macs currently are, meaning a huge amount of work would also be required on this end as well
So while we may be heart broken the journey is coming to a stop in the somewhat near future, hackintoshing will still be a time piece in Apple's history. So enjoy it now while we still can, and we here at Dortania will still continue supporting the community with our guides till the very end!
Getting ready for macOS 11, Big Sur
This will be your short run down if you skipped the above:
Lilu's userspace patcher is broken
Due to this many kexts will break:
WhateverGreen's DRM and -cdfon patches
Many Ivy Bridge and Haswell SMBIOS were dropped
See above for what SMBIOS to choose
Ivy Bridge iGPUs are to be dropped
Currently in 11.0.1, these drivers are still present
For the last 2, see here on how to update: Updating OpenCore, Kexts and macOS In regards to downloading Big Sur, currently gibMacOS in macOS or Apple's own software updater are the most reliable methods for grabbing the installer. Windows and Linux support is still unknown so please stand by as we continue to look into this situation, macrecovery.py may be more reliable if you require the recovery package. And as with every year, the first few weeks to months of a new OS release are painful in the community. We highly advise users to stay away from Big Sur for first time installers. The reason is that we cannot determine whether issues are Apple related or with your specific machine, so it's best to install and debug a machine on a known working OS before testing out the new and shiny. For more in-depth troubleshooting with Big Sur, see here: OpenCore and macOS 11: Big Sur
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.
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
There's been some discussion on Mikasa in the sub lately, both positive and negative, and it's led me to think a bit more about her character. In particular, I've been thinking about her character flaw, what it is exactly, and whether or not she's developed past it – and if she has, what that means for her in the final arc. Isayama once said that Mikasa is a character who 'expresses herself via actions and facial expressions quite a lot'. I sometimes feel that that's why a lot of her personal story gets overlooked – because she's not loud about it, and nor is anyone else. She's one of the most reticent characters in the manga and, more importantly, deliberately written that way. It's intentional on Isayama's part for Mikasa to mostly 'express herself via actions and facial expressions', and so, as difficult as it might be to follow, that's mostly how her personal journey is told. Because she doesn't say much, talks a lot with her fists, and is the team's natural and aggressive protector, it's easy to assume that there's nothing more happening there. Isayama clearly doesn't mean for readers to overlook her, but some inevitably do because she's not as obvious and outspoken as other characters. She's not like Eren, whose dissatisfaction with the world drives him to continuously push back, or like Armin, whose self-doubt and fear of responsibility constantly battle with his natural intelligence and sense of duty. She doesn't outwardly appear to suffer from the neuroses that afflict a lot of the others in the main cast. As a result, her development as a character isn't easy to track. Where does it start? Where does it end? What even is it? It's fair to ask, in Mikasa's case, whether she even has a character arc to begin with. What changes about her? Does she actually react in any way to her experiences and evolve as a result of them, or does she remain the same from beginning to end?
Fans' opinions on Mikasa's character are often based on her feelings for Eren and the actions she undertakes to protect him. It irks some readers that Eren is Mikasa's priority, and that her life seems to revolve around him. Because they consider this her character flaw, they expect that her character development is going to rectify this flaw; that she'll move away from Eren, whether physically, emotionally, or mentally, and find something else to live for. In a 2016 interview, Isayama said: 'Mikasa's growth probably involves separation from Eren'. People generally stop at that and go from there – they either believe that Mikasa can't grow as a person unless Eren stops being important to her, or that a Mikasa who isn't separated from Eren (emotionally, mentally, or physically) is inherently a flawed character. Isayama's explanation of the 'separation' he means is never usually discussed, even though he actually does go on to clarify it: 'Mikasa's growth probably involves separation from Eren. By separation, I mean she might be able to return to that ordinary girl that she used to be in childhood'. If the all-important 'separation' for her growth is about Mikasa returning to the 'ordinary girl' she used to be, it's worth asking what isn't ordinary about the girl Mikasa became, and when that change happened. And once that 'non-ordinary' quality about Mikasa becomes apparent, it can be identified as Mikasa's flaw; the deficiency in her character that we can expect her to overcome. Mikasa loving someone or wanting to protect them isn't in itself a flaw. It's a fairly ordinary, reasonable thing, and it's something plenty of other characters already display in the story: Franz wants to protect Hanna; Ymir, Historia; Eren, Mikasa; Kenny, Uri; Levi, Erwin, and so on ad infinitum. There's a reason that Mikasa's love for and general protectiveness towards Eren never changes. It's because it's not something she was ever meant to 'grow past' or 'get over'. It was never her flaw. Her flaw is fear. Mikasa's overprotectiveness of Eren is what isn't 'ordinary', because it's connected to her deep, abiding fear of loss. Her desire to constantly stay by him is pitiful because, above all else, it represents her fear and her mistrust of the world. And it's why her 'separation' from him is about more than just 'Mikasa finds something else to do apart from care about Eren'; it's a return to her being 'the ordinary girl of her childhood': a normal girl who isn't constantly fixated on how the people she loves can die at any moment: https://preview.redd.it/gpraaqxt1sq51.jpg?width=750&format=pjpg&auto=webp&s=dbcb1a366ae0b26f287143aa4d7e916d1c7b3c49
When Levi says they'll focus on one objective and that won't include outright killing Annie, Mikasa's one objection is: 'How many of our comrades has she murdered?' Mikasa has no problem being straightforward with Levi. If her first and only consideration was Eren, she'd voice it. She'd even get away with it, because they all need Eren at this point. But instead, she reveals that she has a separate, personal desire: avenging their dead. Mikasa wants to kill Annie for her own reasons.
Levi states that their goal is to retrieve Eren. He gives himself the main role of 'slash[ing] away' at the titan, meaning that he will be the one to actually save Eren, who is in the titan's mouth. And he gives Mikasa the job of distracting Annie. Mikasa accepts asecondary role in a planthat isspecificallyto rescue Eren.
And when she does break from the plan, it's not so she can go and get Eren herself. Mikasa risks the objective of the mission – and Levi, and Eren – by going in for the kill. Mikasa risks the plan to save Eren by acting on her own desire to kill Annie.
Two important shifts take place here for Mikasa. One, she entrusts Eren to someone else, as demonstrated by her action of allowing Levi to take the lead. Two, her focus stops being, even for a short while, Eren – as confirmed by her facial expression when Levi challenges her on it, because she doesn't seem to immediately realise she's even capable of that: The objective was: Forget killing the Titan. Rescue Eren. And Mikasa, for no matter how short a time, lost sight of that. The fearful, overprotective aspect of Mikasa's relationship with Eren is beginning to change, because her relationship with the rest of her world is beginning to change. With his rescue of Eren in the forest, Levi proves to Mikasa that other people are just as capable of protecting Eren as she is. And if she happens to take her mind off Eren for a bit, it doesn't mean he'll die. This is where the 'separation' begins. Mikasa starts to accept distance between herself and Eren; the distance of being able to trust others with him, of not needing to constantly be with him and personally oversee his safety. And it leads to this watershed moment in the Uprising arc: Mikasa. Whilst Eren has been kidnapped. And all they know is that he's inside a coffin with some random undertaker at some random inn. Maybe. In Chapter 4, Mikasa couldn't handle Eren being in a different part of the city from her during a mission because of how afraid she was that he'd die without her. In Chapter 30, she let Levi take the lead on getting Eren back, and was shocked when she realised that, even for an instant, she'd prioritised something else over him. In Chapter 57, Eren's been kidnapped, no one's been certain for two days about where he is or what's happening to him, and Mikasa is, well, as pictured above. The debilitating fear that used to tie Mikasa to Eren is gone for good. She's finally let Eren go, and discovered that it doesn't mean she'll lose him.
Post-timeskip Mikasa is in a good place, and long past the fear with which she faced the world as a young girl. She's with Eren, working with the Volunteers, and she and Armin are excited about the possibilities of the widening world. Then Eren effectively betrays the SC for reasons they can't fully understand, and, once again, Mikasa's world begins to change in alarming, unpredictable ways. https://preview.redd.it/y4f97ksi2sq51.png?width=346&format=png&auto=webp&s=a17a0410c8f25e97ee450b57d9636e5fc147b874 For the first time in a long time, she loses someone she loves. Eren's in jail and Mikasa remains by Sasha's grave, pondering the old words that bind her and Eren together: 'If we don't win, we die. If we win, we live. If we don't fight, we can't win.' Ironically enough, Sasha is the only character in the entire manga to have said those words apart from Eren and Mikasa themselves. And she's now dead as a result of Eren's fight. So what exactly is Eren fighting for, and what does winning that fight entail? This is the first time in the manga that Mikasa begins to doubt Eren, and the first time their bond has ever really been threatened. And not by the world, titans, or murderous kidnappers, but by Eren himself. The idea that there is beauty where cruelty also exists has informed Mikasa's perspective on the world since Eren wrapped his scarf around her. He showed her that it is possible for the two things to co-exist; for there to be human cruelty as well as human kindness, cold as well as warmth, life as well as death. But Eren is now showcasing the exact cruelty that Mikasa used him as a beacon against. What he's done is undoing what she believes in; it's not just that it's shaken her view of Eren – it threatens to undo Mikasa's whole world-view. In that same 2016 interview, Isayama spoke of Eren and Mikasa's eventual separation being ideological: 'If I were to draw the separation of Eren and Mikasa . . . Mikasa would have to endure the strain of being stuck between Eren and Armin. Even though she can sympathise with Armin, who considers things from a ''globalism'' perspective, it’s possible that she can't just let the more self-focused Eren go'. This ideological separation begins the moment Eren defects from the SC. It's from this point onwards that EMA's paths truly begin to diverge, and Mikasa in particular is presented with a choice that she's never had to face before. Of the two people she loves most in the world, does she choose the 'self-focused' Eren or the 'globalist' Armin? The choice she makes will most likely conclude Mikasa's character arc once and for all, and it's a choice that's been building since before the time-skip, represented by her interactions with two characters in particular: 1. Mikasa and Floch At the award ceremony in Chapter 90, Floch points out something interesting about Mikasa in what is otherwise an easily overlooked moment in the manga. Although multiple people were present on the rooftop during Serumbowl, he is the only one to explicitly draw attention to the fact that Mikasalet go. She resigned herself to losing Armin because Hanji convinced her that Erwin was more important to humanity and Mikasa's grief at losing him was something that would pass. https://preview.redd.it/oqjfh2gk2sq51.png?width=584&format=png&auto=webp&s=f13d8f9a80608e4ac8a85c30d3ddc79b751ad1dd Floch sees this as maturity, but the realisation that she was willing to let Armin go for the sake of humanity is something that Mikasa is shocked by. It makes her falter, and let go of Eren. Mikasa has always defined herself as Armin and Eren's protector; she's presented in the story as such, and she styles herself as such. She's the one who keeps Eren and Armin safe. But Floch's words make her realise that, on the rooftop, she was able to step away from that role – because her world has expanded beyond Armin and Eren. It has expanded to include Hanji and Levi and the other Scouts – and humanity. Mikasa is capable of making choices that hurt her deeply for the sake of a greater cause. 2. Louise and Mikasa Louise meets Mikasa on three occasions. The first time, Louise tells Mikasa she likes her because Mikasa saved her, and gave her something to strive for: 'You can't save anyone without power. It's okay for us to fight against unjust violence. That's what I learned' (109). In the same way Eren 'gave' Mikasa a motto to live by, Mikasa gave one to Louise. The second time, Louise tells Mikasa that she's happy to be by her side again, fighting for the same goal. Mikasa is ambivalent towards her. And she leaves her scarf behind, choosing to go and fight the titans without it. In between the second and third meetings, Mikasa talks to Armin. She asks him if he's really going to tell Connie to give up on his mother and let her remain a titan; Armin says yes, he is. When Mikasa asks what should be done about Eren, Armin replies that there's nothing to be done; he's a lost cause. After Armin leaves, Mikasa notices that the scarf is missing, and goes to retrieve it. The third and last time they meet, Louise is dying. She tells Mikasa that Eren wanted her to throw the scarf away, but she thought that she could take it to be close to Mikasa. Though she appears to sympathise with Louise's plight, Mikasa demands the scarf back from her. She walks away from Louise even as Louise tells her that she had no regrets, because she chased after Mikasa, devoting her heart. Each meeting between Louise and Mikasa mirrors, in an abbreviated way, the different stages Eren and Mikasa's relationship has gone through. 1: Louise's initial love and gratitude, and her taking Mikasa as an inspiration; 2: their fighting side by side as equals; and, finally, 3: their literal separation as Mikasa chooses to walk away. Louise reminds Mikasa of what Eren means to her. Mikasa never seeks to stop Louise from talking about her feelings; instead, she listens. She might not reciprocate, but she does understand. And her understanding Louise's love reminds her of her own. She walks away, but she takes the scarf with her. Despite what Armin said, and what Louise told her about Eren and the scarf, Mikasa chooses to keep a hold of it in the way she keeps a hold of the hope that Eren can still be brought back. Mikasa is capable of holding on to the person she loves even when he's gone too far. Mikasa Chooses . . . Mikasa Despite the apparently binary choice, Mikasa doesn't have to choose to side with Eren (allow the Rumbling to go ahead) or with Armin (kill Eren to stop him). She said it herself: there's a third option. Her way. Eren's wandered so far down his path that he's lost sight of Mikasa and of Armin; of what connects him to the world. Mikasa chooses, not to support him or to believe that he's a lost cause, but to remind him that walking away from his humanity doesn't mean that he can't turn around and walk back. Kruger said 'Anyone can become a god or a devil. All it takes is for someone to claim it for it to be true' (88). But if there's someone to challenge that belief, then the possibility remains of breaking the facade and setting the story straight – thereby freeing that person from the role they've either taken on out of necessity, or been assigned. It's something we've already seen happen. All it takes is for one person to question it, and the goddess falls apart to reveal an empty, unloved young girl, or the devil's mask cracks open to show the boy still grieving for the world he's lost. Ymir knows that Historia's faking it; Mikasa knows that Eren is kind. Each of them challenges the story that their loved one is telling in order to keep going: Historia to survive, Eren to achieve his dream. It took Mikasa years to truly overcome the cruelty she had seen as a child. Despite everything, she did, in the end, go back to being that 'ordinary girl'. She came to acknowledge that cruelty exists, as does death – but life must nevertheless be lived, people loved, experiences had, and faith kept. Seeing the beauty in a world that is inherently cruel is, and always has been, Mikasa's greatest strength. It's something she is capable of offering Eren, who no longer seems to believe in that duality, or in his own humanity. She can show him what he showed her; that the world isn't black or white, cruel or beautiful, dark or light. It's both. And it's possible to live with that.
Mikasa is no longer fighting to protect Eren from the world; she's fighting to protect the world from Eren. She's the person best suited to do that not only because she's his family, but because Eren's despair and anger at the world is what she might have ended up with herself. If any character was dealt a crueller hand by the world than Eren, or could have become as bitter about the world as him, it was Mikasa. But he stopped that from happening because his kindness showed her that the world, as bad as it was, had good in it. Little by little, Eren's abandoned that view of the world himself. He no longer sees both its beauty and its cruelty, but has confined himself to seeing - and acting on - only one. When they fought Annie in Stohess, Mikasa had to remind Eren that the world was cruel, because Eren had lost sight of that truth. Now, Eren's lost sight of another, equally valid truth; that the world, as cruel as it is, is also beautiful. That he, as inhuman as he thinks he is, is also kind. If Mikasa manages to 'bring Eren back', she'll have come full circle. She started off as a little girl who was seeking something, anything, to hold on to. She needed a saviour, and she got one in the form of Eren. In this scenario, she'll end as a saviour herself, someone who is now able to pass on the light that she once received. Her fear of the world and of losing her loved ones subsided; she managed to find the warmth she needed to carry on. She doesn't need Eren's scarf anymore – but he might need hers.
My perspective on Mikasa is that she's not a very obvious character when it comes to development, and so she sometimes appears static. And because so much of her drive is Eren, a lot of fans look to her relationship with Eren to change for proof that she's somehow developed. But Mikasa's obstacle, her personal flaw, isn't Eren himself, and never has been. Her flaw has always been her deep and debilitating fear about losing the people she loves – Eren and Armin – and her inability to really trust or love anyone apart from them. Mikasa's separation from Eren = her beginning to trust the rest of the world not to stab him in the chest, almost behead him, or eat him alive whilst she's not there. It's good for her because it means she stops being so terrified that she'll lose Eren, not because it means she'll stop loving him or wanting him to be safe. And she reached that point of separation a long time ago in the manga. It was fully realised the moment she decided to trust Levi during the Uprising arc, despite the fact that Eren was literally gone from her side and she had no way of knowing whether he was dead or alive. The final confrontation is where Eren and Mikasa's ideological separation, the one discussed by Isayama in the interview, will/won't occur. It – and its finer details – can unfold in a number of ways, and each one could mean something different for Mikasa's character. But her choosing to face Eren in this way is a natural culmination of her development until now. I've no concrete theories on what will actually happen once the Alliance reaches Eren, but I'm fairly certain that Mikasa is central to the resolution of this arc. And what with the way she's been written by Isayama so far, that's no bad thing. So, to finally end this ramble, I hope that this post at least offers people a different perspective on Mikasa's character and how it's changed over the course of the story. I look forward to reading any other observations/thoughts on Mikasa's development that people might have. Many thanks for giving mine a read!
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.
I am not a top-100 player, as given the inevitable RNG of effects, matchups and draws in card games, and the lack of rewards for ranking up in LoR, I simply don't see the point in painstakingly grinding up to such a level. The highest I've climbed is low Diamond, but considering the above knowledge, I believe that at a certain skill level (perhaps at around Platinum), it's more about how much time one can put in than how skilled they are. HOWEVER, considering all this, I have the absolute conviction that this deck is a top-100 worthy deck.
This is the only deck that I've played since Day 1 of Call of the Mountain, with various modifications, and I believe that it is a completely undiscovered meta unicorn. I've never faced a similar deck on ladder, and my deckbuilding experiments with any other archtypes have left me completely unsatisfied with the lack of interaction and agency, as well as the sheer counterability of the vast majority of tools currently out there. A lot of people are frustrated with the current meta - a lot of points of which are covered by BruisedByGod in his recent video critique. To summarize his main points:
Most answers are completely outclassed by threats
Sheer lack of healing options locks out deckbuilding choices
Most top-tier strategies prey on lack of interactivity (Pirate Burn, Lee Sin OTK, Star Spring)
This is a Control deck which, while originally devised to prey on the inevitably popular Aurelion Sol and Troll Chant and abuse the broken, flexible toolbox of Invoke on Day 1, also manages to both answer all 3 of these problems efficiently.
Lunari Duskbringer x 3
Spacey Sketcher x 3
Lunari Shadestalker x1
Pale Cascade x 3
Unspeakable Horror x 2
Vile Feast x 3
Simply the best available early-game that an Invoke Targon deck could hope to muster - Diana functioning as both early game and late-game removal (we have just enough Nightfall Synergy) for practically no investment, Pale Cascade being legitimately one of the most broken cards currently in the game, and the ping cards also serving a modicum of uses at all stages of a match. Spacey Sketcher has been severely underrated so far - providing critical tools for certain matchups and/or providing early game minions without needing to actually run them (a fundamental weakness of faster decks top-decking late). Its 'discard-replace' synergy with our late-game, as well as Duskpetal Dust and meta-call flex cards is just icing on the cake. Finally, note how every early game card I've chosen scales well and still plays a role as the game goes later; as removal, Elusive blocking, tool-building, Burst-speed Nightfall, pings and cantrip Combat Tricks. This is an often overlooked but fundamental difference between Control early-drops, and aggro early-drops (such as Precious Pet). ~
Sunburst x 3
Vengeance x 3
These two cards, combined with any generated Obliterates, form the only proper removal this deck has - and were the catalyst for me creating this deck in the first place. All three of these removal types leave almost NO room for the opponent to interact with them, and I believe that is the sole condition for a high-cost removal spell to be playable in the current game state. NOTE: Ruination is easily and always played around at a high-level of play - and leaves the opponent with ALL of the agency/choice to play around it/bait it exactly how they wish, instead of you (whose only options are to play the card too early and get out-tempo'd afterward, use more than 3 mana elsewhere to catch-up at which point it becomes unplayable, or lose the game to a sudden-attack completely at your opponent's discretion) - the ultimate NO-NO for this deck: I never even considered putting it in. ~
Meta Call Flex Spots
Divergent Paths x 2
At times I feel as if this card could be cut to 1 copy, but right now 2 feels great against the current meta, and drawing into at least one is almost necessary in order to compete with Star Spring (Obliterate is conditional and too great a tempo loss early on). In other metas previously, I've experimented with 1 copy of Passage Unearned, as well as 2 extra copies of Lunari Shadestalker. ~
Literally Everything Else One Could Ever Hope to Need
Lunari Priestess x 2
Solari Priestess x 3
Mountain Scryer x 3
Moondreamer x 3
Starshaping x 3
I still believe that Invoke is one of the most broken mechanics currently in the game. This is one of the heaviest late-game decks I can possibly imaginable, yet the only cards above 5-mana we run are removal, and our mid-game minions and healing straight up provide whatever early OR late-game tools we might possibly need in any matchup - it's simply overly flexible (flexilibity in card games being a MUCH bigger deal than most people give it credit for) and not enough of a tempo/stat sacrifice IMO. I think that Invoke as a mechanic is even stronger when ran in bulk, and especially in a Control deck - as the game goes on slowly you generate a toolbox that can handle just about any dynamic situation that meta decks can throw your way. The spell-mana nerf to Living Legends has balanced it out quite a bit, however the same-nerf to Cosmic Inspiration still hasn't convinced me that it isn't in the top 5 least healthy effects that a game based on carefully stat-balanced of minion trading could ever have (hit me up with your Cosmic Inspiration hate!) - a large proportion our games are won by this disgusting effect. Solari Priestess and Starshaping need no introduction as some of the most popular, utilitarian Invoke cards, however Mountain Scryer and Moondreamer (not so much Lunari Priestess) really put in the work, and I've never seen anyone else play these cards. The former provides crazy mana-advantage as the game goes on given our huge focus on Celestials (it's a shame we can't afford to push its Invoke chances even higher), and the latter has juuussst the right stat distribution at 3/5 to blockade most midgame tempo plays out opponent might go for. NOTE: Aurelion Sol is straight up unnecessary to compete late-game, is always burdensome and clunky draw, ruins our surprise factor (though that doesn't exist anymore with this post being made), and we often outvalue decks running him anyway (don't forget that the original premise of this deck was 'How can I best remove Aurelion?'). ~
Matchups/Strategy (Order Based on Mobalytics Tier List)
Lee Sin (60/40)
A somewhat favored matchup - although more recent lists that have cut Bastion in favor of Nopify may be a bit more in their favor (a proper Ping Counter). Hard mulligan for Spacey Sketcher, Sunburst and our pings. Generating Silence (Equinox) for Mentor of the Stones/Zenith Blade is our main early game goal. Our Mid-to-Late game goal is removing all 3 Lee Sin's at the expense of practically everything else (the rest of their deck is pretty much completely irrelevant, but rushing them down is also pretty much impossible) - after which our win is basically guaranteed.
This matchup is sadly the most binary thing: Sunburst/Vengeance/Ping's VS Lee Sin/Spell Denial/Zenith Blade
The rest of both decks are basically irrelevant other than to slow down the level up/speed up the level up/Draw into above cards
Draw Draw Draw + Always save enough mana to Removal Spell + Ping if the opponent has 4 mana up late game
I believe that we are very, very heavily favored if played properly (although it's a VERY nuanced matchup to play right), and most of our losses come from bricking our early-game draws and/or not drawing/generating a single Starshaping/Golden Sister as their burn damage inevitably builds up. Hard mulligan for all 1/2 cost cards (only keep 1 Pale Cascade with a 1/2 cost minion).
NEVER, EVER play early minions proactively (e.g. NO turn 1 Lunari Duskbringer unless they play something) - only ever match however many minions the opponent has AND trade right away to minimise Make it Rain/TF value (For instance, if you proactively play a minion with nothing to trade it into, and then find yourself needing to play, say, Diana/Solari Priestess later - the opponent is basically guaranteed free additional AOE value: make EVERY chump blocker count)
ALWAYS open attack into Powder Keg's (usually with our single developed minion)
Take ANY trade you can get (even if somewhat unfavorable) to clear both sides of the board going into turn 8 - one of the ways we can lose is if Riptide Rex clears our heavy board and we only have time to develop one chump blocker before the onslaught - especially because Riptide is MUCH stronger against minions than the nexus > Late game, try to keep both sides of the board as empty as possible
If you find yourself with priority against their activated Plunder past turn 8, play small minions to bait out Rex without having to pass the turn OR play larger minions, especially with uneven health like Moondreamer to protect the rest of your board from potential cannons
ALWAYS try to find a NON-Rex'able position late game to develop Golden Sister, and save Pale Cascade if possible to protect her from Noxian Fervor and recover 6 previous health
ALWAYS have enough mana to remove Leviathan if the opponent has more than 8 mana on any given turn (prioritise Leviathan over Swain himself)
Sacrifice minions to TF attacks and remove Zap Sprayfin ASAP to minimise chip damage (which really builds up)
Be careful and make sure you always have a way to prevent Swain connecting with the Nexus (even if they develop him this turn and open attack the next); Pale Cascade is a good tool here
Pirate Aggro (55/45)
We are much more prone to bricking on draws here than Swain/TF, as we need quite a specific hand to deal with their onslaught - This is probably our most draw-dependent, low-agency matchup by far - as face-deck matchups tend to be. In addition - Captain Farron is much more effective against our removal strategy than the likes of Leviathan. Nonetheless, from my experience I think that we're still every-slightly-so favored in this matchup - often winning by the skin of our teeth. Starshaping/Golden Sister are mandatory late-game, and not bricking by not drawing/generating either is also basically a loss. Hard mulligan for all 1/2 drops, and keep a single Sunburst for Gangplank if your hand is already looking great.
There's nothing much to say here given the nature of their deck - pray your draws are good and take the obvious trades
A very unfavored and binary matchup (see below as to why) that has luckily become rarer recently. Mulligan for Removal/Invoke cards.
Save Starshaping for when you can actually make use of the heal (don't just play it on turn 3 because they're 'starting off slowly' - it's very important to maximise your leeway to survive Atrocity later on)
Try to remove Trundle on curve with Sunburst/Vengeance
Generate/Stockpile removal throughout the midgame
Sadly, none of these choices really matter in the end and the match comes down to luck - if Warmother's pulls a Level 1 Tryndamere on their attacking turn, the obvious open attack followed by a loss is all but guaranteed (Vengeance doesn't stop Atrocity in this case - leading to too great a health/tempo loss, and my previous Passage Unearned tech to deal with specifically this scenario simply wasn't worth the dead card in other matchups). We can also lose to a big levelled Trundle, or simply not generating/drawing into enough removal. Sadly these cases happen more often than not. Warmother's generated too much tempo if left unchecked by hard removal for even a single turn so there is little leeway for bad luck.
If Warmothers' timing and Invoke/draws are on our side, the matchup becomes pretty simple - Smartly use about a removal spell on their big guys for about 8 turns, play around Ruination and Atrocity, then cruise to victory.
This deck was basically created on Day 1 specifically to destroy Trundle/Asol. Sadly though, even at 75/25 the matchup is worse than it should be due to the nature of Invoke RNG - if one player draws into Cosmic Inspiration and the other didn't the match is over, full stop + the occasional shenanigans involving The Great Beyond uninteractibly going face and non-stop Living Legends value. Mulligan for Sunburst, Vengeance and pings.
Remove Trundle ASAP with Sunburst (Vengeance/Obliterates are best saved for Asol so getting Sunburst value while Trundle is still unleveled and 6 health is a big deal in terms of removal distribution)
Always try to remove Asol on the first turn he's played with Vengeance chaining into a ping to minimise the opponent's chance of getting game-winning Invoke RNG/matching your late-game value with free Celestials
If you still haven't drawn a ping late game, try to fish for Crescent Strike with Spacey Sketcher
Play around 7-mana Asol (Augur of the Old Ones) as much as possible
Pray you draw Cosmic Inspiration and the opponent doesn't
Discard Aggro (80/20)
I don't know why this deck is considered competitive - maybe because our matchup here is basically as favored as TF/Swain except without any gameplay nuance required on our part. Mulligan for 1-2 drops. Keep Solari Priestess/Sunburst if hand is good. Only necessary statistical losses to bad early draws against an aggro archtype.
Make obvious trades. Play around Mystic Shot on Diana. Chump block Draven/Jinx. Remove Draven/Jinx. Profit.
Another draw dependent, but quite favored matchup. Quite difficult to play though - you need to balance maintaining some modicum of tempo whilst also being able to deal with their crucial threats. Mulligan for 1-2 drops ESPECIALLY Pale Cascade/Pings, and Removal.
DON'T play ANY minion with less than 3 attack from turns 1-4 UNLESS you're getting tempo'd into the ground OR you have Pale Cascade (otherwise Fiora gets a free trade and the opponent gets to use their buffs reactively rather than proactively - giving you less leeway to remove her)
Save ping's for Fiora Barrier's, NOT Fleetfeather Tracker UNLESS you're getting tempo'd into the ground
Save a removal spell and mana for turn 3 Fiora, turn 4 Shen, turn 6 Genevieve and turn 9 Brightsteel UNLESS you're getting tempo'd into the ground
Basically the Pirate Aggro matchup but a tad bit slower and with no burn - giving you more leeway to make up for bad draws both early and late.
Make the obvious trades, pray to draw well and don't to let Genevieve get 2 attacks off
Basically the Trundle/Asol matchup except with no 'must remove ASAP' threats giving you more leeway to make up for bad draws. Celestial RNG and especially Cosmic Inspiration still give them a chance to win as usual. ~
Shyvana Dragons (50/50?)
I surprisingly, haven't faced too much of this deck yet personally, but looking at it's cards compared to ours, I think the matchup would be about 50/50 (an otherwise favourable looking matchup affected a bit by their high tempo removal and guaranteed Cosmic Inspiration in the form of Kadregrin). ~
This matchup is dependent on whether we draw removal for Ashe somewhat on curve, how much tempo they manage to build early on and whether we draw good enough to afford to play around Reckoning. Mulligan for Sunburst, Solari Priestess, Pings and Diana (only if you've already drawn support) as our other standard early drops are all pretty ineffective against theirs.
Remove Ashe ASAP
Try to Vengeance Sejuani on the attack if she directly attacks your Frostbitten minion in order to prevent the free value trade and maintain tempo on board.
Play around Reckoning as much as possible, especially if it wouldn't affect their own board too much compared to yours - maximise your 5+ attack minions to theirs if Reckoning begins to look more likely
Try to bait out an invested attack/Frostbite support for Trifarian Gloryseeker before pinging her - especially because Elixir of Iron is a bit rarer nowadays
Probably our most favored meta-deck matchup, and unfortunately rarer recently. Their win conditions - Kalista, Blighted Caretaker tempo, Neverglade Collector and They Who Endure simply don't stand a chance against our toolbox. Most losses come from unanswered Blighted Caretaker tempo. Mulligan for Spacey Sketcher, Sunburst and Pale Cascade.
ALWAYS pick Silence (For They Who Endure) or Stun (For Blighted Caretaker) off Spacey Sketcher
Try to hold a minion to play on turn 3/4 to kill an attacking Kalista with Pale Cascade AND get the Nightfall card draw
Play as reactively as possible with your pings - playing them proactively will almost always be answered by Glimpse Beyond, and when they run out of gas later on they will be forced to play their Glipmse proactively - your chance to strike!
Silence/Sunburst Blighted Caretaker as it comes down
SAVE Vengeance for They Who Endure - going into the late game, stockpile Silence/Sunburst and Vengeance and maintain enough mana (usually open-attacking) if necessary (IF can still afford to play They Who Endure that turn) to use one of the former followed by Vengeance to counter into their Atrocity: with this line of play, it's basically impossible to lose the combo
The biggest downside and sheer impossible matchup of this archtype. Maokai manages to pack even less interactivity/inevitability than we do, and the nature of our deck gives us no chance of out-tempoing Deep early OR late. Auto-concede. ~
A simpler aggro matchup than the others. Mulligan for 1-2 drops - especially Spacey Sketcher and Diana, as well as Sunburst.
ALWAYS pick the Stun spell off Spacey Sketcher, and save it for Diana, or of lesser priority, Nocturne/Ephemerals off Stalking Shadows
Removing Nocturne ASAP with either Sunburst or Vengeance is a HUGE priority
ALWAYS play around Pale Cascade
Play around Atrocity and Doombeast damage later on in the match
Another matchup that I haven't faced too much of just yet. Mulligan hard for Divergent Paths and Solari Priestess - Once we remove their uninteractive element trump-card in the Landmark win-condition, if we can survive their early tempo, the rest of the match should be a cinch given our heal/health-ignoring conditionless removal for their Champions. ~
Thanks for reading up to this point, and pardon my formatting, the ridiculous length and the sheer pomposity of it all. I still think Invoke is flexible to the point of being broken and the only reason the matchup spread is so good. I also think that with the release of this guide - more people will come to recognise this archtype and the element of surprise affecting enemy mulligans against an assumed more aggro, Nightfall-focused Diana archtype will be lost. People will also know to play around less common cards such as Sunburst, and I expect winrates to fall somewhat across the board. To conclude this guide, I'd like to say that this is this is not a healthy deck. At the deepest level, this deck is fundamentally about removing agency from your opponent and giving it to yourself, as well as securing the critical boon of having inevitability over your opponent in a game with the nature of LoR. If all decks were like this, LoR would completely cease to be fun. What else do I think is unhealthy right now? - Simple: anything removing interactivity from your opponent - ESPECIALLY as a win condition; Maokai, Star Spring, Cosmic Inspiration, Lee Sin. The avenues through which these cards can be interacted with are way too limited right now. A lot of the metagame nowadays is about having an uninteractable win condition, or focusing damage to face so fast the opponent has no chance to react - another form of non-interactivity. Here's hoping that the meta in the near future heads back in the direction of the close but fair midrange board battles we all came to love back in vanilla LoR. ~ (slinx4)
After the excellent Wasteland 2, we were excited to get our hands on the new installment, and we can say without fear that it has met expectations. Wasteland 3 is a sign of the love that InXile has for his work and Brian Fargo for the genre that has created a name for him. If you are a lover of the saga or the genre, do not hesitate to enjoy it.
Wasteland 3 doesn’t pull any punches with its subject matter in sexuality, violence, and language. But if you are fine with that, I would highly recommend you give Wasteland 3 a shot, especially if you were (or still are) a Fallout fan.
On Paper Wasteland 3 sounds like the perfect RPG-Dream but the execution leaves much to be desired. Bugs, Glitches and graphics that doesn't really represent a game that releases and the end of this console generation are a bit of a letdown. Everything else from the great story, entertaining NPCs, solid battle system, clever leveldesign over to the love for details is amazing, besides some flaws that should soon be fixed, as inXile and Brian Fargo promise. Everyone that wasn't happy with the latest Fallout Games will surely love Wasteland 3.
Wasteland 3 is a old-school role-playing game, with a compelling story, a combat system that promises but is not groundbreaking and some funny moments and black mood, which always remind us that we are in a post apocalyptic world, but with a smile. Don't forget the powerful character editor, rhythm voices, and the beautiful scenery that puts you in that atmosphere of cold and snowy Colorado.
Wasteland 3 can be a bit of slog if you're gunning for marathon gaming sessions with it at the helm. Combat, whilst exciting initially can fall into the traps of repetition. A little more variety could have negated some of the repeated player actions. That said, the story is compelling and the characters an interesting assortment of misfit survivors, although perhaps fitting post-apocalyptic stereotypes. It's a fun, easy to play game overall though that should well-please fans of the series and keep players entertained for quite some time with its high replay-value. However, aside from some bugs here and there, the impressive amount of voice-work on offer, the character building is the best part of the experience where you can really nurture your ranger squad in this snowy post-apocalyptic world.
At least in my time with it, Wasteland 3 has been a fascinating experience. I’ve come to appreciate its depth of gameplay, character, building, and exploration, even if some of its pieces and parts still feel very foreign to me.
I will be even happier with Wasteland 3 once it’s patched and most of the bugs that bit me end up getting squashed. Even in its current state I’m having a grand ol’ time bringing some justice to the cold depths where no Ranger has dared to before. But for as much of a blast as I’m having out northeast in the cold, I hope I can make it back to sunny Arizona in time to save my fellow lawmen!
Wasteland 3 is a throwback to the old School RPGs of yesteryear, while providing a new combat experience and a bigger world. Players that liked previous Fallout Games, or games like Wasteland 2 or Baldur's Gate will feel right at home with this title, and will have the opportunity to try X-Com like combat. For the amount of content provided, 60 USD is a very good price, and fans of the genre should get more than their money's worth.
Wasteland 3 doesn't bring much new to the table, both as a CRPG and as a piece of post-apocalyptic fiction. But, it's a terrifically executed role-playing game that rewards player investment from beginning to end.
Wasteland 3 is a heady crescendo of post-apocalyptic story-telling. Its combat is compelling and fun while its characters and overall plot are engrossing, even when it goes to some dark places. A must-play for tactical RPG fans.
We’ll update this review if the game is fixed, and the issues outlined are fixed or at least addressed; and then I’ll pick it back up. As it stands now, I’ll be playing something else that isn’t as apt to crash. Buyer beware.
There are a few misgivings related to Wasteland 3's technical aspects, mechanics, and overall challenge. However, its cast of characters (both old and new), the switch to a traditional turn-based combat system, and branching paths filled with decisions and dire consequences make for a superb journey with the Desert Rangers.
With a focus on freedom of choice that is second-to-none, Wasteland 3 has set the benchmark for CRPG narratives, all the while being supported by wonderfully engaging gameplay and roleplaying mechanics.
It took me a while to realize how much these interactions, whether it be the interpersonal conversation or combat encounters themselves, stuck with me. Wasteland 3 has rules, but they only exist for you to bend them. With limitless character creation combinations, branching dialogue choices that affect what quests you do or don’t experience, and multiple endings, Wasteland 3 is an expanse of content and opportunity. The change in locale does wonders, no longer relying on a tired post-apocalyptic biome. Wasteland 3 has a wonderful backdrop in Colorado’s frozen wastes, making it the perfect place to spend a nuclear winter.
Wasteland 3 takes players to a new location and presents them with equally unfamiliar challenges, yet still perfectly demonstrates all of the reasons why this series has had die-hard fans for over three decades, and is absolutely worth playing for anyone looking for their next post-apocalyptic fix.
Wasteland 3 doesn't change its predecessor's successful formula but, outside of certain design limitations, it perfects and modernizes it. It's easily the best game in the franchise, in terms of pure technique, and one that clearly gives you an idea of what inXile is able to achieve.
Wasteland 3 is a good role-playing game, technically passable but enriched by a dense network of intriguing subplots that will push the most dedicated to play it several times. Watch out for the ever-present release bugs, though – best to wait a couple patches if you want to avoid unnecessary hurdles.
Wasteland 3 features everything only the best role-playing games do: an engaging story powered by excellent writing, compelling characters, tons of customization options, and a deep tactical combat system that feels fresh even after dozens of hours. But, most of all, it features a living world that reacts to what the player does, and changes depending on how the player decides to deal with the troubles ahead, providing a role-playing experience of the highest degree, one that very few games can boast of.
Wasteland 3 is a testament to the power of the branching narrative, taking it far beyond binary choices and into a grand canopy of cause and effect. It gives the wintry climbs of Colorado a lifelike quality that must have been painstaking to build. The most impressive RPG in years, Wasteland 3 is a masterpiece.
Wasteland 3 shines with clear dedication to crafting the best game its genre has ever seen. Excellent visuals are matched by top notch voice work and some of the best and most natural writing I have seen in a video game not made by Naughty Dog. The combat is a brutal dance where one wrong move can spell disaster, but victory is an exhilarating rush that never becomes old. Wasteland 3 cements inXile as one of the best in the business in the RPG genre and affirms that Xbox has something truly special on their hands.
[OC] Punt Rank 2020: Week 5 - Brett Kern Appreciation Club, the continued painful existence of Kevin Huber, PUNTERS THROWING TDs and the birth of Air Townsend. All this and the best video highlights of the week...
Welcome back, Punt Fans, to your slightly later than usual but there's no Thursday Night Football so what else are you going to be doing edition of our weekly hunt for the King of Punt – it’s /NFL’s own Punt Rank. If you haven’t been here with me before, the concept is both simple and fantastically over-engineered. Lemme break it down: Each punter’s performance against five vital punting metrics is ranked against every other punter in the league. Those rankings are combined into a weighted average ranking – the 2020 NFL Punt Rank. Punt Heroes rise to the top; Punt Zeros sink to the bottom. Last week’s post and Week 4 standings are available here for the archivists, and all of this week’s stats analysis and highlights and lowlights in video form are just moments away. As always I’m excited to get your perspectives on your team’s punter, and you can point me to things that I may have missed or overlooked, so please hit me with your feedback and questions in the comments!
Brett Kern (TEN, +1 to #3). Eh what do you want to know. If you’re reading this it means you like punting. If you like punting, you know that Brett Kern is a really, really great punter. And, Q.E.D – Brett was demonstrably great against the Bills on (the other) TNF. His three punts this week for the no-longer-significantly-infectious-Titans pinned Josh Allen and his shorts at the 9, 9 and 3 yard lines – covering 86% of Average Available Field which is GOAT tier punting. Here’s the pick of the bunch (his 41 yard precisiobomb corralled at the 3 yard line by Chris Milton) covering 93% of Available Field, and measuring in 7.6 yards better than an average punt from the opposing 44 yard line. Tidy. In addition to his really really really great punting, the Kerninator also wrangled at least two uttely horrible snaps into decent holds for Gostkowski to continue his kicking renaissance tour, which is a majorly underrated part of the punter job description... Logan Cooke (JAX, +12 to #13). SPEAKING OF PUNTER HOLDS AND THE EFFECT IT HAS ON KICKERS. Now I’m not saying that Chef had anything to do with the end of Stephen Hauschka’s NFL career on Sunday (0 for 2 within less than two minutes at the end of the first half, not called upon again, then cut PDQ after the weekend), but then I’m not not saying that either. Luckily for Logan (shoot I think I used that joke last week as well) the punting element of his game was without such ugly question marks. 100% of his three punts ended inside the Houston 20 yard line, covering 73%, 83% and 89%of Available Field, sneaking him up to 13th overall. Now let’s see if he can hold onto it. Geddit? Hold?! Pah.
Bad Week for
Kevin Huber (CIN, -8 to #24). On a game where the Bengals only managed the paltry total of 12 first downs (an average of one, yes ONE first down on their 12 offensive drives), K-Hub’s Bad Day was at least somewhat salvaged by the first half holy trinity of Turnover on Downs, INT and Fumble on consecutive drives (2, 3 and 4 – if you’re counting). Without that magical offensive incompetence, he could have been looking at double figure punts (I see you, Tress Way in Washington). As it was, he escaped with just the seven (!), but he takes a slide in the Punt Rank rankings as two of those (admittedly 57 and 60 yard boots) snuck for touchbacks, taking his season touchback percentage total to 26.1% which is second last in the league, just behind Tommy Townsend (more on him later). None of the magnificent seven made it inside the 20, wiping 13% off his season long percentage. However, in Kev’s defence, the first of his two end-zone-botherers this week was another case of coulda woulda shoulda from his coverage team. Alex Erikson heroically made up all the ground to reach the ball as it took a hop into the end zone, but his flailing scoopitty-scoop only managed to floopitty-floop the ball into the wrong side of the pylon. Bengals bungle. Football is a game of inches, and those couple cost Kev. And, after last week’s feature in Egregious Touchback of the Week where basically exactly the same thing happened, it’s entirely possible that Kevin Huber is stuck in some kind of awful groundhog day based time loop. That would at least explain this instagram account. Ty Long (LAC, -5 to #23). Ty Long was the victim of the binary brain of Saints rookie receivereturnerobot automaton Marquez Callaway this week. In Marquez’s awesome little computer mind, he’s going: IF punt_catch_loc > 15THEN SELECTReturn_Like_CraycrayFROMReturn.Options ELSEFair_Catch_That_MF Unfortunately for Ty, six of his seven punts were outside that 15 yard threshold and the big red light on Robot Marquez's head went off like WOO WOO, and he went HAM on bringing those suckers back. 69 (nice) return yards on the day with a long of 19 wiped almost ten yards off Long's Gross Average for the day and left him at just 53% of Average Available Field covered. The Chargers have now leaked 149 return yards for the season which is second worst in the league (behind those irrepressibly awful Jets) and almost three times the league average of 56 through five weeks. Ty will be hoping that they can turn that around before… long. Sorry.
Punt of the week – Week 5
Corey Bojorquez (BUF) continues his wild oscillation between the sublime and the ridiculous. It’s an odd-week so I guess this week it’s Sublime Corey, whose 71 yard scud missile from his own ten yard line in the second quarter of this week’s edition of Tuesday Night Football Bought To You By COVID-19 was an astonishing 28.3 yards longer than my Expected Net Gain model for an average punt from that spot. Look at this baby fly! Bojorquez booms one.
Punters doin’ shit – Week 5
Hey, it’s Corey Bojorquez again! Guess he can do sublime AND ridiculous in a single week now. It’s Puntception. Corey’s first punt of the day was coming alllll the way back for 6 until he decided to put his face on the line to put an end to Kalif Raymond’s 40 yard return. BLOOF. Look at him putting on his cap all swag afterwards like yeah I blew that dude up… Yeah I think tackling with your head is good form? But that’s not all for Punters Doin’ Shit in Week 5, oh no. We have a bonus double edition! and I include this clip with great enjoyment but also great sadness. Gentlemen and Gentlemen (just being real here), this week Riley Dixon (NYG) threw a Touchdown pass! For Giants fans reading this is when someone on your team throws the ball into the big painted area at the end of the field and a player (also on your team) catches it. I know this sounds strange and unusual, but it can happen. And it did happen for Riley on this awesome fake field goal toss to Evan Engram, brilliantly narrated by the incomparable Tony Romo in the clip below. Seriously, this call is outstanding… Nobody look at me, doo doo do, you cant see me... Jim Nantz, don't talK to.. IM OPEN, THROW IT Unfortunately, the play itself was called back due to a player not lined up on the line of scrimmage and the Giants had to settle for a 50 yard field goal. For Chargers and Jags fans reading, this is when your kicker kicks the ball and it goes between the two big tall standy uppy line things. I know this sounds strange and unusual, but it can happen. No TD for Riley, but we have the memories…
Egregious touchback of the week – Week 5
I might start calling this the Kevin Huber Touchback Memorial Column, after ANOTHER narrow miss by the Bengals coverage left Kev high and dry this week against the Ravens (see Bad Week). Outside of that shambles, there were only 6 touchbacks on the other 102 punts in Week 5, and most of them were fairly ordinary so there isn’t much egregiousity (not a word but I’m going with it) to discuss. Instead today we’re going to take some time to appreciate Tommy Townsend (KC) who has apparently got some kind of nuclear powered leg and is playing a game called “look how far away I can kick a touchback from”. For those who haven’t been paying close attention, here’s how Tommy’s rookie season has gone so far in touchback terms. Week 1 – 44 yards, modest. Week 2 – 55 yards, expressive. Week 3 – only punted once so gave myself a week off from this. Week 4 – fucken LOLs this is, how about a 60 AND a 65! Week 5 –hold my beer… Oh my god Becky, look at this punt. 67 yards! SIXTY SEVEN! And that’s from the line of scrimmage - that sucker went almost EIGHTY YARDS in the AIR. It bounced at the two and I think the returner just never even saw it. He probably thought it went into orbit or something. Absolutely ludicrous distance and hangtime here from Tommy. And, thus, I think we have our new moniker for the lad: Air Townsend. Which is also funny because it sounds like hair and he has got long hair. I’m wasted doing this.
Future of Punt Rank: desperate data plea
So part of my data collection for this analysis used to come from the brilliant Pro Football Reference gameplay finder. Which, as of this week, appears to have been absorbed into Stathead. And they’re now charging $8 a month for access to these individual play description tables, which is a massive punt in the balls. Without this data, I’ve got no way to calculate Average Available Field coverage, no plus/minus performance against the Punt Expected Net Gain, and no data on punts inside the 5 and 10 yard lines – all of which come from that analysis of the individual punt plays. Whilst this data doesn’t feed the actual rankings (which come from free NFL.com data tables), they are all metrics that really help add context to the basic stats, and are things that people reading have commented on in the past and said they found interesting. So, if anyone knows of anywhere else where I can access and download these play descriptions for each individual punt (without manually sifting the ESPN play by play reports!!), then please please let me know in the comments below. Alternatively if the eight people who read this each wanna chip in a buck a month on an ongoing basis so we can pay Stathead then that’d be cool too. A sad day for punt stat fans to be sure. Fucken big corporate… And on that note, all that's left is to say I will see you again next week for a likely more analytically constrained but still enthusiastically trying my bestest edition of Punt Rank. Yours, Eyebrows.
Gentlemen, Ladies and those otherwise addressed - we know you've been waiting for a good thing, and the survey results are finally ready! The answers were collected from you all during August 2020 with 1428 unique replies. That's a participation of 0.5% of all subscribers! That's really not too bad, when you keep in mind how popular these kind of surveys are. But we here at /peloton want to show you that this is all about presenting the information in the subreddit to cater better to our audience! Updated after a few hours to include some more historical data the final edit that for some reason wasn't copied properly
Without further ado, let's get cracking on the response
You and Cycling
1. Where do you live?
Largely the same picture as ever, with the US leading the way, the UK in second and then a sliding scale of Europeans countries. Slovenia continues to pick its way up the pile for obvious reasons! World Map to demonstrate
2. What's your age?
Pretty much the same as last year, with the usual reddit demographics of majority 20 somethings dominating.
3. What's your gender?
More normality here for reddit.
4. How much of the men's season do you watch/follow?
March '18 (%)
August '18 (%)
WT Stage races
WT One day races
Non WT Stage races
Non WT One day races
Literally everything I can consume
Whilst GT following may be down (somehow), all the lower level stuff is up, which makes sense considering how desperate we have been for any racing during the season shutdown.
5. Do you maintain an interest in women's professional road racing?
Do you maintain an interest in women's professional road racing?
Still very much a half/half interest in women's cycling on the subreddit.
6. How much of the women's season do you follow?
The following is true for the half of you that follows womens cycling.
Just the biggest televised events
Most of the live televised/delayed coverage stuff
All televised racing
Down to .Pro & beyond
7. How long have you been watching cycling?
Under a year
25 years +
Simplified the years a little this time, but whilst we have a fair number of newbies, most people have picked the sport up since around 2013/14.
8. Do you have like/dislike feelings about WT teams?
Once more, 14.4% of people really don't have feelings on the subject. Of those that do:
So, the most popular team this year is Jumbo-Visma, followed by Quick-Step & Bora-hansgrohe. Least popular are Ineos & UAE. As per usual, no one cares about NTT & CCC, with nearly 81% of users rating NTT as meh. Pretty damning stuff. Lastly, we have the usual historical comparison of how teams have fared over time, normalised to respondents to that question on the survey. Things to note then, firstly that the Astana redemption arc is over, seeing them back in the negative, maybe Fulgsangs spring issues helped aid that? The petrodollar teams of UAE & Bahrain are stubbornly negative too, with Israel keeping up the Katusha negative streak. Meanwhile, at the top end, EF & Jumbo go from strength to strength, whilst some others like Sunweb are sliding over time - their transfer policies no doubt helping that.
10. Do you ride a bike regularly?
No, I don't
Still a fairly small group of racers out of all of us
11. Out of the sports you practice, is cycling your favourite?
A new addition to the survey prompted by a good point last time, just over half of us rate cycling as the favourite sport we actually do.
12. What other sports do you follow?
Association Football / Soccer
Track & Field
Esports (yes, this includes DotA)
Motorsports (Not including F1)
Football always tops the charts, and Formula 1 continues to rank extremely highly among our userbase. Those who have a little following below 5% include Sailing, Fencing, Surfing, Boxing & Ultra-Running. Other cycling disciplines
13. Out of the sports you follow, is cycling your favourite sport?
Good. Makes sense if you hang out here.
14. How often do you participate in a /Peloton Race Thread whilst watching a race?
I always participate in Race Threads during races
I follow Race Threads during races
I often participate in Race Threads during races
I rarely/never participate in Race Threads during races
Slightly less invested than before, reverting back to an older trade.
15. How do you watch Races?
Free Local TV
Desperately scrabbling for Youtube highlights
Paid Streaming services
Year on year, paid streaming services go up - the increasing availability of live content legally continues to improve, and so do the numbers on the survey.
16. Where else do you follow races live (in addition to watching them)?
We can safely say that most of us were wrong about this one. That's not a lot of confidence in Richie Porte either, the man who was to finish on the third spot of the podium. Alexander Foliforov (0,23%) had just a tiny number of votes less, and that man wasn't even in the race.
24. What for you was the defining cycling moment of the previous decade?
We had a lot of brilliant suggestions, but these were the clear five favourites when we tabulated the results.
2018 Giro - Chris Froome Solo Attack
2016 TDF - Chris Froome Running up Ventoux
2019 TDF - Landslides, First Columbian Winner, Pinot's bitter abandon - This was one race for the ages
2016 Paris-Roubaix - Mostly known for Tom Boonen losing. Also, some guy called Mat won.
2019 AGR - MvdP with his incredible catch-up for the win.
Honorable mentions go to the Giro 2018, which had Tom Dumoulin winning, and of almost identical fascination to many of you - Tom Dumoulin going on someones porta-potty in the middle of the stage. Little bit of recency bias perhaps, but that's better than ignoring that this was for the last decade and firmly insisting Tom Boonens 2005 WC win was the biggest thing. Special shoutout to almost all the Danes present in /peloton who voted for Mads Pedersens WC win last year. It's an understandable reaction.
25. Any suggestions for the Survey?
Could you add a section on rider popularity, same as for the teams?
Ask how people became interested in cycling
Ask how people watch cycling (e.g. TV Channels/Streaming etc.)
If you could be an animal for one day, which one would it be?
Would you wear a facemask while watching a cycling race live?
Which race do you look forward to see the most every year?
Favourite riders of your own country?
How many bikes do you own?
We promise to feature one of these suggestions in the next survey Suggestions
Always have a “no” or “not interested” option
We will try to implement this. But it will also skew results. About the Survey
More questions about womens cycling would be nice.
Less questions about womens cycling
The subscribers are torn on Women's cycling, nearly a 50/50 split there as the survey showed - The moderators at /peloton are firmly in the "more cycling is better" basket, and we will continue to get as good coverage of womens cycling as possible.
Are you trying to give the moderators PTSD? Because this is how you give the moderators PTSD.
26. Any suggestions for the sub?
More stationary fitness bike related content
ALSJFLKAJSLDKJAØLSJKD:M:CSAM)=#/()=#=/")¤=/)! - Your moderator seems to be out of function. Please stand by while we find you a new moderator
The Weekly threads are great for these types of questions, where several people can contribute and build up once it is understood which information is relevant.
Allow limited doping talk in result threads.
Our experience is that "limited" will never be so, if we're going to moderate it fairly. Moderating is not a popularity contest, but believe it or not, we're actually trying to be as fair as possible. and for that, we need rules that are not subjective. Unless you have a stationary exercise bike.
Written original content is always great - recaps, old race reviews or interesting rider bios, etc.
More non-race threads
Try and do some AMAs with pro cyclists, coaches, trainers, etc
All of these are good suggestions, but remember that all of you can also contribute - The mods are sometimes stretched thin, specially in the middle of hectic race schedules. It's easier if one of you has a way to contact a rider or a person of interest and can facilitate the initial communication.
Standardize major event thread titles for better search.
We've worked on this! The Official Standard is now as follows: [Race Thread] 202x Race Name – Stage X (Class)
A wiki that explains how races work. Roles of diff riders/support staff. History of racing.
This sounds as a nice community project for the after-season, and hopefully many of you subscribers can contribute.
Tidy up the sidebar!
Come with suggestions on how to tidy it up!
Don't assume everyone reading is a man, "thanks, bro". But that goes for all of Reddit. I know you can't fix that.
We have chastised all the mods. They are now perfectly trained in gender-neutral pronouns. Be well, fellow being.
Have a buy you a beer link for the mods for all the work you do.
If we can implement this for hard liquor, you know we will.
Remove the spoiler rule during grand tours. It kills the hype.
The spoiler rule is one that is discussed frequently - in general - some users absolutely hate it, but a majority love it. Perhaps we'll include a question in the next survey to see how this divide is exactly.
Lose the spoiler tag when it is for serious things; Lambrecht death, Jakobsen fall.
We actually do - whenever there is a matter of life or death, we think public information is more important than a spoiler rule. But at the same time, we try to collect all the different posts into one main thread, so to keep things focused and letting very speculative posts meet with hard evidence from other sources.
Less downvoting of opinions that differ from the fashionable consensus.
This is a tough ask of the internet. While we can agree that voting should be done accordingly to what insights they bring, not subjective opinions, it is very hard to turn that type of thinking around. We can ask of you, our subscribers, that you please think twice about hitting that downvote button, and only do so because of you think a post is factually incorrect, not because it differs with your own subjective opinion. That's the primary analysis of the survey! Feel free to contribute with how you experience things here!
Classic Binary Options, One Touch, 60 Second Options, Long Term Options, Pairs Options: Number of Assets: 58: Option Types: Currency , Commodities , Indices , Stock: Overall Score: 90/100: Introduction . OptionsArea is a newly established binary broker that is owned by a holding company called Dolce Formula Ltd. Although, their headquarters are based in Mahe, Seychelles, OptionsArea also ... Good And Bad Binary Options Trading Conditions. Binary options trading, like other forms of speculative trade, separates itself from traditional trade and investment in a lot of critical ways. There are the very obvious, superficial characteristics, like binary options trading not needing to already have large amounts of money just to start. Or the fact that traders don’t need to hire—and ... They have a decent asset list, good options, adequate expiry and decent terms but no one feature that makes this a must-use broker. On the bright side it is a good choice for us U.S. based traders who are having our options, no pun intended, dwindle. If you are not familiar with Tech Financials it is one of the leading providers of binary options platform solutions and white label brokerages. Binary options trading may have gotten a bad rap because of its all-or-nothing premise, but the high payouts keep traders coming back for more. This is why binary options markets remain strong in various regions around the world, particularly in Asia. To avoid fraud in binary options trading, choose a trustworthy broker. These brokers can help minimize your losses and provide a measure of ... Binary options are embarrassingly bad. They are SO bad, that they have to be marketed. Not only that, they are so bad, that they use deceptive marketing practices and are made out to sound like a get rich quick scheme. Structurally, you are gambli... Compare Binary options Brokers. There are a lot of binary options brokers. Most of them offer a free demo so you can take a look at their trading platform before depositing real money. You should always avoid unregulated brokers. Also take into consideration the return percentage, the minimum required deposit and the trading platform which ... Good signals but bad also - posted in 60 Second Strategies: Hi guys I have this indicator. it is attached. it works well, gives good signals. signal is on previous bar when new bar open and you enter trade for 1min. does not repaint. but there are some bad signals and when you restart the platform the bad signals disappear. is there a way to filter out the bad signals or modify code somehow to ... * Binary options are nothing but scamming brokerages, which creates affiliations programs and those people in-turn churn and gain people like you and me to bet on their platforms to lose in the end. * Stay away from BO as this is nothing but bett... optionsXO is a binary broker based in London, UK and founded in 2012. OptionsXO is regulated by CySEC under the license number 206/13. There are several types of trading assets including 16 currencies, 12 indices and 3 commodities. optionsXO offers a variety of speed options which range from 15 seconds to 24 hours. Is a Binary Options Bonus Right For You? “Invest now and get $500 free!” “You qualify for a $1,000 bonus! Deposit now and claim your free money today!” “$10,000 welcome bonus available for traders!” “200% bonus just for depositing!” These are the kinds of ads that draw traders into the world of binary options. The promise of easy money is hard to resist, particularly in an ...
This channel discusses binary options trading which is very popular in many countries among its binary options trading in usa, delivery trading binary option... Are binary options a good idea? If you're thinking about trading binary options, watch this video first. Check out our FREE training for traders https://bi... Binary options trading good or bad Discover is binary options trading good or bad, and earn upto 80% return on investment per month without doing anything. Fund the broker account and give access ... This video is unavailable. Watch Queue Queue. Watch Queue Queue See This Website: https://bit.ly/2D8NbBe - Fascination About Is BossCapital A Good Or Bad Binary Options Broker? Discovering the finest binary options tradin... http://www.TradingSignalsThatWork.com BINARY OPTIONS GOOD OR BAD BINARY OPTIONS GOOD OR BAD. If you search the web looking for how to make money with binary ...