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
This is the CLI & GUI v0.17.1.3 'Oxygen Orion' point release. This release predominantly features bug fixes and performance improvements. Users, however, are recommended to upgrade, as it includes mitigations for the issue where transactions occasionally fail.
We encourage users to check the integrity of the binaries and verify that they were signed by binaryFate's GPG key. A guide that walks you through this process can be found here for Windows and here for Linux and Mac OS X.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 # This GPG-signed message exists to confirm the SHA256 sums of Monero binaries. # # Please verify the signature against the key for binaryFate in the # source code repository (/utils/gpg_keys). # # ## CLI 38a04a7bd00733e9d943edba3004e44730c0848fe5e8a4fca4cb29c12d1e6b2f monero-android-armv7-v0.17.1.3.tar.bz2 0e94f58572646992ee21f01d291211ed3608e8a46ecb6612b378a2188390dba0 monero-android-armv8-v0.17.1.3.tar.bz2 ae1a1b61d7b4a06690cb22a3389bae5122c8581d47f3a02d303473498f405a1a monero-freebsd-x64-v0.17.1.3.tar.bz2 57d6f9c25bd1dbc9d6b39fcfb13260b21c5594b4334e8ed3b8922108730ee2f0 monero-linux-armv7-v0.17.1.3.tar.bz2 a0419993fbc6a5ca11bcd2e825acef13e429824f4d8c7ba4ec73ac446d2af2fb monero-linux-armv8-v0.17.1.3.tar.bz2 cf3fb693339caed43a935c890d71ecab5b89c430e778dc5ef0c3173c94e5bf64 monero-linux-x64-v0.17.1.3.tar.bz2 d107384ff7b1f77ee4db93940dbfda24d6045bf59c43169bc81a0118e3986bfa monero-linux-x86-v0.17.1.3.tar.bz2 79557c8bee30b229bda90bb9ee494097d639d60948fc2ad87a029359b56b1b48 monero-mac-x64-v0.17.1.3.tar.bz2 3eee0d0e896fb426ef92a141a95e36cb33ca7d1e1db3c1d4cb7383994af43a59 monero-win-x64-v0.17.1.3.zip c9e9dde61b33adccd7e794eba8ba29d820817213b40a2571282309d25e64e88a monero-win-x86-v0.17.1.3.zip # ## GUI 15ad80b2abb18ac2521398c4dad9b8bfea2e6fc535cf4ebcc60d99b8042d4fb2 monero-gui-install-win-x64-v0.17.1.3.exe 3bed02f9db5b7b2fe4115a636fecf0c6ec9079dd4e9284c8ce2c67d4996e2a4a monero-gui-linux-x64-v0.17.1.3.tar.bz2 23405534c7973a8d6908b76121b81894dc853039c942d7527d254dfde0bd2e8f monero-gui-mac-x64-v0.17.1.3.dmg 0a49ccccb561445f3d7ec0087ddc83a8b76f424fb7d5e0d725222f3639375ec4 monero-gui-win-x64-v0.17.1.3.zip # # # ~binaryFate -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEgaxZH+nEtlxYBq/D8K9NRioL35IFAl+oVkkACgkQ8K9NRioL 35Lmpw//Xs09T4917sbnRH/DW/ovpRyjF9dyN1ViuWQW91pJb+E3i9TY+wU3q85k LyTihDB5pV+3nYgKPL9TlLfaytJIQG0vYHykPWHVmYmvoIs9BLarGwaU3bjO0rh9 ST5GDMdvxmQ5Y1LTwVfKkmBJw26DAs0xAvjBX44oRQjjuUdH6JdLPsqa5Kb++NCM b453m5s8bT3Cw6w0eJB1FQEyQ5BoDrwYcFzzsS1ag/C4Ylq0l6CZfEambfOQvdUi 7D5Rywfhiz2t7cfn7LaoXb74KDA/B1bL+R1/KhCuFqxRTOQzq9IxRywh4VptAAMU UR7jFHFijOMoyggIbkD48JmAjlBnqIyQJt4D5gbHe+tSaSoKdgoTGBAmIvaCZIng jfn9pTNzIJbTptsQhhyZqQQIH87D8BctZfX7pREjJmMNGwN2jFxXqUNqYTso20E6 YLtC1mkZBBZ294xHqT1mQpfznc6uVJhhoJpta0eKxkr1ahrGvWBDGZeVhLswnBcq 9dafAkR14rdK1naiCsygb6hMvBqBohVu/bWuhycJcv6XRvlP7UHkR6R8+s6U4Tk2 zaJERQF+cHQpEak5aEJIvDlb/mxteGyvPkPyL7UmADEQh3C4nREwkDSdnitYnF+e HxJZkshoC98+YCkWUP4+JYOOT158jKao3u0laEOxVGOrPz1Nc64= =Ys4h -----END PGP SIGNATURE-----
Note that you should be able to utilize the automatic updater in the GUI that was recently added. A pop-up will appear shortly with the new binary. In case you want to update manually, you ought to perform the following steps:
Extract the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux) you just downloaded) to a new directory / folder of your liking.
Open monero-wallet-gui. It should automatically load your "old" wallet.
If, for some reason, the GUI doesn't automatically load your old wallet, you can open it as follows:  On the second page of the wizard (first page is language selection) choose Open a wallet from file  Now select your initial / original wallet. Note that, by default, the wallet files are located in Documents\Monero\ (Windows), Users//Monero/ (Mac OS X), or home//Monero/ (Linux). Lastly, note that a blockchain resync is not needed, i.e., it will simply pick up where it left off.
You ought to perform the following steps:
Download the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux)) from the official website, the direct download links in this thread, or Github.
Extract the new binaries to a new directory of your liking.
Copy over the wallet files from the old directory (i.e. the v0.15.x.x, v0.16.x.x, or v0.17.x.x directory).
Start monerod and monero-wallet-cli (in case you have to use your wallet).
Note that a blockchain resync is not needed. Thus, if you open monerod-v0.17.1.3, it will simply pick up where it left off.
In the wizard, you can either select Simple mode or Simple mode (bootstrap) to utilize this functionality. Note that the GUI developers / contributors recommend to use Simple mode (bootstrap) as this mode will eventually use your own (local) node, thereby contributing to the strength and decentralization of the network. Lastly, if you manually want to set a remote node, you ought to use Advanced mode. A guide can be found here: https://www.getmonero.org/resources/user-guides/remote_node_gui.html
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
The Challenges of Designing a Modern Skill, Part 3
Okay, Wendy’s or Walgreens or whoever, I don’t care who you are, you’re listening to the rest.
Introduction to Part 3
Welcome back one last time to “The Challenges of Designing a Modern Skill,” a series where we discuss all aspects of skill design and development. In Part 1, we talked about OSRS’s history with skills, and started the lengthy conversation on Skill Design Philosophy, including the concepts of Core, Expansion, and Integration. This latter topic consumed the entirety of Part 2 as well, which covered Rewards and Motivations, Progression, Buyables, as well as Unconstructive Arguments. Which brings us to today, the final part of our discussion. In this Part 3, we’ll finish up Section 3 – Skill Design Philosophy, then move on to chat about the design and blog process. One last time, this discussion was intended to be a single post, but its length outgrew the post character limit twice. Therefore, it may be important to look at the previous two parts for clarity and context with certain terms. The final product, in its purest, aesthetic, and unbroken form, can be found here.
3-C – Skill Design Philosophy, Continued
3-12 - Balancing
What follows from the discussion about XP and costs, of course, is balancing: the bane of every developer. A company like Riot knows better than anyone that having too many factors to account for makes good balance impossible. Balancing new ideas appropriately is extremely challenging and requires a great respect for current content as discussed in Section 3-5 – Integration. Thankfully, in OSRS we only have three major balancing factors: Profit, XP Rate, and Intensity, and two minor factors: Risk and Leniency. These metrics must amount to some sense of balance (besides Leniency, which as we’ll see is the definition of anti-balance) in order for a piece of content to feel like it’s not breaking the system or rendering all your previous efforts meaningless. It’s also worthy to note that there is usually a skill-specific limit to the numerical values of these metrics. For example, Runecrafting will never receive a training method that grants 200k xp/hr, while for Construction that’s easily on the lower end of the scale. A basic model works better than words to describe these factors, and therefore, being the phenomenal artist that I am, I have constructed one, which I’ve dubbed “The Guthix Scale.” But I’ll be cruel and use words anyway.
Profit: how much you gain from a task, or how much you lose. Gain or loss can include resources, cosmetics, specialized currencies, good old gold pieces, or anything on that line.
XP Rate: how fast you gain XP.
Intensity: how much effort (click intensity), attention (reaction intensity), and thought (planning intensity) you need to put into the activity to perform it well.
Risk: how likely is the loss of your revenue and/or resource investment into the activity. Note that one must be careful with risk, as players are very good at abusing systems intended to encourage higher risk levels to minimize how much they’re actually risking.
Leniency: a measure for how imbalanced a piece of content can be before the public and/or Jagex nerfs it. Leniency serves as a simple modulator to help comprehend when the model breaks or bends in unnatural ways, and is usually determined by how enjoyable and abusable an activity is, such that players don’t want to cause an outrage over it. For example, Slayer has a high level of Leniency; people don’t mind that some Slayer tasks grant amazing XP Rates, great Profits, have middling Intensity, and low Risk. On the other hand, Runecrafting has low levels of Leniency; despite low Risk, many Runecrafting activities demand high Intensity for poor XP Rates and middling Profits.
In the end, don’t worry about applying specific numbers during the conceptual phase of your skill design. However, when describing an activity to your reader, it’s always useful if you give approximations, such as “high intensity” or “low risk,” so that they get an idea of the activity’s design goals as well as to guide the actual development of that activity. Don’t comment on the activity’s Leniency though, as that would be pretty pretentious and isn’t for you to determine anyway.
3-13 - Skill Bloat
What do the arts of weaving, tanning, sowing, spinning, pottery, glassmaking, jewellery, engraving, carving, chiselling, carpentry, and even painting have in common? In real life, there’s only so much crossover between these arts, but in Runescape they’re all simply Crafting. The distinction between what deserves to be its own skill or instead tagged along to a current skill is often arbitrary; this is the great challenge of skill bloat. The fundamental question for many skill concepts is: does this skill have enough depth to stand on its own? The developers of 2006 felt that there was sufficient depth in Construction to make it something separate from Crafting, even if the latter could have covered the former. While there’s often no clean cut between these skills (why does making birdhouses use Crafting instead of Construction?), it is easy to see that Construction has found its own solid niche that would’ve been much too big to act as yet another Expansion of Crafting. On the other hand, a skill with extremely limited scope and value perhaps should be thrown under the umbrella of a larger skill. Take Firemaking: it’s often asked why it deserves to be its own skill given how limited its uses are. This is one of those ideas that probably should have just been thrown under Crafting or even Woodcutting. But again, the developers who made early Runescape did not battle with the same ideas as the modern player; they simply felt like Firemaking was a good idea for a skill. Similarly, the number of topics that the Magic skill covers is so often broken down in other games, like Morrowind’s separation between Illusion, Conjuration, Alteration, Destruction, Mysticism, Restoration, Enchant, Alchemy (closer to Herblore), and Unarmored (closer to Strength and Defense). Why does Runescape not break Magic into more skills? The answer is simple: Magic was created with a much more limited scope in Runescape, and there has not been enough content in any specific magical category to justify another skill being born. But perhaps your skill concept seeks to address this; maybe your Enchantment skill takes the enchanting aspects of Magic away, expands the idea to include current imbues and newer content, and fully fleshes the idea out such that the Magic skill alone cannot contain it. Somewhat ironically, Magic used to be separated into Good and Evil Magic skills in Runescape Classic, but that is another topic. So instead of arguments about what could be thrown under another skill’s umbrella, perhaps we should be asking: is there enough substance to this skill concept for it to stand on its own, outside of its current skill categorization? Of course, this leads to a whole other debate about how much content is enough for a skill idea to deserve individuality, but that would get too deep into specifics and is outside the scope of this discussion.
3-14 - Skill Endgame
Runescape has always been a sandbox MMO, but the original Runescape experience was built more or less with a specific endgame in mind: killing players and monsters. Take the Runescape Classic of 2001: you had all your regular combat skills, but even every other skill had an endgame whose goal was helping combat out. Fishing, Firemaking, and Cooking would provide necessary healing. Smithing and Crafting, along with their associated Gathering skill partners, served to gear you up. Combat was the simple endgame and most mechanics existed to serve that end. However, since those first days, the changing endgame goals of players have promoted a vast expansion of the endgame goals of new content. For example, hitting a 99 in any non-combat skill is an endgame goal in itself for many players, completely separate from that skill’s combat relationship (if any). These goals have increased to aspects like cosmetic collections, pets, maxed stats, all quests completed, all diaries completed, all music tracks unlocked, a wealthy bank, the collection log, boss killcounts, and more. Whereas skills used to have a distinct part of a system that ultimately served combat, we now have a vast variety of endgame goals that a skill can be directed towards. You can even see a growth in this perspective as new skills were released up to 2007: Thieving mainly nets you valuable (or once valuable) items which have extremely flexible uses, and Construction has a strong emphasis on cosmetics for your POH. So when designing your new skill, contemplate what the endgame of your skill looks like. For example, if you are proposing a Gathering skill, what is the Production skill tie-in, and what is the endgame goal of that Production skill? Maybe your new skill Spelunking has an endgame in gathering rare collectibles that can be shown off in your POH. Maybe your new skill Necromancy functions like a Support skill, giving you followers that help speed along resource gathering, and letting you move faster to the endgame goal of the respective Production skill. Whatever it is, a proper, clear, and unified view of an endgame goal helps a skill feel like it serves a distinct and valuable purpose. Note that this could mean that you require multiple skills to be released simultaneously for each to feed into each other and form an appropriate endgame. In that case, go for it – don’t make it a repeat of RS3’s Divination, a Gathering skill left hanging without the appropriate Production skill partner of Invention for over 2 years. A good example of a skill with a direct endgame is… most of them. Combat is a well-accepted endgame, and traditionally, most skills are intended to lend a hand in combat whether by supplies or gear. A skill with a poor endgame would be Hunter: Hunter is so scattered in its ultimate endgame goals, trying to touch on small aspects of everything like combat gear, weight reduction, production, niche skilling tools, and food. There’s a very poor sense of identity to Hunter’s endgame, and it doesn’t help that very few of these rewards are actually viable or interesting in the current day. Similarly, while Slayer has a strong endgame goal it is terrible in its methodology, overshadowing other Production skills in their explicit purpose. A better design for Slayer’s endgame would have been to treat it as a secondary Gathering skill, to work almost like a catalyst for other Gathering-Production skill relationships. In this mindset, Slayer is where you gather valuable monster drops, combine it with traditional Gathering resources like ores from Mining, then use a Production skill like Smithing to meld them into the powerful gear that is present today. This would have kept other Gathering and Production skills at the forefront of their specialities, in contrast to today’s situation where Slayer will give fully assembled gear that’s better than anything you could receive from the appropriate skills (barring a few items that need a Production skill to piece together).
3-15 - Alternate Goals
From a game design perspective, skills are so far reaching that it can be tempting to use them to shift major game mechanics to a more favourable position. Construction is an example of this idea in action: Construction was very intentionally designed to be a massive gold sink to help a hyperinflating economy. Everything about it takes gold out of the game, whether through using a sawmill, buying expensive supplies from stores, adding rooms, or a shameless piece of furniture costing 100m that is skinned as, well, 100m on a shameless piece of furniture. If you’re clever about it, skills are a legitimately good opportunity for such change. Sure, the gold sink is definitely a controversial feature of Construction, but for the most part it’s organic and makes sense; fancy houses and fancy cosmetics are justifiably expensive. It is notable that the controversy over Construction’s gold sink mechanism is probably levied more against the cost of training, rather than the cost of all its wonderful aesthetics. Perhaps that should have been better accounted for in its design phase, but now it is quite set in stone. To emphasize that previous point: making large scale changes to the game through a new skill can work, but it must feel organic and secondary to the skill’s main purpose. Some people really disliked Warding because they felt it tried too hard to fix real, underlying game issues with mechanics that didn’t thematically fit or were overshadowing the skill’s Core. While this may or may not be true, if your new skill can improve the game’s integrity without sacrificing its own identity, you could avoid this argument entirely. If your skill Regency has a Core of managing global politics, but also happens to serve as a resource sink to help your failing citizens, then you’ve created a strong Core design while simultaneously improving the profitability of Gathering skills.
3-16 - The Combat No-Touch Rule
So, let’s take a moment to examine the great benefits and rationale of RS2’s Evolution of Combat: This space has been reserved for unintelligible squabbling. With that over, it’s obvious that the OSRS playerbase is not a big fan of making major changes to the combat system. If there’s anything that defines the OSRS experience, it has to be the janky and abusable combat system that we love. So, in the past 7 years of OSRS, how many times have you heard someone pitch a new combat skill? Practically no one ever has; a new combat skill, no matter how miniscule, would feel obtrusive to most players, and likely would not even receive 25% of votes in a poll. This goes right back to Section 3-5 – Integration, and the importance of preserving the fundamentals of OSRS’s design. I know that my intention with this discussion was to be as definitive about skill design as possible, and in that spirit I should be delving into the design philosophy specifically behind combat skills, but I simply don’t see the benefit of me trying, and the conversation really doesn’t interest me that much. It goes without saying that as expansive as this discussion is, it does not cover every facet of skill design, which is a limitation both of my capabilities and desire to do so.
3-17 - Aesthetics
I don’t do aesthetics well. I like them, I want them, but I do not understand them; there are others much better equipped to discuss this topic than I. Nonetheless, here we go. Since the dawn of OSRS, debates over art style and aesthetics have raged across Gielinor. After all, the OSRS Team is filled with modern day artists while OSRS is an ancient game. What were they supposed to do? Keep making dated graphics? Make content with a modernized and easily digestible style? Something in-between? While many players shouted for more dated graphics, they were approached by an interesting predicament: which dated graphics did they want? We had a great selection present right from the start of OSRS: 2002, 2003, 2004, 2005, 2006, and 2007. People hungry for nostalgia chose the era that they grew up in, leading to frequent requests for older models like the dragon or imp, most of which were denied by Jagex (except the old Mining rock models). But which era was OSRS supposed to follow? Jagex elected to carve their own path, but not without heavy criticism especially closer to OSRS’s conception. However, they adapted to player requests and have since gone back and fixed many of the blatant early offenders (like the Kingdom of Kourend) and adopted a more consistent flavour, one that generally respects the art style of 2007. Even though it doesn’t always hit the mark, one has to appreciate the OSRS artists for making their best attempt and listening to feedback, and here’s to hoping that their art style examination mentioned in June 2020’s Gazette bears fruit. But what exactly is the old school art style? There are simple systems by which most players judge it in OSRS, usually by asking questions like, “Would you believe if this existed in 2007?” More informed artists will start pointing out distinct features that permeated most content from back in the day, such as low quality textures, low poly models, low FPS animations, a “low fantasy” or grounded profile that appeals somewhat to realism, reducing cartoonish exaggerations, and keeping within the lore. Compiled with this, music and sound design help that art style come to life; it can be very hard on immersion when these don’t fit. An AGS would sound jarring if its special attack sounded like a weak dagger stab, and having to endure Country Jig while roaming Hosidius suddenly sweeps you off into a different universe. But coming back to skill design, the art, models, and sound design tend to be some of the last features, mostly because the design phase doesn’t demand such a complete picture of a skill. However, simple concept art and models can vastly improve how a skill concept is communicated and comfort players who are concerned about maintaining that “old school feel.” This will be touched on again later in this discussion under Section 5-2 – Presentation and Beta Testing.
3-18 - Afterword
Now we’ve set down the modern standards for a new skill, but the statements that started this section bear repeating: the formula we’ve established does not automatically make a good or interesting skill, as hard as we might have tried. Once again, harken back to the First Great Irony: that we are trying to inject the modern interpretation of what defines a skill upon a game that was not necessarily built to contain it. Therefore, one could just as easily deny each of the components described above, as popular or unpopular as the act might be, and their opinion could be equally valid and all this effort meaningless. Don’t take these guidelines with such stringency as to disregard all other views.
5-0 - The OSRS Team and the Design Process
If you’ve followed me all the way here, you’re likely A) exhausted and fed up of any conversation concerning new skills, or B) excited, because you’ve just struck an incredible skill idea (or perhaps one that’s always hung around your head) that happens to tick off all the above checkboxes. But unfortunately for you B types, it’s about to get pretty grim, because we’re going to go through every aspect of skill design that’s exterior to the game itself. We’ll be touching on larger topics like democracy, presentation, player mindsets, effort, and resource consumption. It’ll induce a fantastic bout of depression, so don’t get left behind.
5-1 - Designing a Skill
Thus far, Jagex has offered three potential skills to OSRS, each of which has been denied. This gives us the advantage of understanding how the skill design process works behind the scenes and lets us examine some of the issues Jagex has faced with presenting a skill to the players. The first problem is the “one strike and you’re out” phenomenon. Simply put, players don’t like applying much effort into reading and learning. They’ll look at a developer blog highlighting a new skill idea, and if you’re lucky they’ll even read the whole thing, but how about the second developer blog? The third? Fourth? Even I find it hard to get that far. In general, people don’t like long detail-heavy essays or blogs, which is why I can invoke the ancient proverb “Ban Emily” into this post and it’ll go (almost) completely unnoticed. No matter how many improvements you make between developer blogs, you will quickly lose players with each new iteration. Similarly, developer blogs don’t have the time to talk about skill design philosophy or meta-analyse their ideas – players would get lost far too fast. This is the Second Great Irony of skill design: the more iterations you have of a lengthy idea, the less players will keep up with you. This was particularly prominent with Warding: Battle Wards were offered in an early developer blog but were quickly cut when Jagex realized how bad the idea was. Yet people would still cite Battle Wards as the reason they voted against Warding, despite the idea having been dropped several blogs before. Similarly, people would often comment that they hated that Warding was being polled multiple times; it felt to them like Jagex was trying to brute-force it into the game. But Warding was only ever polled once, and only after the fourth developer blog - the confusion was drawn from how many times the skill was reiterated and from the length of the public design process. Sure, there are people for whom this runs the opposite way; they keep a close eye on updates and judge a piece of content on the merits of the latest iteration, but this is much less common. You could argue that one should simply disregard the ignorant people as blind comments don't contribute to the overall discussion, but you should remember that these players are also the ones voting for the respective piece of content. You could also suggest re-educating them, which is exactly what Jagex attempts with each developer blog, and still people won’t get the memo. And when it comes to the players themselves, can the playerbase really be relied on to re-educate itself? Overall, the Second Great irony really hurts the development process and is practically an unavoidable issue. What’s the alternative? To remove the developer-player interface that leads to valuable reiterations, or does you simply have to get the skill perfect in the first developer blog? It’s not an optimal idea, but it could help: have a small team of “delegates” – larger names that players can trust, or player influencers – come in to review a new, unannounced skill idea under NDA. If they like it, chances are that other players will too. If they don’t, reiterate or toss out the skill before it’s public. That way, you’ve had a board of experienced players who are willing to share their opinions to the public helping to determine the meat and potatoes of the skill before it is introduced to the casual eye. Now, a more polished and well-accepted product can be presented on the first run of selling a skill to the public, resulting in less reiterations being required, and demanding less effort from the average player to be fully informed over the skill’s final design.
5-2 - Presentation and Beta Testing
So you’ve got a great idea, but how are you going to sell it to the public? Looking at how the OSRS Team has handled it throughout the years, there’s a very obvious learning curve occurring. Artisan had almost nothing but text blogs being thrown to the players, Sailing started introducing some concept art and even a trailer with terrible audio recording, and Warding had concept art, in game models, gifs, and a much fancier trailer with in-game animations. A picture or video is worth a thousand words, and often the only words that players will take out of a developer blog. You might say that presentation is everything, and that would be more true in OSRS than most games. Most activities in OSRS are extremely basic, involve minimal thought, and are incredibly grindy. Take Fishing: you click every 20 seconds on a fishing spot that is randomly placed along a section of water, get rid of your fish, then keep clicking those fishing spots. Boiling it down further, you click several arbitrary parts of your computer screen every 20 seconds. It’s hardly considered engaging, so why do some people enjoy it? Simply put: presentation. You’re given a peaceful riverside environment to chill in, you’re collecting a bunch of pixels shaped like fish, and a number tracking your xp keeps ticking up and telling you that it matters. Now imagine coming to the players with a radical new skill idea: Mining. You describe that Mining is where you gather ores that will feed into Smithing and help create gear for players to use. The audience ponders momentarily, but they’re not quite sure it feels right and ask for a demonstration. You show them some gameplay, but your development resources were thin and instead of rocks, you put trees as placeholders. Instead of ores in your inventory, you put logs as placeholders. Instead of a pickaxe, your character is swinging a woodcutting axe as a placeholder. Sure, the mechanics might act like mining instead of woodcutting, but how well is the skill going to sell if you haven’t presented it correctly or respected it contextually? Again, presentation is everything. Players need to be able to see the task they are to perform, see the tools they’ll use, and see the expected outcomes; otherwise, whatever you’re trying to sell will feel bland and unoriginal. And this leads to the next level of skill presentation that has yet to be employed: Beta Worlds. Part of getting the feel of an activity is not just watching, it but acting it out as well - you’ll never understand the thrill of skydiving unless you’ve actually been skydiving. Beta Worlds are that chance for players to act out a concept without risking the real game’s health. A successful Beta can inspire confidence in players that the skill has a solid Core and interesting Expansions, while a failed Beta will make them glad that they got to try it and be fully informed before putting the skill to a poll (although that might be a little too optimistic for rage culture). Unfortunately, Betas are not without major disadvantages, the most prominent of which we shall investigate next.
5-3 - Development Effort
If you thought that the previous section on Skill Design Philosophy was lengthy and exhausting, imagine having to know all that information and then put it into practice.Mentally designing a skill in your head can be fun, but putting all that down on paper and making it actually work together, feel fully fleshed out, and following all the modern standards that players expect is extremely heavy work, especially when it’s not guaranteed to pay off in the polls like Quest or Slayer content. That’s not even taking into account the potentially immense cost of developing a new skill should it pass a poll. Whenever people complain that Jagex is wasting their resources trying to make that specific skill work, Jagex has been very explicit about the costs to pull together a design blog being pretty minimal. Looking at the previous blogs, Jagex is probably telling the truth. It’s all just a bunch of words, a couple art sketches, and maybe a basic in-game model or gif. Not to downplay the time it takes to write well, design good models, or generate concept art, but it’s nothing like the scale of resources that some players make it out to be. Of course, if a Beta was attempted as suggested last section, this conversation would take a completely new turn, and the level of risk to invested resources would exponentially increase. But this conversation calls to mind an important question: how much effort and resources do skills require to feel complete? Once upon a time, you could release a skill which was more or less unfinished. Take Slayer: it was released in 2005 with a pretty barebones structure. The fundamentals were all there, but the endgame was essentially a couple cool best-in-slot weapons and that was it. Since then, OSRS has updated the skill to include a huge Reward Shop system, feature 50% more monsters to slay, and to become an extremely competitive money-maker. Skills naturally undergo development over time, but it so often comes up during the designing of an OSRS skill that it "doesn't have enough to justify its existence." This was touched on deeply in Section 3-13 – Skill Bloat, but deserves reiterating here. While people recognize that skills continually evolve, the modern standard expects a new skill, upon release, to be fully preassembled before purchase. Whereas once you could get away with releasing just a skill's Core and working on Expansions down the line, that is no longer the case. But perhaps a skill might stand a better chance now than it did last year, given that the OSRS Team has doubled in number since that time. However, judging from the skill design phases that have previously been attempted (as we’ve yet to see a skill development phase), the heaviest cost has been paid in developer mentality and motivational loss. When a developer is passionate about an idea, they spend their every waking hour pouring their mind into how that idea is going to function,especially while they’re not at work. And then they’re obligated to take player feedback and adapt their ideas, sometimes starting from scratch, particularly over something as controversial as a skill. Even if they have tough enough skin to take the heavy criticism that comes with skill design, having to write and rewrite repeatedly over the same idea to make it “perfect” is mentally exhausting. Eventually, their motivation drains as their labour bears little fruit with the audience, and they simply want to push it to the poll and be done with it. Even once all their cards are down, there’s still no guarantee that their efforts will be rewarded, even less so when it comes to skills. With such a high mental cost with a low rate of success, you have to ask, “Was it worth it?” And that’s why new skill proposals are far and few between. A new skill used to be exciting for the development team in the actual days of 2007, as they had the developmental freedom to do whatever they wanted, but in the modern day that is not so much the case.
5-4 - The Problems of Democracy
Ever since the conceptualization of democracy in the real world, people have been very aware of its disadvantages. And while I don’t have the talent, knowledge, or time to discuss every one of these factors, there are a few that are very relevant when it comes to the OSRS Team and the polling process. But first we should recognize the OSRS Team’s relationship with the players. More and more, the Team acts like a government to its citizens, the players, and although this situation was intentionally instated with OSRS’s release, it’s even more prominent now. The Team decides the type of content that gets to go into a poll, and the players get their input over whether that particular piece makes it in. Similarly, players make suggestions to the Team that, in many cases, the Team hadn’t thought of themselves. This synergy is phenomenal and almost unheard of among video games, but the polling system changes the mechanics of this relationship. Polls were introduced to the burned and scarred population of players at OSRS’s release in 2013. Many of these players had just freshly come off RS2 after a series of disastrous updates or had quit long before from other controversies. The Squeal of Fortune, the Evolution of Combat, even the original Wilderness Removal had forced numerous players out and murdered their trust in Jagex. To try and get players to recommit to Runescape, Jagex offered OSRS a polling system by which the players would determine what went into the game, where the players got to hold all the cards. They also asked the players what threshold should be required for polled items to pass, and among the odd 50% or 55% being shouted out, the vast majority of players wanted 70%, 75%, 80%, or even 85%. There was a massive population in favour of a conservative game that would mostly remain untouched, and therefore kept pure from the corruption RS2 had previously endured. Right from the start, players started noticing holes in this system. After all, the OSRS Team was still the sole decider of what would actually be polled in the first place. Long-requested changes took forever to be polled (if ever polled at all) if the OSRS Team didn’t want to deal with that particular problem or didn’t like that idea. Similarly, the Team essentially had desk jobs with a noose kept around their neck – they could perform almost nothing without the players, their slave masters, seeing, criticizing, and tearing out every inch of developmental or visionary freedom they had. Ever hear about the controversy of Erin the duck? Take a look at the wiki or do a search through the subreddit history. It’s pretty fantastic, and a good window into the minds of the early OSRS playerbase. But as the years have gone on, the perspective of the players has shifted. There is now a much healthier and more trusting relationship between them and the Team, much more flexibility in what the players allow the Team to handle, and a much greater tolerance and even love of change. But the challenges of democracy haven’t just fallen away. Everyone having the right to vote is a fundamental tenet of the democratic system, but unfortunately that also means that everyone has the right to vote. For OSRS, that means that every member, whether it’s their first day in game, their ten thousandth hour played, those who have no idea about what the poll’s about, those who haven’t read a single quest (the worst group), those who RWT and bot, those who scam and lure, and every professional armchair developer like myself get to vote. In short, no one will ever be perfectly informed on every aspect of the game, or at least know when to skip when they should. Similarly, people will almost never vote in favour of making their game harder, even at the cost of game integrity, or at least not enough people would vote in such a fashion to reach a 75% majority. These issues are well recognized. The adoption of the controversial “integrity updates” was Jagex’s solution to these problems. In this way, Jagex has become even more like a government to the players. The average citizen of a democratic country cannot and will not make major decisions that favour everyone around themselves if it comes at a personal cost. Rather, that’s one of the major roles of a government: to make decisions for changes for the common good that an individual can’t or won’t make on their own. No one’s going to willingly hand over cash to help repave a road on the opposite side of the city – that’s why taxes are a necessary evil. It’s easy to see that the players don’t always know what’s best for their game and sometimes need to rely on that parent to decide for them, even if it results in some personal loss. But players still generally like the polls, and Jagex still appears to respect them for the most part. Being the government of the game, Jagex could very well choose to ignore them, but would risk the loss of their citizens to other lands. And there are some very strong reasons to keep them: the players still like having at least one hand on the wheel when it comes to new content or ideas. Also, it acts as a nice veto card should Jagex try to push RS3’s abusive tactics on OSRS and therefore prevent such potential damage. But now we come to the topic of today: the introduction of a new skill. Essentially, a new skill must pass a poll in order to enter the game. While it’s easy to say, “If a skill idea is good enough, it’ll pass the threshold,” that’s not entirely true. The only skill that could really pass the 75% mark is not necessarily a well-designed skill, but rather a crowd-pleasing skill. While the two aren’t mutually exclusive, the latter is far easier to make than the former. Take Dungeoneering: if you were to poll it today as an exact replica of RS2’s version, it would likely be the highest scoring skill yet, perhaps even passing, despite every criticism that’s been previously emphasized describing why it has no respect for the current definition of “skill.” Furthermore, a crowd-pleasing skill can easily fall prey to deindividualization of vision and result in a bland “studio skill” (in the same vein as a “studio film”), one that feels manufactured by a board of soulless machines rather than a director’s unique creation. This draws straight back to the afore-mentioned issues with democracy: that people A) don’t always understand what they’re voting for or against, and B) people will never vote for something that makes their game tougher or results in no benefit to oneself. Again, these were not issues in the old days of RS2, but are the problems we face with our modern standards and decision making systems. The reality that must be faced is that the polling system is not an engine of creation nor is it a means of constructive feedback – it’s a system of judgement, binary and oversimplified in its methodology. It’s easy to interact with and requires no more than 10 seconds of a player’s time, a mere mindless moment, to decide the fate of an idea made by an individual or team, regardless of their deep or shallow knowledge of game mechanics, strong or weak vision of design philosophy, great or terrible understanding of the game’s history, and their awareness of blindness towards the modern community. It’s a system which disproportionately boils down the quality of discussion that is necessitated by a skill, which gives it the same significance as the question “Should we allow players to recolour the Rocky pet by feeding it berries?” with the only available answers being a dualistic “This idea is perfect and should be implemented exactly as outlined” or “This idea is terrible and should never be spoken of again.” So what do you do? Let Jagex throw in whatever they want? Reduce the threshold, or reduce it just for skills? Make a poll that lists a bunch of skills and forces the players to choose one of them to enter the game? Simply poll the question, “Should we have a new skill?” then let Jagex decide what it is? Put more options on the scale of “yes” to “no” and weigh each appropriately? All these options sound distasteful because there are obvious weaknesses to each. But that is the Third Great Irony we face: an immense desire for a new skill, but no realistic means to ever get one.
6-0 - Conclusion
I can only imagine that if you’ve truly read everything up to this point, it’s taken you through quite the rollercoaster. We’ve walked through the history of OSRS skill attempts, unconstructive arguments, various aspects of modern skill design philosophy, and the OSRS Team and skill design process. When you take it all together, it’s easy to get overwhelmed by all the thought that needs to go into a modern skill and all the issues that might prevent its success. Complexity, naming conventions, categorizations, integration, rewards and motivations, bankstanding and buyables, the difficulties of skill bloat, balancing, and skill endgames, aesthetics, the design process, public presentation, development effort, democracy and polling - these are the challenges of designing and introducing modern skills. To have to cope with it all is draining and maybe even impossible, and therefore it begs the question: is trying to get a new skill even worth it? Maybe. Thanks for reading. Tl;dr: Designing a modern skill requires acknowledging the vast history of Runescape, understanding why players make certain criticisms and what exactly they’re saying in terms of game mechanics, before finally developing solutions. Only then can you subject your ideas to a polling system that is built to oversimplify them.
[Scheduled Activity] What can a game say beyond “you win” or “you lose?”
The way it all began was “you hit!” or “you miss!”, and once we all put rules to the game of let’s pretend to preempt cries of “no I didn’t” and “you’re cheating,” we had a binary resolution system: pass or fail. Now these days we have many other options: PbtA and Blades in the Dark make options for partial success and partial failure for a richer experience. And yet, the 98 pound gorilla of gaming has never done anything with that. And all the heart breaker games that are based on it, well they carry that baggage with them for the most part. How can we bring levels of success to more games? And does that even matter? Discuss. This post is part of the weekly RPGdesignScheduled Activity series. For a listing of past Scheduled Activity posts and future topics, follow that link to the Wiki. If you have suggestions for Scheduled Activity topics or a change to the schedule, please message the Mod Team or reply to the latest Topic Discussion Thread. For information on other RPGDesign community efforts, see the Wiki Index.
New Cosmos-based Testnet Lays Foundation for De-Fi Roadmap https://i.redd.it/6gxluz1bg0u51.gif Crypto.com Chain released the first version of its new testnet named Croeseid, featuring a new codebase based on the Cosmos SDK today, 19 October 2020. The name “Croeseid” is derived from the world’s first gold and silver bimetallic coin that had a standardized purity, an invention which unleashed the rapid diffusion of coinage throughout the ancient world. This resonates with Crypto.com’s mission: to accelerate the world's transition to cryptocurrency, powered by Crypto.com Chain. The change in architecture also lays a strong foundation for future support of our decentralized finance (DeFi) roadmap. Crypto.com Chain has updated to the new testnet to bring about more benefits, powered by the Cosmos SDK:
For developers: make deployment easier and enable more choices, such as: a) Multi-platform support (e.g., Windows, Mac, Linux) b) Single binary for Crypto.com Chain node c) More options for cloud providers (e.g., Intel SGX support now optional)
For partners: enable more convenient integration;
For users: the ability to support more features (such as delegation of staking and governance):
For the DeFi ecosystem: better support for DeFi use cases, e.g., the IBC (Inter-Blockchain Communication) protocol module could support cross-chain asset transfers and communications.
The Croeseid testnet continues to adopt Tendermint Core as its consensus engine. Tendermint is one of the most mature Byzantine-fault tolerant (BFT) consensus engines for building proof-of-stake systems. For more details on why Tendermint was chosen, please refer to Crypto.com Chain Dev Update #1. The Croeseid testnet codebase is released on Github here written in the Go programming language. Until mainnet launch, the Croeseid testnet will be the new and only official version of Crypto.com Chain going forward. The Crypto.com Chain team always welcome the community to review and provide suggestions to the design. An earlier testnet released by Crypto.com, Thaler testnet, will continue to be updated by the Crypto.com team, but will take the role of an experimental codebase to test certain features. Codebase and resources related to Thaler can be viewed on Github under the folder “crypto-com/thaler” here. Since the initial launch of the testnet in 2019 Q3, Crypto.com Chain has received massive support from the community and industry partners. Today, 50 validators have joined Chain and processed 350K+ transactions in total. We plan to keep this strong momentum as we launch the Croeseid testnet and invite more partners to join our ecosystem to host validators on our chain. To indicate your interest, please complete this form.
Gravity's Rainbow Reading Group | Sections 66-69 | Week 20
Alright, home stretch foax. This section's a beast. Hang in there and keep sharing your insights! All together now... Section 66 "You will want cause and effect. All right." (663) What an opening - it's almost confrontational, mocking our need for clear narrative structure and causality. We discover that Thanatz was tossed overboard in the same storm that sent Slothrop off the Anubis and off on his adventure with Frau Gnahb. Thanatz is rescued by someone even stranger - an unnamed Polish undertaker (think on the etymology of that word) who happens to be a lightening aficionado. I'll stop here and comment that, earlier, when Slothrop fell into the water before and after getting on the Anubis, it brought to mind the river Styx in Hades - another underworld. It washes clean one's identity and memory. Makes you forget who you are. And there's traditionally a ferryman, Charon, to help people cross it. Can't help but think that's who saved Thanatz here, carrying him from the land of the dead to the land of the unliving, the preterite detritus of WWII. (An aside: Speaking of Styx, has anyone listened to Mr. Roboto recently? That song has some Gravity's Rainbow vibes.) Our undertaker here is inspired by the Franklin myth and is trying to get struck by lightening in order to experience that "singular point, [that] discontinuity in the curve of life" (664) passing from a rate of change of positive infinity to one of negative infinity in the blink of an eye. Seems there's something of a conspiracy among those who have been through this point of infinite inflection - a secret society of lightening heads who are aware not of another reality but of a new layer of reality laid on top of our own. Insight into a higher level of reality, of hidden systems. We get an example of the content of the lightning-aficionado's publication A Nickel Saved and it's supposedly full of coded messages for Those Who Know, each part being a veiled reference to other topics that contain the true meaning, requiring a true paranoid's ability to see (make?) connections. For example, there are repeated mentions of April, Easter, and Spring - the season of rebirth. To an Amperage Contest and lightbulbs failing - Byron the Bulb's attempts to strike back, perchance? A screen-door salesman - what is a screen door except a permeable interface? But our undertaker isn't interested in secret knowledge - he just wants to be a better businessman - and he deposits Thanatz on the shore and rows back off into the storm. Here, Thanatz meets a group of 175s - men formerly imprisoned in the Dora camp for being gay - who have formed their own solitary community in this isolated section of northern Germany. I suspect some of this imagery may initially shock readers - concentration camp victims who want to return to their prison? Who set up their own 175-Stadt to recreate the conditions of their imprisonment? But think about it - just last section, we saw Katje, someone who's been used and abused by those in power, balk at the thought of being truly free because she had become dependent on systems of control. She had integrated those control systems as part of her identity, her sense of self. "She needs the whip," Blicero wrote of her (662). Just like Katje, these men became so conditioned to depend on a system of total control and rigid social hierarchies that they don't know how to function without it. Their 175-Stadt doesn't seem like such a ridiculously dark, inappropriate caricature now, does it? Because isn't that a central point of this book - that everyone has been conditioned to need control, to need Their System, to not know how to function without it? Slothrop was our perfect everyman from within this system, and look at what it took for him to actually be free (and even then, the ideal of America still has a colonial outpost in his head). But in their 175-Stadt, these men at least control their system of control. They built it, they staff every level of it, and it's entirely under their control. An isolated state, separate from the broader System. But is there a ruler in this system, a king? No, simply the figment of Blicero. His name, his specter, looming over everything. A system of control with no real king? We've seen that before. Not only that, but this micro-society is not based strictly on the SS command from Dora, but what the prisoners inferred about the rocket command structure in the Mittelwerke. So even their "recreation" of their imprisonment is an approximation of a different system. I'd also stop here to comment that, is this imagery really as ridiculous/insane as it first appears? I'd say no, since the queeS&M community absolutely took inspiration from Nazi uniforms as symbols of dominance and control, repurposing it into fetishwear. But then, as in this 175-Stadt, the control is by choice, as is the submission. As we've seen elsewhere in this book (Blicero's Oven-State), turning submission into a fetish can be a form of rebellion, since it subverts Their means of control (fear of pain) and turns it into a source of pleasure. Is it truly control if you're choosing it? Enjoying it? No one said this book asks easy questions of its readers... Thanatz keeps looking for answers, and gets swept up amidst the vast swarms of preterite Displaced Persons being shifted across the zone. What's concerning is that these supposedly-free, albeit displaced, people, are shuffled without purpose across the Zone, with minimal food, water, or medicine, being "herded into wire enclosure[s]" and shipped around in freight cars, "deloused, poked, palpated, named, numbered, consigned, invoiced, misrouted, detained, ignored" (669). It's almost impossible to miss the painful similarity here to the treatment of Jews and other victims of the Holocaust. Only here the mistreatment isn't out of some pathological hatred, simply a system without a place for so many people, and without the committed resources to actually, effectively help them. The thought is unsettling, since we like to imagine that only Naziesque hatred could prompt such brutal mistreatment, not apathy. Finally, he's rescued by the Schwarzkommando thanks to his knowledge of Blicero and the firing of Rocket 00000. Here, we learn a bit more about what happened that day. Looking into Blicero's eyes, he saw windmills reflected, though none were in the area. Another four-way mandala, like we saw last week with Slothrop. Thanatz isn't in great mental shape by this point, and he's beginning to equate Gottfried and Bianca both as his children. Why? Because he felt some sense of responsibility to them? Because he failed them? Either way, the Schwarzkommando learn all they need from him about that fateful noon on the Heath, though we do not. The section ends with a simple touch of hands between Enzian and Christian, a moment of connection, of trust. Section 67 Man, how do I even start summarizing this complete doozy of a section? As Weissenburger writes, "In this episode the narration begins to fragment." (344) Ya don't say... Well, here goes. We being one serious trip of a section with Slothrop, as part of a rather unimpressive team of quasi-superheros (the "Floundering Four") fighting against evil ol' Broderick Slothrop amidst the factory-state (a Metropolis-like iteration of the Rocket-State with movable buildings?!). Broderick, in the role of comic book supervillain, keeps trying to off Slothrop, but our hero has a lucky streak just wide enough to keep him alive. Right off the bat, we see another image of the chessboard - the whole factory-state is laid out in a grid, and it's all A Game of Chess, as der Springer already informed us, and our movements are limited. Crucially, "Your objective is not the King - there is no King - but momentary targets such as the Radiant Hour." (674) How can you win at chess when there's no King? How can the land be restored and the cycle renewed if there's no King to die and be replaced? Slothrop is joined by a truly slipshod lot: Myrtle Miraculous, the only one who seems to have actual powers; Maximilian, a suave Black club manager who can flow with all natural rhythms and thus able to navigate any scenario with ease, and Marcel, a mechanical chess player (an embodiment of the Mechanical Turk, but crucially, one without the hidden human operator. No hidden Grandmaster lurking inside Marcel here - nope, this android's the real deal. This section includes one of my favorite quotes from the book: "Decisions are never really made - at best they manager to emerge, from a chaos of peeves, whims, hallucinations and all-round assholery." (676) I can think of several times where I've been able to relate to that scenario all too well. Their chances for success and failure are equal, but these opposing odds don't cancel each other out - instead, the two opposing forces just create a "loud dissonance". The crew undertake some truly hallucinatory adventures through the Racketen-Stadt which I will not attempt to summarize, as that would be an exercise in futility. But we are treated to flashes of Slothrop, "Broderick and Nalline's shadow-child, their unconfessed, their monster son," (677) getting locked in an icebox, piloting a mobile building through the grid-streets of the factory-state like a giant chess piece. One line really jumps out at me, here, that I think is important: "Their struggle is not the only, or even the ultimate one. Indeed, not only are there many other struggles, but there are also spectators, watching, as spectators will do, hundreds of thousands of them." (679) Makes me think of the "glozing neuters," mentioned earlier - of the masses of people who are just trying to live their lives, neither part of any conspiracy nor actively aware of being subject to one. Must be nice. At the same time, the idea of other, simultaneous struggles, is noteworthy - it brings to mind the concept of intersectionality, and how people realizing their unique, individual struggles share common sources, and common traits, which they can work together to fight. We end this sub-section in an arena for these exact masses, where our heroes are on a stakeout, with Slothrop in full drag waiting in the Transvestites' Toilet for a message. You may be wondering about the multiple instances of cross-dressing, in various iterations, throughout the book. Slothrop in drag and Blicero in a wig and merkin come to mind. One aspect, I'd say, is that it reflects a blending of two (as far as society is generally concerned) binary opposites. A crossing-over, a transgression against the status quo and an option other than 1 or 0. Eliot, in his Notes on The Waste Land, wrote,
"Tiresias, although a mere spectator and not indeed a 'character', is yet the most important personage in the poem, uniting all the rest. Just as the one-eyed merchant, seller of currants, melts into the Phoenician Sailor, and the latter is not wholly distinct from Ferdinand Prince of Naples, so all the women are one woman, and the two sexes meet in Tiresias. What Tiresias sees, in fact, is the substance of the poem." (Emphasis mine).
Cue Crutchfield the Westwardman's world of only one of everything. Likewise, the women in Gravity's Rainbow often blend together, share traits or imagery. So do the men. The joining of the two sexes in Blicero, as well as Slothrop here at the end, is significant. The Low-Frequency Listeners The introduction here of the character of Rohr, the Keeper of the Antenna, specifically as a Jehovah's witness, was odd. It's such a specific subsect of Christianity. Then we see - he heard a man on the radio, dying, asking for a priest. Rohr says, "Should I have got on and told him about priests? Would he've found any comfort in that?" (682). In what? I had to look it up, but when I did, it clicked - Jehovah's witnesses apparently do not have priests, because they are all ordained. There is no separate priest caste in their church, and thus no Preterite/Elect division. In this section, we also learn that the Nuremberg trials are getting underway. Mom Slothrop's Letter to Ambassador Kennedy You start to feel even more sorry for Slothrop as you realize just how terrible his parents apparently were. His mom cares enough to at least write another letter asking Ambassador Kennedy as to what the hell happened to their son, but her letter quickly devolves into drunken ramblings complaining about striking workers and managing to make an innuendo about Jack Kennedy while also dismissing her love of her sons. Oof. Maybe Otto was right with his conspiracy of mothers... On the Phrase "Ass-Backwards" An entertaining linguistic debate between Säure and Slothrop on American idioms, specifically ones involving a reversal, as in the case of "ass-backwards". The section then slips into a story of Säure, in his youth, breaking into the home of a young woman, Minnie, who is unable to hear or pronounce umlauted letters, and thus manages to shout the word "helicopter" rather than "cute robber" well before the vehicle was ever invented. Her cry is heard by none other than a young aerodynamics student. The word is taken as a prophesy and a warning of the helicopter's symbol of the police state, with armed officers hanging out the sides, aiming down at their targets. My Doper's Cadenza It begins with a serenade from Bodine, and then an exploration of the tenement building "Der Platz" that is home to numerous drug addicts, dope peddlers, and general ne'er-do-wells. They are building an anti-police moat around the building, entirely underground so as to avoid detection, saving breaking through the street for the end. Shit 'n' Shinola Another idiomatic diversion for Säure. A beautiful line is tucked away in here - "from outside, the Hall is golden, the white gold precisely of one lily-of-the-valley petal in 4 o'clock sunlight, serene, at the top of an artificially-graded hill." (687) This building, the Schein-Aula (Seeming-Hall), suggests "persistence, through returns of spring, hopes for love, melting snow and ice, academic Sunday tranquillities, smells of grass just crushed or cut or later turning to hay..." (688) Yet again, imagery of spring, of a return to life from the dead season of winter, of the cycle. We return to the Roseland Ballroom, where shit 'n' Shinola do actually come together. "Shit, now, is the color white folks are afraid of. Shit is the presence of death, not some abstract-arty character with a scythe but the stiff and rotting corpse itself inside the whiteman's warm and private own asshole, which is getting pretty intimate. That's what that white toilet's for.... that white porcelain's the very emblem of Odorless and Official Death." (688) Here Pynchon cuts straight to the point - the almost pathological fear of death and its connections to fears of blackness, excrement. Shit, Death, and the Word. Edwin Treacle hit on this back on p. 276 when he tried to show his colleagues at the White Visitation "that their feelings about blackness were tied to feelings about shit, and feelings about shit to feelings about putrefaction and death." The cycle of life is too organic, too messy. Better to replace carbon with silicon, to hide shit with porcelain, to treat people with dark skin as "other" or sub-human to avoid acknowledging that their non-European, communal ways of life were, in fact, totally natural. An Incident in the Transvestites' Toilet Not King Kong, but a small, costumed ape comes up to Slothrop, who's wearing a Fay Wray dress while waiting in the bathroom for a still-unspecified message. We get a Miltonic blank-verse poem (thanks, Weissenburger!) about the movie King Kong, written in the voice of Anne Darrow (Fay Wray's character). It's honestly quite good - I love the line "in your own stone living space" - the internal rhyme there sounds really nice, and I like the riff on living stone / Livingston, both of which have popped up previously. In the poem, Darrow talks about when she was tied up, hung by the natives as an offering to "the night's one Shape to come" (689), echoing both Greta Erdman's scene in Alpdrücken and the Hanged Man card of the Tarot (willing sacrifice, sacrifice that prompts a return, a renewal of the cycle). Darrow says she prayed, "not for Jack," her suave costar, but for her director Carl Denham, "only him, with gun and camera... making the unreal reel / By shooting at it, one way or the other-" (689). Throughout GR, we've seen a film motif, and this really brings it home. The analogy of a gun to a camera, both of which make the unreal real (a camera creates films that interpret real life - the "unreal reel", a gun makes death, which we've blocked away and tried to avoid, real and inescapable). The director is in control of the movie, the actors, the story, of how it works and what is told. Darrow ends by asking Carl to "show me the key light, whisper me a line..." - a key light is used in cinema and photography to not just shed light on the subject, but to do so in a way that provides form and dimension to the subject and the scene. So Darrow is asking for the director to literally give her form and definition, to tell her what to say next. This ape, though, isn't so Romantic as ol' Kong though, and is much more direct. It hands Slothrop an anarchist's bomb straight out of the comics pages, and takes off. Slothrop freezes and is saved by a helpful transvestite who takes the bomb and flushes it down the toilet. But it explodes anyway, sending geysers of water up out of all the toilets. A Voice comes out of he Loudspeaker informing everyone that it was, in fact, a sodium bomb that explodes upon contact with water. Tellls everyone to get the "dangerous maniac" who threw it. That was supposed to be Slothrop, but he was saved by his indecision and the kindness of a stranger, who is now set upon by the other occupants of the toilet. A Moment of Fun with Takeshi and Ichizo, the Komical Kamikazes We now jump to a pair of comically-mismatched Kamikaze pilots stationed on a remote island well away from any conflict. One flies a Zero, the other flies an "Ohka device" which is basically a rocket-bomb with a pilot's seat. They get moonshine from their radarman, Kenosho, who mocks them daily for the lack of opportunities to fly to their deaths and who comes up with haikus that, while in the right format, really miss the heart of what a haiku is supposed to be. Streets Back to Slothrop, now, and a catalogue of the streets he's traveled down and what he's seen. We get a meditation on the absurdity of army chaplains, who worked for the Army and "stood up and talked to the men who were going to die about God, death, nothingness, redemption, salvation." (693) And it does seem a bit absurd when you consider that the Army that employs the chaplains is the same entity sending the men off to die. We see a bus driver (perchance our maniac bus driver from earlier?) driving through town in the night, his passengers looking out the windows, their faces "drowned-man green, insomniac, tobacco-starved, scared, not of tomorrow, not yet, but of this pause in their night-passage, of how easy it will be to lose, and how much it will hurt..." (693) Going back to the Waste Land, the phrase "I do not find / The Hanged Man. Fear death by water." is symbolic of a death without return (drowning) contrasted to the sacrifice/return symbolized by The Hanged Man. These poor passengers, it seems, aren't to expect any return. Slothrop also, at this point, learns of the bombing of Hiroshima from a discarded Army newspaper, the photo of the atomic blast placed in poor taste next to an image of a pin-up girl. The bomb's mushroom cloud is compared to the Cross, to a capital-T Tree. But which tree? Is this a meditation on the deadly, unforgettable knowledge of how to split the atom, or of the tree of life, with the citizens of Hiroshima as a sacrifice made... but to what? I'm honestly not sure. Would love your thoughts. Listening to the Toilet As others have noted, this book in many ways is about the drug counterculture and hippie movement of the 60s/early 70s. This is the most overt in this section, in which we learn that listening for the cessation of the flow of water to the toilet in the pipes is a cue that a police raid is imminent - shutting off the water being a way to prevent the flushing of illicit substances. But it takes a special ear to hear the cessation of a subtle, pervasive white noise. What if the sun, in fact, massive furnace that it is, emits a constant, low-level roar that is so incessant we don't even hear it? What if eddies in the current of the Soniferous Aether cause rare spots of true quiet, where the noise is no longer transmitted and anyone in that spot can hear their own heartbeat it's so quiet? Interestingly, there are "quiet rooms" designed to absorb nearly all sound, used for precise sound calibration. I remember reading that most people can't sit in one of those rooms for more than 30 minutes or so because it's literally so quiet that you can hear the blood flowing through your veins, and people have even reported auditory hallucinations as a result. But why this digression? Maybe because we need to be asking what other white noise is out there that we've become completely deaf to? I think Roger and Jessica found a pocket of this quiet, early in the book, where the "noise" of modern society and all its associated obligations was muted by the War. Witty Repartee A return to our Komical Kamikazes, and a meditation on the ubiquity of the Hotchkiss machine gun across nations, independent of alliances. We get an image of a false King - an inbred idiot lying naked in a dumpster, attracting the attention of potential revolutionaries. But they can't decide if he's "a diversionary nuisance planted here by the Management, or whether he's real Decadent Aristocracy to be held for real ransom" (698). While the would-be revolutionaries are debating in the alley, sentries with the aforementioned Hotchkiss guns take positions on the rooftops, aiming down... Heart-to-Heart, Man-to-Man A dialogue here between Slothrop and ol' Broderick, with dear old dad interrogating his wayward son about a modern electric drug. Slothrop reassures him that he'd never shoot raw electricity - no, they dope themselves with waves. Major pre-Cyberpunk vibes here, with Broderick warning "Suppose someday you just plug in and go away and never come back?" to which Tyrone replies, "What do you think every electrofreak dreams about? .... Maybe there is a Machine to take us away, take us completely, suck us out through the electrodes out of the skull 'n' into the Machine and live there forever.... We can live forever, in a clean, honest, purified Electroworld-" (699). Matrix, anyone? Not to mention the waves of radio, TV, etc. and the simple, episodic, controlled reality they offer. Pleasantville also comes to mind, with all its commentary on the shows of the era. Some Characteristics of Imipolex G We learn that Imipolex G is the first erectile plastic, stiffening in response to certain electronic stimuli. The potential of a layer of controlling wires just under the outer layer of Imipolex, making it a second skin - a synthetic interface. Alternately, there's the potential to control it via a projection of "an electronic 'image; analogous to a motion picture." (700) My gods, I made it through this section... Section 68 Tchitcherine now, dealing with a spook, Nikolai Ripov, from the Commissariat for Intelligence Activities. His pal Džabajev has run off with "two local derelicts" (700) and is impersonating Frank Sinatra and wooing the ladies of the Zone. We get the line, "While nobles are crying in their nights' chains, the squires sing. The terrible politics of the Grail can never touch them. Song is the magic cape." (701) - Seems another example of folks recognizing the game, the Grail quest, for what it was and checking out - deciding not to play and just enjoy themselves while the Elect lose sleep over the endless searching. Ripov explains to Tchitcherine how "the basic problem... has always been getting other people to die for you." (701) Religion used to serve as an effective control for that reason - death isn't quite as scary if you think you're going to heaven. But modern society has moved on, and needs more secular sources of control, like a commitment to "History" as if you're part of some great narrative, sacrificing yourself for some imagined end-goal of what society is "supposed" to be. Seems Tchitcherine was doping on Oneirine theophosphate. Wimpe, his dealer, argues that a man is "only real at the points of decision. The time between doesn't matter." (702) Points man again - the moment of decision, of choice, that splits the future in two. Points of control. Contrast that to:
"Datta: what have we given? / My friend, blood shaking my heart / The awful daring of a moment’s surrender / Which an age of prudence can never retract / By this, and this only, we have existed." (The Waste Land, Part V: What the Thunder Said - emphasis mine).
Both are arguing that it's these key moments, irreversible junctures in our lives that make us real. Not what comes next, not what people say about us, just our moments. Integrate those moments, run them fast enough (say 24 frames per second) and you might even approximate something close to a person... We learn that Oneirine apparently leads to "the dullest hallucinations known to psychopharmacology" (703) - hauntings of the mundane, the almost-normal. Tchitcherine's Haunting Tchitcherine hallucinates that Ripov is interrogating him, and he becomes fixated on the question of whether or not he was supposed to die. Seems like part of him wants to believe in life after death, in some hope for meaning, which goes against the Soviet doctrine and thus isn't exactly endearing him to those above him. Thankfully this is just an Oneirine haunting, except... wait, it's too real - no subtle violations of reality. He tries to escape, but is outnumbered. But no execution for him here - just a reassignment to Central Asia. A cold and operational death. Section 69
"The dearest nation of all is one that will survive no longer than you and I, a common movement at the mercy of death and time: the ad hoc adventure." - Resolutions of the Gross Suckling Conference (706)
In other words, they seek a nation that does not function independently of its citizens - one that is not some separate identity with a quasi-personhood (much like how corporations are legally "people"). Rather, a nation that is inextricably linked to the people and that will die when they do. No immortality, no denial of the cycle or death. But poor Roger's still dealing with Jessica, and now with Jeremy, too, who he's at least amicable with. But he's struggling with their acceptance of the System, their embracing of it. Jeremy's all about reassembling the rockets and firing them, asking "What else does one do with a rocket?" (note how disassembling it or at least not using the weapon isn't even an option...). Jeremy's even so kind as to invite Roger to a fancy dinner with a bunch of corporate bigwigs, including folks from Krupp, ICI, and GE, and hosted by one Stefan Utgarthaloki, whose name should be a giant red-flag that something's amiss with this shindig. Roger picks Seaman Bodine as his date, the two having struck up a rather theatrical friendship, dress in their absurdist best (Bodine in the mother of all zoot suits), and join the party. We get some insight here into the nature of rebellions, and the danger of them not only fizzling out or failing, but of being co-opted as a tool to "help legitimize Them" (713). Of either dying or "living on as Their pet" - it brings to mind the corporate branding of "rebelliousness" as cool, as "a phase" that it's normal to go through and eventually grow up from. Treating the idealism of youth, the desire to make the world better and to fight against the problems of the system before you become numb to them, as a normal phase of life is such an effective way to neutralize it culturally. How many people have heard the phrase "you get conservative [i.e. more resistant to change] as you get older"? How many of us have seen youth-led movements being dismissed as examples of immaturity, for example? Between that and companies stamping their logo on it (hello, Hot Topic), it's a way to change the cultural narrative around any movement against the status quo to one that's dismissive, just accepting enough to let people burn off their energy and eventually fall into line. Because how else can you continue to live a decent life in a society that refuses to change? You either go build a shack in the woods somewhere, die, or acclimate to the system and just focus on being comfortable yourself, not constantly fighting for change. It's a depressing thought, and I'm sure Pynchon saw a lot of that attitude in the 60s. I have to wonder - do non-industrialized societies have "teenage rebellion" as a normal part of life? Is that a part of human nature, like we tend to think, or is it an explicit reaction to reaching maturity in a system that is anti-human and anti-nature? Anyway, back to the dinner party - between the depressing, anti-social music (kazoos?!) and the lavish dinner, things seem fine, but there's a plot against the Roger and Bodine. Fortunately a journalist, Constance, tips off Bodine that they might just be the main course of this feast, so Bodine cues Roger to begin the evening show - an absurd gross-out session that they planned in advance with the aid of now-deceased Pudding communicating via medium Carroll Eventyr. The pair recite an increasingly disgusting list of alliterative dishes, triggering "well-bred gagging" and guests to flee, though a few find it all quite entertaining. But it's enough to break up the dinner party and allow our heroes to flee. Note: If you made it this far, actually read all this,thank you. Bloom warned me this was a longer section, and boy, he wasn't kidding. I think this is longer than some college essays I wrote... Damn fun, though, and I hope you've found my thoughts informative, interesting, useful, or if nothing else, sufficiently diversionary for a spell. I truly look forward to seeing what you other fine foax have to say on these labrynthine sections. Questions
In the lightning-aficionado's "A Nickel Saved" excerpt, are there any other references or hidden ideas you can find? I have to think there are.
What is the meaning of the windmill reflected in Blicero's eyes? How do you interpret the imagery in this scene in general?
175-Stadt. Oven-State. Hund-Stadt. Rocket-State. Factory-State. We've seen numerous examples of specialized micro-states across the Zone, experiments in different forms of society. What are your thoughts on these? Are they hints at ways to find alternate societies, or manifestations of humanity's tendency to divide by category and put of fences?
In the "Shit 'n' Shinola" subsection, Pynchon connects Jack Kennedy, Malcolm X, and Tyrone Slothrop. What do you make of this intersection?
In "Streets," the bombing of Hiroshima is presented as being similar to the Cross, "it is also, perhaps, a Tree..." - the capitalized "Tree" here could be the tree of knowledge, the tree of life, the tree from which the Hanged Man dangles, or perhaps something else. What's your interpretation of this imagery?
In Section 69, we see references to the Albatross, famous symbol from The Rime of the Ancient Mariner. It's presented that Slothrop is the (now-plucked) albatross, but it's not clear who killed this bird, or who's wearing it around their neck. They? Any ideas?
Space-time rippled as the Horns of Glory snapped into real space. The normally smooth transition from FTL subspace travel back to the laws of relativity was instead dangerously jarring, as the inertial dampeners struggled to hold the innards of the massive warship in their proper places. After straining mightily for the briefest of moments, they failed, throwing Admiral Halon Va and the rest of his bridge crew violently into their restraining harnesses. The ship shuddered under the immense stress, then settled, drifting silently through space on minimal power. “Tactical, get me a status report for the fleet on screen now. I want updates the instant ships jump in.” The Admiral’s voice was still firm and authoritative; it was taking every last shred of resolve he had to keep it that way. “Lieutenant Roshin, put a detail together and work with medical. I’m sure that re-entry caused more than a few extra injuries. Get as many of the crew patched up and ready for emergency action as fast as you can. I want a full casualty report as soon as possible. And if you find Science Officer Lentith and he’s still alive, send him to the bridge immediately.” Admiral Va settled back into his command chair, drawing creaking sounds from the over-stressed frame as it absorbed the weight of his massive form. The bridge was completely silent now, the command crew entirely focused on the tasks at hand. Or they were too afraid to say anything; Va couldn’t be sure. He was thankful for their silence, though. He didn’t have any answers for them about his failure. Keying in a few commands on the command panel at his station, the damage report for his ship popped up, the bridge lights flickering from the extra power draw. The Horns of Glory floated before him in hologram form. Long and slender, the ship was over two kilometers from bow to stern. At least, it had been a few hours ago. The forward 20 percent of the holographic ship was flashing red, indicating heavy damage. This was inaccurate, however, as the forward 20 percent of the ship simply wasn’t there anymore. The graceful lines and carefully crafted angles of the ship's armor were an unrecognizable slagged mess, and deep gouges had been cut into the inner decks all over the ship. Whole sections were missing amidships, two of the main reactors were offline, all the primary weapon batteries had been completely destroyed, and most of the critical systems were barely functioning. It was a miracle that she had survived the jump. That morning, Horns of Glory had been the greatest feat of Arien’Ra engineering, and it was now a barely functioning hulk. And it had all happened under my command, thought Va. He had no time to wallow in his failures, however, as at that moment tactical finally reconnected to the fleet command systems. The hologram of Horns of Glory quickly scaled down, appearing as a small, flashing, red point of light floating in loose formation with several other points of light. Most of them were flashing red as well. A constant stream of data and various reports scrolled down the right side of the hologram, listing in no uncertain terms the doom that Va had subjected his command to. If Va had thought that the bridge was quiet before, it was nothing compared to the complete stillness that now settled over them. No one so much as moved a muscle, as they all sat in stunned silence, reading the reports. Occasionally, the hologram would flash, and a new point of light would join the formation, adding more data to the pile spelling out their damnation. After 30 ticks, new points of light had stopped appearing. Admiral Halon Va had lost over 60 percent of his fleet, and not a single other dreadnaught had survived the slaughter. His defeat was total, and the Federation navy was crippled. Science Officer Beredarin Lentith had been the first member of his family not to enroll in command school in eight generations. They had been some of the finest members of the fleet the Vorqual race had ever contributed to the Federation. His brothers and sisters had all enrolled, which meant that as far as he was concerned, his family had more than fulfilled their duty to the Federation. Military life wasn’t for him, anyway; he wanted to explore. The Federation had been around for over 3000 years, and there were still vast swathes of the galaxy that they knew nothing about. They were still encountering new species every few hundred or so years, and there was nothing he wouldn’t give to find the next one. That had been the dream that directed him away from the military and into academia. The odds of actually finding a new race were so small, though. There were still at least 200,000,000 unexplored systems in the galaxy. There just wasn’t time to visit them all... He snapped out of his reverie as he stepped over the body, or rather, what was left of the body, of a Zelnassi marine. Most of it was just a green stain on the corridor wall at this point, though there had been enough of the chitinous armored torso to partially obstruct his path. The young lieutenant quickly continued on towards the bridge. If he was being honest with himself, becoming an expert on the area of unexplored space directly between the Federation and it’s largest military rival wasn’t the smartest of ideas. Between his family reputation and his unique knowledge base, he was just asking to get pressed into service. Which was exactly what had happened immediately upon the recent outbreak of hostilities. And now here he was stepping over corpses, marveling at the fact that he had somehow survived this long. He still couldn’t believe the insanity of the Dominion forces. Boarding an enemy ship MID-COMBAT. It was like something out of a youngling’s tale from before space travel. It was pure madness, but there were the bodies to prove that it had happened. He gingerly stepped around the remains of yet another Zelnassi. The signs of battle continued all the way to the bridge, where he found security forces still holding quickly fortified positions around the bridge entrance. There were more Zelnassi bodies at their feet. Berendarin shuddered. He had been closer to death than he thought. He quickly pushed those thoughts out of his mind. He could only imagine why he was needed on the bridge so urgently. The door slid open, and Lentith walked into a completely silent room. Admiral Va was slouched at his command station, his enormous arm propped up on the chair arm and supporting his massive, horned head. Lentith didn’t even know that Arien’Ra COULD slouch. Nevermind that the fastidious Admiral could or would ever do such a thing. Maybe things were somehow worse than he thought. No one seemed to notice him enter, so he announced himself to the Admiral. Though he didn’t shout, his voice echoed in the deathly silent room, startling most of the bridge command. Two of the other Vorqual officers swore, and the tiny Jezren manning the com station let out a high pitched sound somewhere between a squeak and chirp. Berendarin would have found it quite funny if the situation wasn’t so dire. Admiral Va immediately snapped back to being the hulk of muscle and horn that imposed his will on a room just by being in it. His booming voice only added to his authority. “Science Officer Lentith. I’m glad to see you’re still alive. Are you seriously injured?” Berendarin had almost forgotten that he had walked the entire way to the bridge holding a bandage to his head just above his left eye. The drop out of subspace hadn’t been kind to him. He pulled the bandage away, revealing a dark orange stain on the bandage and a crack in the bone plate above his eye. “I’m fine, sir, just one of the outer plates, and the bleeding has already stopped.” “Good. Commander Vortith is currently overseeing the emergency repairs. Take his seat. You are going to help me find a way back home.” “Sir? I’m sorry I don’t understand. Why don’t we just go back the way we came?” “That’s not possible. Most of our supply ships and tenders were destroyed when that third wave of Dominion ships hit our flank. Almost all of our pre-prepared fuel reserves are gone. On top of that, some of our ships are so damaged that they don’t have another long jump in them. And if we run into any enemy ships, the whole rest of the fleet is done for. We barely qualify as a fighting force in the state we’re in.” “Is it really that bad?” “It’s worse, but we don’t have time to get into the details. You’re the expert on this section of the galaxy. I need you to find the fleet a hiding hole. Somewhere away from the known jump routes through the Spur. Any system where we can use the few miners we have left to scavenge up some fuel, and get some critical repairs done while we’re at it. And from there either wait for reinforcements or get ourselves patched up enough to limp home. Wherever it is, it needs to be close. I’m not leaving any ships behind because they can’t make the jump.” “Oh. Just that?” The lieutenant knew that Arien’Ra were strict herbivores, but with the look that the Admiral shot him, he couldn’t help but think about the fact that his head would easily fit into that giant, molar filled mouth. “And away from any known pirate hideaways. Like I said, our fleet can’t take any more fighting. And find it quickly. It won’t be long before the Dominion fleet locates us.” “I. Uh. Sure. I’ll see what I can find.” Berendarin shrank into the commander’s chair next to the enormous Arien’Ra, desperately wishing he had been more professional. If he had acted like a proper soldier, it might soften the blow of telling the Admiral that what he wanted was next to impossible. If he had a few weeks, he might be able to find something. So much of the Spur was still un-surveyed. The odds of there being anything useful to the Admiral in the databases was absurdly low, and there was even less of a chance he’d be able to find it in time for the information to matter. He began pouring through his notes anyway. It was better than waiting around to die, which, if the situation was as dire as the Admiral made it sound, was the only other option. He spent the next hour lost in his notes, finding nothing, while the bridge crew went about piecing the ship and the fleet back together. The young scientist had all but given up on the Admiral’s impossible request when a raucous cheer went up from everyone on the command deck. “Sir,” The coms officer called out, “The Consul’s Pride just dropped out of subspace and is hailing us, sir. The main communication screen lit up, and Berendarin Lentith looked to see the face of his oldest sister on screen, strapped into the captain’s chair of her dreadnaught. He let out a sigh of relief; Baraquen was his favorite sibling. Her uniform was drenched in a deep orange blood stain at the shoulder, and she was covered in what looked like flecks of green gore from a Xelnassi. The artificial gravity was clearly malfunctioning, as the captain’s restraining harness was the only thing keeping her from floating around her bridge. But the bone plates of her jaw were turned as always into her calm, self assured smile “My apologies for the delay in joining you, Admiral Va. We had some… guests shut down our drive mid jump. We had to deal with them before we rejoined the fleet. I assume there is a plan to get us back to federation space?” “It’s good to see you in one piece, Captain Lentith,” the Admiral responded. He was barely able to keep the relief from his voice. “And there is indeed a plan.” Berendarin returned to his research as the two ranking officers in the fleet went over the details of their current predicament. He was glad his sister had survived, and not just because they were close. It would have been a terrible blow to the whole family to have lost not only their future matriarch, but the ship she commanded as well. A member of his family had been commanding that dreadnaught uninterrupted for the last 5 generations. Military service had never appealed to Berendarin, but his family history was certainly still important. And then the solution to the current problem hit him like a driver round. He let out a gasp and tore into his notes with a fervor. Both Admiral Va and his sister’s projection turned to look at him, but he didn’t notice. After a few seconds of curious silence from the rest of the onlookers, Berendarin practically jumped out of his seat. “Admiral, I think I’ve got something that will work.” The young Lieutenant punched a few commands into his datapad, and a set of stellar coordinates popped up on the navigation terminal. “It’s a main sequence star, about 500 light years from us, fairly close to the edge of the Spur. It’s not anywhere near any established jump routes. The Consul’s Pride made me think of it.” He nodded towards his sister’s face on the ship's screen. “Our great, great grandsire took the Consul’s Pride through the system on her shakedown run a little over 300 cycles ago. Chased a band of Qorthi slavers out of the system. The outer four planets are all gas giants. If we can’t find Helium 3 there, I don’t know where else we should look.” On screen, Captain Lentith looked impressed, but Admiral Va clearly didn’t seem too sure. “We’re supposed to be going away from Dominion forces, not into them. What were the Qorthi doing there?” “There are also four rocky inner worlds in the system, Sir, according to reports from the encounter. Apparently, the third planet is a Class 7 Deathworld, and the Qorthi were running some experiments on the primitive lifeforms there. They were caught completely by surprise by the Consul’s Pride, and it was the first time that she fired her weapons in anger. I can’t find any reports of Dominion ships in that section of the Spur since.” There was a long pause before Va responded. “Good work, Lieutenant. I knew my trust in you wasn’t misplaced.” Admiral Va replied, before turning to the rest of the bridge and booming “Coms! Tactical! Get those coordinates to every ship in the fleet. I want every ship we have left formed up and ready to jump as soon as possible. Any captain who feels that his drives can’t make the jump is to focus all repair efforts on getting their drives functioning immediately. I will transfer repair crews from less damaged ships to more damaged ships if that means we jump even a tick earlier. Get to it everyone. I’m not losing any more of my fleet today.” The four revolution long jump to Science Officer Lentith’s newfound sanctuary had done wonders for Halon Va’s mental state. The initial shock of his fleet's terrible defeat had worn off, and he had been able to focus on what came next. Repair crews were able to stabilize most of his ship's core systems, and he was no longer worried about the life support systems cutting out and killing the rest of his crew. There had also been time for him to visit with the wounded. To thank them for their sacrifices. He had expected it to be an act of contrition, maybe even a chance to start begging for forgiveness. But there had been no anger in his crew, and no blame hung on his horns. Most had just been relieved that he had survived, and had expressed as much. He would be forever grateful to them for that. Most importantly, the four revolutions in hyperspace had given the admiral time to really think about what had gone wrong in the nebula. He had barely rested in the preceding four revolutions, spending every scrap of spare time in his office, pouring over records from the battle. That’s where he found himself now, tucked behind his massive ceramic and titanium alloy desk of Tellarim design. It had been custom made for him upon his promotion to this command, a gift from the high admirals and the council. It was the only luxury that Va allowed in his office. The rest of Va’s space he kept strictly utilitarian. There were no trophies adorning his walls, as was customary for other members of his species. The plain bulkheads of his office were instead lined entirely with screens, and each of them were now filled with footage and reports from the battle, running on loop. Va soaked it all in. The more he watched, the more a singular conclusion crystallized in his mind. He had done everything right; he was sure of that now. 1000 years of doctrine and theory for fighting the Dominion had gone into his preparation for that battle, and he had followed it to the letter. And he had been winning. Then that attack on his flank by the Zelnassi had blown all of that out of the airlock. Something significant had changed in the way the Dominion fought... Commander Vortith’s voice rang out over the com system. ”Admiral Va, we’ll be transitioning back to real space in moments.” “Thank you. I’ll be there shortly. And get Science Officer Lentith to the bridge. I want him nearby just in case. He’s the only one who has any idea of where we are.” The Admiral pulled himself from his desk. He would have to leave the rest of his analysis for later. There was just enough time for him to reach the bridge and settle into his command chair before the Horns of Glory snapped back to real space. This time, the inertial dampeners held. “Tactical, status report.” “All ships accounted for, Admiral. Though the Consul’s Pride, several cruisers, and three of our escorts are all reporting massive failures in their Drive Cores. They won’t be jumping anywhere anytime soon.” “Wonderful.” Va wasn’t sure if he meant that sarcastically or not. “Get scans up and running and deploy the pickets that aren’t crippled in a standard scouting formation. How close are we to the nearest gas giant?” “We’re approximately half a light tick from the system’s innermost gas giant, sir.” “Excellent. Deploy the rest of the fleet. Put us in a high orbit around the planet in a defensive formation, and get our miners working immediately. Once our orbit is stable, I want every hand, paw and hoof in the fleet working on repairs.” “Yes sir.” Admiral Va settled into his command chair for a long shift. It would be a drawn out, boring process to refuel the ships. With his fleet limping along, and only two functioning miners, it would take far longer than it should. After all the chaos of the last few revolutions, boring would be a welcome change of pace. Va started to relax, sinking into his chair’s acceleration padding. His fleet and his crews were finally safe. The first priority would be to get one of the subspace beacons repaired and to get word back to the Federation that the fleet still existed. And hopefully call for aid. He was sure to be stripped of his rank as soon as contact was made, but hopefully he would avoid a Tribunal. That was an unpleasant prospect… “Sir, we have unidentified ship signatures appearing from around the planet we’re approaching.” Va had never heard panic in the voice of his young sensors officer before, but it was certainly there now. Va understood the sentiment, though. He found it difficult to keep the panic from his own voice as he started issuing orders “Bring the fleet up to combat status immediately. How many ships are there?” “I’m showing 35 individual signatures. All approaching us at combat speed and still accelerating. At current speeds, they will intercept us in just over 30 ticks, sir.” “I want details as soon as you have them, Lieutenant. Size, make, estimated firepower. Who they are. And keep scanning the system. Find out where they came from.” The panic had partially subsided for Va. 35 unknowns was not too terrible a threat. He still had almost 240 warships under his command. Still, if there was a way to avoid combat, he had to try. His fleet couldn’t suffer any more losses. “Coms, any attempt by these unknown ships to contact us?” “I”m not sure, sir,” the diminutive Jezren at the coms replied. “There’s nothing on standard communications channels. The ships are transmitting something, but I can’t figure out what it is.” “Admiral,” the Lieutenant at the sensors station called out. “I think I might have an idea of where these ships came from. Preliminary scans show there is extensive urbanization on the third and fourth planets, as well as what appear to be habitation sized artificial satellites around the second and sixth planets. One of the moons of the gas giant we’re approaching shows signs of habitation as well. All of them are emitting significant signal pollution. This system clearly already belongs to someone, and they’re broadcasting everywhere.” Halon Va, High Admiral of the Combined Federation Fleets, turned, slowly and with as much composure as he could muster, to face the young science officer seated to his left. Berendarin sat, mouth agape, staring transfixed at the sensor readouts in front of him. Va had never seen a Vorqual more confused in his life. “I want answers, Officer Lentith.” “I… I don’t.. This doesn’t make any sense,” the young science officer stammered. “There shouldn’t be anything here.” “Admiral,” The comms officer cut in, “The signal that we’re picking up from the unknown ships is definitely some kind of communication. I managed to put together audio from it.” “Play it,” commanded Va. A series of short, guttural, and completely unintelligible sounds came over the speakers in reply. There was a short pause before the sounds repeated themselves again. “Coms, what was that?” “No idea, sir, but it’s being transmitted on loop. If it is intended as a communication, our translators have no idea what to do with it.” “Admiral.” The voice came from Va’s left, and was barely audible. Va turned yet again to look at the young science officer. His gaze was locked on the tactical readout, and there something in his eyes that Va couldn’t recognize. A mixture of pure terror and something else. Was it wonder? The young Vorqual’s voice was still barely above a whisper when he continued to address the admiral: “I think we should run the transmission through First Contact Protocols.” Captain Benjamin Alvarez-León slammed against his restraining harness as the USCS Aurora started it’s decel burn. He had pushed the engines on the outdated cruiser to their limits, and the ship groaned in protest as it started counteracting his rather zealous acceleration orders. He hoped that his mad scramble with his small squadron of outdated ships had been an overreaction. The alternative was something he’d rather not think about. All Ben had was the reserves; the rest of the fleet was on maneuvers at Sirius. The Admiralty had wanted to test the new, fully modernized fleet’s maneuvering abilities in the gravwell of a binary system. And, in their infinite wisdom, they decided they needed ALL of the new fleet assets, leaving nothing in Sol except for the handful of cruisers and escorts that couldn’t match the capabilities of the modern ships. A handful of cruisers and escorts that were now hurtling towards more than 200 unknown contacts. It was the unknown part of all of this that was unnerving Ben. There were no familiar energy signatures. No familiar scan data. No IFF. No signals coming off the contacts of any kind for that matter. Two of the contacts were too big to even be ships. If it wasn’t for the fact that they were moving towards Jupiter in formation, Ben wouldn’t even think they WERE ships. “So what do you think, Alexi?” Ben asked, turning towards his second in command. “You and the rest of the bridge crew are always making inane bets. Have you whipped up an over-under for what we’re throwing ourselves at yet?” “Haven’t had time,” came the quick reply from Ben’s right. The short, stocky man from Vladivostok was missing his trademark joviality. “Though, my money is on them being Ithacan, sir.” Ben bristled at Alexi calling him sir. They’d been friends for twenty years, damnit, and had been practically joined at the hip since going through the Academy together. Outranking him still felt a little off. Now was hardly the time to worry about formalities, though. “What makes you think they're from Ithaca?” “It’s the only thing that makes sense. The locals have been getting increasingly radical, and Ithaca is the only sector where reports of piracy have been increasing.” “Yeah, I could see a rebellion coming from Ithaca,” Ben added slowly, turning over that scenario in his head. “But there’s no way they could swing something of this magnitude. There aren’t even any shipyards in the sector. And even if there were, there’s no way they could keep the construction of over two hundred ships a secret.” Alexi could only offer him a shrug in response. It was at that moment that the coms station informed him there was a transmission incoming from the unidentified ships. Ben instructed the ensign to play it, and the bridge was suddenly filled with a stream of grotesque bleating noises and strange grunts, with the occasional recognizable syllable interspersed throughout the transmission. Ben thought he picked out ‘dentify’ from the mess, but he wasn’t sure. There was a long moment of silence on the bridge. “What the hell was that?” When no one had any answers for him, Ben tapped his command console and recorded a new message to broadcast. “This is Captain Alvarez of the USCS Aurora. Unidentified ships, please clarify. Your transmission is badly garbled. We did not receive your identification. You are still trespassing in Commonwealth space and are on an unauthorized course towards Jupiter. Begin decelerating immediately and re-identify yourselves.” He wouldn’t admit it to the crew, but Ben was profoundly unsettled. Something was deeply, deeply wrong about this whole situation. Not only was he vastly outnumbered by these things, but they were unwilling to communicate properly. He was almost believing this whole thing was some kind of bizarre prank. “How much longer before we can get a decent visual on these things? “Any moment now, sir.” A new transmission arrived just then, and Ben had it played back immediately. This time, instead of almost bovine bleats and grunts, the sounds coming over the speakers were mostly intelligible. Or, they would have been, if any of the syllables were in the right order. It was almost like a toddler was rattling off all of his new favorite sounds, spitting them out in a random order and not knowing how they went together. There were still a few heavy grunts sprinkled in, just for good measure. Before Ben could process this new joke of a transmission, the contacts finally started slowing. In a matter of moments, the strange wall of contacts was hanging lazily in Jupiter’s orbit, barely moving fast enough to keep their orbit from decaying. They were still in perfect formation. “Huh. Well, I guess that’s something.” With nothing to do but sit back and wait as his ship closed the distance, Ben tried to relax and began running over all of the possibilities in his mind of what the new contacts could be. He came up with nothing. Well, nothing feasible, anyway. He took a series of long, calming breaths, trying to clear his mind and focus. This was no time for his imagination to be running wild. But he couldn’t shake the feeling that logic was failing him. Something was off. Something… “Captain, bringing visual of the unknown contacts up on screen now.” Ben actually felt his jaw drop. Every contact on his display was clearly a ship. Most were long and spindly, wrapped in layers of some kind of highly reflective armor; a fleet of crystalline arrows hanging in the darkness. The two largest contacts, which Ben had just moments ago thought were too big to be ships, were large enough on the screen for him to clearly see details. In addition to their immense size and strange armor, both ships were dotted with what were clearly weapons platforms, though what kind, Ben couldn’t tell. Noticeably, almost all of the ships on his screen were heavily damaged. Chunks were missing from some ships, and most had deep lines gouged into their hulls. Any form of decorative paint or markings had been burned away. Something had put these ships through absolute hell. But still, the damage could not take away entirely from the elegance of the ship’s designs. They were graceful and sleek, completely different from anything Ben had ever seen before. It was all so different. So strange. So very, very… Alien. Despite every effort he had made to avoid the word, it finally forced itself to form inside Ben’s mind, and forced him to acknowledge the reality that legitimate, extra-Solar life was hanging in the darkness in front of him. It forced him to acknowledge the screams he had been suppressing in the back of his mind. The screams of his imagination crying out in glorious triumph over reality. And with those screams came a deluge of accompanying thoughts and emotions. He was a child again, staring up at the stars above Armstrong and wondering what else, and who else, was out there. He was a teen again, signing his name to the Academy enrollment paperwork, determined to get out there between the stars and see the galaxy himself. He was a young officer again, screaming and pleading with the Admiralty to at least consider a modern First Contact scenario. He was sitting in his command chair now, hurtling towards honest-to-god aliens, all of his dreams made manifest in an instant. He was overwhelmed. He was terrified. And he had never imagined that he could feel such elation. It was the young warrant officer at the coms that snapped Ben out of his reverie. “Sir, the contacts are hailing us on all standard channels, requesting a video feed.” She sounded very, very nervous. Ben immediately stood up, straightening his uniform as best he could. “If they’re anything less than genocidal monsters, I’m going to offer them aid and repairs. As long as they’re peaceful, there’s no reason not to extend them the full hospitality of humanity.” “Ben,” Alexi asked, clearly choosing his words carefully, “Are you sure that’s the… Wisest course of action? How will the Admiralty respond to Goddamned alien ships docking at Hephaestus?” “Alexi, in the 250 years the Commonwealth has existed, the First Contact protocols haven’t been updated since the charter was signed. No one has cared. This has been nothing but a fantasy for most people. I am NOT letting this opportunity get away. Every child that has ever looked up at the stars and wondered finally got an answer, and I will not waste this moment. We’re making friends, the Admiralty and the government be damned.” “You do realize you’re potentially deciding the fate of our entire species on a whim, right?” “Is there someone else you’d prefer to have making this call?” Alexi, apparently deciding that there was not, stood up and straightened his uniform, standing next to his friend as he ordered the connection of the video feed. The channel connected, and the human bridge crew found themselves looking at the bridge of a ship crewed by not one, but three alien races. The largest alien in the center of the screen opened its mouth to speak. This time, instead of bleats and grunts, a choppy, mechanical voice that didn’t sync up to the alien at all proclaimed from the bridge speakers in broken, stuttering English: “I. Am Admiral. Halon. Va. Of the Federation of. Sentient Races. Greetings and. Welcome. To the. Galaxy.” Ben couldn’t suppress his smile. “On behalf of the United Solar Commonwealth, and all of Humanity, greetings, and welcome to Sol. Your ships look like they’ve had a bad time on your way here. If there’s any way we could aid with your repairs, we’d be happy to help.” Slave 782 slammed his right appendage onto the control console hard enough to rupture his outer membrane and smear ichor over the panel. It had been four days since the battle in the nebula, and with the latest round of reports, he finally had to admit that the rest of the Federation fleet had escaped him. It was a minor frustration, all things considered, but the escape prevented this from being a total victory. Still, he had proven his worth to his owners in this battle, and his experiments with the Zelnassi had paid dividends beyond his wildest imagination. He had earned a command today, and with every success in that command, his ability to bargain for his people's freedom only increased. For what he would be asking, it might take the total defeat of the Federation to earn that kind of leverage. Also frustrating, but not a task that he couldn’t handle. It would be a long war, he was sure, but like his owners, he was patient. He would earn his freedom, even if it meant reducing the entire Federation to glass. Author Wiki Series Wiki NEXT
THE BEST BINARY OPTIONS SYSTEMS Buy Bonus: For those who purchase the product after visiting their website by our hyperlink, we obtain a fee from the proprietor of the product,Not many individuals know this, however virtually all evaluation websites obtain a fee from the businesses that they hyperlink to. Binary Options System Wiki. binary options traders choice; facebook investing in bitcoin; non binary option birth certificate; binary option malaysia; how to make money binary options; Get in the game. Free tools and resources like this shipped to you as they happen. Email Address. JOIN UP We won't send you spam. Unsubscribe at any time. Powered by ConvertKit. 0 share; Facebook; Twitter ... Binary options can involve the trading and hedging strategies used in trading traditional options. You should always conduct a market analysis prior to each trade. There are many variables to consider when trying to decide whether the price of a stock or other asset is going to increase or decrease within a specific time period. Without analysis, the risk of losing money increases substantially. Binäre Optionen, auch binary options, binary trades oder binary trading genannt, sind kurzlaufende Optionen, mit denen innerhalb von wenigen Minuten Erträge zwischen 65 und 85 % erzielt werden ... To trade binary options, be sure to trade on Nadex, the Chicago Board Options Exchange, or the Cantor Exchange, which are the 3 legal markets approved by the U.S. Commodity Futures Trading Commission. You can make direct trades on all of them, but be sure to read the different rules for each market. To make informed trades, analyze fundamental information like current growth reports ... Welcome to the largest expert guide to binary options and binary trading online. BinaryOptions.net has educated traders globally since 2011 and all our articles are written by professionals who make a living in the finance industry and online trading. We have close to a thousand articles and reviews to guide you to be a more profitable trader in 2020 no matter what your current experience ... Binary Options trading isn’t a scam, but it’s financial gambling that will only work well in the long term for the most devoted and knowledgeable users. 2017 Update: Binary Options Industry Changes. If you read our thoughts from 2014, you know that binary options is legit, but extremely risky and difficult to take part in profitably. But ... As today team of BinarySignalsAdvise.com has decided to make a list of all binary options scam system to prevent our readers from the traps of these scam softwares. Let me tell you a harsh truth if you are beginner at Binary options that 99% of the products are actually scam. (You can even check out Binary Signals Reviews section to find out that more than 95% of the products which we review ... Zenitel Wiki contains technical information about the platforms IC-Edge, Pulse, SIP Intercom, ICX and AlphaCom.Here you will find up to date installation instructions, feature descriptions, configuration guides, application examples, integration with 3rd party systems, software download library, upgrade procedures and more. Binary Options vs. Vanilla Options . A vanilla American option gives the holder the right to buy or sell an underlying asset at a specified price on or before the expiration date of the option. A ...
Momentum Trading Strategies binary options trading system ...
WikiTrader Review http://thedailyharrison.com/reviews/wikitrader-software-wiki-trader-scam-not WikiTrader Review Is Wiki Trader System Scam Or Legit? Get Wi... 60 Seconds binary options strategy 99 - 100% Winning (100% profit guaranteed) 90 - 95% Winning Binary Options Strategy in case of correct prediction - 1 to 5... binary options best BROKER - http://goo.gl/XpEX8c Momentum Trading Strategies binary options trading system 2014 binary options trading system 2014, binary o... Trading Strategy: Binary Options System - Binary Options Bonuses ★ TRY FOR FREE http://binares.com/bonus - [Free register on binary options] ★ REAL REGISTE... How to trade Binary Options Binary Options trading Binary Options how to Binary Options strategy Binary Options strategies Binary Options system Binary Optio... * http://www.abestforexindicator.weebly.com https://ebay.com/usr/Alfredo000 Most Accurate FOREX indicator system ARROWS 2020 ALERTS 2021 PROGRAMS best platfo... BINARY OPTIONS TRADING SYSTEM - REAL ACCOUNT - Binary Options Brokers ★ TRY STRATEGY HERE http://iqopts.com/demo ★ WORK ON REAL MONEY http://iqopts.com/r... This is how I have traded Binary for the past 3 years. Thank you for watching my videos, hit the subscribe button for more content. Check out our members res... Click The Link Below: ----- CLICK HERE: http://45.gs/trading-code-fast-online ----- Binary opt... Sign in now to see your channels and recommendations! Sign in. Watch Queue Queue. Watch Queue Queue. Remove all; Disconnect