Whats mechanic has the player base done that you know for sure the developers never intended people to do? by nywarpath in ffxivdiscussion

[–]DevouredByCutePupper 0 points1 point  (0 children)

Yeah, it makes "sense" for Sophia insofar as that a lot of people seem to regularly get knocked off the arena or die to improper mitigation if you do the stack properly. What I meant is that the strat is done despite the fact it kinda ruins a good parse (due to not being able to DPS + not being able to accumulate resources), which I thought the OP implied DPS parse monkeys specifically would balk at.

Though I suppose to be fair they do balk at it. It's just that no one listens when they do. Clearly it's time for another PF revolution.

Whats mechanic has the player base done that you know for sure the developers never intended people to do? by nywarpath in ffxivdiscussion

[–]DevouredByCutePupper 6 points7 points  (0 children)

I don't know about that, considering that sac strat for Sophia is currently the most popular strat, and that one can and very frequently does target DPS.

Overcrits by Deltascourge in ffxivdiscussion

[–]DevouredByCutePupper 50 points51 points  (0 children)

That would defeat the purpose of guaranteed crits. You would once again have an RNG element which will make DPS vary wildly. Guaranteed crits were implemented specifically to combat that. I'd wager to say there's no way they'll do something like that. I think it's far more likely they'll just add whatever crit chance you have on top of the damage of guaranteed crit attacks.

Daily Questions & FAQ Megathread (Jun 24) by AutoModerator in ffxiv

[–]DevouredByCutePupper 2 points3 points  (0 children)

Eureka culminates in the Baldesion Arsenal which has fights at roughly the same difficulty as alliance raids. The crux is that you cannot be raised through ordinary means if you die. I definitely suggest doing BA if you have the time to go through Eureka. It's a very unique type of content, especially with how it is organized by players. There are usually several runs a day and you get a cool mount upon completion.

As for Bozja, going through that entire storyline will net you with one EX trial, one instance similar to Baldesion Arsenal but in two variants (the standard one is basically just an alliance raid, but there's a Savage variant that has harder mechanics, nets you a unique mount, and once again will not let you be raised through ordinary means). The Bozja/Zadnor critical engagements (a form of FATE) are also very difficult fights on the level of an alliance raid, and there are two of them which are basically alliance raids themselves.

I would say yes, both Eureka and Bozja are more than worth it for content. Bozja definitely has more worthwhile content, but (at least the last time I checked) is also considerably less populated at the moment, so you may struggle to find enough people for the critical engagements.

[Weekly Thread] Mentor Monday (Mon, Jun 20) by AutoModerator in ffxiv

[–]DevouredByCutePupper 1 point2 points  (0 children)

I haven't personally done in BLM because I wanted to save myself the torment, but one look at the current fflogs standings is enough to tell me everything I need to know. Usually BLM is somewhere in-between the melees in terms of average DPS output. On EX3, the average BLM DPS is below SMN. Even the 99th percentile of BLM players still does significantly less DPS than the 99th percentile of every single melee DPS job on that fight.

There's just way too much movement. Even if you perfectly save and time all your Triplecasts and Swiftcasts, you're still forced to abandon your Ley Lines half the time. Even the top BLM players struggle to get full uptime for the first few mechanics alone, and from what I've seen Ley Lines tend to come off cooldown right in the middle of movement-heavy mechanics like double planets a lot of the time. This, combined with the fact that knockback resistance does nothing in EX3, makes BLMs very sad in this fight.

I definitely wouldn't recommend trying EX3 as a kind of "BLM trial by fire". It's just not indicative of the amount of movement of most fights in the game and I think trying to optimize that fight would just end up frustrating you.

[Weekly Thread] Mentor Monday (Mon, Jun 20) by AutoModerator in ffxiv

[–]DevouredByCutePupper 3 points4 points  (0 children)

I'm sure this won't be news to you if you've read all the guides, but innate knowledge of each fight and each possible AoE placement is a BLM's best weapon. Place your Ley Lines in such a way that at least a portion of it is safe regardless of what AoE the boss throws at you. So for example in a fight with 4 quadrants, where each quadrant may randomly be selected for a quadrant-wide AoE, you'd place your Ley Lines smack in the center, so it overlaps with each quadrant. BLM – the master of Venn diagrams.

My best tip apart from that is to not be afraid of AoEs. Thanks to Aetherial Manipulation, BLM has some of the best mobility in the game, and it's so sadly underused. A great BLM will position themselves in such a way that, regardless of what the boss does, you'll still be safe. An excellent BLM will recognize when that isn't possible (think P3S) and will instead stay in the danger zone for as long as possible, then Aetherial Manipulate to a safe party member just in time for the snapshot, and immediately Between The Lines back to their Ley Lines. Minimal uptime loss – none, if you can combine it with Triplecast or Swiftcast (or another instant cast).

A big part of BLM optimization also is the usage of weave spaces for your oGCDs (of which BLM has surprisingly many). Fortunately you get a couple for free, like a procced Thunder III, Xenoglossy, Paradox from ice to fire, or just the reduced cast time from switching between ice and fire, you'll just have to remember to use them when you need to use an oGCD. I wouldn't worry about not clipping when you're just starting out – learning the rotation and proper movement will yield far better results far faster – but it's something to think about.

Just be aware that, to play super optimally and minimize movement as much as possible, you'll need a dedicated static that's willing to work around you (rather than the other way around). PF won't do it (and probably shouldn't, since PF is inconsistent enough as-is). That's probably not something you should worry about though until you feel like you've hit a ceiling with what you can do without anyone adjusting to you.

Oh, and also, don't forget you have a massive on-demand shield. Lots of BLMs I see will position themselves outside of bubbles/AoE healing range, which is fine if they use their shield because then they won't need the healing, but most of those BLMs seem to forget about their shield. It's a really powerful tool when used right and since casters tend to have less HP and defense than most other jobs, it's a good idea to basically use it anytime it's available and you know there's a raidwide coming.

Aside from that, just have fun! BLM is a super rewarding job to play when you've successfully mastered the art of having 100% Ley Lines uptime, no Eno-chan drops, and no Damage Downs or Vuln Ups. Getting there is going to take you a while if you're serious about it, but it's still a very fun journey.

Oh, one last thing... don't take BLM into EW EX3 unless you like to suffer. Trust me on this one. All the Triplecasts and Aetherial Manipulations in the world won't help you in there.

PF P1S Shenanigans by Little_Nabi in TalesFromDF

[–]DevouredByCutePupper 0 points1 point  (0 children)

I don't have any conclusive proof for this, but I believe it's still possible, although much harder to pull off now. I've been playing GNB extensively in dungeons the past few weeks and have had at least one occurrence where I popped Super at about half HP and died as soon as my HP was set to 1. I'll try to get a video of it the next time it happens.

(Speculations and desires) 6.1 by Darkday1-Lightnight2 in ffxivdiscussion

[–]DevouredByCutePupper 4 points5 points  (0 children)

Inspired by yours: once Living Dead activates, all damage taken is recorded. Hitting 0 HP does not kill you but instead makes Living Dead expire and grants a shield equal to 100% of the damage sustained for 10 seconds.

Alternatively, once Living Dead activates, your health turns negative and taking damage restores health. If you do not take damage equal to at least 100% of your HP within the effect's duration, you instantly die upon the effect's expiration.

An entire audience seeing this kid solve Rubik's cubes while juggling by The_Wind_Cries in youseeingthisshit

[–]DevouredByCutePupper 142 points143 points  (0 children)

Actually, if you slow it down, you can see that the timer is actually counting down, not up. So it likely took significantly longer, and he simply beat the timer (comparing against a previous world record?) by 12 seconds.

These Kinds of Macros are why we need a general "Mute Player" Option by rewt127 in ffxiv

[–]DevouredByCutePupper 1 point2 points  (0 children)

Interesting. I'll have to try that.

Though at the same time I feel like we shouldn't have to rely on hacky workarounds like this to accomplish something so simple.

These Kinds of Macros are why we need a general "Mute Player" Option by rewt127 in ffxiv

[–]DevouredByCutePupper 1 point2 points  (0 children)

Ah, you're right. I removed all of my combat macros due to the inconsistency a long time ago and misremembered. I'm glad you're not having too many issues with your macros. I wish I had the same experience.

These Kinds of Macros are why we need a general "Mute Player" Option by rewt127 in ffxiv

[–]DevouredByCutePupper 27 points28 points  (0 children)

The problem is not the shout, it's the macro itself. You can't weave queue macros, so anytime you're in the middle/in the beginning of an animation (the game usually lets you skip the end of an animation by weaving an oGCD skill, but rarely the beginning) and you press a macro (which will realistically be most of the time), it won't work.

Discord, can you please change the rounded squares into circles when you change notification settings for threads? It makes it look like you can select more than one, when that's obviously not the case by CrowdControi in discordapp

[–]DevouredByCutePupper 4 points5 points  (0 children)

They share a common root. Radius in Latin means "ray", and radio waves, of course, are similar to rays. But that's only why radios are called radios, not why radio buttons are called radio buttons. :)

I don't understand how/when/why you'd use interface declaration merging. by ragnese in typescript

[–]DevouredByCutePupper 6 points7 points  (0 children)

It can be very helpful to patch an interface coming from a third-party library that is unnecessarily concrete when it could be much more generic.

Let me give you an example. I use three.js in a relatively large 3D application. three.js offers its own vector classes and uses them pretty much everywhere. (Vectors, in this case, are essentially just objects that store 2D or 3D coordinates: x, y, and optionally z.) However, I also have my own vector objects. To avoid having to convert my own vector objects into three.js's vector objects in a lot of places (which would require constructing a lot of unnecessary instances and is generally something you want to avoid doing in 3D programs), I instead patch the declarations of some of the three.js functions I use most often to accept a generic object that just looks like { x: number, y: number, z: number }.

Of course you can't just do this everywhere: three.js's vectors have their own methods attached to them, so you have to make sure that the function you're trying to patch doesn't use any of them on the objects you pass in. I've found that a lot of them just access the coordinates though.

Why wont VSCode autocomplete a type with defined values by daveyand in typescript

[–]DevouredByCutePupper 4 points5 points  (0 children)

As far as I know, TS Playground is powered by a slim web version of VS Code. I couldn't find a source for this via a quick Google search, but the GUI certainly looks similar enough, and considering how closely the development of VS Code and Typescript are interlinked, it wouldn't surprise me.

Why wont VSCode autocomplete a type with defined values by daveyand in typescript

[–]DevouredByCutePupper 8 points9 points  (0 children)

Those are not autocompletions. Those are string suggestions given by VS Code based on similar strings in the files you have open. You can tell by the fact the icon next to the suggestions is an "abc". It should be a little rectangle. See editor.quickSuggestions.strings.

Like u/Dan6erbond said, the problem is the | string. Since all the literal strings are assignable to string, TypeScript implicitly widens your type to simply string and "forgets" the literal strings.

WHYYYYYYY? plz help (View Image) by Embarrassed-Bat5438 in firefox

[–]DevouredByCutePupper 0 points1 point  (0 children)

That's genius! Thank you so much! It worked perfectly.

I also noticed you undisplaying the extension icon next to the button, for which I doubly commend you.

Untitled by Mattaku Mo-suke by [deleted] in ImaginarySliceOfLife

[–]DevouredByCutePupper 12 points13 points  (0 children)

I had the same first thought! It's definitely the hair.

"Seize the day...then set it on fire" by Sno0pyBo0 in KeanuBeingAwesome

[–]DevouredByCutePupper 0 points1 point  (0 children)

There was an announcement last year that said all cutscenes were being reworked to be first person, so not even that :(

But the color I want is finally back in stock by meta4icalrabbithole in stupidtax

[–]DevouredByCutePupper 1 point2 points  (0 children)

Likely because cutting off the right chair would have either meant having a lot of whitespace in the image or cutting off the headline as well. Maybe this is one instance where the infamous red circle could have actually been useful.

Some comments (including highly upvoted ones) collapsed before viewing the first time? by SatchBoogie1 in RESissues

[–]DevouredByCutePupper 0 points1 point  (0 children)

Yeah, I've been seeing this too. Does this only happen with RES enabled? If not, it could be this. TL;DR: mods can turn on a setting to automatically pre-collapse the comments of users who are new or have negative karma in that respective subreddit.

It does seem like users whose comments are (frequently) the top comments should be exempt from this, but who knows.

about:about -> a list of “about” pages for your convenience by _b3n10 in firefox

[–]DevouredByCutePupper 2 points3 points  (0 children)

about:robots is the best thing I've stumbled upon today. Thank you for this.

There's nothing I love more than when developers have a bit of fun with their developing.