#but instead adding the generational inheritance element to getting the powers with them originally being intended for Billy’s father | Explore Tumblr posts and blogs

shellheadtm-a · 5 years ago

Text

i’m stealing the idea of a topical mcu/616 differences list from @suprnovas because while i know i’ve done them before, they’re scattered and scattered brain and picking through it by topic is a good idea. and this is more, obviously, for people who may not realize that 616 tony stark is an entirely different character from mcu tony, in terms of personality and the way his life has played out, and that’s important to me to point that out.

arc reactor / rt node - mcu tony had an arc reactor, a miniaturized nuclear battery, in his chest after afghanistan to keep the shrapnel out of his heart. no such creature exists in 616 - instead, tony wore the chestplate of the original iron man armors (which were much different than the first iterations of the mcu armors) under his clothes and it required charging every so often to function as a fancy pacemaker. there was a big to-do about tony getting the shrapnel out, using an experimental tissue transplant surgery ages and ages before anything glowy ever sat in his chest. later he had the rt node, which while visually similar to the arc reactor served an entirely different purpose. the rt node was also a nuclear battery/electromagnet combo, and served to power the iron man at the time (the bleeding edge), but it also served as tony’s brain in a lot of ways. tony had both wiped his own mind and been beaten so badly by norman osborn he had severe brain damage. the rt was the fine line between tony in a persistent vegetative state and tony upright and walking and talking. while not a part of his physiology any longer, he had it for several years, considering until his complete body reboot it was the only thing working as the automatic functions of brain and removing it would literally kill him.

alcoholism - tony’s alcoholism is background in the mcu, and quietly just whisked away (and while a lot of that has to do with disney...). however, in 616, tony’s alcoholism isn’t a once-mentioned deal and everyone goes on their merry way. tony didn’t just “handle” it, he took that plunge from grace and hit rock bottom face first. he spent some time broke. homeless. missing. it’s a prominent feature of his character, once he gets himself in aa and sober, and it’s tested multiple times. his sobriety is used as a bargaining chip. people try and have exploited it for their own gain (notably obadiah stane and justine hammer, the original justin hammer’s daughter). aa plays a big part in tony’s story, he does meetings, the steps, sponsors other people (notably carol danvers). it’s not a quiet, hidden thing, it’s very public and very honest, and something tony is very frank about being a daily struggle.

obadiah stane - mcu obadiah was a father-figure to tony. in 616, this isn’t even remotely close to the case, and instead he was absolutely villainous from the start, in the sense that he tried (and succeeded) to legally both maneuver tony’s company right out from under him and lay claim to everything tony had ever called his own. he manipulated tony’s need for love and problems with alcohol to secure that. he kidnapped literally everyone he could get his hands on that meant something to tony, from pepper to the baby of a friend he helped deliver. and after he took himself off the playing field he still had a minefield laid for tony, in the form of tony’s entire fortune (sure tony inherited the company from howard, but every penny stane took tony earned himself) behind a wall of failsafes to keep tony out if certain conditions weren’t met. tony ultimately succeeded, but it wasn’t a one and done deal, it was a massive climb up a mountain from the very bottom. later, obadiah’s son, zeke stane, also came after tony.

pepper potts - you know how the mcu story goes, tony gets the girl, they get married, have a kid. yeah, 616 didn’t happen that way. 616 didn’t happen that way so much that tony and pepper have literally never been in a relationship. they pined after each other for years, sure, and pepper is literally one of the people tony cares about most in the world and always will, but they’re not in love. pepper ended up marrying happy and while they had their issues ultimately they were still together at the time of happy’s death. tony and pepper have slept together ultimately a grand total of one time, and that’s been that. tony acknowledges that his role in pepper’s life is more overly protective best friend, not partner material. pepper is super, super important to tony, but she’s not and probably never will be his endgame. they aren’t like that.

extremis - in mcu, extremis is a mess. a literal, whole-ass mess. with a fake mandarin in the deal. so here’s how it works in 616: tony was the one (1) extremis enhancile that didn’t completely lose his marbles, and even then it can’t be said it didn’t cause some issues, as anyone who’s ever read the civil war storyline and his duration as director of shield will know. tony’s version of extremis rewired his body from the inside out, literally. he had a level of technopathy, a healing factor, he could literally tap into anything electronic he wanted to, connect to satellites, whatever. it also made him cold, distant, and more than a little less human, with less control over his already prodigious temper. it wasn’t a fun time. it essentially turned his brain into a computer’s harddrive, and he used it exactly that way, to the point he was backing himself up in the chance it was ever needed (spoiler: he did). pepper didn’t get extremis. in 616 you literally have to have a special genetic marker, or it will kill you. gruesomely. and, put another, easy to parse way: extremis basically made tony a technopathic steve rogers, a super soldier.

secret identity - the mcu has tony blowing off the idea of iron man as a bodyguard as ridiculous. 616 tony posed as his own bodyguard for years. he kept that secret so close to his vest only a handful of people knew for years and most of the avengers weren’t on that list. actually, the one who did know was thor, not anyone else you might think. or...that knew because tony told them so. lots of people caught a glimpse of it, or suspected. he’s revealed and then covered up his identity numerous times, finally coming out officially and staying out as iron man during the fight over superhero registration. while the whole world knows now that tony stark and iron man are one in the same, for the majority of tony’s time as the armored avenger, that simply wasn’t the case.

chitauri - chitauri were an mcu/ultimates thing strictly up until secret empire (which we don’t talk about in this house), when they were introduced into 616. that battle of new york? in the mcu? yeah that’s kinda...normal, for 616. it happens often enough that the world ending or aliens trying to invade or...look, 616 is entirely more perilous of a universe. the battle of new york is actually a conglomeration of several elements from several different 616 and ultimates battles, including the nukes. tony doesn’t have a fear in space because of things like that, he’s actually spent lots and lots of time in space, and notably with the guardians of the galaxy (of which he was one for a hot minute).

the avengers - mcu follows the ultimates storyline for the avengers, in that they’re formed by shield. in 616, that’s not so much the case. the avengers formed on their own, with an entirely different line up for the team, coming together as a group to fight loki and deciding that, overall, there’s something to be said about working together. originally it was janet van dye and hank pym (who are tony’s generation - hope van dyne does not exist in 616, instead we have nadia van dyne, who is hank’s daughter that jan has claimed as her own), thor, bruce banner, and tony. steve is not an actual founding member, he was grandfathered in and has all the perks because it’s captain america and you just don’t leave captain america in the cold. shield had diddly fuck all to do with them, and has worked with them in the past, sure, but it’s always been a very uneasy alliance. to the point that shield has tried to take over tony’s company at points. the avengers are a free-wheeling operation, funded largely through donations, the maria stark foundation, and tony’s own personal fortune. they’re peace-keepers, classified as a non-profit, and operate by their own by-laws and regulations, which if you’re really interested, you can find here. the only thing i’ve personally added to that is section five, and even that has some basis in canon itself.

ultron - ultron was created by hank pym (giant man, ant-man, wasp, yellowjacket, goliath), not tony. for very different reasons. and he’s been a thorn in the side of the world since his inception, having caused the destruction of the world more than once that’s had to be fixed. the living creature that is time in the 616 universe is so punched full of holes from having to do shit like this it looks like swiss cheese, let’s be honest here. vision did ultimately come from ultron, yes, but his personality is based off of that of simon williams, a superhero in 616 known as wonder man.

avengers mansion / tower / compound - the avengers used to operate out of tony’s childhood home, which he opened up to that cause, 890 fifth avenue. when that was destroyed, they moved to stark tower. that’s been destroyed about a hundred times at this point. currently the main team is operating out of the body of a dead celestial in the north pole. 616 tony stark would never lower himself to buying property in upstate new york unless it’s a cabin in the adirondacks, he’d buy (and has bought) property in new jersey first, and the avengers compound, such as it is, does not exist.

civil war - there is no such thing as the sokovia accords in 616. instead, 616 had what’s called the superhuman registration act (shra for short) which required all superhumans to register their identities with the us government. it was strictly us-based, for the record, and happened after nitro, a villain in 616 who can basically blow himself up like a bomb at will, did so in the town of stamford after being caught out by a group of superheroes known as the new warrirors for a reality tv show. it was the final nail in the coffin for a lot of people about superheroes (which are a part of daily life in 616) and people were scared and wanted something done. tony was pro-registration. steve was anti-registration, and was especially hostile after maria hill opened fire on him. they scrapped, and scrapped hard, in multiple public battles, until steve turned himself in when he realized not only was he literally about to murder a basically defenseless tony in the middle of a street (and what do you do when your best friend’s under you and tells you to “finish it” through his broken faceplate?) and that they, both sides, were just fighting to fight, instead of fighting for something. on the way to his arraignment, steve is assassinated. tony literally falls apart and loses his shit utterly and completely. there’s a lot of awful things that happen that can’t be contained to a blurb. and it all leads to the point where tony erases his brain and norman osborn lays siege to asgard, which is near the town of broxton, oklahoma. it’s a mess, both more contained, and bigger, because the stakes are bigger and the number of players are bigger, and there’s a skrull invasion taking place behind the whole damn thing. there are also approximately a million conspiracy theories, some people wondered if tony had something to do with steve’s death (he didn’t, it was red skull), and it’s since shaped the entirety of what it’s like to be a superhero in the world of 616 since, even if shra has been repealed.

captain america - is this really a tony blog without a special mention for steve rogers? the mcu, once again, defers to the ultimates storyline (which is not 616) for steve, with shield handling the thawing and reintroducing steve into the world. in 616, the avengers find him looking for the hulk and realize he’s still alive, and end up offering him a place with them, which obviously he ends up agreeing to. there’s a lot of differences even with steve himself which i’m not going to get entirely into but he and bucky didn’t grow up together, bucky had fuck all to do with civil war for the most part, and tony and steve are literally attached at the hip. tony literally has a captain america collection. the cap collection is a thing, everyone knows about it, it’s not a secret, because captain america was tony’s hero before tony ever became a superhero. there’s none of this tension right off the bat, steve ends up friends with tony and iron man before he knows they’re the same person. they fight so hard because they love each other so hard. they’re close, fullstop. tony and steve have been leading teams together since almost the very beginning, and that’s that. also steve and tony are literally almost the same age when steve is thawed from the ice; tony becomes iron man much earlier in 616.

bucky barnes - and while we’re at it: bucky is a super soldier in the mcu, and there’s that whole mess with civil war and tony trying to kill him. in 616 it’s the opposite: bucky tries to kill tony. tony talks him down and shows him the letter that was given to him from steve after steve’s death and offers bucky the shield. bucky agrees. bucky has intimate knowledge of the iron man’s inner workings and how to shut it (and effectively tony) off. completely. tony doesn’t remember any of this. bucky is not a super soldier in 616, he’s literally just a dude with a metal arm and a plucky attitude who has a very unique skillset and was frozen for long periods of time. he and tony have also been on a team together with bucky as captain america, and they’re friends outside of that. tony does the arm maintenance that bucky can’t do, knows where bucky lives, knows bucky’s cat. there’s none of this resentment there, they’re comfortable with each other.

physicality - this is a big one. it’s what makes him and mcu tony at a glance glaringly different, because he’s so much taller and differently framed. he’s huge and imposing in the suit, standing level with thor and at least half a head taller than steve. outside of it he’s still unfairly tall, but built lanky. he doesn’t build muscle mass the way other superheroes do, and tends to shed weight with a vengeance when he’s overly stressed. and while disney princess eyes are a thing they both share, tony’s got that bonus striking combination of blue eyes and dark hair. he’s also about a decade younger than mcu tony, and looks a bit younger than that bc of everything he’s done to his body to enhance it (which is mostly all moot at this point, for the record).

personality - this is really the main thing with this. the tony you see in the mcu is not 616 tony. at all. 616 tony is actually a fairly serious character; he’s only occasionally flighty about his company, and when he is there’s usually some iron man/avengers motivation behind it. he works. he works hard. and he’s known as a good man to work for, has good company morale, and takes a very micromanaging interest in everything his company does. he also occasionally hides out in his workshop for weeks on end and has to be dragged out to see sunlight again. he makes his jokes, he has some levity, but he’s more prone to rambling complete with flailing arms and technobabble with some philosophical footnotes than he is making nothing but solid pop culture references. he has interests outside of the iron man, outside of engineering, and whole those are his passion, he’s a student of history and philosophy and art, and when he has time he plops down in front of dog cops just like the rest of the 616 universe. he has unique vocal tics that are separate and distinct from mcu tony, that, while they both self edit, 616 tony is more obvious with it, stutters over words, gets stuck. and then has a hard time unsticking himself. he’s more sensitive; he’s less likely to give you an insulting nickname and reach instead for terms of endearment, and literally no one is safe. he calls steve rogers beloved, for crying out loud, and steve doesn’t bat an eyelash at it. he’s soft, and easily bruised, but he’s also steel spined and hot tempered. when he’s angry, you’ll know it. he’s also very kind, and very generous, and hates himself utterly and completely. anyone who spends any amount of time around him realizes very quickly that the plastic i’m king of the world act is a facade. tony will work himself down to the bone to make up for sins, real and imagined. he overreaches in making decisions for other people. and all around is probably a less appealing character in some ways - his flaws are very obvious and very human - but is in a lot of ways entirely more layered because there’s so much at work between his different masks and what’s underneath them all. he’s the first to offer himself up as a sacrifice if it’s needed, and reaches for the worst case scenario first. he’ll push people away because he thinks that will somehow save them, from himself and those he’s crossed. he’s complicated, and his complications are not always easy or appealing or fixable. there’s a truly ugly side to it that doesn’t get glossed over, and he’s willing to go so much darker if he considers it the right thing to do.

overall, there’s only some surface stuff between 616 and the mcu. there’s a guy named tony stark who does duty as a superhero named iron man, but how they both got to the present day is completely different, and their lives and experiences are also completely different. diving into 616 will be like...well. culture shock. and i’m gonna say it (even if i know the intake of breath on the 616 side is gonna be dramatic): for people wanting to find a characterization more closely related to the mcu? let me point you toward the ultimates runs. it’s kinda gross, but i have a soft spot for it and also it’s more narrowly related, you’ll see things that feel entirely more familiar, before jumping off into the crazy ass world that is 616, where things like steve rogers becoming a werewolf is just...tuesday. the mcu takes elements from both, sure, but you’re gonna see a hell of a lot more ultimates influence, and that’s a fact.

#constant //:�� ( about )#long post #long post for ts #// boy i know i missed a lot but #// i'm working off memory here #// and this is already entirely too long #// but here you go #// a friendly handy dandy guide to the differences that are #// the most obvious and the most important

6 notes · View notes

fannishcodex · 7 years ago

Photo

AU where Star is even more literally Eclipsa 2.0 and falls in love with a monster from Mewni, and they eventually have a half-monster/half-mewman child together (who physically takes after monster dad the most and doesn’t really look mewman, except for inheriting Star’s hair and eyes).

Quick OC intro before doing some more elaboration below the cut: the monster of Star’s affections is Kit, one of Rasticore’s nephews. (Wanted to toy around with the concept of look-a-like next gen/generation xerox--Moon’s look-a-like daughter falls in love with Rasticore’s look-a-like nephew. Also toy with the animosity between Moon and Rasticore, more intense and different in this AU.) Their daughter is Nimbus, whose cheek marks are narwhals. If Nimbus holds the wand--broken under different circumstances in this AU--it turns into a pale pink watering can, the broken wand crystal takes the shape of a raindrop and its green color reflects her monster heritage.

This is still a work-in-progress brainstorm for this AU. (It does have similarities with another AU for Star that I posted about before [x].)

Complete AU where a lot of the backstory on Mewni (i.e. for Moon, Toffee, Eclipsa, Heinous, etc.) is different, and an AU where season 3 definitely doesn’t happen, but neither do seasons 1 and 2. For example, Ms. Heinous is a full-blooded mewman.

I was working on this before canon “monster bash” personally disappointed me. (This is also what I had been showing WIP sneak peeks of earlier [x] )

Below is more about this AU, including even more of my salty af response to canon:

This is absolutely not MonsterArm!Marco or Monster!Marco. This is Star/OC. No Marco in sight.

No offense to anyone, but unpopular opinion: part of this AU came from the fact I’m honestly getting weary of all the Starco OC children, and Starco in general.* It’s too much of the same stuff for me. I want something else--and something that ties in more directly with the monster-mewman themes that I’m more interested in, and feel are more important. Also part of this AU is coming from me being salty AF about current SVtFoE canon developments wrt to monster-mewman themes, and just really focusing on what I would prefer over canon right now. (Again, I started making this post before the new episodes in November. I just felt even more salty af about all of this after those new episodes in November.) Other personal reasons behind why I made this AU, and this gets salty af too in some parts:

-I really am way more invested and interested in the monster-mewman themes in svtfoe, and expanding on that and focusing on that, even down to tying Star’s romantic arc to that, making her romantic arc more plot- and character- and theme-relevant through that IMO. Like if Star /has/ to have a romance, why not tie it directly into monster-mewman themes? Why not have her fall in love with a monster from Mewni?

-I literally keep wondering what if Star was even more like Eclipsa, down to romantic interest in a monster.

-I like the idea of monster-humanoid couples having children who take after their monster parent more. Of half monster-half humanoid children that don’t look that humanoid. (Because I feel like that’s happened too much, and it’s getting old; I’m tired of the idea that there’s this half-monster/half-humanoid kid, but she/he is still so humanoid-looking, and I’m like “what about her/his monster heritage??” and it turns me off; like, when the hybrid is too humanoid-looking, it feels like the monster heritage is barely present, and I don’t care for that. I want more half monster/half humanoid kids actually looking more like their monster parents. Also I feel like the face is like the most key part of the design--if the face looks too humanoid, then the whole design is too humanoid.)

-I like the idea of a half-monster princess--who physically takes after her monster heritage the most--having a claim to the Butterfly matrilineal throne. (Bonus points for Septarian monster heritage.) Even though I’d rather see the system torn down, I also can’t help but like the idea of a half-monster princess taking the Butterfly throne (before she eventually ends it after doing what she can do with it to help monsters--because ultimately part of helping monsters should have an end to the Butterfly kingdom itself, and/or its removal from the original monster homeland; or it /is/ completely reclaimed by monsters.) Or again, she just has a claim to the throne that conquered the monster half of her family--but that doesn’t mean she ever takes the throne, and may just help tear it down instead.

-I like the idea of mixed race half-monster/half-mewman children in general, especially if they’re members of the Butterfly royal family tree, and again if they physically take after their monster heritage more, if they don’t look so mewman/humanoid.

-Also tbh I keep enjoying the idea of throwing Star onto the Lizard Love/Septarian Love wagon.

- And I just finally wanted Star’s half-monster daughter way more than another Starco kid.

-I know in a previous post [x] I did say I didn’t like Starco being used for marriage and babies for Star’s endgame--but like I mentioned before, I’m interested in the idea of, if Star has to have a romance, let it tie more directly into monster-mewman themes. Let her romance arc have actual interracial themes that deal with a race oppressing another, and how individuals of those races can come together, and come to want to end that oppression. Just in this case, I find marriage and babies /as a part of/ Star’s endgame more interesting and meaningful to me if she chooses a monster for her love and has a mixed-race child with him, and who physically takes after monster heritage more than mewman heritage. I also feel like that ties more into Star’s individual life in a way, not just her romantic/family side--like it ties more into those monster-mewman themes where she feels more like an individual with her own goals. Just, it feels like it ties into Star having other concerns outside of romance, it feels like it ties into Star having increased agency and exerting power to change her world for the better, and having to deal with what her family history did. That’s something I just can’t really get out of Starco.

Again, this AU is still a rough work-in-progress. I’m still trying to figure things out, particularly more about the OCs/Star’s monster husband and half monster daughter. Below is what I have down so far that I feel like sharing, besides the designs I came up with. Also will involve a bit more WIP brainstorming on AU worldbuilding, including info on characters other than the canon/oc ship and their child:

-The monster of Star’s affections is Kit, one of Rasticore’s nephews and nieces. I literally thought of Rasticore having a large extended family through his multiple siblings each having their own offspring, and altogether giving him quite a few nephews and nieces for my AU started in between seasons 2 and 3, ‘wrong space wrong time’ [x] . I decided I wanted to combine that element with this AU (and to actually just make this part of an alternate continuity with ‘wrong space wrong time’ AU). Also my pre-season 3 AU has Rasticore and Moon personally loathing each other, like they actually know each other enough to really hate each other, which makes it even harder for me to resist the idea that Moon also has to conflict with Star falling for someone related to a monster she really /personally/ detests, combined with the racism that’s been ingrained in her. And again, I wanted to toy around with the concept of look-a-like next gen/generation xerox--Moon’s look-a-like daughter falls in love with Rasticore’s look-a-like nephew.

-Kit Chaosus Disastorvayne, son of one of Rasticore’s younger brothers--who shared a resemblance to Rasticore, and passes this down to Kit--is the same age as Star. He and his siblings have long been orphaned, and currently live with one of their aunts (one of Rasticore’s younger sisters). Like many other monsters, they’re impoverished and face mewman aggression.

-I’m not dealing with S3 canon directly, and going with my AU backstory in “wrong space wrong time” AU instead because tbh I prefer it, and it’s more fleshed out and ready for me to use--but more about that AU is another post for another day. Just to sum up one detail, I’ll say that Rasticore and Moon have different backstories in this and detest each other for some different reasons, and more intensely because they are more familiar with each other.

-In this “Star is even more literally Eclipsa 2.0″ AU, Toffee was captured and brainwashed along with Rasticore by Miss Heinous--who also has a different backstory and is a full-blooded mewman--and St.O’s after a savage battle with Moon (before Star or Kit were ever born). Both Toffee and Rasticore have been brainwashed into working for Ms. Heinous and her related interests, and that’s where they are while Star is born and eventually inherits the royal wand. (This does include Toffee/Rasticore ship because I like that ship.)

-In this AU, Moon chooses to focus more on personally training Star rather than sending her to Earth once she immediately screws up with the royal wand after first receiving it. Maybe just spend more time with your kid and teach her more about the magical artifact she’s been given with seemingly little prep beforehand, instead of immediately shipping her off to another dimension with still not much instruction on newfound power boost granted by said magical artifact. So Star is never sent to Earth when she’s 14, she stays on Mewni.

-Star continues to go around picking fights with monsters in her spare time, and this now includes fending off Ludo’s attempts to steal her wand. In this AU and with Toffee brainwashed and forced to serve St. O’s, the events of “Storm the Castle” don’t exactly happen--and it’s Star who finds the monster tadpole babies, instead of Ludo. After her initial disgust, Star watches them more closely, and finds their behavior adorable, and they actually look kinda cute. Instead of Buff Frog, Star takes the monster tadpole babies in, and secretly cares for them at Butterfly Castle.

-Through caring for the monster tadpole babies in secret, Star starts to realize the brutal truth about the upcoming annual observance of Mewnipendance Day, and hesitates with attacking Buff Frog when he tries to steal her wand again.

-When Mewnipendance Day actually comes, it’s the usual for Star: on Mewni, Star always makes public appearances with her parents celebrating the holiday, presiding over huge reenactments and festivities per their status as the royal rulers and heir to the throne. Star is much more apprehensive this year and worrying even more about the monster babies she left in her Secrets Nursery (codenamed Secrets Closet). Some of Star’s older cousins on her father’s side convince Star to join them for their own little celebration, thinking she’s old enough now that she has the wand and thinking this’ll be a treat for her; for once really thinking about appearances and actually realizing it’ll look strange if she resists this invite too much after years of behaving a certain way--last year she would have been immediately thrilled by such an invitation--Star agrees and sneaks away with them.

-Star relaxes with her cousins--their cheerful mood is infectious, and the corn milkshakes they’ve grabbed taste delicious.

-Star’s older Johannsen cousins take her to the edge of the Forest of Certain Death, to what ends up being her first meeting with Kit--locked up in a cage, in front of a decent-sized topiary maze. Star’s cheered up mood drops. Star stares at the caged monster, and he’s shorter than her, and she’s seen and fought shorter monsters before, like Boo Fly, but this--Star thinks this monster could be her age. Her cousins tell her they’re gonna let loose this beast later for a monster hunt, through this new topiary maze grown from this new line of magic seeds from Quest Buy. Unsettled, Star tries asking why, what did this monster do to end up like--her cousins get really confused by her line of questioning, wondering why she’s overthinking this.

-Star’s the only one to notice Kit move quickly but carefully, slipping a claw through the bars and take a key from one of her cousins standing too close and completely clueless. Too late, Kit realizes Star saw, and he catches her eye, looking freaked out--Star says in a loud voice that her cousins are right, but their topiary maze needs a complete makeover. Taking out her wand, Star goes to town using it to make the topiary maze bigger and thornier and with a million more flowers, all while her cousins watch in awe, sufficiently distracted from Kit unlocking the cage door and bolting into the deeper woods.

-When her cousins finally realize Kit is gone, they freak out and start to look for him. Star stops them, calming them down a bit, and confidently insisting she has this covered. She’ll just turn this topiary maze into a topiary bloodhound that’ll track that monster down--oh no, /oops/, what do you know, my spell backfired /again/, don’t worry, I’ll totally make the topiary hound spit you guys out, just give me a few...hours? Sorry, please don’t tell my mom--she’d doubly freak out if she knew you guys sneaked me out, and with me screwing up my spells /again./ Just, essentially Star feigns another spell backfire--like she’s been known to do--to further help Kit escape. It works.

-Back at Butterfly Castle, Star coos over the monster tadpole babies, but is still freaked out. Star’s certain that monster must have gotten away, her cousins didn’t get him--but there were a lot of mewmans celebrating, what if someone else had?... Star flips through her ancestral Book of Spells for some kind of locator spell, and asks Glossayrck for help, but acting cagey about her exact reasons. Glossayrck seems to consider, then seemingly unconcerned, he unlocks Eclipsa’s chapter without identifying who wrote it, and shows Star the spying spell.

-Star uses the spying spell for the image in her mind, of that monster… When Star finds him still making his way through the woods looking like no one followed him and looking unhurt, she reflexively audibly voices her relief, “Okaycoolyou’refine”. Star jumps back when Kit whirls around and spots her. They’re both startled and confused and freaked out, Star says she didn’t think he would notice her, Kit points out there’s a hole in the sky and she just talked, and Kit bristles, wary, is this some really sick mewman game, letting him go like this to track him down again, was this her own hunt but longer--Star, bug-eyed, insists she’s not hunting him, she just wanted to check to see if he was okay--and their strained interaction goes on. Kit remains tense and biting, and Star awkward and unused to dealing with someone like this. When Star says she was only trying to help, Kit asks why, and what does she want, his complete gratitude? Her mercy that still confuses him isn’t going to make him suddenly agreeable with any mewman, least of all their princess. And again, her mercy is confusing, doesn’t make sense, and he’s still wary of her, especially since she’s watching him through this giant magic hole in the air. But eventually Kit concedes that Star saw him take the keys and didn’t expose him like she could have, and did distract his captors, so he gives a small gruff thank you, but he isn’t charmed by Star, and she doesn’t feel any better. Star leaves Kit alone, deactivating the spying spell.

-Completely freaked out by Mewnipendance Day and what just happened because of it and hitting a new fever pitch in her fear of what would happen if her parents or the royal court or any mewman discovered she was caring for monster tadpole babies--well, Star realizes she can’t secretly care for them while living in Butterfly Castle and being the crown princess. So bundling herself up in a disguise made from old goth gear that had been on sale in Quest Buy--that she had got during her spiky leather phase with Pony Head before--Star secretly leaves the monster babies at Ludo’s castle for Buff Frog to find, and Buff Frog happily adopts them. Star gradually develops more sympathy for monsters and disillusionment with her own people.

-Star begins raiding the food hoards of mewman nobility for monsters while in a dark drab disguise cobbled together from Quest Buy goth gear, the same ensemble she used for when she secretly took the monster tadpole babies to Buff Frog, with some modifications. She continues to do this and other acts of sabotage against ruling mewmans while in disguise, and her alter ego comes to be bluntly called the Rogue, hated by most mewmans and appreciated by monsters, but both think the bandit is a monster. ( @lemonadesoda drew some images of this Rogue Star AU [x] )

-Wanting to check on the monster tadpole babies--and feeling a strange new loneliness in Butterfly Castle after growing increasingly wary of the main beliefs her ancestral home holds--Star uses the spying spell to contact Kit, and ask him to do it for her. He’s freaked out again and wary of her locating him like this again, but Star says it’s her only way to get in touch, and asks for another way to please reach him, because she has a request. Kit first wants to know what it is, right now. Star tells him about the monster tadpole babies and shows photos on her mirrorcell for proof; she asks if Kit could please check up on them for her, and she would compensate him with money, food. Star says she doesn’t want to use this spying spell to check on them, because she doesn’t want the tadpoles’ new family to know about her, and if Kit spotted her, they might too; it would be the same risk if she tried sneaking around there again. Star’s emotions and photos make Kit reconsider her, but he’s still not entirely certain. But the promise of compensation strikes a desperate chord with him, he and his family could really use food and money. Kit agrees, and he and Star plan to meet in the woods to exchange info for payment.

-For this, Kit goes to Castle Avarius saying he’s looking for a job--which would be nice, actually, really fulfill that job hunt he had started before insanely getting some help from the Butterfly princess. Kit had heard some rumors about Ludo, but none had been clear about his efforts in Avarius Castle; when he gets there, he gets confirmation of what they’re doing. If Kit could get some kind of paying position here on top of what he was doing for the princess, that would be beneficial; even more so if a steady position here would give him a steady business arrangement with the princess, if she continued to want to pay for this specific information. It works out, Buff Frog even seems to like him--seeing the babies in person made Kit warm up and admire their cuteness, and compare them to his younger siblings and cousins, and when Buff Frog asks if he ever looks after them, Kit says ‘yes’--and Kit has the job and the info. The job is really just babysitter assignment to Buff Frog’s babies, but it’s a job, and Kit had experience with his younger siblings and cousins. Buff Frog had shouted down Ludo and put his foot down, saying that though Kit was newly of age at 14 years old, he would still be the youngest; and the babies needed care for when he was away on missions. Kit could look after them, and also help with upkeep of castle, and generally free up the older monsters for more mission work while he tended to those things.

-Kit meets with Star afterward, and they do the exchange, of info for payment. They maintain this arrangement periodically, through texts after sharing mirrorcell numbers. Star takes more care to repel Ludo’s forces--Buff Frog among them--through less harmful and more benignly defensive spells. (Ludo, Buff Frog, and the other monsters notice. Princess Star’s spells remain quirky, but they also seem strangely less violent. They aren’t sure what to make of this though.)

-Star and Kit are the same age. At 14, Star is taller and thinner, Kit shorter and bulkier. Their size and shape difference are actually similar to young Moon and River in the comics. But as they grow, Kit sprouts and becomes more slender, while Star becomes bulkier, and still grows taller, and she and Kit end up at about the same height.

-Star knows most people either have disdain for her and then are charmed and soften up and they appreciate her in quick order, or people just have disdain for her. Star figures Kit was the latter, but still he was new--his disdain was more blunt, more than any other; and she didn’t entirely run from his disdain like others, or write him off as annoying and opposition to be safely ignored. How could she? Star felt he had every reason to dislike her, and it unsettled her. It unsettled Star, not only because she wasn’t used to this, but also because she felt she deserved it. She hadn’t directly done anything, but somehow that felt worse; to have his disdain (wariness) exist due more to her people--and how her people seemed to define her whether she wanted them to or not--felt worse. Sometimes Kit seemed to try to catch himself, and looked at her in a different way that made her stomach squirm, and then he’d try to act more careful and deferential in a way that made her feel gross and reminded her of servants back home in the castle (that made her think of a picture book where the pop-up flames now seemed ominous and the monsters terrified rather than terrifying). Star was grateful when those moments didn’t last long, and found that she preferred his blunt bite over his remembering that she was someone to fear and defer to due to her race and rank. She was unsettled, but Star found the latter unsettled her more than the former. Star preferred Kit’s disdain, his challenge to her, because it felt like he was getting less freaked out by her, that he wasn’t afraid to speak more of his mind with her, that he saw her, and not just her people and her rank; saw that she was someone who could listen to him, and not shut him down by any means necessary.

-But Kit wasn’t angry like Tom, to Star’s mind. In her mind, Kit felt angry-justified-and-truly-hurt, not angry-controlling-tantrum. And Kit could never be as explosively angry as Tom. But Kit’s anger made Star pay attention, it carried more weight (while she would often roll her eyes at Tom’s anger, and finally leave him partially due to that). And Kit was angry, but deep down Star thought he was soft, and wounded.

-There were little moments of something less strained between them, as time went on. Those moments grew more frequent. (They had always gushed over the photos Kit secretly took of the babies to show to Star. Their texts to each other had grown more relaxed outside of business terms.)

-To her surprise--and even gratitude--Star found Kit seemed to grow less wary of her.

-Kit didn’t know how to feel when he realized he felt a certain level of comfort and trust to be gruff with Star. That he could, in a way, vent with her like with some of his friends, though more gruffly, harshly. It grew less harsh as time went on.

-Star and Kit reached a crisis point when it occurred to them--the first time seemed okay, but were they just being creepers now with continuing to keep an eye on the monster tadpole babies like this? Star felt particularly like a creeper. Did she really not think Buff Frog would take care of them? She left the babies with him, she had to...really leave the babies with him. She probably shouldn’t keep secretly looking over his shoulder like this.

-Kit reconsiders a little, saying the babies get photographed all the time by Ludo’s other monsters, and they text the pix to their other friends, and Buff Frog is fine with it, he could do the same with Star, it’s not a big deal--

- “...We’re friends?” Star asks Kit, and for some reason, for a snap second, he feels completely doomed by this truth. (When had it happened? When had Star’s steadily increasing excess of text emojis brought a small smile to his face, when had her rambling and brightness and stumbling earnestness to listen and tolerate and even act nicer made him stop seeing her race and rank first?) After that, Star and Kit meet each other outside of the business arrangement they made, and text even more outside of it.

-Star eventually makes friends with the Alternative Monsters too.

-Things between Star and Ponyhead become more strained. Star is getting these other concerns about her kingdom, but Ponyhead isn’t too interested in hearing about this, and still just wants to party with Star. They start to drift apart a bit. But later, Ponyhead shows to be more loyal to Star, and while she’s not particularly interested or understanding, when it comes down to it, Ponyhead will stand by Star. They still have less to talk about and bond over as time passes, but Ponyhead remains loyal, and Star does appreciate this. (Ponyhead does whole-heartedly approve of Kit later, though she’s really just approving his superficial appearance.)

-Kit and Ludo develop an odd friendship.

-Eyepatch Bull Dog, Porcupine Warrior, and Turtle Monster still meet Buff Frog, eventually hired by Ludo through Boo Fly. Eyepatch Bull Dog clashes with Buff Frog /and/ Ludo. But along with Kit, Eyepatch Bull Dog inspires Buff Frog to be more firm with Ludo, and cause a shift in prioritization. Buff Frog starts to move from looking to loyalty to Ludo and the wand as an effort for monster survival and betterment, and back to the raids for food and supplies, and other means to resist mewman power. Boo Fly, Kit, Eyepatch Bull Dog, and the other monsters rally around Buff Frog, and Ludo becomes more of a figurehead, until he shapes up with Kit’s help and follows Buff Frog’s lead.

-Star eventually confesses to Kit she’s the Rogue.

-Star eventually loses an eye in a Game of Flags. Over the years since inheriting the wand at 14--and gaining and losing the monster tadpole babies, gaining Kit’s friendship, becoming the Rogue--her relationship to that Butterfly tradition has become complicated. She’s also started to challenge the value and nature of that too, but also grew to see it as a way to try to assert her authority as the future queen. (Throwing a guard into lava during her first Game of Flags both alarmed and hardened Star and made her more questioning. The guard had survived, Star had turned back at his pained yell and helped him out, but he had been grievously injured, and Star had been greatly impacted.) Star is vocal about her increasingly radical beliefs, especially about helping monsters and giving up mewman power to do so. Star still tries to be more calculated with how vocal she is about this, it’s a work-in-progress; see if going slower will help; act more benign sometimes to try to make sure no one suspects she’s the Rogue, and to also avoid Moon snapping and sending her to St. O’s. It’s a balancing act Star maneuvers a lot. Moon is a mix of alarmed, incredulous--and skeptical, not taking her daughter seriously and believing she’s too flighty and immature and it’s a phase she’ll grow out of, and refrains from genuinely threatening or even considering St. O’s as an option in response to this. The rest of the mewman nobility just steadily get angrier, and eventually this results in a more severe attack during Game of Flags that costs Star one of her eyes. Star still manages another victory, but there’s no saving her eye, it was cursed off through a mix of spells the healers and Moon can’t rectify. Star tries to be nonchalant, but this is now more ammo for her detractors in the royal court--they’re now attacking her marred appearance/beauty. But Star refuses any attempts to remake her image with two eyes in any form of royal portraiture of her after she’s been maimed.

-Star ditches the intricately embroidered eyepatch Queen Moon commissioned for her when Kit gives a simpler eyepatch he made for her. She wears it exclusively and lies to any mewmans who ask about it, saying she picked it up from Quest Buy.

-Kit convinces Star to come clean with Buff Frog, especially since there’s already been a weirdly silent confused understanding between them ever since she hesitated to attack him, and then continued to avoid aggressively repelling him and Ludo’s other monsters from wand theft. Just tell Buff Frog. After confession and discussion, a more formalized alliance between Star and Buff Frog and the other monsters is made--and eventually friendship with them. (Star can babysit the tadpoles with Kit now.)

-Ludo and Star grow to...tolerate each other. But they’re not exactly friends. They still dislike each other quite a bit.

-Star literally does not learn of Eclipsa’s existence, which is largely kept hidden in Butterfly castle, and becomes more of a fiercely guarded secret as Star grows more vocally radical. The concern grows that even telling Star about her as a cautionary tale will backfire and only serve to give her the wrong ideas, and so any word of Eclipsa is forbidden.

-Star tries to pass relevant info about the ruling mewmans to Buff Frog and his increasingly rebellious group, tries to provide a distraction for any of their efforts. On top of her continued activity as the disguised Rogue, Star generally tries to sabotage mewman power from behind the scenes while also publicly trying to diminish and reform it.

-Star only manages to get a handful of allies among mewmans--Ruberiot the Songstrel, Foolduke the Jester, and the genius Mime. They’re not much in numbers, but Star is grateful for them, and they ultimately also end up being the closest thing she has to friends that are actually mewmans, a first for her. (Ruberiot, Foolduke, and Mime proved more open, partly because they took to heart their partial outcast status--they all aren’t the highest ranking mewmans, and experience issues over their lack of rank, such as some mistreatment from the highest born mewmans they serve, i.e. Star’s uncle Heartrude, Ruberiot fearing Moon will execute him for any screw-ups because he heard the previous queen had done the same before; partly because their trained deference to higher ranking mewmans ends up taking the form of actually listening to Star and really acknowledging her role as their future queen, and thinking she must have a point, and hoping that she will be a good queen. The three also grow charmed by Star’s essentially eccentric, bright personaltiy.)

-Star both breaks away from and is forced out by mewman society, she rejects them as the majority of them reject her, and she throws her lot in with Buff Frog and Kit and the latest iteration of a growing monster rebellion. Ruberiot, Foolduke, and Mime join her.

-Moon and River stay with the status quo that upholds mewman power, and are estranged from their daughter. They feel as if Star is still an immature child whose mess they have to clean up, and they need their daughter back home to finally set her straight.

-Eventually Star and Kit become romantically involved, further estranging Star from her parents and mewman society, but ultimately giving her immeasurably more happiness. Their wedding is somehow small and crowded at the same time, packed mostly with Buff Frog and other monsters that are friends, allies, Kit’s family, as well as Ruberiot, Foolduke, Mime. (Ludo is grudgingly there and hates that Kit married Star; and Star is still confused about how Kit made friends with him.)

-When Star is pregnant with her and Kit’s child, she finally meets a brainwashed Toffee; and Kit discovers his uncle Rasticore hadn’t actually died in battle against Queen Moon like the rest of his family had believed, but had been brainwashed along with Toffee by St. O’s instead. Toffee and Rasticore are eventually freed from their brainwashing and start to recover, while taking refuge with the new monster rebels that include Buff Frog, Kit, Star, and others.

-Star and Kit have a daughter. They try to come up with names before she’s born, but Kit keeps drawing a blank, Star can’t decide on which adorable name she wants, there are too many. But when Star realizes she and Kit have a daughter, with cheek marks of her own, Butterfly tradition occurs to her, and even some concerns. Star actually really hadn’t let herself think she might have a daughter, because that would make things more complicated, that might make Star’s mixed race child seem like she might have the slimmest chance of inheriting the throne and make the Butterfly kingdom want to target her more; Star thought more she would have a son, and kept thinking of cute names for him. But it’s a girl, and Star considers Butterfly inheritance; she fears her daughter being even more of a target; but she really considers the idea of her mixed race daughter inheriting and becoming Queen, and it’s not an entirely unpleasant thought, in terms of personal and practical and moral reasons--it could be fitting, it may be good, it may be fair--but she really wants to put her daughter’s best interests first--and one of the ideas Star has grown to consider is that the line of Butterfly queens and mewman rulership as it is should simply end--she should have taken control and ended it, but she had failed, she hadn’t managed it yet--Star is still not sure what exactly to do, but she wants to keep and protect her daughter… But Star also considers the monster heritage of her daughter, and she’d like the name to reflect that in some way too.

-Star suggests to Kit to name their daughter Nimbus, rambling off her reasons: many names of Butterfly women have had some sort of sky/aerial quality, Star included; Nimbus fits in with that, and acknowledges Star’s like of clouds, and her Cloudy spell, and actually sounds pretty cute in her head. /If/ she ever becomes queen, she’ll have a name that could go well enough with that role. (But above all Star wants her daughter safe and happy. Her becoming queen is not a priority.) And a cloud sounds like an aerial object physically closer to the land that Nimbus’ monster heritage has a true claim to. After listening to Star’s rambling reasons, Kit agrees. Kit nicknames her Nim, and Star loves that. The ability to shorten it to Nim is even cuter to Star, and the sound of it and its three letters reminds Star more of Kit.

-(Princess) Nimbus “Nim” Chaosus Disastorvayne Butterfly (she knows she’s in trouble when either of her parents use her full name) largely resembles her father, but inherits her mother’s hair and the color/shape of her eyes. She has cheek marks like her mother and the rest of the Butterfly women. They’re the shape of narwhals, which delights Star and amuses Kit. And her cheek marks are red, like the markings on Kit.

-Buff Frog is essentially Nim’s loving grandfather. The aunt that raised Kit is essentially Nim’s grandmother, though is literally her great aunt. Ludo and Boo Fly and Ruberiot and others are some of her many uncles. Nim calls Rasticore and Toffee her uncles too (Ludo takes pleasure in pointing out Toffee would be her great uncle; Kit tells her Rasticore is his uncle, so that makes him her great uncle too; and sometimes Nim will use the full term with them). Some of her many aunts include Porcupine Warrior, Foolduke and others.

-With my AU world backstory, I have Star even more like Eclipsa--my AU continuity has Eclipsa fall in love with a Septarian monster, and together they have Toffee, their half-monster, half-mewman child. So, Toffee is a mixed race member of the Butterfly family tree too. This is eventually revealed while Nimbus is an infant. I also like the idea of adding this nuance to a bond between Toffee and Nimbus--they have very similar common ground that they can’t really share with anyone else, except each other. Mixed race Toffee also has a mewberty form, indicating that his mixed race is the cause, given that is a defining difference between him and other full-blooded Butterfly women and their mewberty forms. It may indicate that for this mixed race, female gender stops mattering to the unique mewman Butterfly bloodline, or the monster half does not read as male to the Butterfly blood, or something else. (This is based on this fantastic AU fanart of Mewberty!Toffee, half-monster son of Eclipsa [x].)

-Ever since she was little, Nim took comfort in Toffee having hair like her, the only Septarian monster she’s met who does. She took comfort in knowing Toffee’s half-monster/half-mewman like her. (Toffee never knew that comfort until Nimbus was born.)

-Star still has a brightness and goofiness around her, but she’s also grown more fierce and crafty after years of trying to undermine mewman power in battle and in royal court maneuvering. She’s developed a pretty good poker face, an evolution of what she demonstrated in her old family portrait made a few months before her 14th birthday, but she doesn’t use it that often. Yet Star has become kinder too.

-Nim’s personality takes a lot after Star’s--especially a 14-year-old Star’s--though in some ways she’s gentler. She keeps her quarters messy like Star had at her age. (Star keeps her quarters only a little messy now.) Nim loves to garden. She likes adventuring a lot too, and likes to combine it with gardening, discovering and studying new plants. Among her garden are Mewni carnivorous plants that she finds adorable and full of personality. Nim’s embarrassed by her allergy to corn, especially when her parents try to guard very seriously against it.

-Kit has become more warm over the years. But there can still be a bite to him after what he’s lived through.

-As Star grew more powerful, so did her mewberty form. Its appearance changed a bit too. It remains colored purple, with some yellow speckling. Her lower body has grown more spider-like, ending in many spiked legs.

-Nim has a mewberty form too. Though she was an example of mewberty being triggered by something other than discovering a romantic interest in anyone. At 14, when she accidentally took a bite of something that had corn in it, her face broke out--in many copies of her narhwal cheek marks. Her corn allergy triggered her first mewberty transformation. Her mixed race heritage may be the reason for why a large growth increase was demonstrated in her mewberty form as well as a more difficult time experiencing it--while in mewberty, Nim seemed to vocalize pain, and vomited many narwhal marks, as many as the amount of narwhal marks fell off her body and webbing. While in mewberty, Nim’s two legs merged into a unified tail-like structure, that ultimately was more reminiscent of an insect’s lower body.

-When (if) Nim holds the royal wand--broken under different circumstances--its shape isn’t a wand like her mother’s, or her grandmother’s, or many other Butterfly ancestors’. When Nim holds the wand, it turns into a pale pink watering can. Nim is told her ancestor Festivia was similar--when she held the wand, it turned into a goblet. The broken crystal on Nim’s watering can-wand resembles a (broken) rain drop; its green color reflects her monster heritage. Nim tends to come up with a lot of garden-themed spells, like Poison Ivy Bomb, Venus Fly Jawtrap, etc. Nim takes to carrying her watering can-wand around in a backpack.

-The above is more, “if Nim got the wand,” I’m still fuzzy on how the context of that would work to my tastes, if the wand would still even be around for Nim to use, or if it’s broken under different circumstances. But I do like the thought of her getting to use the wand too.

-Poetry makes me nervous, but I’ve even come up with a Mewman propaganda-fueled caption for Star’s tapestry in this AU:

Underneath the crown

Lied a fierce and wild girl

Who ran away with her monster lover

Acting just like another

-...I also keep thinking of silly mixed-naming for this Star/OC ship too, like just StarKit.

*Tbh for me, it’s getting to a point where it’s like ultimately all the Starco kids are kinda bleeding into each other, it’s started to feel all the same to me--though that sorta makes sense because it’s all variations of offspring from one extremely popular pairing that I’m now honestly feeling overwhelmed with. I can’t take the Starco overload anymore. I’m missing real variety. Also I feel like Starco keeps distracting from themes and plot in svtfoe I care way more about, and think are/should be far more important, i.e. monster-memwan themes. If Star /has/ to have a romance, I keep thinking I wish it was tied directly to those monster-mewman themes then, that she should fall in love with a monster from Mewni. And I just...don’t like Starco. I don’t really care for Marco tbh, I just...don’t. There are way more interesting characters than Marco in svtfoe, and more interesting themes. Star’s awesome, but I just don’t care for her Earth roommate and friend that much. Princess Marco and Monster Arm are more interesting, but they don’t happen enough. And Marco still just...rubs me the wrong way, tbh. It’s a gut dislike/apathy, I suppose. If I have to ship Marco with anyone, then Tom (and sometimes Jackie). I just...don’t feel the Starco ship. I don’t care for it. I’ve been enjoying brainstorming a Star/Septarian Monster OC ship and their half-monster/half-mewman daughter way more.

#svtfoe #star vs the forces of evil #star butterfly #svtfoe critical #my fanart #my fanfic

42 notes · View notes

katohz-blog · 7 years ago

Text

The Importance of Near In Death Note

The Death Note Netflix movie came out last week, and somehow as they always do whenever anything Death Note related comes out, people used the opportunity to shit on Near. Well, I'm gonna come out and say it. I love Near. He is my favorite character in Death Note. And today, I'm gonna explain why. Because let me tell you, this has been a LONG time coming. Near is actually my favorite character in the entire series, but so many people think he’s terrible, or an L-clone with no originality, or just a plain-old jerk, or that Mello should have won in the end. Well, let me tell you why you’re all WRONG about Near. But before that, let's examine some of the problems that people have with Near.

There are a lot of complaints about his personality. Frankly, I can't argue with that, because if you don't like his personality, I can't get you to like it, unless you blatantly misunderstand what his personality traits are. I think one misunderstanding of his personality that gets thrown around a lot is embodied in this scene. Here, we see the SPK headquarters is being stormed by rabid Kira supporters being led by Demogawa. Near has a contingency plan to use money that he inherited from L to create a distraction so that he and the SPK can escape. People point to this scene as evidence that Near is wasteful and he disrespects L. This is a huge misunderstanding of Near's motivation here, and of what this scene represents. Near believes that there are good people in the world who agree with what Kira's doing because they think it'll lead to a better world. However, he also believes that there are people who just want to jump on the bandwagon because they're too stupid or too weak-willed to examine Kira's philosophy for themselves. He knows that those people are the ones at his door, and he wants to demonstrate their lack of dedication to Kira, which they use as an excuse for violence, by proving how easily distracted they are by blinding them with money. He uses the last remnant of L on this Earth to display how worthless these Kira supporters are. From a thematic standpoint, L's battle with Kira was all about defending himself from Kira's attempts to kill him. If there was ever a move that Light was about to make that could prove dangerous to L, L foresaw that move and took action to stop Light from being able to make it. And here, the last remnant of L is blocking Kira's attack. With all of that in mind, this moment should be celebrated, but instead it's pointed to as evidence that Near has a bad personality by people who don't understand what the point of this moment is. It's a testament to Near's respect of L. By showing everyone that Demogawa and his army of blind followers are greedy and not noble, he challenges Kira's very philosophy that the people who oppose him are the ones who are truly evil, and that good people would inevitably support him. This moment is evidence that Near is a perfect foil for Light's own belief of himself as a God. But we'll get to that later.

The next point that I want to combat is the ideas that Near is a clone of L. Near and Mello are both like L in their own way, because they were both raised to be L. Near is the intellectual side that has an out there way of thinking that leads him to make connections that no one else really sees and Mello is the emotional side that is driven to act, and will do whatever is necessary to achieve victory. That's the idea behind the theme that the two would have to work together to beat Kira. The most iconic Mello scenes are him speeding down the highway on a motorcycle with a hostage, or blowing up his headquarters to escape capture. He even attains a position of power that allows him to combat Kira through violence, namely finding a mafia boss that even Kira couldn't identify and cutting his head off Jason Todd style, while Near attains a position of power through more bureacratic means. Near outsmarts and Mello acts. This makes Mello stand out more as being different from L than Near does, as he's even more radical than L was. The contrast distorts people's perceptions of the character, causing them to view L and Near as being too similar despite their many differences, simply because they're both understated personalities and socially inept geniuses. Really, people simply overestimate the actual similarities between the two characters when all that they really have in common is their possession of genius level intellects and general dismissal of social norms. And of course, their childish nature.

Finally, we have the claim that the final arc of Death Note, the battle between Near, Mello, and Light was the weakest in the series because of Near. Even if that is what you believe, it doesn't make a lot of sense that people seem to pin that on Near. What people love about L's interactions with Light is how he confronts and challenges him almost constantly, often coming out and saying that he's suspicious of him and trying to catch him off guard. If these interactions were something that really pulled you into their conflict, then that's all the more reason you should love Near, because he is constantly doing the same thing. The very first sentence he ever says to Light is accusatory and throws him off from the very beginning. He's the character that keeps the cat and mouse element of the series alive. The characters that cause the biggest tonal shifts are Mello and Takada, as Mello's actions elevate the level of spectacle we're used to and Takada's involvement with Light add a romance element to the series. Personally, I think the Yotsuba arc is the weakest in Death Note, and I'd even say the dynamic between Near, Mello, and Light made the show more interesting and less predictable than the dynamic between L and Light, just by adding another major player. My favorite arc in the show is the first 9 episodes, when Light and L are both making moves to reveal each other without being in direct contact. It's the most interesting part of the show because being unable to directly speak to each other forces them to be creative regarding how they try to get to each other. Light leaving coded messages in suicide notes and L televising what can essentially be called a diss track are two of my personal favorite events. Don't get me wrong, I think every single arc in this show is a masterpiece, but the specific set up of two anonymous forces subtly working against one another was the most interesting part of the show for me. In that sense, Near's battle with Light feels like a return to form. They are able to speak to each other directly, but Near still has to figure out who Kira is and what he's up to, while Light also has to try to figure out ways to kill Near. It's different enough that it's not a complete rehash of what we've seen before while also having the same allure of the earliest episodes of the show, and it's all thanks to Near.

Now that I'm done defending him, let's get into what I like about Near.

Looking at all of the major players in Death Note, you'll see that most of them have an identifiable quirk. Specifically, the ones related to Wammy's House. L has his iconic sweet tooth, Mello has his penchant for chocolate, and Near has his toys. One of the things that I like about Near is that his toys actually mean something, contrasted from L's sweets accompanying him in most scenes as just another way to make him a weird character, or Mello's chocolate pretty much meaning nothing to the character at all, every single time we see him playing with his toys, it's a metaphorical representation of his thought process. For example, take this scene from the final chapter of Death Note, the flash forward one year after the conclusion of the Kira case. Here, we see Near surrounded by an impossibly huge house of cards. The metaphor here is that he's been spending the last year building something incredibly intricate and substantial: his career as L. There's also the scene where Light and Near speak for the first time, and Near is tossing darts at a dart board while he explains his thoughts on the case. With each comment, he tosses a dart at the board. He suggests that Kira might have killed Mello's hostage, which would suggest that he's someone with access to the Japanese police force's information. He's correct, but he doesn't have all of the details. At the conclusion of his statement, he misses the dartboard. He's not quite on the mark. Then, there's the moment when Near calls Light to tell him that they'll be meeting in the near future. During the call, Near is building a model of a tower. Then, we see imagery of Light and Near standing face-to-face in a similar tower. This metaphorically foreshadows that Near is in control of this confrontation. For a less subtle example, there's a scene where many of the SPK members are killed by the Death Note, and later the scene where Aizawa first calls Near. At the same time that the first SPK member falls, a stack of dice that Near had been meticulously piecing together falls. It all comes tumbling down as the organization that Near had built from the ground up is dismantled by Mello. When he talks with Aizawa, he begins building a new stack of dice. Clearly, like the house of cards in the one shot, these stacks of dice represent his career as a detective, or more specifically, his Kira investigation. These metaphors are abundant in the series and they add a level of insight into Near's world view that's pretty interesting to me. He uses his toys to represent the world, and plays with them the same way that he plays at life. This is consistent with him referring to L's death and Light's defeat as having "lost the game". Life's a game, and Near's Yugi Moto, baby.

Now, for the most important point in this entire video. Not only is Near a cool character, he is also the perfect person to succeed L, and to defeat Kira. The rivalry between L and Kira is elevated to absolute importance in the series, but what L and no one in the show seems to acknowledge or even realize is that this rivalry actually deifies Kira. L’s very introduction proves beyond a doubt to the entire world that Kira does exist, that someone out there actually is punishing the wicked. He puts a huge spotlight on Kira and their rivalry from the very moment that he becomes known to the world. A man with godlike power versus the greatest mind in the world. L states multiple times that stopping Kira is a cause that’s worth his life. This not only deifies Light in the eyes of society at large, resulting in cultist followers like Teru Mikami forming around the world, but it especially does so in the eyes of Light himself. This dude really starts buying into his own hype like crazy, to the point that by the time he does meet Near, he calls him “far inferior to L”, and dismisses him as a threat. The reason that this makes Near a great foil to Light is that Near does not think Light is special, allowing him to humble him in unique ways. Near says something to Light that I, as a viewer, had wanted to say to him throughout the entire show, and something that I guarantee you L would never say. Near calls Kira, Light Yagami, nothing more than a crazy serial killer. Light, who had defeated the greatest detective on Earth, his greatest personal challenge, is bested by a child who doesn’t even grasp the importance of what’s at stake. This is what goes through his mind in his final moments, and it’s the ultimate reality check. While Near tells Light that he’s nothing special, he holds up the Death Note as the most dangerous weapon of mass murder in history. The spot light isn’t on Light for Near. He instead identifies the truly unique evil and the real remarkable detail in this case, the Death Note itself. Light isn’t special to Near. The Death Note is. This, I think, is what makes Near the only character in the show that actually grasps the truth of the situation. The reason that Mello wouldn’t be as good of a foil as Near was, despite the fact that he’s in the same position of being L’s successor, is that he has the same problem that Light and L had, but regarding Near. To him, his rivalry with Near is the most important thing. Rather than denouncing Light as Near did, he’d probably have said something like “Beating you was the best way for me to beat Near.” All of this made him an even more perfect candidate for the final victor than Mello or even L himself in my opinion. Light believes that he is a God, and that it takes the greatest man he's ever known to even pose a challenge to him. Near defeats him, basically saying "I'm not as great a man as L was. I'm not as experienced a detective or as righteous as he was. However, I'm still enough to beat you, because you, Light Yagami, are not special." That's what I love about Near, both as a character and as a part of the plot.

#near #death note #anime analysis #character analysis

3 notes · View notes

just-mythyk · 5 years ago

Note

Whatcha thinking about? What idea have you beem kicking around for awhile?

when i read that first sentence my brain was like “well now i can read in benrey’s voice and that mildly concerns me that i get his speech patterns + sound”

but uh yeah, writing. that’s what that second part means.

mostly my jahl’kin/mythos/freakshow story that just loves adding on things and details in the weirdest ways and i’m *pretty* sure i’m at like, 3 aus at this point of what happens “now” though i want to stick to a single, more rational canon.

i believe the jahl’kin is my latest topic. they actually originated from @a-piece-in-time, a story blog i made that i’ve kinda let die due to current circumstances.

anyways, the whole deal with jahl’kin is actually doing my best to limit their abilities. they’re a bit like... if a dnd spellcaster that “stocks” spells but instead it was basically tattoos on their arms.

so, tattoo spells they can dispel at any time they wish, and use just about anything to draw them on (then ~magic~ to turn them into these “tattoos”). i drew inspiration from The Inheritance Cycle, in that they have to draw the energy from somewhere and can gain more energy with practice. oh, and then i added on a discernment between “precision” and “intention” for how they can use their magic (which might also be inspired by the aforementioned series).

in addition, my brain’s decided it wants to figure out some reasoning to have a character that can reincarnate for generations which leads to being super powerful.

and then in that specific freakshow, there’s some au in this lil’ head that there are places where time is strange and people live for much longer due to... something.

and then my personal universe i don’t really talk about having “children of elements” because i binge-read the webtoon comic Urban Animal.

I have a lot of thoughts.

#mythyk chat #anon #mythyk writes #jahl'kin #ask mythyk #thanks for asking me about this #it's kinda nice to just ramble a bit #go ahead and ask details for anything #i don't mind #in fact i encourage it #it helps to ramble so i can worldbuild #Anonymous

0 notes

suzanneshannon · 5 years ago

Text

Using Custom Property “Stacks” to Tame the Cascade

Since the inception of CSS in 1994, the cascade and inheritance have defined how we design on the web. Both are powerful features but, as authors, we’ve had very little control over how they interact. Selector specificity and source order provide some minimal “layering” control, without a lot of nuance — and inheritance requires an unbroken lineage. Now, CSS Custom Properties allow us to manage and control both cascade and inheritance in new ways.

I want to show you how I’ve used Custom Property “stacks” to solve some of the common issues people face in the cascade: from scoped component styles, to more explicit layering of intents.

A quick intro to Custom Properties

The same way browsers have defined new properties using a vendor prefix like -webkit- or -moz-, we can define our own Custom Properties with an “empty” -- prefix. Like variables in Sass or JavaScript, we can use them to name, store, and retrieve values — but like other properties in CSS, they cascade and inherit with the DOM.

/* Define a custom property */ html { --brand-color: rebeccapurple; }

In order to access those captured values, we use the var() function. It has two parts: first the name of our custom property, and then a fallback in case that property is undefined:

button { /* use the --brand-color if available, or fall back to deeppink */ background: var(--brand-color, deeppink); }

This is not a support fallback for old browsers. If a browser doesn’t understand custom properties, it will ignore the entire var() declaration. Instead, this is a built-in way of handling undefined variables, similar to a font stack defining fallback font families when one is unavailable. If we don’t provide a fallback, the default is unset.

Building variable “stacks”

This ability to define a fallback is similar to “font stacks” used on the font-family property. If the first family is unavailable, the second will be used, and so on. The var() function only accepts a single fallback, but we can nest var() functions to create custom-property fallback “stacks” of any size:

button { /* try Consolas, then Menlo, then Monaco, and finally monospace */ font-family: Consolas, Menlo, Monaco, monospace; /* try --state, then --button-color, then --brand-color, and finally deeppink */ background: var(--state, var(--button-color, var(--brand-color, deeppink))); }

If that nested syntax for stacked properties looks bulky, you can use a pre-processor like Sass to make it more compact.

CodePen Embed Fallback

That single-fallback limitation is required to support fallbacks with a comma inside them — like font stacks or layered background images:

html { /* The fallback value is "Helvetica, Arial, sans-serif" */ font-family: var(--my-font, Helvetica, Arial, sans-serif); }

Defining “scope”

CSS selectors allow us to drill down into the HTML DOM tree, and style elements anywhere on the page, or elements in a particular nested context.

/* all links */ a { color: slateblue; } /* only links inside a section */ section a { color: rebeccapurple; } /* only links inside an article */ article a { color: deeppink; }

That’s useful, but it doesn’t capture the reality of “modular” object-oriented or component-driven styles. We might have multiple articles and asides, nested in various configurations. We need a way to clarify which context, or scope, should take precedence when they overlap.

Proximity scopes

Let’s say we have a .light theme and a .dark theme. We can use those classes on the root <html> element to define a page-wide default, but we can also apply them to specific components, nested in various ways:

CodePen Embed Fallback

Each time we apply one of our color-mode classes, the background and color properties are reset, then inherited by nested headings and paragraphs. In our main context, colors inherit from the .light class, while the nested heading and paragraph inherit from the .dark class. Inheritance is based on direct lineage, so the nearest ancestor with a defined value will take precedence. We call that proximity.

Proximity matters for inheritance, but it has no impact on selectors, which rely on specificity. That becomes a problem if we want to style something inside the dark or light containers.

Here I’ve attempted to define both light and dark button variants. Light mode buttons should be rebeccapurple with white text so they stand out, and dark mode buttons should be plum with black text. We’re selecting the buttons directly based on a light and dark context, but it doesn’t work:

CodePen Embed Fallback

Some of the buttons are in both contexts, with both .light and .dark ancestors. What we want in that case is for the closest theme to take over (inheritance proximity behavior), but what we get instead is the second selector overriding the first (cascade behavior). Since the two selectors have the same specificity, source order determines the winner.

Custom Properties and proximity

What we need here is a way to inherit these properties from the theme, but only apply them to specific children. Custom Properties make that possible! We can define values on the light and dark containers, while only using their inherited values on nested elements, like our buttons.

We’ll start by setting up the buttons to use custom properties, with a fallback “default” value, in case those properties are undefined:

button { background: var(--btn-color, rebeccapurple); color: var(--btn-contrast, white); }

Now we can set those values based on context, and they will scope to the appropriate ancestor based on proximity and inheritance:

.dark { --btn-color: plum; --btn-contrast: black; } .light { --btn-color: rebeccapurple; --btn-contrast: white; }

As an added bonus, we’re using less code overall, and one unified button definition:

CodePen Embed Fallback

I think of this as creating an API of available parameters for the button component. Sara Soueidan and Lea Verou have both covered this well in recent articles.

Component ownership

Sometimes proximity isn’t enough to define scope. When JavaScript frameworks generate “scoped styles” they are establishing specific object-element ownership. A “tab layout” component owns the tabs themselves, but not the content behind each tab. This is also what the BEM convention attempts to capture in complex .block__element class names.

Nicole Sullivan coined the term “donut scope” to talk about this problem back in 2011. While I’m sure she has more recent thoughts on the issue, the fundamental problem hasn’t changed. Selectors and specificity are great for describing how we build detailed styles over top of broad patterns, but they don’t convey a clear sense of ownership.

We can use custom property stacks to help solve this problem. We’ll start by creating “global” properties on the <html> element that are for our default colors:

html { --background--global: white; --color--global: black; --btn-color--global: rebeccapurple; --btn-contrast--global: white; }

That default global theme is now available anywhere we want to refer to it. We’ll do that with a data-theme attribute that applies our foreground and background colors. We want the global values to provide a default fallback, but we also want the option to override with a specific theme. That’s where “stacks” come in:

[data-theme] { /* If there's no component value, use the global value */ background: var(--background--component, var(--background--global)); color: var(--color--component, var(--color--global)); }

Now we can define an inverted component by setting the *--component properties as a reverse of the global properties:

[data-theme='invert'] { --background--component: var(--color--global); --color--component: var(--background--global); }

But we don’t want those settings to inherit beyond the donut of ownership, so we reset those values to initial (undefined) on every theme. We’ll want to do this at a lower specificity, or earlier in the source order, so it provides a default that each theme can override:

[data-theme] { --background--component: initial; --color--component: initial; }

The initial keyword has a special meaning when used on custom properties, reverting them to a Guaranteed-Invalid state. That means rather than being passed along to set background: initial or color: initial, the custom property becomes undefined, and we fallback to the next value in our stack, the global settings.

We can do the same thing with our buttons, and then make sure to apply data-theme to each component. If no specific theme is given, each component will default to the global theme:

CodePen Embed Fallback

Defining “origins”

The CSS cascade is a series of filtering layers used to determine what value should take precedence when multiple values are defined on the same property. We most often interact with the specificity layers, or the final layering based on source-order — but the first layer of cascade is the “origin” of a style. The origin describes where a style came from — often the browser (defaults), the user (preferences), or the author (that’s us).

By default, author styles override user preferences, which override browser defaults. That changes when anyone applies `!important` to a style, and the origins reverse: browser `!important` styles have the highest origin, then important user preferences, then our author important styles, above all the normal layers. There are a few additional origins, but we won’t go into them here.

When we create custom property “stacks,” we’re building a very similar behavior. If we wanted to represent existing origins as a stack of custom properties, it would look something like this:

.origins-as-custom-properties { color: var(--browser-important, var(--user-important, var(--author-important, var(--author, var(--user, var(--browser)))))); }

Those layers already exist, so there’s no reason to recreate them. But we’re doing something very similar when we layer our “global” and “component” styles above — creating a “component” origin layer that overrides our “global” layer. That same approach can be used to solve various layering issues in CSS, which can’t always be described by specificity:

Override » Component » Theme » Default

Theme » Design system or framework

State » Type » Default

Let’s look at some buttons again. We’ll need a default button style, a disabled state, and various button “types,” like danger, primary and secondary. We wan’t the disabled state to always override the type variations, but selectors don’t capture that distinction:

CodePen Embed Fallback

But we can define a stack that provides both “type” and “state” layers in the order that we want them prioritized:

button { background: var(--btn-state, var(--btn-type, var(--btn-default))); }

Now when we set both variables, the state will always take precedence:

CodePen Embed Fallback

I’ve used this technique to create a Cascading Colors framework that allows custom theming based on layering:

Pre-defined theme attributes in the HTML

User color preferences

Light and dark modes

Global theme defaults

Mix and match

These approaches can be taken to an extreme, but most day-to-day use-cases can be handled with two or three values in a stack, often using a combination of the techniques above:

A variable stack to define the layers

Inheritance to set them based on proximity and scope

Careful application of the `initial` value to remove nested elements from a scope

We’ve been using these custom property “stacks” on our projects at OddBird. We’re still discovering as we go, but they’ve already been helpful in solving problems that were difficult using only selectors and specificity. With custom properties, we don’t have to fight the cascade or inheritance. We can capture and leverage them, as-intended, with more control over how they should apply in each instance. To me, that’s a big win for CSS — especially when developing style frameworks, tools, and systems.

The post Using Custom Property “Stacks” to Tame the Cascade appeared first on CSS-Tricks.

Using Custom Property “Stacks” to Tame the Cascade published first on https://deskbysnafu.tumblr.com/

0 notes

recruitmentdubai · 5 years ago

Text

Using Custom Property “Stacks” to Tame the Cascade

I want to show you how I’ve used Custom Property “stacks” to solve some of the common issues people face in the cascade: from scoped component styles, to more explicit layering of intents.

A quick intro to Custom Properties

/* Define a custom property */ html { --brand-color: rebeccapurple; }

In order to access those captured values, we use the var() function. It has two parts: first the name of our custom property, and then a fallback in case that property is undefined:

button { /* use the --brand-color if available, or fall back to deeppink */ background: var(--brand-color, deeppink); }

Building variable “stacks”

If that nested syntax for stacked properties looks bulky, you can use a pre-processor like Sass to make it more compact.

CodePen Embed Fallback

That single-fallback limitation is required to support fallbacks with a comma inside them — like font stacks or layered background images:

html { /* The fallback value is "Helvetica, Arial, sans-serif" */ font-family: var(--my-font, Helvetica, Arial, sans-serif); }

Defining “scope”

CSS selectors allow us to drill down into the HTML DOM tree, and style elements anywhere on the page, or elements in a particular nested context.

/* all links */ a { color: slateblue; } /* only links inside a section */ section a { color: rebeccapurple; } /* only links inside an article */ article a { color: deeppink; }

Proximity scopes

CodePen Embed Fallback

Proximity matters for inheritance, but it has no impact on selectors, which rely on specificity. That becomes a problem if we want to style something inside the dark or light containers.

CodePen Embed Fallback

Custom Properties and proximity

We’ll start by setting up the buttons to use custom properties, with a fallback “default” value, in case those properties are undefined:

button { background: var(--btn-color, rebeccapurple); color: var(--btn-contrast, white); }

Now we can set those values based on context, and they will scope to the appropriate ancestor based on proximity and inheritance:

.dark { --btn-color: plum; --btn-contrast: black; } .light { --btn-color: rebeccapurple; --btn-contrast: white; }

As an added bonus, we’re using less code overall, and one unified button definition:

CodePen Embed Fallback

I think of this as creating an API of available parameters for the button component. Sara Soueidan and Lea Verou have both covered this well in recent articles.

Component ownership

We can use custom property stacks to help solve this problem. We’ll start by creating “global” properties on the <html> element that are for our default colors:

html { --background--global: white; --color--global: black; --btn-color--global: rebeccapurple; --btn-contrast--global: white; }

[data-theme] { /* If there's no component value, use the global value */ background: var(--background--component, var(--background--global)); color: var(--color--component, var(--color--global)); }

Now we can define an inverted component by setting the *--component properties as a reverse of the global properties:

[data-theme='invert'] { --background--component: var(--color--global); --color--component: var(--background--global); }

[data-theme] { --background--component: initial; --color--component: initial; }

We can do the same thing with our buttons, and then make sure to apply data-theme to each component. If no specific theme is given, each component will default to the global theme:

CodePen Embed Fallback

Defining “origins”

When we create custom property “stacks,” we’re building a very similar behavior. If we wanted to represent existing origins as a stack of custom properties, it would look something like this:

.origins-as-custom-properties { color: var(--browser-important, var(--user-important, var(--author-important, var(--author, var(--user, var(--browser)))))); }

Override » Component » Theme » Default

Theme » Design system or framework

State » Type » Default

CodePen Embed Fallback

But we can define a stack that provides both “type” and “state” layers in the order that we want them prioritized:

button { background: var(--btn-state, var(--btn-type, var(--btn-default))); }

Now when we set both variables, the state will always take precedence:

CodePen Embed Fallback

I’ve used this technique to create a Cascading Colors framework that allows custom theming based on layering:

Pre-defined theme attributes in the HTML

User color preferences

Light and dark modes

Global theme defaults

Mix and match

These approaches can be taken to an extreme, but most day-to-day use-cases can be handled with two or three values in a stack, often using a combination of the techniques above:

A variable stack to define the layers

Inheritance to set them based on proximity and scope

Careful application of the `initial` value to remove nested elements from a scope

The post Using Custom Property “Stacks” to Tame the Cascade appeared first on CSS-Tricks.

source https://css-tricks.com/using-custom-property-stacks-to-tame-the-cascade/

from WordPress https://ift.tt/3163VCL via IFTTT

#web developer #web development #website developer

0 notes

meditationadvise · 7 years ago

Text

Tonight`s Halloween New Moon In Scorpio Is The Most Powerful Of The Year. THIS Is The Time To Manifest Your Wildest Dreams

Abracadabra! On Sunday, October 30, the Scorpio brand-new moon does an effective vanishing act, burying our globe in darkness-- in the best way possible.

As la luna shrouds us in a shroud of mystery, we plunge into the darkness of the hidden universe within ourselves. As our external eyes, as well as our internal vision, change to the darkness, it is right here we could begin to see the light. New moons are generally unnoticeable to the nude eye, yet we could want to the dark evening skies as if it were an empty canvas-- symbolic for new beginnings and also intention setting.

There's nothing midway about the intensity of Scorpio energy, which can often drift to the extremes. While Scorpio is associated with control, prominence, and intensity, it births an exceptionally powerful and spiritual power, as well. Scorpio is the leader of makeover, making this lunation additional effective when it concerns changing components of our lives that have been-- until now-- previously blocked.

Sunday's Scorpio new moon could be absolutely alchemical. Are you all set to turn a leaden element of your life right into pure, shimmering gold? Obtain the round rolling on those metamorphic initiatives. Actual change takes job-- as well as it never ever simply occurs overnight. However this is a NEW moon, so it's everything about establishing clear intents then jumping off the beginning block. We have until May 10, 2017-- the date of the matching moon in Scorpio-- to break out of limiting routines as well as replace them with routines that give us life.

The Scorpio brand-new moon will certainly rest at a close level to calculated Mercury, so operating from a specific plan is the way to win. Mercury is the social butterfly of the zodiac, so ignore having a hard time alone making change. Sign up with a support system, online and in real-time, to champion each other as we rise from the ashes!

Here are a couple of routines you could do to alchemize your life at the Scorpio new moon:

1. Transform garbage into treasure.

Scorpio is the regenerator of the zodiac: the typical Phoenix, the best recycler. Its alchemical powers can transform metaphorical introduce gold. Today, you simply might discover something in a dump worth salvaging. A connection, a pair of shoes, a journal entry that turns into a prize-winning short film ... there's something you've deserted that's ripe for reinvention. Discover it. Re-spin it. Make something old shiny and also new again.

2. Inspect beneath 'the hood.'

Scorpio is the indication of interior wellness, and the Scorpio new moon is a golden time to restore your inner well-being before the winter. Ruled by Pluto, god of the underworld, Scorpio is consumed with exactly what's occurring on the in. Have not had your blood attracted for some time? Make a consultation for a little needling. (Scorpio is specifically connected to hematology, so if you're feeling worn down, you could find a need for more iron at this new moon.) Befalled of touch with your gyno? Come by for a tete-a-tete with the ol' speculum. Cleans, detoxes, colonics, severe facials (think: aestheticians pressing the s *** outta your pores) will certainly siphon out all the cruds, rejuvenating and restoring your glow.

3. Rebirth your sexual prowess.

Scorpio is best referred to as the 'sex indication,' as it rules the reproductive organs. However, sex is much from leisure under Scorpio's reign. It's a way of getting to greater airplanes of euphoria, consciousness, and spiritual understanding. The Scorpio new moon is an excellent time to up your libidinous literacy. T is for tantra, so start your sex-related alphabet lessons there. Back up a few letters to O, and clean up on climaxes as well as oxytocin. Oxytocin is the 'bonding hormone' that's released when ladies nursed, so look adoringly at a baby/kitten/puppy as well as (drumroll) at a climax. Scorpio rules perma-bonding, so this hormone is of unique rate of interest today. If you do not desire to wind up fixated with a no-strings fling, find out about your inner drug store and its transformative chemical powers.

4. Embrace the urge to merge.

So you're generating income, however what are you truly doing besides spending it? Scorpio comprehends that true riches originates from possession: actual estate, assets, intellectual home. Scorpio guidelines joint resources, whether it's a residence that you co-own (with a partner OR the bank), money that you've borrowed from a financial institution, or intellectual legal rights to an item of work that pays you passive income.

Today, look at your portfolio as well as count your properties. Perhaps you have actually got a varied spread of stocks, a lodge, as well as aristocracies from an optioned flick. Perhaps you've just got your great-grandma's wedding ring ... or nothin' a lot at all.

Whatever the situation, the Scorpio new moon is ideal for establishing your mind on making your money job harder for you. If you're in financial obligation, develop a settlement strategy or decrease your rate of interest by changing to a zero-percent equilibrium transfer card. You might also hock some things on eBay as well as put the profits right into an interest-bearing account. Reduce your carbon impact AND ALSO your costs creatively: Bike to work (or carpool), host meals to lower the grocery store costs, or begin an investment club with some wise friends.

5. Harness your psychic powers.

Scorpio has a track record for being uncannily intuitive, even downright psychic. This brand-new moon will certainly open up a powerful website, producing sixth sense as well as recognizing flashes. In this uber-practical, material globe (the domain name of Scorpio's OPPOSITE indication, Taurus), the majority of us might have the tendency to brush these messages apart, never ever giving much support to our inner assistance. However in Scorpioville, absolutely nothing is also freaky, psychedelic, or astonishing to be explored.

What would take place if we spent the whole day communing with the little voice in our heads? If we did 5 to ten minutes of free-writing on top of each hr, allowing our hand dancing throughout the web page, revealing the inner workings of our minds? What may look like crazy-talk could in fact be the kernels of brilliant thought. Shush the inner movie critic and also let it move. We guarantee that you'll be surprised on your own at least when throughout this brand-new moon.

An eyes-closed, lights-off meditation might also yield brand-new 'view.' You might also position a crystal on the area in between your eyebrows, that little location called the third-eye chakra which is the physical factor where greater awareness as well as intuition circulations. Battering out an ancient rhythm in a drum circle could get you in a close to trancelike state also, quieting the mind and also awakening your extrasensory assumption. Allow go and let it stream. Deep space is your psychic hotline now.

6. Take a digital detox.

In maintaining with Scorpio's 'tune in, activate, leave' ethos, circle the Scorpio new moon for a 24-hour media diet plan. Silence social media and give on your own a breather from the blogosphere. You might not understand what does it cost? you're zombie-walking with life, absorbing the ads, feeds, as well as hundreds of images you see daily. In the words of Scorpio thought leader Terence McKenna, 'Stop consuming images and also begin creating them.' Paint. Draw. Develop a collage ... and don't be amazed if your images manifest into kind in the days ahead under Scorpio's effective influence.

7. Fan the flame of desire.

To allow sex-related power to training course with our bodies is to touch the force of life-- this is something Scorpio well recognizes. Although this indicator obtains a representative for being vampy and also compulsive, in its highest expression, Scorpio could evoke a sacred sexuality. Believe: tantra, mind-body-soul links, a timeless as well as timeless appeal. Our sexual triggers never head out, yet we must maintain the pilot burner lit.

Forget just what the style mags have announced as attractive as well as stop obsessing in the mirror. Sexuality does not live there. It stays in our link to eros, which originates from being incredibly present and fired up about life. Relocating your body in a manner that makes you feel sensual is the method to obtain this magnetic pressure moving. Who cares if Sunday is a college night? Welcome the evening owl vibes of this new moon as well as dancing 'til way previous your going to bed. (For extra on this, look into the sacred seduction mentors of Cat Cavalier.)

Scorpio is the indication that is also connected with fatality and renewal. Sometimes, inescapable finalities must occur in order for us to come to life-- and right into our sexuality-- once again. This eclipse might hint 'the start of the end,' as we muster the nerve to claim bye-bye to scenarios (or limiting ideas about ourselves and also others) that are deadening, draining, as well as downright unsexy.

Of course, farewells are not always a fatal issue. The French refer to an orgasm as 'La petit mort,' translated straight as 'the little death.' May this new moon bring you such, ahem, delighted endings.

8. Reveal economic abundance.

Scorpio rules our larger, swelling sum material resources (commissions, aristocracies, incentives, inheritances) in addition to the loan we share with others. How finest to shake that moneymaker during the brand-new moon as well as sow the seeds of success? Not by jumping in the daily grind, playing a ruthless video game of shark-eat-shark. That would certainly be the reduced power of Scorpio in activity ... which always comes 'rounded to attack us in the ass in the end.

Instead, we ought to fly like the eagle-- the secondary icon representing Scorpio. Manifesting wealth from a visionary place is as a lot a matter of confidence as it is skill. We could enroll in workshops as well as courses till the cows get home, however if we don't believe that we actually deserve this loan, it will stream out of our lives like water via a filter. In her publication The Law of Divine Compensation, miracle-maven Marianne Williamson (a Cancer) schools us in shifting our state of mind so we can open up to the miracles as well as success the universe has to offer.

Simple mantras could be effective, also. Make a listing of the limiting thoughts you have concerning your sources ... for example, 'There's insufficient cash to go about.' When these limiting beliefs have actually been lit up, reframe them as positives, as in 'I am well dealt with by the globe as well as my enjoyed ones.' Tape that mantra to your mirror and repeat each morning. Soon enough, this credo will certainly become extra than a platitude ... it will certainly be the way you watch the world.

9. Revenge is a meal finest acted as success.

The mention of Scorpio sends out shivers down some people's spinal columns, however that's because they just know component of the tale. Scorpio in fact has 3 stages, or energetic resonances. The most affordable is the ground-dwelling Scorpion, the conveniently endangered animal with the dangerous, malevolent sting. Above that is the rising eagle, the wizened Scorpio who's learned his life's lessons and also keenly observes whatever with laser understanding. The greatest indication is the Phoenix az, the mythological bird that rises from the ashes of devastation to create new life.

At the Scorpio new moon, we could pick to access any type of one of these energies-- consisting of getting back at. If you need to stir a wish for payback, do so proactively. Keep in mind the adage that success is the very best revenge. Win the fight AND the battle by making your personal life incredible rather compared to taking someone else's happiness down.

#meditation #meditation quotes #spiritual

0 notes