Final Fantasy XIV Database - Ffxivpro.com

Did you mean dump bags?


Ideally, ALL of your gear is frozen to your dump bags unless it's in your inventory(because you're currently on that job), it lives in your wardrobes or it's on slips, mule, ect.



The freeze is basically a list of the items in each of your inventories, based on your current job. When you call the organize function it will calculate and evaluate the following:

goal_items = current_items

goal_items - The number of items listed in your freeze/lua for a bag
current_items - The number of those items that are currently in that bag

If the statement is true, you are considered to be organized because all of the items are where they were when you froze them. While the statement is false, you pass through a loop that attempts to correct it.

get > update > tidy

Get pulls as many of the missing items as it can into the bag, update increments current_items to reflect the change and finally tidy cleans up or makes room for more items if necessary. The function then goes back to re-evaluate the updated statement and loops until it has satisfied the equation.

Well, I just saw that they nerfed an important exploit I was using up till now.

I guess there is no excuse anymore, this update now formelly annulled like 70% my playthrough.

It will be hard to see how much I can save, but at this point, maybe best to just restart over.

Is it safe to assume it has a built-in Acc- negative bonus then?

its 1am pendejo

and I'm going now

It ia 3 am,

Go sleep nerd

*** Palworld

Verso's Drafts is where its at

Dang…

Palworld new update brought a couple of changes that can potentially change some of my early steps in my playthrough.

Yeah, right when I was about satisfied with my progress, they dropped changes that trivializes some of the most cumbersome stages in my playthrough.

If I had to retcom it, probably I would have to go from day 27 to like day 5 or 6…

Ugh…

My results have been in line with Linsivi's - mostly trash. Got a Headshard: SAM and a Hadean body abj for a lockstyle, I guess. I suspect I won't make back the 10k I spent for alts to get the hat.

I appreciate that, but it doesnt seem to be working that way.

I do //org freeze on BLU, it creates a bunch of Char_BLU files for all the bags/storage. I checked the contents of the files, and they look accurate from a couple spot checks.

I change to a job I rarely use (but do use rarely), do //gs org to pull the gear from safe/2/locker. Gear moves to main inventory.

I change back to BLU, do //org o, and the SMN gear gets dumped to sack/satch/case.

Again, my organizer settings are set to only use sack/satch/case as dump bags (I want to make sure I dump gear to field accessible bags incase I run off without pulling gear), so if this matters, then so be it. But I was under the impression, based on the readme, that //org organize will attempt to put items back based on the saved freeze?

Just an update to the pentapeck amnesia thing: I had some time today and went into Brenner with a GEO alt to test this. Both BST and GEO are barely equipped, just having ambuscade sets.

Without +pet mAcc gear, amnesia was landing everytime but getting partially resisted, for a duration of 7 seconds. When I switched to +pet mAcc gear it was landing full duration of 13-ish seconds. I was able to get that pretty consistently. At full TP it seemed to land for 24-ish seconds.

So, it's actually a reasonably good duration IF it lands. Which is easy on a newbie GEO in a Jhakri set, but apparently pretty tough on anything else.

We did Run, Pup x2, Smn, Whm, geo and got two kills. Was slow though and the Run was excellent but got it down.

Correct.


For tidy, you want to use [bag] and [filename] to specify which bag you want to remove items from and which items you want to remain in that bag.



//org o should default to your current job (assuming you were on that job, you correctly setup your inventories and used the //org freeze command), unless you specify otherwise with [filename].


I haven't used it since the update so I guess it's possible that something broke, but it was working as expected last I used it. Double check freeze files for accuracy is the obvious, but maybe try to create/load some freezes with [filename]?

The assumption is 10 over time is fine, but that's going to be an unknown for a while unless we can get more than one key a day.

For alts you should be able to start the Giftgiving event (with the Smilebringers) to get a key.

Steps:
Buy a Dream Hat from the in town Moogle vendor for 10,000 gil
Equip Dream Hat
Speak to Smilebringer. gives 'Present for the kiddies' (kiddie present)
Trade the kiddie present to a child NPC in the zone
-in game message "You've brought barrelfuls of joy to the children of Vana'diel!"
Teleport to another city via Smilebringer
#FES key is placed in inventory prior to zoning.

Loot:
Gabbrath Horn
Flame of crimson rancor
Little Worm belt
Cluster of Startling Memories
Legshard: WHM
Snowy Rolanberry
Lenitive Abjuration: Head
Shaman Garlic

Seems very SP Gobbie Key-ish.

Do we think we need to save up 10 to see the bonus?
Or just trade 10 at our leisure?

Just to be 100% sure: It is one FES Key per day total, and not one FES Key per event per day, correct?

Yeah you can tell SE is trying hard.

The only thing I would change at this point is making the CN zones have a random spawn time after the objectives are done. I'd like to try the fights but rarely around near JP midnight and since NMs will be the last thing to unlock each term the bigger fights will also always be popped right after JP midnight.

"ugh i hate 6man content and daily lockouts this ***sux!!111"

and now it's

"SERVER WIDE content with no lockout ... what the ***?!?!?!"

-

we just got a massive update with a ton of new equipment and synthesis recipes and people are STILL mad. it's kinda funny tbh

If you have the items from the curator moogle recipe you might be able to trade still, I think.

Check curio moogle, they may have added the halloween event pieces there.

This week was a good one.

Union promoted a 2 days strike. Despite I still having to work remotely, at least it was 2 workdays at office less (just oneed to go once).

Next two weeks there is no day at office so Im in a good mood.

My playthrough project seemes to be a little more solid, I think Im converging to my best strategy and decent execution.

Maybe the end is near.

Gonna say this for like the 10th time, but maybe I can finish this off this week

Added 14 titles, 37 ML and 121 roe(788 total). I was going down the list of UNM on ROE and finally hit rank 5 again.

Maybe? But it would still be way better than the "absolute nothing" people are getting right now, which I still have a hard time to believe they thought it would've been fine.


@Brimxtonefox
Yeah that's a nice idea.
Not sure it would work but sounds solid to me.
They need to do something about the way these NMs work though.
I'm super fine with them not being stuff you afk on or that dies too fast like DI, I'm super fine with them lasting hours etc (actually that could be good so more people can participate, given they are rare and limited per month) but making them ignore DT, defense adn everything else is way too much, imho.
If anything raise their health, give them immunity phases, more DT, whatever, but their offensive capabilities should definitely be toned down A BIT, or to say the least solve the issues Martel outlined months ago already.

I did, back then, and found exactely what was happening.
Now I don't remember anymore lol.
I *think* the pet_aftercast set was sometimes being equipped too early, and as a consequence the pet BP was shot with that set.
But I could be wrong hey, don't remember anymore.
It's still here on the FFXIAH history, probably in one of those two threads I mentioned.

Oh and btw it wasn't an issue specifically with my lua because I built it from zero and multiple people with different luas were having the same issue.

That sounds like a setup issue based on that descriptor Ie: youre doing volt strike but its using your flaming crush set

Turn on debugmode and see what its doing

For who's wondering on what is the "issue" I mentioned, described in the other two threads.
Sometimes BPs were being fired off in the WRONG set. Not the Pet BP one but another.
Could easily notice that with the damage being very off from your average, too big of a difference for being a miss, a resist and whatnot.

So yeah, it wasn't happening every single time but a minority.
Yet, while a minority, it was way too common for people not to notice or not to bother.
I mean I do get "casting in wrong set" on other jobs as well occasionally, especially when there is a lot of lag, packets are getting lost. I mean nothing you can do about it, right? But those are extremely rare situations.
The one with SMN was still rare, but way more common and, appearently, not simply derived from extreme lag.

Thats coming from king complainer lmao

Absolutely, but in my case (and several other people in my LS back then) the source of the issue was NOT player's aftercast.

Can read it the three pages thread here, dated like what, 2015?
I didn't fix it, but the way my GS logic was behaving, player aftercast was being ignored regardless if the action was a BP, so that wasn't the cause of my BPs being fired off with the wrong set.

I remember in another thread (which I couldn't find) Byrth suggested to change the millisecond timer of a specific value in gearswap, manually. That did nothing to me and the others.

I simply ignored the issue for years because I wasn't playing SMN enough for me to bother (lol, I know, shame on me). I know /equipset weren't producing this issue, and a mixed Lua (handling player actions though GS and pet actions through equipsets) was working like a charm, iir Perg was using a similar solution back then.

I then came back to the issue in like ~2018 where I simply disabled pet aftercast, with my "new" logic of the cycle stopping at pet midcast (I would return to idle manually with a hotkey/macro).
Can read some details/discussions/tests in the 2 pages here.

Since then I never had any issue but recently, like last year? I went to SMN again to update a few things with Nirvana and whatnot and simply "automated" my return-to-idle hotkey/macro with a coroutine.
Again, haven't experienced the issue ever again. Now I get stuck in pet midcast like for a few seconds more than I should, but no manual action is required and I return to the intended set that the pet aftercast would get me to.
Of course there are exceptions for Astral Conduit, different logic when that buff is up.


All of this to say what? Well, that things SHOULD work in theory like you said Lili, but in reality they were not, for whatever reason (some hypothesys made by Thorny and Comeatmebro in the second thread made a lot of sense to me though).
Now I don't know if this "issue" was solved by Gearswap already from 2018 until today, maybe? I haven't tested so I wouldn't know.

Oh boy, more minor item text errors that they won't try to fix until the day after Return to Vanadiel ends, so that they can have an excuse to kick us free-play bums off after it ends. Right?