|
 |
By NynJa on 2025-12-16 13:38:25
|
|
Thats coming from king complainer lmao
|
|
 |
|
Both of these things have a midcast and an aftercast! 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?
|
|
 |
|
It's baaaaaack!
Quote: Campaign Period
Friday, December 19, 2025, at 12:00 a.m. (PST)
to Monday, January 5, 2026, at the same hour.
As usual, expect them to start enabling accounts early on Thursday. Probably around the previous JP midnight from past experience.
|
|
 |
By Genoxd on 2025-12-16 13:13:05
|
|
Literally do anything at all. They need any reward at all for individual contribution. I don't care if it's a 0.1% chance at an upgrade item or 10k points for limbus or anything at all.
|
|
 |
|
|
CN is just CeNtral, feel like y'all are putting too much thought into it
|
|
 |
By Radec on 2025-12-16 12:52:06
|
What are the, "CN" areas called in Japanese?
English Dialog from Temenos Operator: Code ≺Selection Dialog≻Level settings.
Temenos.
Temenos Units.
The Temenos Furnace.
Equipment list.
Grace.
Notorious monsters.
Tresure coffer timings.
≺Unknown Parameter (Type: 80) 1≻≺Possible Special Code: 01≻≺Possible Special Code: 05≻%≺BAD CHAR: 8280≻≺BAD CHAR: 80≻≺BAD CHAR: 80≻.
CN Opening.
≺Unknown Parameter (Type: 80) 1≻≺Possible Special Code: 01≻≺Possible Special Code: 05≻%a≺BAD CHAR: 80≻≺BAD CHAR: 80≻.
Reforging.
Nothing for now.≺Prompt≻
JP Dialog: Code ≺Selection Dialog≻レベル設定
テメナスについて
テメナス粒子について
テメナス錬炉について
装備品リストを見る
グレースについて
ノートリアスモンスター
宝箱の更新時間
≺Possible Special Code: 01≻≺Possible Special Code: 05≻≺Possible Special Code: 13≻≺BAD CHAR: 8280≻≺BAD CHAR: 80≻≺BAD CHAR: 80≻について
中央塔地下1階の開通
≺Possible Special Code: 01≻≺Possible Special Code: 05≻≺Possible Special Code: 13≻a≺BAD CHAR: 80≻≺BAD CHAR: 80≻について
強化の引き継ぎについて
とくになし≺Prompt≻
Google Translate of the 10th line: Code
中央塔地下1階の開通
Chūō-tō chika 1-kai no kaitsū
Opening of the first basement floor of the central tower
Apol is just CN in both, similar menu table: Code
EN: CN Opening
JP: CNの開通
Translated: CN no kaitsū / CN opening
|
|
 |
|
|
If it's putting in Null Loop, it could be that you're low on accuracy in the sub optimal set.
|
|
 |
By Rairin on 2025-12-16 12:32:15
|
|
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
|
|
 |
By NynJa on 2025-12-16 11:25:36
|
|
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
|
|
 |
By Wotasu on 2025-12-16 10:08:51
|
Carbuncle.Maletaru said: »
Ok, so what does your macro for flaming crush look like then?
/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.
|
|
 |
|
What does "CN" stand for in Limbus, as in "CN Opening"? The only thing I can come up with is Crawlers' Nest but that doesn't seem right. 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?
|
|
 |
By Weeew on 2025-12-16 08:58:41
|
"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.
Materials can be sold. Demand will be high. Prices will be high. People will still farm. Need I say more.
|
|
 |
By Lili on 2025-12-16 07:29:38
|
Me and some other users (not all, alas) have been experiencing issues with GS and SMN for the longest time.
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.
|
|
 |
|
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.
Limbus continues to be extremely convoluted and I don't get it.
|
|
 |
|
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.
Ok, so what does your macro for flaming crush look like then?
|
|
 |
|
Carbuncle.Maletaru said: »I imagine a gearswap macro for a BP is just one line: 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.
|
|
 |
|
Wait all this is moot, since Delve still has the 3 player minimum, does it not??? Yep. Delve, Incursion, Dyna-D (regular, not new instance) still all have 3-player minimum.
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!
|
|
 |
By Lili on 2025-12-16 02:39:59
|
It really wouldn't be hard to keep server-side track of who participated and just mail drops to their inbox when the mob dies.
All the people whose inboxes are completely full because they use them as a sort of additional storage box with 255 slots: seethe.
|