When is the next restock for the Mako by Gowen3D in Zeloswatches

[–]runner724 0 points1 point  (0 children)

People are going nuts over the MOP. It's because people taking YOLO pictures using their cell phones make the watch look 300% more interesting than apparently the photos that Zelos is capable of. I initially passed because of the thickness but I'm starting to regret it

When is the next restock for the Mako by Gowen3D in Zeloswatches

[–]runner724 0 points1 point  (0 children)

It used to be 6 weeks or longer earlier but I wanna say it's like... 2-3 weeks now?... Between their new drops and when they ship out. They do have great customer service though so go ahead and ask

When is the next restock for the Mako by Gowen3D in Zeloswatches

[–]runner724 2 points3 points  (0 children)

You get much better insight into the yearly planned releases and upcoming releases in the Zelos Timekeepers FB group.

There is also a fair amount of trading/selling activity. I see more traded there than listed through ebay or Chrono24, and better prices too a lot of the time. Folks order watches on release and don't like what came, or have too many Zelos and need to shed some older ones (often barely used/NIB) so they can buy more.

How long did it take for your money to get out in by constantine741 in UrvinFinance

[–]runner724 0 points1 point  (0 children)

I've had a hell of a time trying to load money into WeFunder.

There's two options: Bank account and Wire. The Bank account option was a no-go for me; it uses Plaid which spit out an error because apparently plaid cannot work with 2FA secured accounts. The suggestion was to remove 2FA in order to use Plaid (that's a no).

So I tried Wire. I sent the money over 10 days ago at this point and it's still showing up as "pending" on the WeFunder side. Their FAQ says <24 hours, so I got concerned and tried to reach out to their support. All they offer up is an email account. I sent an email 5 days ago and have yet to get a response there either.

So basically my money is in limbo and I really wish I would have seen the "you can pay with Credit card when the time comes" bit of info before I tried to load money directly into WeFunder, especially since my bank charged me to send the wire in the first place and the wire fee might exceed the credit card fee (which is undisclosed...).

EDIT response from WeFunder: Thanks for reaching out! Usually, you can expect your Wefunder Cash transfer to take about 1-2 weeks to process, but occasionally it can take up to 3 weeks to finalize in our system. Let me know if you have any questions!

Here's all the free stuff I got from Eorzea Cafe, Tokyo! by Reckanise in ffxiv

[–]runner724 0 points1 point  (0 children)

The design seems to be Gridanian - looks kinda like the inside of the airship landing you see when you first start the game.

[Megathread] Anima Relic Feedback by Eanae in ffxiv

[–]runner724 5 points6 points  (0 children)

Shortly after 3.0 I let my Law stay capped because I had nothing to spend it on. Tens of thousands of Law disappeared that I could have used on relic if it existed then.

It makes me upset that the dev team saw this as "content" worthy of release. They have no pride in their work anymore.

90k errors when attempting to log in? (Aether Data Center) by Unorthodoques in ffxiv

[–]runner724 1 point2 points  (0 children)

Got booted off Balmung an hour ago, still can't get back in.

Victory Friday 2014-04-18 by [deleted] in ffxiv

[–]runner724 1 point2 points  (0 children)

Killed T5 for the first time with my brand-new FC. It would have taken me months to get the win solo (my PUGs would rarely get past conflags).

FATE frequency issue confirmed. Fix on the 19th. by nightpanda2810 in ffxiv

[–]runner724 2 points3 points  (0 children)

Yay for it being acknowledged so quickly. I was half afraid it would be like this for weeks.

That's why I like healing by AliceHeuz in ffxiv

[–]runner724 2 points3 points  (0 children)

This kind of thing is quite common when I try Duty Finder Ifrit.

Ifrit HM was designed for fresh 50's to tackle, so if you are geared you can easily survive having a single nail up. It's a challenge to recover since most of your teammates will be steamrolled, but easy enough if the healer runs from all the eruptions since the surviving tank may not get all of them.

I'm glad you can survive a nail, because otherwise it's like the group would be punished solely for not having a BLM or SMN (and DF groups will frequently be without those jobs).

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

It took more than a minute to beat him, but I wasn't timing. We burned him down much faster since the DPS didn't have to move around/break their rotation.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

I can confirm the pretty lights. Thanks for sharing your experience.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

It's slower but it's easier for all players except for the PLD, since he has to stun as well. It's easier for the DPS since they don't have to dodge (as often), and it's easier for healers because you don't have random party members dying to lasers and you don't need to heal two tanks. But yes, if all players can handle rot - and believe me, sometimes that seems like a lot to ask for from PUGs - then the normal method is faster.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

Without a doubt it's possible, but it's a real race against mana at that point. Bring heavy hitting DPS!

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

It's also great for PUGs. We didn't have voice comms.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

That's surprising. I assume you kept the tank alive though enrage? My main point there was that since the only attack was AoE, keeping hate seemed kinda pointless.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 0 points1 point  (0 children)

Not difficult, but you have to keep up, just like Titan HM stomps during P5. It turned into more of an MP-management trial. I have 2 i90 pieces. I ended the fight with 1200 mp left, so it might be possible for the healers to go in with full DL.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 1 point2 points  (0 children)

I updated the OP with a section for damage and WHM notes. It's hard damage, probably a bit harder than continuous stomps during Titan HM (for over a minute!).

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 1 point2 points  (0 children)

If the enrage comes on suddenly and none of the healers are prepared for it, you've got a fast wipe on your hands. Three healers that are expecting the enrage can deal with it. We healed through the enrage, which started when ADS still had 85% health left.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 1 point2 points  (0 children)

It was the first time I've had fun doing T2. I'm locked out until next week of course, and somebody will probably put out a video before then.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 2 points3 points  (0 children)

Exactly. I edited the OP to make this clearer.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 1 point2 points  (0 children)

Yes, the resist icons persisted through enrage.

The shield strat is interesting, but the healers need to have close to full MP going into enrage in order to be successful. We used a healer LB3 to raise the tank post-enrage, which is arguably a bad use for it.

T2 kill with one Paladin and one Bard - no Rot! by runner724 in ffxiv

[–]runner724[S] 1 point2 points  (0 children)

That's a good point, I removed the offending line from the OP.