11-24 23:37 - 'Cash Loophole Software Scam Uncovered!' (self.Bitcoin) by /u/bestbinaryoptionssig removed from /r/Bitcoin within 1857-1862min
''' Over the years, a lot of changes have occurred in the trading world which have helped make the whole thing much easier for institutions and entity investors. It seems that binary options are for all time evolving. The introduction of innovation are often being presented to traders, such as automatic binary options trading, where best Binary robots are the ones that are actually conducting the trading whilst the trader gets to lay back and like the profits. What Exactly Is Automated Binary Options Trading? For those of you who are not fully aware, automatic binary options trading (also referred to as algorithmic trading) is what is binary options autotradingthe use of platforms, which are of electronic nature, in order to enter trading orders with an algorithm. This type of platform is able to execute pre-programmed trading instructions whose variables might include initiation of an order by a robot that is controlled by human, price, or timing. Automated binary option trading is utilized a lot, to divide large trades into several smaller trades to be able to manage market risk and impact, by mutual funds, pension funds, investment banks, and other institutional traders. Automated Binary Options Robot If we take a look at the most popular tools that have been presented on the market for binary options in the last couple of years, the trading robot definitely stands tall. The robot trading in binary options is a new trading tool that has become very successful on the market. This tool serves both for Forex and for the purchase and sales of shares. ''' Cash Loophole Software Scam Uncovered! Go1dfish undelete link unreddit undelete link Author: bestbinaryoptionssig
Welcome to Atlas Forex ! I'm offering you a complete 60 second binary options solution. My system is extremely easy to follow and is almost fully automatic. I developed the system myself and use it every day. It has been consistent and reliable with up to.
^ (Purchase) Binary Options Trading Signals Live! (Cheap) More Information About Binary Options Trading Signals Live!: Binary Options Trading Signals Live Product Reviews ... Binary Options Trading Signals Live Service Guide: Trading Signals To Change Your Forex Life. There are so many times that we have been weighted by a lot of ... Binary Options Trading Signals Live ... Binary Options Trading Signals Live Service Guide: Trading Signals To Change Your Forex Life. There are so many times that we have been weighted by a lot of ... Binary Options Trading Signals Live! - S.A.P. Binary Options Trading Signals Live New Trading System ! Uploaded by Enrique Burns on January 16, 2015 at 10:54 pm Binary Options Trading Signals Live! ALBANY NEW YORK ... Find the binary options trading signals live review charts. franco binary options signals 2015 advice, ... Best Binary Option Signals Service zanardifonderie.com. Binary Options Trading Signals Live New Trading System ... ... Binary Options Trading Signals LIVE 2) Winning Binary Signals 3) Guaranteed Trading Signals - Automatic Binary Options Alerts. Posted by Top Buy Reviews at ONLINEPRO7 :: Binary Options Trading Signals Live ... Binary options zero risk strategy the complete money making guide , Get Ready To Trade! Statistics Canada To Release Canadian Trade. Our news. Forexport ar com
Do any other nonbinary people have complicated feelings about "transmasc" or "transfem"?
I'm an AFAB nonbinary person and I feel some pressure to refer to myself as transmasc. It's hard to find resources for transition without searching either for resources for trans men or for resources for trans masc people. I don't view my transition as masculinizing as much as de-feminizing but it's kind of a weird area to be in because I don't really feel like this is accepted. Anyone else feel similar? How do you navigate this language?
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
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
Updated projectile VFX to better represent its hitbox, especially when it is traveling towards your POV
We’re keeping an eye on the overall power level of Paranoia, but as a first step wanted to resolve visual issues where players hit with Paranoia appear outside of its impact on their screen.
Blade Storm (Burst Fire)
The time between consecutive Burst Fire use has increased from 0.33 seconds >>> 0.45 seconds
Daggers thrown in Burst now have a damage falloff that begins at 12 meters and drops steadily (to 35 damage) at max falloff
Headshot multiplier on Burst Fire reduced from 3x >>> 2x
While we continue to investigate some of her outsized strengths, we think the burst fire on her Blade Storm has been over-performing at long ranges. The burst fire is intended to be a close range attack, but we found it frequently getting frags at over 20 meters away. These changes aim to rein in its effective range while retaining its close range potency.
Viper now starts the round at 100 fuel (previously 50)
Now that Viper can place her wall pre-round, we want her to be able to act with her team right at barrier drop without the tension of also trying to maximize her fuel for an initial move.
Vulnerable debuff applied from Snake Bite now lingers for 2 seconds after leaving Viper’s acid
Immediately dropping the vulnerable debuff upon exit wasn’t creating the threat we’ve hoped for when we added it. This change should make the Viper (and team) advantage window more realistic, as well as project a unique threat on opponents playing around it.
Move speed doubled while casting
Viper now fast equips her weapon after casting, re-equip times vary per gun—but on average will reduce her weapon down time by .4 seconds
The combination of a slow placement and re-equip time was resulting in Viper players getting too hurt or killed while casting ults in a situation we felt should be pretty safe. This change should increase the positional options available while casting, and get your weapon up sooner.
Fire rate bonus decreased from 25% >>> 15%
At its previous fire rate, we felt Empress was too effective when using heavies/smgs, AND too fast to master the change in spray pattern on rifles. We hope this change allows us to address both issues at once, while also giving us a chance to have a unified fire rate increase (matching Brimstone’s stim below) that players can learn and master.
Fire rate bonus increased from 10% >>> 15%
Paired with Reyna’s change (above), we felt Brimstone’s stim could use a little more punch. This also unifies our two fire rate increase buffs, making them easier to learn.
Increased price from 4500 >>> 5000
Decreased scoped movement speed from 76% >>> 72%
Adjusted weapon deadzone from becoming inaccurate at 30% movement speed >>> 15% (become inaccurate sooner, become accurate later when stopping)
Firing rate reduced from .75 >>> .6
Instant equip time adjusted from 0.3 >>> 0.5 (instant equip plays after tapping orb, bomb defuse/plant tap, Jett Cloud Burst, and Phoenix Curveball)
Leg shot damage decreased from 127 >>> 120
Jump land inaccuracy state changed from gradual >>> binary
Jump land inaccuracy duration increased from .2 >>> .225
Jump land inaccuracy value increased from 5.0 >>> 7.0 (more inaccurate for .225s after a land)
During this patch, the chances of being in an hour+ queue should be notably reduced
This is already a very rare occurrence, but it can happen more often for high rank players—especially in premade groups. We are also doing some tuning behind the scenes to keep high rank matches found after long queue times reasonably balanced and fair.
Riot ID Reviews
Players that have been reported for inappropriate Riot IDs will now be reviewed automatically after the match has ended. If their name is flagged as inappropriate, they will be forced to change their Riot ID the next time they log in to the Riot Client.
Removed Multi-line Breaks in Chat
Some sneaky people were impersonating system messages to troll others into quitting a match. Enough!
Changes to party push to talk settings will now take effect immediately
The chat window can now be pinned to stay open across menus
Social Panel Sorting Logic
Sorting algorithm for the social panel has been updated to make it more intuitive for players as they interact with it.
Fixed issue where Sova’s hitbox was incorrect while using his Owl Drone
Fixed bug where Omen’s glowing eyes weren’t properly removed when he cancelled his ult
Fixed a bug where Custom Game preferences would be wiped after navigating away from the Custom Game lobby
Coredns for local DNS resolution and forwarding over TLS (with Adblocking)
Greetings all -- I know how much y'all love unbound and pihole, but I just wanted to throw out another option that I think is super simple...CoreDNS. CoreDNS is a single-binary DNS server written in GO with many plugin options. Use Case discussed here: A complete solution for DNS resolution of internal hosts that is easy to manage while still providing AdBlocking capabilities to the entire network, and forwarding all non-local DNS requests over TLS so my crappy ISP can't see what I am doing. Solution Overview: Configure DHCP to give out pihole address as the DNS server, tell Pihole that it's upstream DNS server is CoreDNS (running on same box on a different port). CoreDNS:
NOTE IN CONFIG BELOW: My original example remains, however DanTheGreatest pointed out that there are other cloudfare examples based on your use case. Repeating here: Cloudflare introduced 18.104.22.168 (and .3) back in April. .2 Includes a malware filter and .3 also filters adult material. .2 is a great upstream for this use case.
#Here is where you will want to put your hosts style dns entries for local 10.0.20.19 server1.mydomain.com server1 10.0.20.10 database.mydomain.com database 10.0.20.42 server2.mydomain.com server2
service restart coredns
Now configure Pihole to use your Coredns as upstream. Go to http://pihole/admin settings DNS. Uncheck any DNS servers on the left hand side. Check Custom 1, and enter 127.0.0.1 and port 5300 (assuming CoreDNS is installed on same server as pihole).
.:5300 -- listen on all interfaces and bind to port 5300.
cache 3600 -- cache entries for 5 minutes. Remove this if you do not want to chache
hosts /etc/coredns/home.hosts - Use the hosts plugin and read entries from this file. CoreDNS will automatically pick up new entries when this file is updated
fallthrough -- This is important. It tells CoreDNS to try the next forwarder if it doesn't find a hit using the hosts plugin. Essentially -- if not on the internal network, keep going.
forward -- This forward block is the complete configuration for forwarding DNS over TLS to cloudfare DNS servers using round robin. If cloudfare isn't your thing, you can use any other DNS over TLS provider such as Quad9, etc. Just change the config.
Multiple stock tickers that scrolls across the screen with real-time stock prices. This can becustomized based on user's portfolio
A stock market indicator, that shows if the stock market is open or closed
An unlimited array of color combinations
Multiple themes (The watch face can remember up to 3 different customized themes set up by the user)
Full- and minimal theme options
Option to automatically change day- and night themes
All colors available in AOD mode
Option to display leading zero in hour display (a feature requested by many)
Full month calendar with customizable week start day
Customizable shortcuts that includes Flash Light, Breathing exercises and Workouts
Besides the above original features, the following standard features are available as well:
Heart rate measurement
Week number display
Dedicated application shortcuts button
Direct shortcuts to Calendar and Samsung Health
Even while running multiple functions, the watch face is ultra battery-efficient. The size of thewatch face is less than one MB and uses less battery than the built-in Samsung "Premiumanalogue" watch face. As the StockChrono watch face has been developed without using Galaxy Watch Studio, I am unfortunately not able to share the watch face easily. If anyony knows a way of distributing a precompiled binary that has not been signed by Samsung, please let me know, and I will happily share the watch face. It has been a great experience and venture for me to develop the watch face, but unfortunately it all ends here. I will not contribute further to the Samsung Galaxy platform. All the best to my fellow watch facers out there. Edit: link to the .tpk file: https://www.dropbox.com/s/cg8w215e3lpn85o/org.virtcore.StockChrono102-1.0.0.tpk?dl=0
What is up Depthians! We are back with another monstrous update as this one incorporates five beta test builds, so we have a lot to cover. If you want to dive straight into the massive changelog/dissertation Click We should probably start with the biggest change to From The Depths in this update and that is the change of fuel and ammo storage. Quoting Nick, our lead developer
The change is quite simple: "remove ammo and fuel as separate resources. Weapons will consume materials directly, fuel engines and CJEs will burn materials directly". Before I dig into why I think this is the right thing for FtD, I'd like to explain a few details. Energy, fuel and ammo are still needed for your constructs. We have changed the "ammo barrels (etc)" and "fuel tanks" so they are just alternative material storage containers, but with the following properties: --"ammo barrels" now increase the maximum possible rate of usage of materials as "ammo" for reloading guns. They still explode. --"fuel tanks" increase the maximum possible rate of use of materials as "fuel" for fuel engines and CJEs, with the future stretch goal of fuel tanks being flammable. --So ammo racking is going to remain a feature of the game- vehicles that need to reload a large amount of materials may need additional ammo barrels Ammo and oil processors are replaced ship-wide with existing material storage containers of the same size. They'll be made decorative blocks so you can still use them decoratively in future if you want to. The oil refinery will be repurposed (described later in the patch notes) There are two main reasons why I think this is the right move. Why it's right for the business and why it's right for the player. Let's start with why I think it's right for the player: Ammo and fuel containers are currently purchasable as either "empty or full". This is confusing when considered in the context of the campaign, story missions, custom battles, multiplayer matches...how do empty and full tanks behave in these modes? I'd need an hour to study the code and a small essay to explain it. That's not good game design. Localised resources, when considering just the moving of material (and energy, if you want), becomes infinitely more manageable. The supply group system and the transit fleet system are not intuitive and for a lot of situations, their usage becomes fiddly and too complicated. We've replaced these systems with a new supply system that is much more intuitive for moving materials and energy around. The UI is less cluttered now that ammo and fuel bars are not shown. This is not a minor point...it'll reduce the amount of data on screen by about 40% in a lot of the different views. It'll be so much easier to know at a glance if a particular fleet is running low on "materials" or doing fine. Is a transport ready to leave, or does it need to pick up more materials? Will a set of vehicles have enough materials for the next fight...this is so much easier with just one main resource type per vehicle. When you or an enemy run out of ammo or fuel in a battle it's just frustrating. By combining fuel, ammo and materials for repairing you can guarantee that if someone runs out, the fight is going to be over quickly. I imagine that deep down the majority of players would rather not have to create, stock and resupply fuel and ammo. I know that personally, the requirement to do this puts me off playing the campaign. By using a single material it still focuses the game on making efficient war machines, maintaining supply lines and growing your economy, but without the extra confusion of mat->ammo and mat-> fuel conversion. Being able to assess weapons, engines and vehicles in terms of material cost and running cost is elegant. Most grand strategy games and RTS games don't have localised resources, and many don't have more than 2 resource types to handle. Very few combine localised materials with multiple types. Why it's right for the business: The ammo and oil processors were created about 8 years ago. Boring single blocks that don't add much to the game. It's been our intention to add something similar to the oil refinery but for ammo creation. That's a lot of work and adds to the complexity of the logistical part of the game, which we feel is already a burden. Making the localised resource supply system more user friendly to make it easy/natural/pleasant to move ammo, fuel and material around the map would require a lot of effort and, quite frankly, I'm not sure we'd ever manage it. The complexity of the UI scares off a lot of our customers. The barriers to getting a gun firing or a boat moving will be lowered if a single material container can theoretically get everything working. Running out of ammo/fuel in combat is a problem for our players. We want to find a solution to that, but it would take a lot of effort to do so. We also want the strategic AI to always enter a battle with enough ammo and fuel for the fight- that's another massive bunch of work. The campaign's strategic AI has to work hard to get materials where it wants them. It's a bundle of work and added complexity to get NPC fleets to restock ammo and fuel as well. We had proposed work to make resource dumps (from dead ships) contain ammo and fuel...again, that's more work, more bugs, more testing. Certain game modes such as story missions, tournament mode, and multiplayer maps should theoretically allow the player to choose the amount of ammo or fuel stocked into their vehicles before the match begins. That's another bundle of work and added complexity we'd like to avoid. Currently out of play units on the map can run out of fuel and will still continue to move "for free". It's exploitable and we don't have a solution to that...but if all the different out of play movement calculations are burning material, there will be no avoiding the cost. The development effort can be much better spent polishing up other features that I actually believe in, rather than flogging the dead horse of logistical complexity in an attempt to make it interesting, approachable and fun for everyone (which I fundamentally don't think it would ever be). Fundamentally I think that by winding back this feature we tie up a large number of loose ends and it results in a far more finished and enjoyable product. And what's-more everyone on the development team agrees that we enjoy the game for fighting, looting and creating...not staring blankly at dozens of resource bars trying to figure out who needs to head back for more fuel and how long we need to wait for ammunition to process. We've also simplified the resource transfer system. "Supply groups" and "Transit Fleets" have been replaced with a simple but comprehensive three-tier system. You can mark a vehicle as a "Creator", a "Cargo" or a "User". Creators fill up Cargos (and Users), Cargos give to Users (up to procurement levels). Users equalise their material with their neighbours, so do Creators, and there are a few handy transfers from Users back to Cargo and Creator to make sure they maintain their procurement levels as well. This system covers 95% of the way people were using the resource system and does it all semi-automatically. This simplification is much more possible now that materials are the only resource, as they invariably just need to flow from the resource zones to the front line, with everyone (Creators and Cargo) keeping what they need and passing the rest on. This new resource system also facilitates the long-range transport of materials from refinery to refinery, which is neat. The system also has an option, for Creator and Cargo types, to set their "supply chain index", so if you want to relay materials from output to output in order to accumulate them at a central location you can set the supply chain index to determine which way along the chain the materials will flow. It's all explained in the game.
After spending a lot of time with this new system from adventure to campaign and designer mode, the gameplay feels a little faster to get going and a little simpler for fleet management. As if you didn’t already know, you can shift+right click (with your supply construct selected) on the target construct / flagship of a fleet to keep supplied, keep holding down shift and right-click where you want to pick the resources up from and once again while not letting go of shift, shift+right click on the target construct/flag ship to finish the loop. This would be done of course after setting up the settings Creator, Cargo and User. Creator as an example is the harvesting construct, Cargo which would be the supply ship, User which would be a single target construct that uses the mats. This will keep the supply ship target waypoint updated and therefore your supply ship will always head to the target construct no matter where it has moved to after setting up the loop. You still need ammo and fuel boxes on your constructs, as these are governing the transfer rate / the speed that stock your turrets and fuel engine with the materials needed for them to run. You can run a construct without fuel or ammo boxes, however, once your APS clips are empty you will see a drop in your rate of fire as the material is not being transferred fast enough, this is the same for fuel engines and CJE. Another change that goes hand in hand with resource management is the changes to fuel refineries. In short:
Refineries on a force with greater than 1 million materials on it will begin refining the material into 'commodities' that are stored centrally. Commodities (AKA centralised materials) can be added by the player to any vehicle in allied territory, at any time.
Steam was previously totally unbalanced and arbitrary. For example, 9 small boilers with 1 small piston was the optimal steam setup, which was more efficient and denser than almost all other engines; and turbine power generation only depended on its pressure, so compact turbines were always optimal.
It lacked many critical info in its UI.
It was hard to control the usage of steam
What's good with new steam:
A bit more of realism and complexity
Larger steam now generally have better efficiency and density than equivalent smaller steam
More useful info such as total power production, performance over time
Possibility to regulate steam usage with valves
Pros of steam compared to injector fuel:
Denser and more efficient
Even denser with turbines
Easier to fit into irregular space
Provides a buffer with flywheels or steam tanks
More efficient when used for propellers
Doesn't require fuel containers, uses material directly from any type of storage
Computationally less intensive
Cons of steam compared to fuel:
Still hard to regulate, so it's only useful when the power usage is constant or there's a buffer energy storage
Turbines waste energy when batteries are full
Crankshafts waste energy when reaching speed limit
More susceptible to damage (injector engines can often still run fine even when half of it is gone, steam can stop working when a single pipe is destroyed)
Why cost of parts is hilariously high: Steam engines have better efficiency and density (many players seem to forget that one) than injector engines. So a higher initial costs makes it less overpowered. (In my opinion, the potential waste of energy is a major drawback of steam and justifies for its high potential power. But iirc Draba said that injector engines would be useless on designs that require a lot of power if steam doesn't have higher initial cost, which also makes sense.) Problem with new steam that can't be fixed:
Many old designs are broken due to low power output
Problems that can probably be fixed but I don't have a solution:
Inefficient steam engines are ridiculously bad (a bad steam engine is like 30 PPM and 50 PPV, while a good one is around 600 PPM and 110 PPV) (I tried to fix this and spent like 40 hours on that, but I only managed to make it easier to build a mediocre engine)
Cannot be simulated to calculate a stable power output, like fuel engines do (actually it's easy but would take a lot of time to do and I don't think it's necessary)
Another massive change is the detection rework which I also left a few questions for Ian AKA Blothorn to explain the system and how it works. Why a change was warranted:
Different types of detection weren't well balanced--for instance, visual components had better accuracy than IR and vastly better range.
Detection autoadjust used an incorrect formula, so optimizing adjustment was both mechanical and tedious.
Trackers having much better detection ranges than search sensors meant that detection was very binary--if you could see something at all you could usually get a precise lock (barring ECM, which was only counterable by large numbers of components).
Needing both sensors and munitions warners made reactive missile defence difficult on small vehicles.
There were a number of other inconsistencies/imbalances, e.g. some visual/IR sensors working through water, steam engines producing no heat, etc.
Overview of the new system: On the offensive side, each sensor type now has a role in which it is optimal, and large vehicles are best using a variety to cover their weaknesses. Visual probably remains the default for above-water detection--it remains impossible to reduce visual signature other than reducing size. IR is better against fast vehicles, as they have trouble avoiding high IR signatures from thrust and drag. Both visual and IR are weak in rangefinding (although coincidence rangefinders are adequate for most purposes); radar is correspondingly strong in range and weak in bearing, although it often offers better detection chances against vehicles that don't pay attention to radar stealth. On the defensive side, there are two approaches. Most obvious is signature reduction--while it is deliberately difficult to avoid detection entirely, reducing signature reduces detection chances and thus degrades opposing accuracy. At short ranges, however, this doesn't work well--detection chances are likely high regardless, and low errors at short range mean even sparse detections can give a good fix. Smoke and chaff can be useful here: they increase detection chance while adding a distance-independent error to opponent's visual and radar sensors, respectively. ECM, buoys, and radar guidance have also been reworked. Buoys are more powerful, becoming more accurate as they get closer to the target. While their base error is high, at long ranges a buoy at close range can beat the accuracy of any onboard sensor. If you worry about opponents’ buoys, ECM can now intermittently jam them--except if they are connected to their parent vehicle by a harpoon cable, in which case they don't need the vulnerable wireless connection. Most blueprints should need no modifications under the new system, although a few may want a few more or less GPP cards. The one exception is water interactions--IR cameras, laser rangefinders, and retroreflection sensors can no longer work through water, so submarines that used them underwater or vehicles that used them to detect submarines will need to replace them (likely with buoys). Vehicles that predominantly used visual detection should also consider adding a greater variety of sensors--in particular, visual camera trackers tied to AA mainframes should likely be replaced with IR cameras. Also, radars and cameras can take over missile and projectile detection (radar is required for projectile detection), so munitions warners can be removed/replaced with additional sensors. Last but not least a sweet little addition to our build menu prefabs. https://preview.redd.it/iqw1ymabu9t51.png?width=1920&format=png&auto=webp&s=aa1e3cdba6e1d62e07aef83caf0acad2a39249ed Please do make sure you go through the changelog as a hell of a lot has changed!
The Challenges of Designing a Modern Skill, Part 3
Okay, Wendy’s or Walgreens or whoever, I don’t care who you are, you’re listening to the rest.
Introduction to Part 3
Welcome back one last time to “The Challenges of Designing a Modern Skill,” a series where we discuss all aspects of skill design and development. In Part 1, we talked about OSRS’s history with skills, and started the lengthy conversation on Skill Design Philosophy, including the concepts of Core, Expansion, and Integration. This latter topic consumed the entirety of Part 2 as well, which covered Rewards and Motivations, Progression, Buyables, as well as Unconstructive Arguments. Which brings us to today, the final part of our discussion. In this Part 3, we’ll finish up Section 3 – Skill Design Philosophy, then move on to chat about the design and blog process. One last time, this discussion was intended to be a single post, but its length outgrew the post character limit twice. Therefore, it may be important to look at the previous two parts for clarity and context with certain terms. The final product, in its purest, aesthetic, and unbroken form, can be found here.
3-C – Skill Design Philosophy, Continued
3-12 - Balancing
What follows from the discussion about XP and costs, of course, is balancing: the bane of every developer. A company like Riot knows better than anyone that having too many factors to account for makes good balance impossible. Balancing new ideas appropriately is extremely challenging and requires a great respect for current content as discussed in Section 3-5 – Integration. Thankfully, in OSRS we only have three major balancing factors: Profit, XP Rate, and Intensity, and two minor factors: Risk and Leniency. These metrics must amount to some sense of balance (besides Leniency, which as we’ll see is the definition of anti-balance) in order for a piece of content to feel like it’s not breaking the system or rendering all your previous efforts meaningless. It’s also worthy to note that there is usually a skill-specific limit to the numerical values of these metrics. For example, Runecrafting will never receive a training method that grants 200k xp/hr, while for Construction that’s easily on the lower end of the scale. A basic model works better than words to describe these factors, and therefore, being the phenomenal artist that I am, I have constructed one, which I’ve dubbed “The Guthix Scale.” But I’ll be cruel and use words anyway.
Profit: how much you gain from a task, or how much you lose. Gain or loss can include resources, cosmetics, specialized currencies, good old gold pieces, or anything on that line.
XP Rate: how fast you gain XP.
Intensity: how much effort (click intensity), attention (reaction intensity), and thought (planning intensity) you need to put into the activity to perform it well.
Risk: how likely is the loss of your revenue and/or resource investment into the activity. Note that one must be careful with risk, as players are very good at abusing systems intended to encourage higher risk levels to minimize how much they’re actually risking.
Leniency: a measure for how imbalanced a piece of content can be before the public and/or Jagex nerfs it. Leniency serves as a simple modulator to help comprehend when the model breaks or bends in unnatural ways, and is usually determined by how enjoyable and abusable an activity is, such that players don’t want to cause an outrage over it. For example, Slayer has a high level of Leniency; people don’t mind that some Slayer tasks grant amazing XP Rates, great Profits, have middling Intensity, and low Risk. On the other hand, Runecrafting has low levels of Leniency; despite low Risk, many Runecrafting activities demand high Intensity for poor XP Rates and middling Profits.
In the end, don’t worry about applying specific numbers during the conceptual phase of your skill design. However, when describing an activity to your reader, it’s always useful if you give approximations, such as “high intensity” or “low risk,” so that they get an idea of the activity’s design goals as well as to guide the actual development of that activity. Don’t comment on the activity’s Leniency though, as that would be pretty pretentious and isn’t for you to determine anyway.
3-13 - Skill Bloat
What do the arts of weaving, tanning, sowing, spinning, pottery, glassmaking, jewellery, engraving, carving, chiselling, carpentry, and even painting have in common? In real life, there’s only so much crossover between these arts, but in Runescape they’re all simply Crafting. The distinction between what deserves to be its own skill or instead tagged along to a current skill is often arbitrary; this is the great challenge of skill bloat. The fundamental question for many skill concepts is: does this skill have enough depth to stand on its own? The developers of 2006 felt that there was sufficient depth in Construction to make it something separate from Crafting, even if the latter could have covered the former. While there’s often no clean cut between these skills (why does making birdhouses use Crafting instead of Construction?), it is easy to see that Construction has found its own solid niche that would’ve been much too big to act as yet another Expansion of Crafting. On the other hand, a skill with extremely limited scope and value perhaps should be thrown under the umbrella of a larger skill. Take Firemaking: it’s often asked why it deserves to be its own skill given how limited its uses are. This is one of those ideas that probably should have just been thrown under Crafting or even Woodcutting. But again, the developers who made early Runescape did not battle with the same ideas as the modern player; they simply felt like Firemaking was a good idea for a skill. Similarly, the number of topics that the Magic skill covers is so often broken down in other games, like Morrowind’s separation between Illusion, Conjuration, Alteration, Destruction, Mysticism, Restoration, Enchant, Alchemy (closer to Herblore), and Unarmored (closer to Strength and Defense). Why does Runescape not break Magic into more skills? The answer is simple: Magic was created with a much more limited scope in Runescape, and there has not been enough content in any specific magical category to justify another skill being born. But perhaps your skill concept seeks to address this; maybe your Enchantment skill takes the enchanting aspects of Magic away, expands the idea to include current imbues and newer content, and fully fleshes the idea out such that the Magic skill alone cannot contain it. Somewhat ironically, Magic used to be separated into Good and Evil Magic skills in Runescape Classic, but that is another topic. So instead of arguments about what could be thrown under another skill’s umbrella, perhaps we should be asking: is there enough substance to this skill concept for it to stand on its own, outside of its current skill categorization? Of course, this leads to a whole other debate about how much content is enough for a skill idea to deserve individuality, but that would get too deep into specifics and is outside the scope of this discussion.
3-14 - Skill Endgame
Runescape has always been a sandbox MMO, but the original Runescape experience was built more or less with a specific endgame in mind: killing players and monsters. Take the Runescape Classic of 2001: you had all your regular combat skills, but even every other skill had an endgame whose goal was helping combat out. Fishing, Firemaking, and Cooking would provide necessary healing. Smithing and Crafting, along with their associated Gathering skill partners, served to gear you up. Combat was the simple endgame and most mechanics existed to serve that end. However, since those first days, the changing endgame goals of players have promoted a vast expansion of the endgame goals of new content. For example, hitting a 99 in any non-combat skill is an endgame goal in itself for many players, completely separate from that skill’s combat relationship (if any). These goals have increased to aspects like cosmetic collections, pets, maxed stats, all quests completed, all diaries completed, all music tracks unlocked, a wealthy bank, the collection log, boss killcounts, and more. Whereas skills used to have a distinct part of a system that ultimately served combat, we now have a vast variety of endgame goals that a skill can be directed towards. You can even see a growth in this perspective as new skills were released up to 2007: Thieving mainly nets you valuable (or once valuable) items which have extremely flexible uses, and Construction has a strong emphasis on cosmetics for your POH. So when designing your new skill, contemplate what the endgame of your skill looks like. For example, if you are proposing a Gathering skill, what is the Production skill tie-in, and what is the endgame goal of that Production skill? Maybe your new skill Spelunking has an endgame in gathering rare collectibles that can be shown off in your POH. Maybe your new skill Necromancy functions like a Support skill, giving you followers that help speed along resource gathering, and letting you move faster to the endgame goal of the respective Production skill. Whatever it is, a proper, clear, and unified view of an endgame goal helps a skill feel like it serves a distinct and valuable purpose. Note that this could mean that you require multiple skills to be released simultaneously for each to feed into each other and form an appropriate endgame. In that case, go for it – don’t make it a repeat of RS3’s Divination, a Gathering skill left hanging without the appropriate Production skill partner of Invention for over 2 years. A good example of a skill with a direct endgame is… most of them. Combat is a well-accepted endgame, and traditionally, most skills are intended to lend a hand in combat whether by supplies or gear. A skill with a poor endgame would be Hunter: Hunter is so scattered in its ultimate endgame goals, trying to touch on small aspects of everything like combat gear, weight reduction, production, niche skilling tools, and food. There’s a very poor sense of identity to Hunter’s endgame, and it doesn’t help that very few of these rewards are actually viable or interesting in the current day. Similarly, while Slayer has a strong endgame goal it is terrible in its methodology, overshadowing other Production skills in their explicit purpose. A better design for Slayer’s endgame would have been to treat it as a secondary Gathering skill, to work almost like a catalyst for other Gathering-Production skill relationships. In this mindset, Slayer is where you gather valuable monster drops, combine it with traditional Gathering resources like ores from Mining, then use a Production skill like Smithing to meld them into the powerful gear that is present today. This would have kept other Gathering and Production skills at the forefront of their specialities, in contrast to today’s situation where Slayer will give fully assembled gear that’s better than anything you could receive from the appropriate skills (barring a few items that need a Production skill to piece together).
3-15 - Alternate Goals
From a game design perspective, skills are so far reaching that it can be tempting to use them to shift major game mechanics to a more favourable position. Construction is an example of this idea in action: Construction was very intentionally designed to be a massive gold sink to help a hyperinflating economy. Everything about it takes gold out of the game, whether through using a sawmill, buying expensive supplies from stores, adding rooms, or a shameless piece of furniture costing 100m that is skinned as, well, 100m on a shameless piece of furniture. If you’re clever about it, skills are a legitimately good opportunity for such change. Sure, the gold sink is definitely a controversial feature of Construction, but for the most part it’s organic and makes sense; fancy houses and fancy cosmetics are justifiably expensive. It is notable that the controversy over Construction’s gold sink mechanism is probably levied more against the cost of training, rather than the cost of all its wonderful aesthetics. Perhaps that should have been better accounted for in its design phase, but now it is quite set in stone. To emphasize that previous point: making large scale changes to the game through a new skill can work, but it must feel organic and secondary to the skill’s main purpose. Some people really disliked Warding because they felt it tried too hard to fix real, underlying game issues with mechanics that didn’t thematically fit or were overshadowing the skill’s Core. While this may or may not be true, if your new skill can improve the game’s integrity without sacrificing its own identity, you could avoid this argument entirely. If your skill Regency has a Core of managing global politics, but also happens to serve as a resource sink to help your failing citizens, then you’ve created a strong Core design while simultaneously improving the profitability of Gathering skills.
3-16 - The Combat No-Touch Rule
So, let’s take a moment to examine the great benefits and rationale of RS2’s Evolution of Combat: This space has been reserved for unintelligible squabbling. With that over, it’s obvious that the OSRS playerbase is not a big fan of making major changes to the combat system. If there’s anything that defines the OSRS experience, it has to be the janky and abusable combat system that we love. So, in the past 7 years of OSRS, how many times have you heard someone pitch a new combat skill? Practically no one ever has; a new combat skill, no matter how miniscule, would feel obtrusive to most players, and likely would not even receive 25% of votes in a poll. This goes right back to Section 3-5 – Integration, and the importance of preserving the fundamentals of OSRS’s design. I know that my intention with this discussion was to be as definitive about skill design as possible, and in that spirit I should be delving into the design philosophy specifically behind combat skills, but I simply don’t see the benefit of me trying, and the conversation really doesn’t interest me that much. It goes without saying that as expansive as this discussion is, it does not cover every facet of skill design, which is a limitation both of my capabilities and desire to do so.
3-17 - Aesthetics
I don’t do aesthetics well. I like them, I want them, but I do not understand them; there are others much better equipped to discuss this topic than I. Nonetheless, here we go. Since the dawn of OSRS, debates over art style and aesthetics have raged across Gielinor. After all, the OSRS Team is filled with modern day artists while OSRS is an ancient game. What were they supposed to do? Keep making dated graphics? Make content with a modernized and easily digestible style? Something in-between? While many players shouted for more dated graphics, they were approached by an interesting predicament: which dated graphics did they want? We had a great selection present right from the start of OSRS: 2002, 2003, 2004, 2005, 2006, and 2007. People hungry for nostalgia chose the era that they grew up in, leading to frequent requests for older models like the dragon or imp, most of which were denied by Jagex (except the old Mining rock models). But which era was OSRS supposed to follow? Jagex elected to carve their own path, but not without heavy criticism especially closer to OSRS’s conception. However, they adapted to player requests and have since gone back and fixed many of the blatant early offenders (like the Kingdom of Kourend) and adopted a more consistent flavour, one that generally respects the art style of 2007. Even though it doesn’t always hit the mark, one has to appreciate the OSRS artists for making their best attempt and listening to feedback, and here’s to hoping that their art style examination mentioned in June 2020’s Gazette bears fruit. But what exactly is the old school art style? There are simple systems by which most players judge it in OSRS, usually by asking questions like, “Would you believe if this existed in 2007?” More informed artists will start pointing out distinct features that permeated most content from back in the day, such as low quality textures, low poly models, low FPS animations, a “low fantasy” or grounded profile that appeals somewhat to realism, reducing cartoonish exaggerations, and keeping within the lore. Compiled with this, music and sound design help that art style come to life; it can be very hard on immersion when these don’t fit. An AGS would sound jarring if its special attack sounded like a weak dagger stab, and having to endure Country Jig while roaming Hosidius suddenly sweeps you off into a different universe. But coming back to skill design, the art, models, and sound design tend to be some of the last features, mostly because the design phase doesn’t demand such a complete picture of a skill. However, simple concept art and models can vastly improve how a skill concept is communicated and comfort players who are concerned about maintaining that “old school feel.” This will be touched on again later in this discussion under Section 5-2 – Presentation and Beta Testing.
3-18 - Afterword
Now we’ve set down the modern standards for a new skill, but the statements that started this section bear repeating: the formula we’ve established does not automatically make a good or interesting skill, as hard as we might have tried. Once again, harken back to the First Great Irony: that we are trying to inject the modern interpretation of what defines a skill upon a game that was not necessarily built to contain it. Therefore, one could just as easily deny each of the components described above, as popular or unpopular as the act might be, and their opinion could be equally valid and all this effort meaningless. Don’t take these guidelines with such stringency as to disregard all other views.
5-0 - The OSRS Team and the Design Process
If you’ve followed me all the way here, you’re likely A) exhausted and fed up of any conversation concerning new skills, or B) excited, because you’ve just struck an incredible skill idea (or perhaps one that’s always hung around your head) that happens to tick off all the above checkboxes. But unfortunately for you B types, it’s about to get pretty grim, because we’re going to go through every aspect of skill design that’s exterior to the game itself. We’ll be touching on larger topics like democracy, presentation, player mindsets, effort, and resource consumption. It’ll induce a fantastic bout of depression, so don’t get left behind.
5-1 - Designing a Skill
Thus far, Jagex has offered three potential skills to OSRS, each of which has been denied. This gives us the advantage of understanding how the skill design process works behind the scenes and lets us examine some of the issues Jagex has faced with presenting a skill to the players. The first problem is the “one strike and you’re out” phenomenon. Simply put, players don’t like applying much effort into reading and learning. They’ll look at a developer blog highlighting a new skill idea, and if you’re lucky they’ll even read the whole thing, but how about the second developer blog? The third? Fourth? Even I find it hard to get that far. In general, people don’t like long detail-heavy essays or blogs, which is why I can invoke the ancient proverb “Ban Emily” into this post and it’ll go (almost) completely unnoticed. No matter how many improvements you make between developer blogs, you will quickly lose players with each new iteration. Similarly, developer blogs don’t have the time to talk about skill design philosophy or meta-analyse their ideas – players would get lost far too fast. This is the Second Great Irony of skill design: the more iterations you have of a lengthy idea, the less players will keep up with you. This was particularly prominent with Warding: Battle Wards were offered in an early developer blog but were quickly cut when Jagex realized how bad the idea was. Yet people would still cite Battle Wards as the reason they voted against Warding, despite the idea having been dropped several blogs before. Similarly, people would often comment that they hated that Warding was being polled multiple times; it felt to them like Jagex was trying to brute-force it into the game. But Warding was only ever polled once, and only after the fourth developer blog - the confusion was drawn from how many times the skill was reiterated and from the length of the public design process. Sure, there are people for whom this runs the opposite way; they keep a close eye on updates and judge a piece of content on the merits of the latest iteration, but this is much less common. You could argue that one should simply disregard the ignorant people as blind comments don't contribute to the overall discussion, but you should remember that these players are also the ones voting for the respective piece of content. You could also suggest re-educating them, which is exactly what Jagex attempts with each developer blog, and still people won’t get the memo. And when it comes to the players themselves, can the playerbase really be relied on to re-educate itself? Overall, the Second Great irony really hurts the development process and is practically an unavoidable issue. What’s the alternative? To remove the developer-player interface that leads to valuable reiterations, or does you simply have to get the skill perfect in the first developer blog? It’s not an optimal idea, but it could help: have a small team of “delegates” – larger names that players can trust, or player influencers – come in to review a new, unannounced skill idea under NDA. If they like it, chances are that other players will too. If they don’t, reiterate or toss out the skill before it’s public. That way, you’ve had a board of experienced players who are willing to share their opinions to the public helping to determine the meat and potatoes of the skill before it is introduced to the casual eye. Now, a more polished and well-accepted product can be presented on the first run of selling a skill to the public, resulting in less reiterations being required, and demanding less effort from the average player to be fully informed over the skill’s final design.
5-2 - Presentation and Beta Testing
So you’ve got a great idea, but how are you going to sell it to the public? Looking at how the OSRS Team has handled it throughout the years, there’s a very obvious learning curve occurring. Artisan had almost nothing but text blogs being thrown to the players, Sailing started introducing some concept art and even a trailer with terrible audio recording, and Warding had concept art, in game models, gifs, and a much fancier trailer with in-game animations. A picture or video is worth a thousand words, and often the only words that players will take out of a developer blog. You might say that presentation is everything, and that would be more true in OSRS than most games. Most activities in OSRS are extremely basic, involve minimal thought, and are incredibly grindy. Take Fishing: you click every 20 seconds on a fishing spot that is randomly placed along a section of water, get rid of your fish, then keep clicking those fishing spots. Boiling it down further, you click several arbitrary parts of your computer screen every 20 seconds. It’s hardly considered engaging, so why do some people enjoy it? Simply put: presentation. You’re given a peaceful riverside environment to chill in, you’re collecting a bunch of pixels shaped like fish, and a number tracking your xp keeps ticking up and telling you that it matters. Now imagine coming to the players with a radical new skill idea: Mining. You describe that Mining is where you gather ores that will feed into Smithing and help create gear for players to use. The audience ponders momentarily, but they’re not quite sure it feels right and ask for a demonstration. You show them some gameplay, but your development resources were thin and instead of rocks, you put trees as placeholders. Instead of ores in your inventory, you put logs as placeholders. Instead of a pickaxe, your character is swinging a woodcutting axe as a placeholder. Sure, the mechanics might act like mining instead of woodcutting, but how well is the skill going to sell if you haven’t presented it correctly or respected it contextually? Again, presentation is everything. Players need to be able to see the task they are to perform, see the tools they’ll use, and see the expected outcomes; otherwise, whatever you’re trying to sell will feel bland and unoriginal. And this leads to the next level of skill presentation that has yet to be employed: Beta Worlds. Part of getting the feel of an activity is not just watching, it but acting it out as well - you’ll never understand the thrill of skydiving unless you’ve actually been skydiving. Beta Worlds are that chance for players to act out a concept without risking the real game’s health. A successful Beta can inspire confidence in players that the skill has a solid Core and interesting Expansions, while a failed Beta will make them glad that they got to try it and be fully informed before putting the skill to a poll (although that might be a little too optimistic for rage culture). Unfortunately, Betas are not without major disadvantages, the most prominent of which we shall investigate next.
5-3 - Development Effort
If you thought that the previous section on Skill Design Philosophy was lengthy and exhausting, imagine having to know all that information and then put it into practice.Mentally designing a skill in your head can be fun, but putting all that down on paper and making it actually work together, feel fully fleshed out, and following all the modern standards that players expect is extremely heavy work, especially when it’s not guaranteed to pay off in the polls like Quest or Slayer content. That’s not even taking into account the potentially immense cost of developing a new skill should it pass a poll. Whenever people complain that Jagex is wasting their resources trying to make that specific skill work, Jagex has been very explicit about the costs to pull together a design blog being pretty minimal. Looking at the previous blogs, Jagex is probably telling the truth. It’s all just a bunch of words, a couple art sketches, and maybe a basic in-game model or gif. Not to downplay the time it takes to write well, design good models, or generate concept art, but it’s nothing like the scale of resources that some players make it out to be. Of course, if a Beta was attempted as suggested last section, this conversation would take a completely new turn, and the level of risk to invested resources would exponentially increase. But this conversation calls to mind an important question: how much effort and resources do skills require to feel complete? Once upon a time, you could release a skill which was more or less unfinished. Take Slayer: it was released in 2005 with a pretty barebones structure. The fundamentals were all there, but the endgame was essentially a couple cool best-in-slot weapons and that was it. Since then, OSRS has updated the skill to include a huge Reward Shop system, feature 50% more monsters to slay, and to become an extremely competitive money-maker. Skills naturally undergo development over time, but it so often comes up during the designing of an OSRS skill that it "doesn't have enough to justify its existence." This was touched on deeply in Section 3-13 – Skill Bloat, but deserves reiterating here. While people recognize that skills continually evolve, the modern standard expects a new skill, upon release, to be fully preassembled before purchase. Whereas once you could get away with releasing just a skill's Core and working on Expansions down the line, that is no longer the case. But perhaps a skill might stand a better chance now than it did last year, given that the OSRS Team has doubled in number since that time. However, judging from the skill design phases that have previously been attempted (as we’ve yet to see a skill development phase), the heaviest cost has been paid in developer mentality and motivational loss. When a developer is passionate about an idea, they spend their every waking hour pouring their mind into how that idea is going to function,especially while they’re not at work. And then they’re obligated to take player feedback and adapt their ideas, sometimes starting from scratch, particularly over something as controversial as a skill. Even if they have tough enough skin to take the heavy criticism that comes with skill design, having to write and rewrite repeatedly over the same idea to make it “perfect” is mentally exhausting. Eventually, their motivation drains as their labour bears little fruit with the audience, and they simply want to push it to the poll and be done with it. Even once all their cards are down, there’s still no guarantee that their efforts will be rewarded, even less so when it comes to skills. With such a high mental cost with a low rate of success, you have to ask, “Was it worth it?” And that’s why new skill proposals are far and few between. A new skill used to be exciting for the development team in the actual days of 2007, as they had the developmental freedom to do whatever they wanted, but in the modern day that is not so much the case.
5-4 - The Problems of Democracy
Ever since the conceptualization of democracy in the real world, people have been very aware of its disadvantages. And while I don’t have the talent, knowledge, or time to discuss every one of these factors, there are a few that are very relevant when it comes to the OSRS Team and the polling process. But first we should recognize the OSRS Team’s relationship with the players. More and more, the Team acts like a government to its citizens, the players, and although this situation was intentionally instated with OSRS’s release, it’s even more prominent now. The Team decides the type of content that gets to go into a poll, and the players get their input over whether that particular piece makes it in. Similarly, players make suggestions to the Team that, in many cases, the Team hadn’t thought of themselves. This synergy is phenomenal and almost unheard of among video games, but the polling system changes the mechanics of this relationship. Polls were introduced to the burned and scarred population of players at OSRS’s release in 2013. Many of these players had just freshly come off RS2 after a series of disastrous updates or had quit long before from other controversies. The Squeal of Fortune, the Evolution of Combat, even the original Wilderness Removal had forced numerous players out and murdered their trust in Jagex. To try and get players to recommit to Runescape, Jagex offered OSRS a polling system by which the players would determine what went into the game, where the players got to hold all the cards. They also asked the players what threshold should be required for polled items to pass, and among the odd 50% or 55% being shouted out, the vast majority of players wanted 70%, 75%, 80%, or even 85%. There was a massive population in favour of a conservative game that would mostly remain untouched, and therefore kept pure from the corruption RS2 had previously endured. Right from the start, players started noticing holes in this system. After all, the OSRS Team was still the sole decider of what would actually be polled in the first place. Long-requested changes took forever to be polled (if ever polled at all) if the OSRS Team didn’t want to deal with that particular problem or didn’t like that idea. Similarly, the Team essentially had desk jobs with a noose kept around their neck – they could perform almost nothing without the players, their slave masters, seeing, criticizing, and tearing out every inch of developmental or visionary freedom they had. Ever hear about the controversy of Erin the duck? Take a look at the wiki or do a search through the subreddit history. It’s pretty fantastic, and a good window into the minds of the early OSRS playerbase. But as the years have gone on, the perspective of the players has shifted. There is now a much healthier and more trusting relationship between them and the Team, much more flexibility in what the players allow the Team to handle, and a much greater tolerance and even love of change. But the challenges of democracy haven’t just fallen away. Everyone having the right to vote is a fundamental tenet of the democratic system, but unfortunately that also means that everyone has the right to vote. For OSRS, that means that every member, whether it’s their first day in game, their ten thousandth hour played, those who have no idea about what the poll’s about, those who haven’t read a single quest (the worst group), those who RWT and bot, those who scam and lure, and every professional armchair developer like myself get to vote. In short, no one will ever be perfectly informed on every aspect of the game, or at least know when to skip when they should. Similarly, people will almost never vote in favour of making their game harder, even at the cost of game integrity, or at least not enough people would vote in such a fashion to reach a 75% majority. These issues are well recognized. The adoption of the controversial “integrity updates” was Jagex’s solution to these problems. In this way, Jagex has become even more like a government to the players. The average citizen of a democratic country cannot and will not make major decisions that favour everyone around themselves if it comes at a personal cost. Rather, that’s one of the major roles of a government: to make decisions for changes for the common good that an individual can’t or won’t make on their own. No one’s going to willingly hand over cash to help repave a road on the opposite side of the city – that’s why taxes are a necessary evil. It’s easy to see that the players don’t always know what’s best for their game and sometimes need to rely on that parent to decide for them, even if it results in some personal loss. But players still generally like the polls, and Jagex still appears to respect them for the most part. Being the government of the game, Jagex could very well choose to ignore them, but would risk the loss of their citizens to other lands. And there are some very strong reasons to keep them: the players still like having at least one hand on the wheel when it comes to new content or ideas. Also, it acts as a nice veto card should Jagex try to push RS3’s abusive tactics on OSRS and therefore prevent such potential damage. But now we come to the topic of today: the introduction of a new skill. Essentially, a new skill must pass a poll in order to enter the game. While it’s easy to say, “If a skill idea is good enough, it’ll pass the threshold,” that’s not entirely true. The only skill that could really pass the 75% mark is not necessarily a well-designed skill, but rather a crowd-pleasing skill. While the two aren’t mutually exclusive, the latter is far easier to make than the former. Take Dungeoneering: if you were to poll it today as an exact replica of RS2’s version, it would likely be the highest scoring skill yet, perhaps even passing, despite every criticism that’s been previously emphasized describing why it has no respect for the current definition of “skill.” Furthermore, a crowd-pleasing skill can easily fall prey to deindividualization of vision and result in a bland “studio skill” (in the same vein as a “studio film”), one that feels manufactured by a board of soulless machines rather than a director’s unique creation. This draws straight back to the afore-mentioned issues with democracy: that people A) don’t always understand what they’re voting for or against, and B) people will never vote for something that makes their game tougher or results in no benefit to oneself. Again, these were not issues in the old days of RS2, but are the problems we face with our modern standards and decision making systems. The reality that must be faced is that the polling system is not an engine of creation nor is it a means of constructive feedback – it’s a system of judgement, binary and oversimplified in its methodology. It’s easy to interact with and requires no more than 10 seconds of a player’s time, a mere mindless moment, to decide the fate of an idea made by an individual or team, regardless of their deep or shallow knowledge of game mechanics, strong or weak vision of design philosophy, great or terrible understanding of the game’s history, and their awareness of blindness towards the modern community. It’s a system which disproportionately boils down the quality of discussion that is necessitated by a skill, which gives it the same significance as the question “Should we allow players to recolour the Rocky pet by feeding it berries?” with the only available answers being a dualistic “This idea is perfect and should be implemented exactly as outlined” or “This idea is terrible and should never be spoken of again.” So what do you do? Let Jagex throw in whatever they want? Reduce the threshold, or reduce it just for skills? Make a poll that lists a bunch of skills and forces the players to choose one of them to enter the game? Simply poll the question, “Should we have a new skill?” then let Jagex decide what it is? Put more options on the scale of “yes” to “no” and weigh each appropriately? All these options sound distasteful because there are obvious weaknesses to each. But that is the Third Great Irony we face: an immense desire for a new skill, but no realistic means to ever get one.
6-0 - Conclusion
I can only imagine that if you’ve truly read everything up to this point, it’s taken you through quite the rollercoaster. We’ve walked through the history of OSRS skill attempts, unconstructive arguments, various aspects of modern skill design philosophy, and the OSRS Team and skill design process. When you take it all together, it’s easy to get overwhelmed by all the thought that needs to go into a modern skill and all the issues that might prevent its success. Complexity, naming conventions, categorizations, integration, rewards and motivations, bankstanding and buyables, the difficulties of skill bloat, balancing, and skill endgames, aesthetics, the design process, public presentation, development effort, democracy and polling - these are the challenges of designing and introducing modern skills. To have to cope with it all is draining and maybe even impossible, and therefore it begs the question: is trying to get a new skill even worth it? Maybe. Thanks for reading. Tl;dr: Designing a modern skill requires acknowledging the vast history of Runescape, understanding why players make certain criticisms and what exactly they’re saying in terms of game mechanics, before finally developing solutions. Only then can you subject your ideas to a polling system that is built to oversimplify them.
(This is kinda lengthy, but a TL;DR can be found below.) I, 25F, just got out of my first ever relationship about three months ago. The relationship wasn't anything to write home about and although my ex is not a bad guy, I am glad the relationship is over. In saying that, for the short time we were together, it also opened my eyes to a lot of things. One of which being my sexual and/or romantic orientation, something I've been pretty nonchalant about nearly my whole entire life. Thinking back even before this relationship, I have had a few instances in my life where I've questioned my sexual orientation because for me it feels like such a grey area. If I talked about this from day one, I'd be writing you guys a book because it's amazing how clear things become when you finally find something you identify with. When you finally find something that let's you say, okay I'm not weird and this is actually a thing and there's a word for it. I guess that's how I'm feeling now. Over the past 2-3 years, I have been trying to be more open and honest with myself as I am currently on a journey of self-discovery and introspection. I have opened up to the possibility that I might not be Straight despite identifying myself as such by default when the topic is brought up. It just never felt right and as someone who comes from a household with parents that are religious, being anything other than Heterosexual just wasn't an option. So I guess, here's kinda my thought process and what went into me basically going through every single orientation to get to Demisexuality because... apparently, nothing else made sense.
Homosexuality or Bisexuality? I ruled these two possibilities out because although I have had small crushes on two of my female friends (one of which I'm no longer friends with) in the past, I did not realistically see myself pursuing a romantic relationship with them. I realized that I only really questioned my feelings for them when we started getting close and had established a strong emotional connection. I liked being around them because I felt like I could talk to them comfortably about anything and they appealed to my mind. However, I did not want to have sex with them nor did I want to make out with them or... be physical with them in any sort of way. It was merely a "friend crush" aka alterous attraction, a term I discovered after trying to google how I felt.
Pansexuality? I've never really indentified with any aspects of this, despite me joking to my friends that I just won't have a sexuality and I'll be attracted to whatever. However, on a more serious note, while I can like both women and men romantically on some level, I don't see myself dating someone who is Transgender or Non-Binary. With those affirmations in mind, that automatically ruled out pansexuality as an option for me as I figured that was the only distinction between that and Bisexuality. (Feel free to correct me if I'm wrong here!)
Asexuality? I definitely still feel as if I might be somewhere on this spectrum, but I am not particularly sure where or if I am. I don't have enough sexual experience to confidently say that I am asexual, but I'm not ruling it out as a possibility. For as long as I can remember, I've just never been an overly sexual person. Actually, I've never really seen myself as a sexual being in general and my thoughts are rarely of sex. I do enjoy the occasional dirty joke or NSFW meme, but anything outside of that realm and I'm completely uninterested. I don't ever feel the need to pleasure myself or have others do it for me. I don't think I've ever been "sexually frustrated" and I'm not even sure that I've ever found someone sexually attractive. With that said, I have also never had sex before and I feel that I won't truly know how I feel about sexual experiences until I actually cross that threshold... if I ever do.
It's been a long time coming, but I think I can almost confidentally say that I am most likely Demisexual. I didn't come to this realization until a few hours ago after getting out of a call with one of my guy friends. I told him the story of a guy I met two years ago on Tinder that I grew to really like and compared my feelings for him to my feelings with my most recent ex. With Tinder guy, we met and hit it off right away. However, he made it clear that he was not open to a serious relationship as he'd just gotten out of a long term one. He said that he was looking for a FWB arrangement and I admitted that I wanted something more serious, so we agreed it would be best for us to be friends. He tried on several occasions throughout our friendship to pursuade me to take up his offer, but every time I would say no. He was never pushy about it and always respected my boundaries. Although I found it somewhat annoying that he would ask from time to time, it wasn't overbearing to the point of ruining our friendship and that aside, we had a pretty good friendship. In the few months that we were friends, we would go out to eat and play games together. I even went to his workplace a couple of times (he owned his own restaurant) and help him clean up or just talk to him to pass the time before closing. Although I did find him very physically attractive, it wasn't until we were chatting one day that he said, "you know, I think we have really good chemistry" that I realized it was much more than that. I felt 110% comfortable with him as a person and looking back, we had an amazing emotional connection too. The more we hung out and got to know each other, the more I found myself wanting to take up his offer to become his FWB. Even though that was not something I was initially interested in, because our emotional connection was so strong (and a combination of other boxes he checked), I was genuinely considering having sex with this guy. When it came to my ex, we had a lot of things in common as far as interests go and our values seemed to line up for the most part. He was a total gentleman and I felt that he would have done anything for me if I asked him to. We spent a lot of time together trying to get to know each other and after about a month, decided to get into a relationship. From the start, things felt a little off to me but I wasn't particularly sure why. I didn't have a spark when it came to him and although I was somewhat excited to see him, I was also very nervous and when we were together it just felt very lukewarm. We continued seeing each other and even tried to get intimate a handful of times and I just wasn't feeling it... at all. I quickly realized that while I did find him physically attractive, we lacked any sort of chemistry or emotional connection. I feel like the average person would have probably been jumping for joy to get him in bed or at least be somewhat intimate with him, but for me because we had no emotional connection... I just couldn't feel anything for him past friendship and even now, I don't know that I would be friends with him either. He didn't make me feel the way the Tinder guy did and even though I had ample oppurtunity to have sex with him, I didn't want to because he didn't give me those urges. This is what made me realize that I may be less of an asexual and more of a demisexual. To me, being sexual with someone is almost like a glass. Only after that glass has been filled up (with comfort and emotional connection) can I see people in a sexual light. It doesn't matter how physically attractive I might find them or how many of my boxes they check. If the emotional connection isn't there or if it doesn't manifest within a certain amount of time, no attraction will develop and if it does, it will merely be aesthetic. TL;DR - I've always known that I wasn't Straight and considered the possibility of being Asexual but that didn't feel right either. After accessing my relationship with both my ex and a former friend I met from Tinder, I realized that I am most likely Demisexual. This realization was made when I realized that I was not sexually attracted to my ex-boyfriend mostly because we did not have any sort of emotional connection with each other. If anyone has anything to add or has been in a similar situation, please feel free to comment and let me know. I'm still new to all of this and I'm still trying to figure myself out, so any words of wisdom or stories from personal experience are welcome.
I was pondering RPG design and realized I'm not really sure which kind of skill check implementation I personally prefer. From what I can recall, there's a handful of aspects and approaches devs usually take, the ways the check itself works:
deterministic binary - either your skill > X or it isn't
perk-based - like above, but requires you to possess a specific perk instead of numerical skill value
classic rolling - modify skill with randomly generated number, compare with X.
multi-stage resolution - no matter how you determine the result (1/2/3), it results in more than just pass/fail scenarios depending on how your skill value ends up
And also different ways to present them:
secret - you won't know the interaction is even possible unless you select the skill and apply on the item / activate it at the right moment in conversation
hidden - the player is not aware of the option unless they meet the requirements
visible but unavailable - the game tells you there's this option but doesn't let you pick it unless you meet requirements
visible and available - you always have the option, even if using it is automatically going to fail
surprise - the game doesn't warn you upfront, just shows you after it happens (like a DM suddenly teling you to roll for charisma after you do something)
And of course the option of telling players the difficulty of what they're attempting, either by spelling out the numbers or color-coding the options (is there a game that never tells you the difficulty of a test?). So, which of those approaches do you prefer to see in games and why? And what approaches did I miss? To kick things off, I'm more of a fan of deterministic checks, but it does invite problems in that not every skill point may matter (e.g. if the checks are always a multiple of 5, then raising your skill by 4 points does nothing). And I appreciate the meta-gaming view of seeing the option being there even when my character is too stupid for it, but it probablyt hurts replayability somewhat when you can see instead of experiment. I would, however, never actually select an option knowing I'd fail, because I don't tend to roleplay like that. I am also not a hardcore gamer who enjoys failing, so I prefer knowing the difficulty of what I'm trying to do.
As the title says, I've been thinking about a couple of ideas that I think would make the kiss package manager just a bit nicer to use, as great as it already is.
A description file with a short description of the package.
Running kiss s would then match against and display the description for each package. This would make discovering packages easier if you want something general but don't already want something specific (such as wanting a music player, for example). It could also help users more quickly understand what the dependencies of a package do and what they are "automatically" installing.
A provides file to allow for dependencies on executables instead of specific packages (similar to what Arch Linux has).
For example, this would allow having a binary package alternative to a package that takes a while to compile, or a git/nightly/etc. alternative to a package that tracks the stable version (in my case, I use nightly Rust and it would be nice to not have to override the official rust package locally). When installing a package with a dependency with multiple alternatives, the package manager could then prompt the user to decide which alternative to use. This file would preferably be created by kiss through a command similar to kiss c after building a package and seeing which files have the executable permission set. Thanks to kiss a, multiple packages that are alternatives to each other could be installed at the same time and be swapped at will, unlike in Arch Linux. Adding an alternatives feature could also mean that different repositories no longer have to shadow packages depending on their order in $KISS_PATH.
Optional dependencies (both make and normal) and features.
This would be nice so that users don't have to copy a package to enable a feature that the maintainer didn't enable themselves. Obviously the maintainer would have to provide the ability to enable the feature, but this makes it easier for the user to enable what they care about and disable what they don't. For an example where this would be useful, the openssh package in community doesn't compile with libedit support. This means that anyone using sftp will have a bad time as tab-completion among other things aren't supported. I currently have my own version of the package where all I did was add libedit to depends and --with-libedit to build, but this is not something I want to have to maintain myself when an "official" package exists.
The option to save and reuse the build directory of a package that failed to build.
This would be extremely helpful in the event that an issue that is easily fixable occurs (maintainer forgot to add a package as a dependency and the user was missing it, or sudo timing out waiting for a password when not configured to wait indefinitely, for some examples). There's been a few times where I spent a long time compiling a package only for it to fail for a dumb reason and then had to start compiling again from the start. Tell me what you think about these ideas (maybe some of them aren't KISS enough) and I'd love to hear other ideas that people may have.
Ethereum on ARM. New Eth2.0 Raspberry Pi 4 image for joining the Medalla multi-client testnet. Step-by-step guide for installing and activating a validator (Prysm, Teku, Lighthouse and Nimbus clients included)
TL;DR: Flash your Raspberry Pi 4, plug in an ethernet cable, connect the SSD disk and power up the device to join the Eth2.0 medalla testnet. The image takes care of all the necessary steps to join the Eth2.0 Medalla multi-client testnet , from setting up the environment and formatting the SSD disk to installing, managing and running the Eth1.0 and Eth2.0 clients. You will only need to choose an Eth2.0 client, start the beacon chain service and activate / run the validator. Note: this is an update for our previous Raspberry Pi 4 Eth2 image  so some of the instructions are directly taken from there.
Based on Ubuntu 20.04 64bit.
Automatic USB disk partitioning and formatting
Adds swap memory (ZRAM kernel module + a swap file)
Changes the hostname to something like “ethnode-e2a3e6fe” based on MAC hash
Automatically syncs Eth1 Goerli testnet (Geth)
Includes an APT repository for installing and upgrading Ethereum software
Includes 4 Eth2.0 clients
Includes EF eth2.0-deposit-cli tool
Includes 5 monitoring dashboards based on Grafana / Prometheus
Geth: 1.9.20  (official binary) configured for syncing Goerli Testnets
Eth2.0-deposit-cli: 0.2.1 (bundled) 
Prysm: 1.0.0alpha24 
Beacon Chain (official binary)
Validator binary (official binary)
Teku: 0.12.4alpha+20200821 (compiled) 
Lighthouse 0.2.8 (official binary) 
Nimbus 0.5.0 (compiled) 
Grafana 7.0.4 (official package) 
INSTALLATION GUIDE AND USAGE
RECOMMENDED HARDWARE AND SETUP
Raspberry 4 (model B) - 4GB or 8GB (8 GB RAM highly recommended)
MicroSD Card (16 GB Class 10 minimum)
SSD USB 3.0 disk (see storage section)
A case with heatsink and fan (Optional but strongly recommended)
USB keyboard, Monitor and HDMI cable (micro-HDMI) (Optional)
STORAGE You will need an SSD to run the Ethereum clients (without an SSD drive there’s absolutely no chance of syncing the Ethereum blockchain). There are 2 options: Use an USB portable SSD disk such as the Samsung T5 Portable SSD. Use an USB 3.0 External Hard Drive Case with a SSD Disk. In our case we used a Inateck 2.5 Hard Drive Enclosure FE2011. Make sure to buy a case with an UASP compliant chip, particularly, one of these: JMicron (JMS567 or JMS578) or ASMedia (ASM1153E). In both cases, avoid getting low quality SSD disks as it is a key component of your node and it can drastically affect the performance (and sync times). Keep in mind that you need to plug the disk to an USB 3.0 port (in blue). IMAGE DOWNLOAD AND INSTALLATION 1.- Download the image: http://www.ethraspbian.com/downloads/ubuntu-20.04.1-preinstalled-server-arm64+raspi-eth2-medalla.img.zip SHA256 149cb9b020d1c49fcf75c00449c74c6f38364df1700534b5e87f970080597d87 2.- Flash the image Insert the microSD in your Desktop / Laptop and download the file. Note: If you are not comfortable with command line or if you are running Windows, you can use Etcher  Open a terminal and check your MicroSD device name running: sudo fdisk -l You should see a device named mmcblk0 or sdd. Unzip and flash the image: unzip ubuntu-20.04.1-preinstalled-server-arm64+raspi-eth2-medalla.img.zip sudo dd bs=1M if=ubuntu-20.04.1-preinstalled-server-arm64+raspi.img of=/dev/mmcblk0 conv=fdatasync status=progress 3.- Insert de MicroSD into the Raspberry Pi 4. Connect an Ethernet cable and attach the USB SSD disk (make sure you are using a blue port). 4.- Power on the device The Ubuntu OS will boot up in less than one minute but you will need to wait approximately 7-8 minutes in order to allow the script to perform the necessary tasks to install the Medalla setup (it will reboot again) 5.- Log in You can log in through SSH or using the console (if you have a monitor and keyboard attached)
User: ethereum Password: ethereum
You will be prompted to change the password on first login, so you will need to log in twice. 6.- Forward 30303 port in your router (both UDP and TCP). If you don’t know how to do this, google “port forwarding” followed by your router model. You will need to open additional ports as well depending on the Eth2.0 client you’ve chosen. 7.- Getting console output You can see what’s happening in the background by typing: sudo tail -f /valog/syslog 8.- Grafana Dashboards There are 5 Grafana dashboards available to monitor the Medalla node (see section “Grafana Dashboards” below).
The Medalla Eth2.0 multi-client testnet
Medalla is the official Eth2.0 multi-client testnet according to the latest official specification for Eth2.0, the v0.12.2  release (which is aimed to be the final) . In order to run a Medalla Eth 2.0 node you will need 3 components:
An Eth1.0 node running the Goerli testnet in sync . Geth in our case.
An Eth2.0 Beacon Chain connected to the Eth1.0 node. You will need to choose a client here (Prysm, Lighthouse, Teku or Nimbus)
An Eth2.0 Validator connected to the Beacon Chain (same client as the Beacon Chain)
The image takes care of the Eth1.0 setup. So, once flashed (and after a first reboot), Geth (Eth1.0 client) starts to sync the Goerli testnet. Follow these steps to enable your Eth2.0 Ethereum node: CREATE THE VALIDATOR KEYS AND MAKE THE DEPOSIT We need to get 32 Goerli ETH (fake ETH) ir order to make the deposit in the Eth2.0 contract and run the validator. The easiest way of getting ETH is by joining Prysm Discord's channel. Open Metamask , select the Goerli Network (top of the window) and copy your ETH Address. Go to: https://discord.com/invite/YMVYzv6 And open the “request-goerli-eth” channel (on the left) Type: !send $YOUR_ETH_ADDRESS (replace it with the one copied on Metamask) You will receive enough ETH to run 1 validator. Now it is time to create your validator keys and the deposit information. For your convenience we’ve packaged the official Eth2 launchpad tool . Go to the EF Eth2.0 launchpad site: https://medalla.launchpad.ethereum.org/ And click “Get started” Read and accept all warnings. In the next screen, select 1 validator and go to your Raspberry Pi console. Under the ethereum account run: cd && deposit --num_validators 1 --chain medalla Choose your mnemonic language and type a password for keeping your keys safe. Write down your mnemonic password, press any key and type it again as requested. Now you have 2 Json files under the validator_keys directory. A deposit data file for sending the 32 ETH along with your validator public key to the Eth1 chain (goerli testnet) and a keystore file with your validator keys. Back to the Launchpad website, check "I am keeping my keys safe and have written down my mnemonic phrase" and click "Continue". It is time to send the 32 ETH deposit to the Eth1 chain. You need the deposit file (located in your Raspberry Pi). You can, either copy and paste the file content and save it as a new file in your desktop or copy the file from the Raspberry to your desktop through SSH. 1.- Copy and paste: Connected through SSH to your Raspberry Pi, type: cat validator_keys/deposit_data-$FILE-ID.json (replace $FILE-ID with yours) Copy the content (the text in square brackets), go back to your desktop, paste it into your favourite editor and save it as a json file. Or 2.- Ssh: From your desktop, copy the file: scp [email protected]$YOUR_RASPBERRYPI_IP:/home/ethereum/validator_keys/deposit_data-$FILE_ID.json /tmp Replace the variables with your data. This will copy the file to your desktop /tmp directory. Upload the deposit file Now, back to the Launchpad website, upload the deposit_data file and select Metamask, click continue and check all warnings. Continue and click “Initiate the Transaction”. Confirm the transaction in Metamask and wait for the confirmation (a notification will pop up shortly). The Beacon Chain (which is connected to the Eth1 chain) will detect this deposit (that includes the validator public key) and the Validator will be enabled. Congrats!, you just started your validator activation process. CHOOSE AN ETH2.0 CLIENT Time to choose your Eth2.0 client. We encourage you to run Lighthouse, Teku or Nimbus as Prysm is the most used client by far and diversity is key to achieve a resilient and healthy Eth2.0 network. Once you have decided which client to run (as said, try to run one with low network usage), you need to set up the clients and start both, the beacon chain and the validator. These are the instructions for enabling each client (Remember, choose just one Eth2.0 client out of 4): LIGHTHOUSE ETH2.0 CLIENT 1.- Port forwarding You need to open the 9000 port in your router (both UDP and TCP) 2.- Start the beacon chain Under the ethereum account, run: sudo systemctl enable lighthouse-beacon sudo systemctl start lighthouse-beacon 3.- Start de validator We need to import the validator keys. Run under the ethereum account: lighthouse account validator import --directory=/home/ethereum/validator_keys Then, type your previously defined password and run: sudo systemctl enable lighthouse-validator sudo systemctl start lighthouse-validator The Lighthouse beacon chain and validator are now enabled PRYSM ETH2.0 CLIENT 1.- Port forwarding You need to open the 13000 and 12000 ports in your router (both UDP and TCP) 2.- Start the beacon chain Under the ethereum account, run: sudo systemctl enable prysm-beacon sudo systemctl start prysm-beacon 3.- Start de validator We need to import the validator keys. Run under the ethereum account: validator accounts-v2 import --keys-dir=/home/ethereum/validator_keys Accept the default wallet path and enter a password for your wallet. Now enter the password previously defined. Lastly, set up your password and start the client: echo "$YOUR_PASSWORD" > /home/ethereum/validator_keys/prysm-password.txt sudo systemctl enable prysm-validator sudo systemctl start prysm-validator The Prysm beacon chain and the validator are now enabled. TEKU ETH2.0 CLIENT 1.- Port forwarding You need to open the 9151 port (both UDP and TCP) 2.- Start the Beacon Chain and the Validator Under the Ethereum account, check the name of your keystore file: ls /home/ethereum/validator_keys/keystore* Set the keystore file name in the teku config file (replace the $KEYSTORE_FILE variable with the file listed above) sudo sed -i 's/changeme/$KEYSTORE_FILE/' /etc/ethereum/teku.conf Set the password previously entered: echo "yourpassword" > validator_keys/teku-password.txt Start the beacon chain and the validator: sudo systemctl enable teku sudo systemctl start teku The Teku beacon chain and validator are now enabled. NIMBUS ETH2.0 CLIENT 1.- Port forwarding You need to open the 19000 port (both UDP and TCP) 2.- Start the Beacon Chain and the Validator We need to import the validator keys. Run under the ethereum account: beacon_node deposits import /home/ethereum/validator_keys --data-dir=/home/ethereum/.nimbus --log-file=/home/ethereum/.nimbus/nimbus.log Enter the password previously defined and run: sudo systemctl enable nimbus sudo systemctl start nimbus The Nimbus beacon chain and validator are now enabled. WHAT's NEXT Now you need to wait for the Eth1 blockchain and the beacon chain to get synced. In a few hours the validator will get enabled and put into a queue. These are the validator status that you will see until its final activation:
DEPOSITED (the beacon chain detected the 32 ETH deposit with your validator public key)
PENDING (you are in a queue for being activated)
Finally, it will get activated and the staking process will start. Congratulations!, you join the Medalla Eth2.0 multiclient testnet!
We configured 5 Grafana Dashboards to let users monitor both Eth1.0 and Eth2.0 clients. To access the dashboards just open your browser and type your Raspberry IP followed by the 3000 port:
Lots of info here. You can see for example if Geth is in sync by checking (in the Blockchain section) if Headers, Receipts and Blocks fields are aligned or find Eth2.0 chain info.
Updating the software
We will be keeping the Eth2.0 clients updated through Debian packages in order to keep up with the testnet progress. Basically, you need to update the repo and install the packages through the apt command. For instance, in order to update all packages you would run: sudo apt-get update && sudo apt-get install geth teku nimbus prysm-beacon prysm-validator lighthouse-beacon lighthouse-validator Please follow us on Twitter in order to get regular updates and install instructions. https://twitter.com/EthereumOnARM
Binary options robots could serve as an excellent binary trading solution, available to traders worldwide. One of the main reasons behind the popularity of trading binary options, is the fact that traders know possible gain or possible loss entailed in the predicament they opted for. Trading binary options may have many advantages, such as the possibility of using a variety of features and ... Automated Binary is a relatively new automated binary options trading system. As with any new system, there may be some hesitation as to whether this system is an accurate and legit or perhaps a scam like so many other trading platforms. In our following review, we will rate this system and give you our honest The software will normally recommend binary options brokers to open an account and deposit with. Programme The Software. We don't mean that you need to be a programmer to operate the software, but you do need to tell it what you want. Set your technical indicators which will include your investing limits, frequency etc. then leave the rest to the auto trader software. Sit Back, Relax And Enjoy ... There are many automatic binary options trading systems available, but not all are created equal. The largest percentage of these automatic trading systems do not give the trader any control over the settings that their system will use in performing trades on the investor’s account. Yes, the trader may be able to set the amount of each trade, but other than that, they have no control over ... Best Automated IQoption Bot with high 80% win rate and Money management. Trade using our Proven Binary Option Secret Strategy. Semi-automatic robots for binary options. Semi-automatic robots (or counselors) are famous for their market analysis and prompt the trader regarding favorable signals for the buying/selling of an option. A user estimates a situation and makes a decision about entering in the position or ignoring a signal. That’s why robots have a disadvantage: without the command of a trader, a deal can’t ... Binary options auto trading is quite famous among both professional and young online investors.Yet, many of them try to get the opinions of the market leaders towards it. As a lack of financial literacy and opposing views in the trader’s network lead to the doubts of the effectiveness of these trading bots. The Binary Options Auto Trading Money Generator Benefits of Binary Options Auto Trading The Cons of Binary Options Auto Trading Choosing between Auto Trading or Signals Binary Options Auto Trading Scams It is likely that you will have heard the word ‘scam’ connected with automatic binary trading software. However, although there are some ... Risk warning: "Binary options are not promoted or sold to retail EEA traders" If the broker is not authorized in your area, e.g. IQ Option, OlympTrade (Eurozone / Usa), you can choose from our Broker Comparison (reliable brokers who accept traders from all over the world, following image): If you sign up with one of our brokers above you will have access to a number of free trading systems, as ... Binary options trading have been made easier with auto-trading solutions and applications. Automated trading is essentially a tri-party arrangement. The binary options broker has an arrangement with a trading advisor to advise preferred options trades for its trading account holders. Whenever the advisor enters a trade or suggests so, the trades are automatically replicated in your account’s ...
Hey there! Today we bring you a new video tutorial. This time, we show you arround the different configurations that our platform allows. Thanks to this func... Canal destinado a compartilhar os vídeos do Catalogador Automático de opções Binárias para operação nas corretoras IQOption, Binomo, Binary, Alpary, Spectru,... Ist der Binäre Optionen AutoTrader der richtige Signalgeber für Anfänger? - Leider ist der Autotrader nichtmehr verfügbar, hier finden Sie die alternative zu... Binary Option Robot is an automated software that trades automatically the Binary Option Market Online. It is simply the Best Binary Option Robot, it is very... Binary Options Robot - Automated Binary Options Trading Using Binary Option Robot Test Binary Options Robot here - http://track.logic.expert/67b0b668-c6a4-42... More info here: http://bit.ly/1k19nbs Automatic Binary Options Review Binary Option Robot Auto Trading Software. Watch later. Share. Copy link. Info. Shopping. Tap to unmute. If playback doesn't begin shortly, try restarting your device. Up Next. Auto Binary Signals Testbericht : Auto Binary Signals : http://go.binary-options-pro.com/autobinary gehören zu den besten Handelssignalen für binäre Optionen... Binary Options Robot Scams. http://www.financial-spread-betting.com/ PLEASE LIKE AND SHARE THIS VIDEO SO WE CAN DO MORE! This is a warning on auto trading so...