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
A non-D&D game you *need* to play: Ironsworn (FREE)
Why you need to play Ironsworn:
Ironsworn is a Viking themed low fantasy game it's completely FREE and you can play it in a group, with or without a GM or completely solo.
It has a highly customizable, modular setting.
It has a streamlined and elegant system that focuses on the narrative whilst still being deep and robust.
There are no classes, characters are created freely by mixing and matching modular thematic abilities.
The combat system is fast, dramatic and full of tension.
The game requires absolutely 0 prep, the rules and random tables how you make a satisfying game with no prior prep
It can be played completely alone or in a group with or without a GM. The games rules and random tables ensure that even without a GM it still goes in interesting directions you could never anticipate.
And it's COMPLETELY FREE.
I give the game a glowing recommendation and if that's enough for you here is the link. For those of you who need more details, I go into them below...
SETTING Ironsworn is set in the Ironlands, a gritty low fantasy wild frontier. The Ironlanders settled here a few generations ago after a cataclysm drove them out of the Old World. The Ironlander live in small settlements and villages or nomad and are constantly threatened by the things that lurk in the dark. You are an Ironsworn, one of the few people brave enough to venture wild for glory and adventure. The setting is fully customizable. There is a setting book that comes with pages on major setting elements like "communities" "religion" or "magic". These pages have 3 different options for what to do with the set element as well as a plot hook to go with it. You can choose one of these options or create your own using the setting elements as guidance. Creating a setting is quick, easy and engaging. PLAYER CHARACTERS You are an Ironsworn, a badass adventurer that travels the land fulfilling oaths called "Iron Vows." The game is human-centric, it assumes you are human but you can choose to flavour your character as a different race. Character creation is freeform, characters are made out of stats and assets. Stats: There are 5 stats: Iron (stcon), Edge (dex), Wits (wis/int), Shadow (stealth/deception), Heart (cha). Assets: PC's start with 3 assets. Assets are cards with 3 abilities tied to a specific theme, you start with one of these abilities marked and can spend XP to gain more of an asset's abilities or get new entirely (there are 70+ assets to choose from). These abilities generally aren't just number bonuses they are meant to give your more gameplay options or make you feel more like your character. A few example assets: Alchemist, Infiltrator, Archer, Swordmaster, Cave lion companion, Raven Companion, Divination ritual, Awakening ritual. CORE MECHANICS The game revolves around the action roll when you do something risky you roll 1d6 +stat vs 2d10s.There are 3 different results to a roll, unlike D&D binary system. If the d6 is higher than both d10s then you succeed, if it's only higher than 1d10 you succeed but at a cost or consequence, if it isn't higher than either then you fail and something bad happens. If you roll the same number on both d10's then its a critical success or failure. Only the PC's roll, how NPC's react depends on the result of your roll. The game gives you specific guidance on what to do through a system called moves. Moves are a chunk of rules that tell you how to resolve a specific part of the game, like fighting or compelling people to do what you want. Moves give you specific guidance on how to resolve the situation in an interesting way based on the result of your roll and often give you choices on how you would like to move the story forward. SOLO / GMLESS PLAY EXPLAINED You can play Ironsworn with a GM, with multiple players and no GM or completely alone. Playing without a GM just works, everything about the game's rules facilitate GMless play. The moves substitute for a GM by pushing the story in interesting and unexpected directions, and the game features many random tables to roll on if you get stuck. You won't even feel the GM's absence. COMBAT Combat is fast fluid and dramatic and it places a heavy emphasis on tension. It is nothing like D&D wargame-like combat system. There no, turn order or action economy or complex rules. Combat flows like a movie scene, you describe your action, you trigger a move and roll dice then depending on your role the enemies react appropriately. The combat system is designed to create quick, adrenaline and dynamic fights. A fight that could take an hour or more in D&D could take 10-15 minutes in Ironsworn and be just as compelling if not more. Ironworn's combat is nothing like D&D's slow tactical combat, but It is still filled with depth and meaningful decisions. You also don't have to have to worry about NPC stat blocks, an entire encounter can be designed on the fly. SEEING THE GAME IN ACTION Ironsworn is likely, unlike any game you've played before, so you may need to see it in action before you fully understand it. If you want an in-depth reading of the rules I recommend Adam Koebel's "Ironsworn First Look." If you want to an actual play of the game I recommend "Ask the Oracle," it's an actual play podcast made by the game's designer Shawn Tomkin and I also recommend the youtube series "Me Myself and Die" season 2 by Trevor Devall, (you don't need to watch season 1 first.) Thanks for reading those post I really hope you give my favourite game a try :)
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.
No gods, no kings, only NOPE - or divining the future with options flows. [Part 3: Hedge Winding, Unwinding, and the NOPE]
Hello friends! We're on the last post of this series ("A Gentle Introduction to NOPE"), where we get to use all the Big Boy Concepts (TM) we've discussed in the prior posts and put them all together. Some words before we begin:
This post will be massively theoretical, in the sense that my own speculation and inferences will be largely peppered throughout the post. Are those speculations right? I think so, or I wouldn't be posting it, but they could also be incorrect.
I will briefly touch on using the NOPE this slide, but I will make a secondary post with much more interesting data and trends I've observed. This is primarily for explaining what NOPE is and why it potentially works, and what it potentially measures.
My advice before reading this is to glance at my prior posts, and either read those fully or at least make sure you understand the tl;drs: https://www.reddit.com/thecorporation/collection/27dc72ad-4e78-44cd-a788-811cd666e32a Depending on popular demand, I will also make a last-last post called FAQ, where I'll tabulate interesting questions you guys ask me in the comments! --- So a brief recap before we begin. Market Maker ("Mr. MM"): An individual or firm who makes money off the exchange fees and bid-ask spread for an asset, while usually trying to stay neutral about the direction the asset moves. Delta-gamma hedging: The process Mr. MM uses to stay neutral when selling you shitty OTM options, by buying/selling shares (usually) of the underlying as the price moves. Law of Surprise [Lily-ism]: Effectively, the expected profit of an options trade is zero for both the seller and the buyer. Random Walk: A special case of a deeper probability probability called a martingale, which basically models stocks or similar phenomena randomly moving every step they take (for stocks, roughly every millisecond). This is one of the most popular views of how stock prices move, especially on short timescales. Future Expected Payoff Function [Lily-ism]: This is some hidden function that every market participant has about an asset, which more or less models all the possible future probabilities/values of the assets to arrive at a "fair market price". This is a more generalized case of a pricing model like Black-Scholes, or DCF. Counter-party: The opposite side of your trade (if you sell an option, they buy it; if you buy an option, they sell it). Price decoherence ]Lily-ism]: A more generalized notion of IV Crush, price decoherence happens when instead of the FEPF changing gradually over time (price formation), the FEPF rapidly changes, due usually to new information being added to the system (e.g. Vermin Supreme winning the 2020 election). --- One of the most popular gambling events for option traders to play is earnings announcements, and I do owe the concept of NOPE to hypothesizing specifically about the behavior of stock prices at earnings. Much like a black hole in quantum mechanics, most conventional theories about how price should work rapidly break down briefly before, during, and after ER, and generally experienced traders tend to shy away from playing earnings, given their similar unpredictability. Before we start: what is NOPE? NOPE is a funny backronym from Net Options Pricing Effect, which in its most basic sense, measures the impact option delta has on the underlying price, as compared to share price. When I first started investigating NOPE, I called it OPE (options pricing effect), but NOPE sounds funnier. The formula for it is dead simple, but I also have no idea how to do LaTeX on reddit, so this is the best I have: https://preview.redd.it/ais37icfkwt51.png?width=826&format=png&auto=webp&s=3feb6960f15a336fa678e945d93b399a8e59bb49 Since I've already encountered this, put delta in this case is the absolute value (50 delta) to represent a put. If you represent put delta as a negative (the conventional way), do not subtract it; add it. To keep this simple for the non-mathematically minded: the NOPE today is equal to the weighted sum (weighted by volume) of the delta of every call minus the delta of every put for all options chains extending from today to infinity. Finally, we then divide that number by the # of shares traded today in the market session (ignoring pre-market and post-market, since options cannot trade during those times). Effectively, NOPE is a rough and dirty way to approximate the impact of delta-gamma hedging as a function of share volume, with us hand-waving the following factors:
To keep calculations simple, we assume that all counter-parties are hedged. This is obviously not true, especially for idiots who believe theta ganging is safe, but holds largely true especially for highly liquid tickers, or tickers will designated market makers (e.g. any ticker in the NASDAQ, for instance).
We assume that all hedging takes place via shares. For SPY and other products tracking the S&P, for instance, market makers can actually hedge via futures or other options. This has the benefit for large positions of not moving the underlying price, but still makes up a fairly small amount of hedges compared to shares.
Winding and Unwinding
I briefly touched on this in a past post, but two properties of NOPE seem to apply well to EER-like behavior (aka any binary catalyst event):
NOPE measures sentiment - In general, the options market is seen as better informed than share traders (e.g. insiders trade via options, because of leverage + easier to mask positions). Therefore, a heavy call/put skew is usually seen as a bullish sign, while the reverse is also true.
NOPE measures system stability
I'm not going to one-sentence explain #2, because why say in one sentence what I can write 1000 words on. In short, NOPE intends to measure sensitivity of the system (the ticker) to disruption. This makes sense, when you view it in the context of delta-gamma hedging. When we assume all counter-parties are hedged, this means an absolutely massive amount of shares get sold/purchased when the underlying price moves. This is because of the following: a) Assume I, Mr. MM sell 1000 call options for NKLA 25C 10/23 and 300 put options for NKLA 15p 10/23. I'm just going to make up deltas because it's too much effort to calculate them - 30 delta call, 20 delta put. This implies Mr. MM needs the following to delta hedge: (1000 call options * 30 shares to buy for each) [to balance out writing calls) - (300 put options * 20 shares to sell for each) = 24,000net shares Mr. MM needs to acquire to balance out his deltas/be fully neutral. b) This works well when NKLA is at $20. But what about when it hits $19 (because it only can go down, just like their trucks). Thanks to gamma, now we have to recompute the deltas, because they've changed for both the calls (they went down) and for the puts (they went up). Let's say to keep it simple that now my calls are 20 delta, and my puts are 30 delta. From the 24,000 net shares, Mr. MM has to now have: (1000 call options * 20 shares to have for each) - (300 put options * 30 shares to sell for each) = 11,000 shares. Therefore, with a $1 shift in price, now to hedge and be indifferent to direction, Mr. MM has to go from 24,000 shares to 11,000 shares, meaning he has to sell 13,000 shares ASAP, or take on increased risk. Now, you might be saying, "13,000 shares seems small. How would this disrupt the system?" (This process, by the way, is called hedge unwinding) It won't, in this example. But across thousands of MMs and millions of contracts, this can - especially in highly optioned tickers - make up a substantial fraction of the net flow of shares per day. And as we know from our desk example, the buying or selling of shares directly changes the price of the stock itself. This, by the way, is why the NOPE formula takes the shape it does. Some astute readers might notice it looks similar to GEX, which is not a coincidence. GEX however replaces daily volume with open interest, and measures gamma over delta, which I did not find good statistical evidence to support, especially for earnings. So, with our example above, why does NOPE measure system stability? We can assume for argument's sake that if someone buys a share of NKLA, they're fine with moderate price swings (+- $20 since it's NKLA, obviously), and in it for the long/medium haul. And in most cases this is fine - we can own stock and not worry about minor swings in price. But market makers can't* (they can, but it exposes them to risk), because of how delta works. In fact, for most institutional market makers, they have clearly defined delta limits by end of day, and even small price changes require them to rebalance their hedges. This over the whole market adds up to a lot shares moving, just to balance out your stupid Robinhood YOLOs. While there are some tricks (dark pools, block trades) to not impact the price of the underlying, the reality is that the more options contracts there are on a ticker, the more outsized influence it will have on the ticker's price. This can technically be exactly balanced, if option put delta is equal to option call delta, but never actually ends up being the case. And unlike shares traded, the shares representing the options are more unstable, meaning they will be sold/bought in response to small price shifts. And will end up magnifying those price shifts, accordingly.
NOPE and Earnings
So we have a new shiny indicator, NOPE. What does it actually mean and do? There's much literature going back to the 1980s that options markets do have some level of predictiveness towards earnings, which makes sense intuitively. Unlike shares markets, where you can continue to hold your share even if it dips 5%, in options you get access to expanded opportunity to make riches... and losses. An options trader betting on earnings is making a risky and therefore informed bet that he or she knows the outcome, versus a share trader who might be comfortable bagholding in the worst case scenario. As I've mentioned largely in comments on my prior posts, earnings is a special case because, unlike popular misconceptions, stocks do not go up and down solely due to analyst expectations being meet, beat, or missed. In fact, stock prices move according to the consensus market expectation, which is a function of all the participants' FEPF on that ticker. This is why the price moves so dramatically - even if a stock beats, it might not beat enough to justify the high price tag (FSLY); even if a stock misses, it might have spectacular guidance or maybe the market just was assuming it would go bankrupt instead. To look at the impact of NOPE and why it may play a role in post-earnings-announcement immediate price moves, let's review the following cases:
Stock Meets/Exceeds Market Expectations (aka price goes up) - In the general case, we would anticipate post-ER market participants value the stock at a higher price, pushing it up rapidly. If there's a high absolute value of NOPE on said ticker, this should end up magnifying the positive move since:
a) If NOPE is high negative - This means a ton of put buying, which means a lot of those puts are now worthless (due to price decoherence). This means that to stay delta neutral, market makers need to close out their sold/shorted shares, buying them, and pushing the stock price up. b) If NOPE is high positive - This means a ton of call buying, which means a lot of puts are now worthless (see a) but also a lot of calls are now worth more. This means that to stay delta neutral, market makers need to close out their sold/shorted shares AND also buy more shares to cover their calls, pushing the stock price up. 2) Stock Meets/Misses Market Expectations (aka price goes down)- Inversely to what I mentioned above, this should push to the stock price down, fairly immediately. If there's a high absolute value of NOPE on said ticker, this should end up magnifying the negative move since: a) If NOPE is high negative - This means a ton of put buying, which means a lot of those puts are now worth more, and a lot of calls are now worth less/worth less (due to price decoherence). This means that to stay delta neutral, market makers need to sell/short more shares, pushing the stock price down. b) If NOPE is high positive - This means a ton of call buying, which means a lot of calls are now worthless (see a) but also a lot of puts are now worth more. This means that to stay delta neutral, market makers need to sell even more shares to keep their calls and puts neutral, pushing the stock price down. --- Based on the above two cases, it should be a bit more clear why NOPE is a measure of sensitivity to system perturbation. While we previously discussed it in the context of magnifying directional move, the truth is it also provides a directional bias to our "random" walk. This is because given a price move in the direction predicted by NOPE, we expect it to be magnified, especially in situations of price decoherence. If a stock price goes up right after an ER report drops, even based on one participant deciding to value the stock higher, this provides a runaway reaction which boosts the stock price (due to hedging factors as well as other participants' behavior) and inures it to drops.
NOPE and NOPE_MAD
I'm going to gloss over this section because this is more statistical methods than anything interesting. In general, if you have enough data, I recommend using NOPE_MAD over NOPE. While NOPE in theory represents a "real" quantity (net option delta over net share delta), NOPE_MAD (the median absolute deviation of NOPE) does not. NOPE_MAD simply answecompare the following:
How exceptional is today's NOPE versus historic baseline (30 days prior)?
How do I compare two tickers' NOPEs effectively (since some tickers, like TSLA, have a baseline positive NOPE, because Elon memes)? In the initial stages, we used just a straight numerical threshold (let's say NOPE >= 20), but that quickly broke down. NOPE_MAD aims to detect anomalies, because anomalies in general give you tendies.
I might add the formula later in Mathenese, but simply put, to find NOPE_MAD you do the following:
Calculate today's NOPE score (this can be done end of day or intraday, with the true value being EOD of course)
Calculate the end of day NOPE scores on the ticker for the previous 30 trading days
Compute the median of the previous 30 trading days' NOPEs
Find today's deviation as compared to the MAD calculated by: [(today's NOPE) - (median NOPE of last 30 days)] / (median absolute deviation of last 30 days)
This is usually reported as sigma (σ), and has a few interesting properties:
The mean of NOPE_MAD for any ticker is almost exactly 0.
[Lily's Speculation's Speculation] NOPE_MAD acts like a spring, and has a tendency to reverse direction as a function of its magnitude. No proof on this yet, but exploring it!
Using the NOPE to predict ER
So the last section was a lot of words and theory, and a lot of what I'm mentioning here is empirically derived (aka I've tested it out, versus just blabbered). In general, the following holds true:
3 sigma NOPE_MAD tends to be "the threshold": For very low NOPE_MAD magnitudes (+- 1 sigma), it's effectively just noise, and directionality prediction is low, if not non-existent. It's not exactly like 3 sigma is a play and 2.9 sigma is not a play; NOPE_MAD accuracy increases as NOPE_MAD magnitude (either positive or negative) increases.
NOPE_MAD is only useful on highly optioned tickers: In general, I introduce another parameter for sifting through "candidate" ERs to play: option volume * 100/share volume. When this ends up over let's say 0.4, NOPE_MAD provides a fairly good window into predicting earnings behavior.
NOPE_MAD only predicts during the after-market/pre-market session: I also have no idea if this is true, but my hunch is that next day behavior is mostly random and driven by market movement versus earnings behavior. NOPE_MAD for now only predicts direction of price movements right between the release of the ER report (AH or PM) and the ending of that market session. This is why in general I recommend playing shares, not options for ER (since you can sell during the AH/PM).
NOPE_MAD only predicts direction of price movement: This isn't exactly true, but it's all I feel comfortable stating given the data I have. On observation of ~2700 data points of ER-ticker events since Mar 2019 (SPY 500), I only so far feel comfortable predicting whether stock price goes up (>0 percent difference) or down (<0 price difference). This is +1 for why I usually play with shares.
Some statistics: #0) As a baseline/null hypothesis, after ER on the SPY500 since Mar 2019, 50-51% price movements in the AH/PM are positive (>0) and ~46-47% are negative (<0). #1) For NOPE_MAD >= +3 sigma, roughly 68% of price movements are positive after earnings. #2) For NOPE_MAD <= -3 sigma, roughly 29% of price movements are positive after earnings. #3) When using a logistic model of only data including NOPE_MAD >= +3 sigma or NOPE_MAD <= -3 sigma, and option/share vol >= 0.4 (around 25% of all ERs observed), I was able to achieve 78% predictive accuracy on direction.
Like all models, NOPE is wrong, but perhaps useful. It's also fairly new (I started working on it around early August 2020), and in fact, my initial hypothesis was exactly incorrect (I thought the opposite would happen, actually). Similarly, as commenters have pointed out, the timeline of data I'm using is fairly compressed (since Mar 2019), and trends and models do change. In fact, I've noticed significantly lower accuracy since the coronavirus recession (when I measured it in early September), but I attribute this mostly to a smaller date range, more market volatility, and honestly, dumber option traders (~65% accuracy versus nearly 80%). My advice so far if you do play ER with the NOPE method is to use it as following:
Buy/short shares approximately right when the market closes before ER. Ideally even buying it right before the earnings report drops in the AH session is not a bad idea if you can.
Sell/buy to close said shares at the first sign of major weakness (e.g. if the NOPE predicted outcome is incorrect).
Sell/buy to close shares even if it is correct ideally before conference call, or by the end of the after-market/pre-market session.
Only play tickers with high NOPE as well as high option/share vol.
--- In my next post, which may be in a few days, I'll talk about potential use cases for SPY and intraday trends, but I wanted to make sure this wasn't like 7000 words by itself. Cheers. - Lily
I'm reading every Hugo, Nebula, Locus, and World Fantasy Award winner. Here's my reviews of the up to 1980 (Vol 4)
It is that time once more, folks. Links to previous posts at the end, links to full length blog reviews are all in one comment. Man Plus by Frederik Pohl
Plot: A normal human could not survive on Mars... our only option? Cyborgs!
Page Count: 183
Award: 1976 Nebula
Worth a read: No... but consider it for a laugh.
Primary Driver: (?????????)
Bechdel Test: Pass... but a real weak pass.
Review: Imagine if you took subplots from a trashy romance, a political thriller, a horror flick, and a space travel story... and forgot to put in the main plot. Starts decently, spirals wildly out of control with astounding speed. Almost worth reading to experience the hilarious concluding deus ex machina. This one is probably in the "so bad it's good category" - but sweet skittles is it bad. Also, turn on safe search if you look this book up.
Where Late the Sweet Birds Sang by Kate Wilhelm
Plot: After a pandemic causes infertility (and every other apocalypse hits), the only way for humans to survive is through cloning. But are they really human?
Page Count: 251
Award: 1977 Hugo and 1977 Locus
Worth a read: No
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Review: Disappointing and disjointed. There are a lot of messages here that just get blended together to nothingness. Cumbersome writing, uncompelling characters, bland dystopia, and just a dull story. Odd choices on where to discuss science at length and where to just skip over it. First third was its own story originally, and is the best part.
Doctor Rat by William Kotzwinkle
Plot: There is no joy like dying to advance science, at least according to Doctor Rat.
Page Count: 243
Award: 1977 World Fantasy Award
Worth a read: No... but worth a glance at a chapter or two.
Primary Driver: (Plot, World, or Character)
Bechdel Test: N/A
Technobabble: Frequent descriptions of animal experiments.
Review: This book is truly horrifying to read. It's about the gruesome nature of animal testing - and cruelty to animals in general - and is chock full of graphic animal gore. It's the child of The Jungle and Animal Farm but without subtext. Consider checking it out to read a couple of chapters - the grotesque fascination wears thin. Some might consider the unambiguous use of Nazi imagery for animal testing to be a step or three too far.
Gateway by Frederik Pohl
Plot: The Heechee left behind technology so advanced that we cannot understand it; that doesn't stop us from using it to get rich or die trying.
Page Count: 313
Award: 1977 Nebula, 1978 Hugo, and 1978 Locus SF
Worth a read: Yes. Very yes.
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Review: Really good. Cleverly bounces between the story as it unfolds and therapy sessions afterwards - we know that our hero survives, but something terrible has happened. A bit too Freudian. Still, excellent job of making a complex protagonist, interesting world, compelling story. Wanting to know what went wrong kept me reading - and it pays off.
The Silmarillion by J. R. R. Tolkien
Plot: Turns out Middle Earth had other jewelry too.
Page Count: 386
Award: 1978 Locus Fantasy Award
Worth a read: Yes.
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Review: This is epic fantasy in its purest form; it is myth and legend, at times obtuse, but absolutely riveting. Tolkien's world is fully immersive. Had the physical book to follow the story, the audiobook for pronunciation, and laptop for family trees. Absolutely worth it - even as a casual LoTR fan.
Our Lady of Darkness by Fritz Leiber
Plot: Something sinister is haunting Franz Westen, and dealing with it involves unearthing answers that might be best left buried.
Page Count: 183
Award: World Fantasy Award 1978
Worth a read: Yes
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Review: This is a horror story. Atmosphere is excellent. Book begins with some truly unsettling images and world building. The narrative itself is slow and frequently self-indulgent, but atmosphere stays on point. A qualified recommendation; but some scenes from this will stick with me for quite a while.
Dreamsnake by Vonda N. McIntyre
Plot: Long after the end of the world as we know it, Snake wanders the world, healing those she meets to the best of her abilities.
Page Count: 288
Award: 1978 Nebula, 1979 Hugo, and 1979 Locus
Worth a read: Yes
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Technobabble: Minimal to moderate.
Review: Less-is-more world building with good execution. A lot of interesting tidbits to keep you wondering what the rules are, who the people are, and so on. Story itself can be slow and stakes are consistently low. "I'm going to a place, surprise! something comes up, I will go to another place along the way." Characters are well written though not particularly complex.
Gloriana, or The Unfulfill'd Queen by Michael Moorcock
Plot: In an alternate timeline, Queen Elizabeth I rules over the vast empire of Albion and must do her best to manage a corrupt and twisted court.
Page Count: 368
Award: 1979 World Fantasy Award
Worth a read: Absolutely No.
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Review: This book is remarkable in that it combines shockingly dull and lengthy exposition with some truly awful and problematic ideas about sex. A whole lot of parallel world court intrigue that just does not matter at all. The actual plot starts developing halfway or later into the book - and is not interesting. The title addressing Gloriana's inability to orgasm is a big ol' red flag. A deeply unpleasant read. Really awful.
The Fountains of Paradise by Arthur C. Clarke
Plot: Humans have built many marvels, but nothing can compete with a space elevator.
Page Count: 317
Award: 1980 Hugo and 1979 Nebula
Worth a read: Yes
Primary Driver: (Plot, World, or Character)
Bechdel Test: Fail
Review: Overall enjoyable. Main narrative is about the space elevator, secondary is about an equally ambitious ancient building project - woven together in interesting ways. The science and vision offered are interesting, though characters are not and tension is infrequent. Marred somewhat by some truly bizarre (and underdeveloped) side plots and unnecessary epilogue.
The Riddle-Master Trilogy by Patricia A. McKillip
Plot: All the wizards left behind were riddles, and the only one who might be able to solve them is the biggest riddle of all.
Page Count: 578 (Full Trilogy)
Award:Harpist in the Wind (Book 3): 1980 Locus Fantasy
Worth a read: Yes
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Technobabble: Fantasy Babble: Minimal.
Review: It's an epic fantasy trilogy. It's a good one. Kinda loved it. Heroes and villains are complex, magic is interesting and coherent. Excellent characters. Cool development of powers, though it is far more power sprint than power crawl. Pacing can be odd; a few long pauses followed by frenetic scenes. Very well written. A satisfying read.
Watchtower by Elizabeth A. Lynn
Plot: The Southerners picked the wrong keep to invade; Ryke will do everything he can to get it back.
Page Count: 240
Award: World Fantasy Award 1980
Worth a read: No
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Technobabble: Fantasy Babble: Minimal.
Review: The sweet, sweet taste of subpar writing. World building: "You people from the hot South are not used to how cold it is here up North!" Character Development: "You mean... I don't just need to indiscriminately murder people?!" and "You mean... women can fight too?!" Writing Quality (Verbatim): "He thought it might have ben a room in Tornor. The room was hot. He went to the window to open the shutters. They stuck. He had to force the latch. At last one opened."
Titan by John Varley
Plot: The intrepid crew of the Ringmaster crash in alien territory and must figure out how to survive.
Page Count: 309
Award: 1980 Locus SF
Worth a read: No
Primary Driver: (Plot, World, or Character)
Bechdel Test: Pass
Technobabble: Minimal to moderate.
Review: It is hard to find such a dumb book that takes itself so seriously. Some legitimately interesting exploration bits not enough to redeem this one. Extremely juvenile. Raises interesting questions and offers insultingly insipid answers. There are elements that are quite good - particularly some crisp dialogue - but it's just not worth it.
Any questions or comments? Fire away! A truly massive thank you to u/gremdelfor mailing me a bunch of books! People like you are what make this endeavor worth the effort. I’ve been using this spreadsheet, as well as a couple others that kind Redditors have sent. So a huge thanks to u/velzerat and u/BaltSHOWPLACE At the request of a number of you, I’ve written up extended reviews of everything and made a blog for them. I’ve included the links with the posts for individual books. I try to put up new reviews as fast as I read them. Take a look in the comments for that link! The Bechdel Test is a simple question: do two named female characters converse about something other than a man. Whether or not a book passes is not a condemnation so much as an observation; it provides an easy binary marker. Seems like a good way to see how writing has evolved over the years. At the suggestion of some folks, I’m loosening it to non-male identified characters to better capture some of the ways that science fiction tackles sex and gender. For a better explanation of why it’s useful, check out this comment from u/Gemmabeta
When it comes to Binary Options, there have been quite a few examples of people who have been taken for a ride by a Broker and have lost a large amount of money. Binary Option Scams are quite common and come down to a number of factors including improper due diligence and manipulation by the broker. This is an unfortunate situation as it has tainted the image of Binary Options in it’s ... Binary options brokers, just like any other type of business, come and go. You need a solid binary options trading education to get success and one fundamental thing is to be sure you get paid when you win and expect binary options highest payout. Unregulated BrokersThey might have found that their business model wasn’t as successful as they had hoped it would be and went out of business, or ... why binary options are bad. Why You Should Avoid Binary Options. July 27, 2016 By Nick James 1 Comment. There is no doubt that binary options trading has become increasingly popular among retail ... Why Binary Options Are Bad. tradingview trading platform capabilities and features; scalping trading platform ; www.365 binary option.com; Previous post. Instagram did not return a 200. MENU. About us; SHOP; Our Terms; PRODUCTS. #HelpAKarigar during Covid-19 lockdowns; Nadex forex binary options; Indo Western Fusion ; Wedding; SUBSCRIBE. Sign up for our latest news and updates. Sign up. Leave ... * 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... Why are unlicensed binary options brokers dangerous? Although officially outside EU/USA it’s not required for a ... Be ready for a long game and, lots of high and lows and keep control of your emotions in good times and in bad times. Easy money – people think binary options trading is a very easy thing, but it’s not. You will have to learn to be a successful trader, and you will have to ... Binary Options 50% Acuraccy rate simulation. While a 50% winning ratio should be enough in Forex to at least not losing your account, in Binary Options that means losing everything. In case that you are able to make a profit trading binary options, as you can see, you are going to earn less money, and in most cases, you are going to lose ... Binary option sucks! You may have heard this phrase thousands of times from binary options traders and through other platforms. We often say this after facing a loss in binary options but tell me honestly; have you ever thought why binary option sucks. There is a reason behind everything and in this article we will try to find the reason behind ... Over the past year, Cyprus-based industry regulator CYSEC has actively trying to reform the binary options industry and clean it of it’s bad image following many unscrupulous brokers scamming their customers or putting them through duress, and has also been in long-drawn debate on banning binary options altogether. Why embracing life’s complexity – not binary thinking – could save your career. As automation enters the workplace, we must leave binary thinking to the machines. As humans, this level of intellectual laziness will quickly make employees irrelevant and leave them on the scrapheap. As technology engulfs the world of business, every ...
Why Binary Options, Forex And Options Trading Sucks - YouTube
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... There are SO many scams in the finance world these days, and yes I know, I know I trade penny stocks which everyone hates, but if you read my free http://tim... How Binary Options Work. To get the transcript and MP3, go to: https://www.rockwelltrading.com/coffee-with-markus/how-binary-options-work/ Try it for yoursel... Do binary options really work why binary options is better than forex why binary options are bad https://blogs-forex.com Do binary option trading profita... 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 ... https://binaryoptionsbeat.com/ For Inquiries contact us via: [email protected] Binary options has been banned in Europe due to decision made by ESMA.... Join The Binary Lab: https://thebinarylab.net/join-binary-lab/ Facebook: http://facebook.com/thebinarylabpage *** To get into the Binary Lab faster, after re... A look at why binary options are not really an instrument for serious traders. Basically, they offer unfavorable reward/risk setups, and don't have money man... Have you ever been tempted to join binary options? Ever had a bad experience with binary options Recovery? Have you ever been scammed? How do you recover fro...