Forum Replies Created
-
Posts
-
I still feel like 81 is a good decision, the only argument I have is that we do 81, 85, and 89. I feel like last time the 5.3 patch is the best time to add the 90 dungeon for weekly because the sooner you add the 90 one the less effective it becomes over the course of an expansion.
I.E. 50/run becomes 30 eventually, and even less as they add new dungeons.
Adding 89 to the mix will also make it so in 7.0 we can run 89 instead of 85 for the next expansion.
Doing the math it is approximately 50 Qitana Ravels to go from level 80 to level 90. Not bad at all in retrospect, thats with food/rested/FC buff/XP earrings however so it may be a little more. (not counting challenge log though)
One perk as well is you can get gear to trade to GC for the new loot boxes with this process as well.
Your Scion team also gains experience with this process too, so it’s a viable way to get them to 90 as well.
Holminster Switch came out in November, 4-5 months after the expansion. Qitana Ravel came out approximately August. It’s usually a pretty slow development because it also includes the rotations included for the jobs. Don’t take this as quoting, but it’s a pretty accurate model for development though the community also influences the decision making process for prioritizing different things.
Once 81 dungeon comes out though, you can max out your trust and your jobs very quickly. It’s also nice for seal farming and minions.
When 80 is updated though, we can use /micon to visually fake miqobot to do gathering/crafting rotations with the new skills. (We’ve done it before bwah)
I.E. using groundwork, but listing it as another skill.
-
This reply was modified 3 years, 1 month ago by
edgedy.
Thanks to @sirvg for this, I made a modified version which encompasses all of the crystals at each node and switches element. It may not be 100% optimized but it should be better it also adds a cordial consumption to rotation.
EDIT: Added Repeat. (oops)
I feel the next time that a decision is made by the community on the development cycle we should probably attach estimate project times to each of the selections. Picking the widespread ‘QoL’ seems to have been a poor decision and while it may work in the long run I feel there may have been better options the community could have chosen instead. Not being sassy because the thing I wanted wasn’t chosen but I’d rather smaller tangible projects over large overwhelming overhauls when it’s unclear what Endwalker will bring.
I also recognize that redundancy is also a consideration, will this new feature become obsolete over time is definitely a concern.
-
This reply was modified 3 years, 1 month ago by
-
This reply was modified 3 years, 1 month ago by
