Final Fantasy XIV Database - Ffxivpro.com

CN is just CeNtral, feel like y'all are putting too much thought into it

English Dialog from Temenos Operator:

JP Dialog:

Google Translate of the 10th line:

Apol is just CN in both, similar menu table:

If it's putting in Null Loop, it could be that you're low on accuracy in the sub optimal set.

I'm going with something relating to Central, given the way every other limbus subsection is labeled.

Glad ffxi had a good run. Ill stay till the servers close. Shouldn't be long now with these stale updates

BTW im still using the September 06a version. maybe i should have checked for a newer version.

so i think i found it this time. a Suboptimal generated set
Between testing sets i removed the null loop from the available choice. and then it spit out a better set. meaning the prior was suboptimal choice

Below ive added the cmd line output and the gear setting i had for the first generation



info Dump:
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current best set: PDT:0, MDT:-29
Current iteration: 1
Current iteration: 2
Current best set: PDT:-15, MDT:-34
Current iteration: 1
Current iteration: 2
Current best set: PDT:-20, MDT:-39
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current best set: PDT:-21, MDT:-40
Current iteration: 1
Current iteration: 2
Current best set: PDT:-26, MDT:-45
Current iteration: 1
Current iteration: 2
Current best set: PDT:-31, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-35, MDT:-50
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current best set: PDT:-38, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-43, MDT:-50
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current iteration: 4
Current best set: PDT:-44, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-49, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-50, MDT:-50
==============================================================
Best "Time to WS" "Melee TP set" set
==============================================================
main Twashtar R15
sub Centovente2
ranged Empty
ammo Coiste Bodhar R30
head Skulker's Bonnet +3
neck Null Loop
ear1 Sherida Earring
ear2 Skulker's Earring +1
body Pillager's Vest +4
hands Malignance Gloves
ring1 Moonlight Ring A
ring2 Murky Ring R30
back Toutatis's Cape DEX Store TP
waist Reiki Yotai
legs Malignance Tights
feet Skulker's Poulaines +3

Avg WS Time = 6.416 s
Avg TP per round = 357.4 TP
==============================================================
==============================================================

List of potential swaps within 1% of the best set (6.416 ):
ring2 Defending Ring 6.416 0.0%
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current iteration: 4
Current iteration: 5
Current iteration: 6
Current best set: PDT:0, MDT:-29
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current best set: PDT:-15, MDT:-34
Current iteration: 1
Current iteration: 2
Current best set: PDT:-20, MDT:-39
Current iteration: 1
Current iteration: 2
Current best set: PDT:-25, MDT:-44
Current iteration: 1
Current iteration: 2
Current best set: PDT:-30, MDT:-49
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current iteration: 4
Current best set: PDT:-31, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-35, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-38, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-40, MDT:-50
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current iteration: 4
Current iteration: 5
Current iteration: 6
Current best set: PDT:-45, MDT:-50
Current iteration: 1
Current iteration: 2
Current iteration: 3
Current best set: PDT:-48, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-49, MDT:-50
Current iteration: 1
Current iteration: 2
Current best set: PDT:-50, MDT:-50
==============================================================
Best "Time to WS" "Melee TP set" set
==============================================================
main Twashtar R15
sub Centovente2
ranged Empty
ammo Coiste Bodhar R30
head Skulker's Bonnet +3
neck Assassin's Gorget +2 R25
ear1 Sherida Earring
ear2 Skulker's Earring +1
body Malignance Tabard
hands Malignance Gloves
ring1 Moonlight Ring A
ring2 Murky Ring R30
back Toutatis's Cape DEX Store TP
waist Reiki Yotai
legs Pillager's Culottes +4
feet Skulker's Poulaines +3

Avg WS Time = 6.279 s
Avg TP per round = 365.1 TP
==============================================================
==============================================================



--- equipment selection

Main:
Twastshatar R15

Sub:
Centovente2

Ranged:
<None>

Ammo:
Coisted Bodhar R30

head:
Adhemar Bonnet +1 A
Gleti's Mask R15
Malignace Chapeau
Null Masque
Pill. bonnet +4
Plund. Bonnet +4
Skulk. Bonnet +3

Neck:
Assassins gorget +2 R25
Combatans torque
Null Loop

Ear 1:
brutal
Cassancre
crematio
crepuscular
Eabani
Odr
Sherida
Suppa
Telos

Ear2:
brutal
cessance
crematios
crepuscular
Sherida
Skulkers +1
Suppa

Body:
Adhemar +1 A
Malignance
Pill. +4
Plund. +4
Skulk. +3

Hands:
Adhemar +1 A
Gleti's R15
Malignance
Pill. +4
Plund. +4
Skulk +3

Ring1:
Chirich +1 A
Defending
Moonlight A
Petrov



Ring2:
Chirich +1 B
defending
Gere
Hetairoi
Moonlight B
Murky R30

Back:
null Shawl
Toutatis Dex DA
Toutatis Dex DW
Toutatis Dex STP

Waist:
Cornelia
NUll Belt
Reiki Yotai
Windbuffet +1

Legs:
Adhemar +1 A
Gleti's R15
Malignace
Pill. +4
Plund. +4
Skulk. +3

Feet:
Adhemar +1 A
Gleti's R15
PIll. +4
Plund. +4
Skulk+3

What are the, "CN" areas called in Japanese? Might be more revealing, giving how little care they've been giving the English scripts for Limbus thus far.

Combat Node makes sense to me.

Only other thing I could come up with is:

Creation Nexus

Since it's featuring new lifeforms for testing as the shallow lore of Limbus.

Warviper: Scroll of Protectra IV
Blackmageviper: Slice of lynx meat

Can someone explain what I'm doing wrong with the organizer freeze and tidy/organize commands?

doing //org freeze should take snapshots of all my inventory in its current place, saved to a file named Char_JOB

doing //org tidy should attempt to dump anything from my inventory into the location based on Char_JOB. Do I have to be on said job for the tidy to work properly?

Doing //org organize should do repeated attempts to move my inventory around until all the items are in the place denoted by the Char_JOB? Again, do I have to be on said job for this to work properly?


Unless its a matter of how I have my organizer settings (dump bags are sack/satch/case), its just attempting to dump everything in my dump bags when I do org tidy or org organize even though the items in question should be going to safe/2/locker

/equipset 41 (precast smn BP delay gear)
/pet "Flaming Crush" <stnpc> <wait 1>
/equipset 51 <wait 4> (Hybrid set)
/equipset 47 (idle/refresh)

I have gearswap issues in Omen type zones I so I tend to just disable gearswap when I have issues and use equipsets.

There were areas in original Apollyon called "CS", which I always interpreted as "Central South". When the new one's "CN" I think that might still be the case?

Not that I know what the hell "central north" means, in relation to floating Promvyion islands. Or why there'd be an identical "CN" descriptor in Temenos when the original areas were Central Temenos - Basement/4th Floor I/II.

But since the other areas were named after cardinal directions, and Central Temenos was explicitly named Central Temenos, I just assumed it was Central South.

Did anyone dust off their -Breath Taken gear specifically to test whether that worked in CN?

I assume not. And I don't have any or I'd do it myself next month. But I'm wondering - like how Banish works on the Limbus DT on the Undead and I assume it's not supposed to, maybe this does too?

Materials can be sold. Demand will be high. Prices will be high. People will still farm. Need I say more.

This is an issue with how userfiles are written, not with how macros are done. The crux of the matter here is that there's TWO separate actions taking place: your JA usage of the Blood Pact, and after 75 delay the Avatar doing its thing. Both of these things have a midcast and an aftercast!

So:
Player presses macro -> precast is equipped -> JA executes -> AFTERCAST IS EQUIPPED -> avatar initiates action -> pet_midcast is triggered -> avatar ends action -> pet_aftercast is triggered

That's the entire issue.

The most reliable way to fix this is to do what you did: make sure that your gearswap userfile does not equip any gear in the regular aftercast if the action was a blood pact, AND THEN do the "regular" aftercast stuff in the pet_aftercast() event instead.

This has the unfortunate side effect of leaving you in blood pact gear if your avatar is unable to conclude the action (stunned paralized dead...), so a button to put your Idle gear back on manually is a good idea.

No logic based on timing or delay is needed, really.

Limbus continues to be extremely convoluted and I don't get it.

Ok, so what does your macro for flaming crush look like then?

Wrong.
Me and some other users (not all, alas) have been experiencing issues with GS and SMN for the longest time.
I don't remember the exact source of the problem (it's here in the thread somewhere) but the result is that BP action were being executed in the wrong set.
If I recall it was a matter of idle gear being processed a bit too early and as a consequence BP firing out with Idle gear instead of pet midcast.
This only happened "sometimes", but still was extremely undesireable.

I don't know how other people solved this issue, which I know is not present if you use in-game equipsets functions.

Personally I initially solved it by removing the "return to idle" part in aftercast and related, so that if a pet action was performed, the Aftercast was completely ignored.
(then I bound a "return to idle" command to a hotkey/macro).
After a long time with this solution and never experiencing any issue, I slghtly modified with a custom return to idle that happens automatically, but delayed by a couple of seconds compared to what would happen in the "regular" aftercast.

Haven't played SMN much since then but, to date, didn't experience the "BP firing in idle gear" issue again.

"Assuming".
Yes, and likewise with the regular NMs.
And how long do you think that's gonna last?
For a little while it won't be a problem given the "new" feeling, the interest in gear, mats, stuff, I'm sure it's gonna be downhill for several months.

But after that? For a fight that requires so much effort and so much annoyace? Once it's no longer "new" and you already had your chance at enjoying it the first few times?
With no direct reward at all?

I'm not sure it's gonna last, and I said the same for the 22 NMs in each zone.
But, BUT! That's not gonna be an issue any time soon, at least on Asura, and I guess SE can always change their mind and add "something" to these parts of the content to incentivize it, why not?
Don't "need" incentives now, as sad as it sounds.

I went to test it out and didn't realize that equipset locked you out of generating another equipset command for two packets.

While it's kinda shitty to wait a month, keep in mind that it's the only month you need to wait, assuming we keep kill killing Omega and Ultima in the future.

Vagary too.

What I mean is, if you injected chunks directly and did equipset -> action (BP) -> equipset and they were all sent in the same packet, you'd be wearing your BP damage gear when the BP went off. The `wait 1` forces the second equip command to be sent in the next packet, but if SE just sent the chunks in the order they were generated then it wouldn't need to be delayed.

If they wanted to give a "reward" to everyone who participated and not just who got the killshot, they could use an NPC in a similar way to how they handle the vana'bout thing.
Could be the same limbus NPC used for many other purpose.

This would solve issue #2 that I mentioned in my previous post, i.e. "handling people who participate in the fight but do not get the killshot".

It does ***for issue #1 though.
These are issues for both the roaming NMs and the new Ultima/Omega special floors too.
If you give a reward that's too good, people are rightfully going to complain that they had no chance to get it. And this is even more true for a content that's once a month, compared to the roaming NMs where you have 22 chances to participate each month I guess, lol.
I think we can all agree they need to avoid making the potential reward something too good so you don't feel you "missed out" if you didn't participate.
At the same time though, the reward being absolutely nothing is imho not the right solution.
They need to find a compromise somewhere!

All the people whose inboxes are completely full because they use them as a sort of additional storage box with 255 slots: seethe.

The server collaboration thing is great.
The fact that these are not just YAWN like Domain Invasion is good too.

I like the fact these don't go down in 30 seconds.
Pumping on the DT, damage nullification phases and overinflated mob HP is great. If anything, they should emphasize these aspects even more.

They might have gone a bit too hard on the "damage done to players" part though. If anything I would tone it down a bit, but this goes for normal NMs as well (see Martel's report) and they've done absolutely nothing about those so... doubt anything is gonna happen.


Another good/bad part is the fact you can do it only once per month.
With Domain Invasion you have predictability, you know it's happening every what, 15 mins? 20?
Which is good if you want to spam the content or simply participate.
But the "epicness" of the fight suffers because it's so frequent you barely even care in the end.

Here you don't have something to farm so you don't need to have frequent fights. At the same time though not being able to participate for a whole month can be a bit... frustrating.
Can there be a better compromise between these two extremes, somewhere? I wonder about that but I have no answer in mind honestly.

And to be fair, especially now that these fights are so stressing for your EP reserve, once you've participated a couple of times you probably don't want to take part in it anymore.
So yeah, I really don't know what would the best solution be to allow interest, participation and sustainability of these fights on the long run.

It's a mixture of very annoying NMs (ignore DT, Sentinel, blocks, blah blah) that offer no incentive at all other than "better rewards next month".

They should do something for who contributes in killing.
It's not an easy thing to solve though, there are some problems to take into consideration:

1) What do you give as reward? If it's useless, it makes no difference. If it's too good, it makes people who cannot take part in it rightfully annoyed. (and not taking part is a good chance for something that happens once per month, like Ultima/Omega)

2) How do you handle people who participated in the fight, but weren't there on the kill?


I'm sure SE asked themselves these questions, couldn't find a valid solution and in the end they just opted for "*** it, make it drop absolutely nothing".

Yep. Delve, Incursion, Dyna-D (regular, not new instance) still all have 3-player minimum.

Damn Richy ;-; *hug*