⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠ !!! WARNING !!! This Number Evolution may contain popups, jumpscares, scary sound effects, scary audio, scary images and insulting content. If you're under the age of 11, or if you get scared easily, or if you are sensitive to flashing colors, DO NOT WATCH THIS PROJECT!!! Oh and one more warning: This Number Evolution will contain 13 and 666, the devilish numbers! If you are unlucky to these numbers and don't want to see them, you can look away, shut your eyes, or stop watching this project. Otherwise, you may watch at your own risk, but don't say I didn't warn you... ⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠ Increasing Effort Barney Error Number Evolution This is the first Number Evolution and IENE related to Barney Errors. Barney Errors generally don't make sense, but the few ones that do truly represent what computer viruses can do to your computer. What typically happens in Barney Errors is that an incredibly outdated operating system is interrupted for a Barney Error. The narrator explains that Barney was killed by another fictional character, and a bomb has been placed inside his lair for an absurdly long time, instead of 5 minutes. The amount of chances can vary, with some within the hundreds range. In the Barney Error, it's somehow so important that every computer and game system was hacked to give everyone in that universe the message. Obviously, the user doesn't know anything better to do, and shuts off the computer. When the computer boots back up, it returns to the error as it (maybe) hacked into the MBR. After more and more turn offs, the background will change into more of a creepypasta-like background and the time will decrease. More and more methods of "counting as a turnoff" happen, and Barney becomes more and more evil. Jumpscares may also happen from time-to-time and once the user wastes all their chances, a "coding time" will happen. The code will always be "4 8 15 16 23 42", the obligatory Lost reference, but in the endings apart from the "Good Ending", the user always gets it wrong, and they face non-sensical punishments, that even lead to things like dragging the computer to the underworld and knowing the user's location. In the "Good Ending", the user gets the code right, and they are guaranteed they won't get any errors again. There are many different styles of Barney Errors, and they will be showcased in this NE. So, basically, you need to evolve the number and increase the effort while making the NE look like a Barney Error. current number: 0 effort level: -∞ effort percentage: N/A effort version: N/A training time: 0 seconds (go off NO!'s numbers 0 to 1 (through the small numbers) for what to change this to next) what's changed: We interrupt your blank project for a Barney Error. Past this border is the original description of the project. ==============================
